Description
Use Case document of LOS
Indian Institute of Information Technology & Management
Use Cases
For
Version 1.0 approved
Prepared by
Arti Omar (IPG_2008108)
ABV-IIITM
31-10-2011
Indian Institute of Information Technology & Management
Use Case List
Primary Actor
Data Entry Operator Bank Administrator Lenders (Normal/Supervisory) CIBIL Underwriter Customer
Use Cases
Enter Application Information Loan Configuration, Loan Assignment, Fetch Report Loan Verification Credit Score checking Underwriting, Issued Draft Track loan
Loan Originating system.simp
Use case for project Page 1 of 44
Indian Institute of Information Technology & Management
1.0 Enter application Information Use Case Template
Use Case ID: Use Case Name: Created By: Date Created: 1 Enter application Information Arti Omar Last Updated By: N/A 31-10-2011 Date Last Updated: N/A Data entry operator/customer Submission of loan application To Scan document and enter in LOS Form Availability, User Authorization, enough memory Information entered, LAN assigned 1.0 submission of form, scanning, entering loan information N/A N/A N/A Form availability, Clear downloading, Send confirmation mail 3 times in a day on daily basis unit of time N/A Consistency, Access locally, Open source N/A TBD
Actors: Trigger: Description: Preconditions: Post-conditions: Normal Flow: Alternative Flows: Exceptions: Includes: Priority: Frequency of Use: Business Rules: Special Requirements: Assumptions: Notes and Issues:
Use case for project Page 2 of 44
Indian Institute of Information Technology & Management
1.
Use Case Identification 1.1. Use Case ID ? 1.0 1.2. Use Case Name. ? Enter Application Information 1.3. Use Case History
1.3.1 Created By ? Arti Omar 1.3.2 Date Created ? 31-10-2011 1.3.3 Last Updated By N/A 1.3.4 Date Last Updated N/A 2. Use Case Definition 2.1. Actors 3.1.1 Data Entry Operator 3.1.2 Customer As mentioned, this case study is divided in two parts at the beginning of the case. If customer fills the loan application form in offline mode then Data Entry Operator will be the first actor who will trigger the event but if customer fills the loan application form in online mode then customer itself will be the first actor who will trigger the event.
Use case for project Page 3 of 44
Indian Institute of Information Technology & Management
2.2.
Trigger
Loan applications are submitted at submission counter. 2.3. Description ? After submission of loan application forms data entry operator will scan all the forms with the documents are attached with them for any missing information. When scanning is done then he will feed all the information has been provided into LOS (loan originating system) in Enter application information use case. 2.4. Preconditions
1. User’s identity has been authenticated. 2. User’s computer has sufficient free memory available to launch task. 3. Form should be available online/offline. 2.5. Post-conditions
1. Loan information has been entered into system 2. Scanned documents are in document management system 3. LAN is assigned to customer 4. Unique document number is assigned to document. 5. After the execution of Enter application information use case, system state will be in partial application state. 6. Send acknowledgment to customer.
2.6. ?
Normal Flow
How does Data Entry Operator accomplish the task stated in Enter Application Information?
Use case for project Page 4 of 44
Indian Institute of Information Technology & Management
1. Submission of application form on the application submission counter. 2. Data entry operator will be responsible for scanning all the applications for any missed information and accordingly 3. Acceptance or rejection of the form. 4. Enter loan information from accepted form. Like type of loan, loan product, personal, address, employment, asset & liability and loan information into the LOS 5. Scanning attached documents and accordingly accepts and rejects them. 6. Assigned document number to accepted form. 7. Generate Loan Application Number (LAN) 8. Save image in document management system with the key as . 2.7. Alternative Flows
1. If form missed in offline mode make a customer entry in entry register before giving form so that customer can be informed for resubmission. 2.8. N/A 2.9. N/A 2.10. Priority 1. Form should be available to customer either online and offline mode. 2. System should have enough memory space. 3. System should send conformation mail to customer with LAN. 4. System should classify different loan products under each loan category.
Use case for project Page 5 of 44
Exceptions
Includes
Indian Institute of Information Technology & Management
5. System should show interest rate fixed tenure and type of interest rate information with loan product. 6. Tight scanning of provided information. 7. Reject false positives. 2.11. Frequency of Use In daily basis this use case can be used by customers at most 3 times. 2.12. Business Rules N/A 2.13. Special Requirements Nonfunctional requirement (NFR) can be stated as soft goal. Under NFR we define 1. Consistency 2. Access Locally 3. Open source system 4. Response time 5. Replicate in all nodes 2.14. Assumptions 1. Server has enough memory 2. Data base has enough capacity
Use case for project Page 6 of 44
Indian Institute of Information Technology & Management
2.15. Notes and Issues Name TBD TBD Due Date Result TBD TBD TBD TBD Issue TBD TBD
Revision History
Name N/A N/A
Date N/A N/A
Reason For Changes N/A N/A
Version N/A N/A
Use case for project Page 7 of 44
Indian Institute of Information Technology & Management
2.0 Loan Configuration Use Case Template
Use Case ID: Use Case Name: Created By: Date Created: 2.0 Loan Configuration Arti Omar 31-10-2011 Last Updated By: N/A Date Last N/A Updated:
Actors: Trigger: Description: Preconditions: Post-conditions: Normal Flow: Alternative Flows: Exceptions: Includes: Priority: Frequency of Use: Business Rules: Special Requirements: Assumptions: Notes and Issues:
Bank Administrator Calling for loan configuration Configured loan application for loan assignment purpose Information should be entered by data operating system/customer Loan application are configured, loan status update 2.0 fetching loan information from LOS, classifying application form N/A N/A N/A System should proper classify loan product, update data base Once in a day on daily basis unit of time N/A Consistency, Maintainability, reliability N/A TBD
1.
Use Case Identification 1.1. Use Case ID ? 2.0 1.2. Use Case Name ? Loan Configuration
Use case for project Page 8 of 44
Indian Institute of Information Technology & Management
1.3.
Use Case History
1.3.1 Created By ? Arti Omar 1.3.2 Date Created ? 31-10-2011 1.3.3 Last Updated By N/A 1.3.4 Date Last Updated N/A 2. Use Case Definition 2.1. Actors
1. Bank Admin 2.2. Trigger
Bank admin calls system for loan configuration 2.3. Description
Configured loan applications are in the system for loan assignment purpose. 2.4. Preconditions
1. All information form application should be entered by Data entry operator/Customer. 2. Admin should have enough memory to launch the task. 2.5. Post-conditions
1. After the execution of loan configuration use case system state will be in Pending state from consumer point of view whereas from bank’s perspective it is Evaluation state.
Use case for project Page 9 of 44
Indian Institute of Information Technology & Management
2. Identifying loan product and creating a loan list 3. All the applications will be divided in two parts, ? Loans beyond 5 lacs. ? Loans lesser than 5 lacs 2.6. ? Normal Flow
How does Bank Administrator accomplish the task stated in Loan Configuration use case? 1. All required information has been entered by data entry operator into LOS 2. Bank admin will run query in the system to get information about the loan request in a specific date under specific loan category, 3. System response for information about all the loan products under specific category. 4. Loans are classified in two parts [1] Loan applications beyond 5 lacs. [2] Loan applications within 5 lacs range
2.7. N/A 2.8. N/A 2.9. N/A
Alternative Flows
Exceptions
Includes
2.10. Priority 1. Entered information should be loaded properly.
Use case for project Page 10 of 44
Indian Institute of Information Technology & Management
2. All types of loan products should be properly classified. 3. Replicate update in all parts. 2.11. Frequency of Use On the daily basis it is used once in a day. 2.12. Business Rules N/A 2.13. Special Requirements 1. Consistency [object] 2. Loose_coupling [objects] 3. Maintainability [system] 4. Reliability 5. Duplication reduce 2.14. Assumptions N/A 2.1. Name TBD TBD Revision History Name N/A N/A Date N/A N/A Reason For Changes N/A N/A Version N/A N/A Notes and Issues Due Date Result TBD TBD TBD TBD Issue TBD TBD
Use case for project Page 11 of 44
Indian Institute of Information Technology & Management
3.0 Loan Assignment Use Case Template
Use Case ID: Use Case Name: Created By: Date Created: 3.0 Loan Assignment Arti Omar 31-10-2011 Last Updated By: N/A Date Last N/A Updated:
Actors: Bank Administrator Trigger: Calling configured loan for assignment Description: To Assign loan application to normal and supervisory lender according to business rules. Preconditions: Valid lenders Ids, No lender should open cases as mentioned in the rule. Post-conditions: Update lender status, prepared report, loan are assigned Normal Flow: 3.0 configured loan application is called, check lender status, assign loan application Alternative Flows: N/A Exceptions: N/A Includes: N/A Priority: System should upload configured loan list, classify loan application according to loan amount, follow round robin process Frequency of Use: Once in week Business Rules: 1. Loan beyond 5 lacs assigned to supervisory lender, 2. loan assignment should follow round robin process 3. Normal lender can have only 5 open cases at any point of time and supervisory lender can have 7 open cases at any point of time. Special Requirements: Consistency, maintainability, reliability Assumptions: Supervisory lenders also have their IDs. Notes and Issues: TBD .
Use case for project Page 12 of 44
Indian Institute of Information Technology & Management
1.
Use Case Identification 1.1. ? 3.0 1.2. Use Case Name Use Case ID
? Loan Assignment 1.3. Use Case History
1.3.1 Created By ? Arti Omar 1.3.2 Date Created 31-10-2011 1.3.3 Last Updated By N/A 1.3.4 Date Last Updated N/A 2. Use Case Definition 2.1. Actors
? Bank Administrator 2.2. Trigger
Calling configured loan for assignment 2.3. Description
Assign loan to Normal and Supervisory lenders as per the Business Rules for loan verification.
Use case for project Page 13 of 44
Indian Institute of Information Technology & Management
2.4.
Preconditions
1. Lenders should have unique IDs 2. Normal lenders should not have more than 5 open cases at any point of time and Supervisory lenders should not have more than 7 open cases at any point of time. 3. Each loan application should contain valid loan ID 4. Loan applications are properly configured with all information and documents. 2.5. Post-conditions
1. After the execution of loan assignment use case loan status will be in Pending state from consumer point of view whereas from bank’s perspective it is Evaluation state. 2. Loan applications are assigned to lenders for verification. 3. Lenders status are update as per the number of open cases are assigned. 4. Report is prepared for numbers of loans are assigned to different lenders. 2.6. ? Normal Flow
How does Bank Administrator accomplish the task stated in Loan Assignment use case? 1. Configured loan applications data base is called. 2. Check loan amount and lender status in parallel. 3. Loan applications beyond 5 lacs are assigned to supervisory have less than 7 open cases at that point of time. 4. Loan applications below 5 lacs are assigned to Normal lenders have less than 5 open cases at that point of time. 5. Loans are assigned to lenders on round robin basis sequential lender IDs.
2.7. N/A
Alternative Flows
Use case for project Page 14 of 44
Indian Institute of Information Technology & Management
2.8. N/A 2.9. N/A
Exceptions
Includes
2.10. Priority 1. Upload configured loan application list 2. Loans beyond 5 lacs make their status 1. 3. Loans below 5 lacs make their status 0. 4. Update lenders status. 5. System should follow round robin process. 6. Assigned IDs to lenders 2.11. Frequency of Use Once in week 2.12. Business Rules There are three business rules for assignment of loan application to lenders. 1. All loan applications beyond 5 lacs can only be assigned to Supervisory lenders. 2. Loan cases will be assigned on round robin basis of sequential Normal Lender IDs. 3. A Normal lender cannot have more than 5 open cases assigned to him at any point of time and a Supervisory lender cannot have more than 7 open cases at any point of time. 2.13. Special Requirements 1. Consistency 2. Performance
Use case for project Page 15 of 44
Indian Institute of Information Technology & Management
3. Maintainability 4. Reliability 5. Security 2.14. Assumptions 1. Assuming Supervisory lenders also have IDs. And loan cases will be assigned on round robin basis of sequential Supervisory lender IDs. 2. Assuming all lenders do not violated the condition at the time of assignment. Like if loan is assigned to Normal lender he does not have more than 5 open cases at any point of time. This condition is applicable with Supervisory lender too. 3. Assuming Bank has enough lenders for loan assignment if not then alternative flow will be applicable. 2.15. Notes and Issues Name TBD TBD Due Date Result TBD TBD TBD TBD Issue TBD TBD
Revision History Name N/A N/A Date N/A N/A Reason For Changes N/A N/A Version N/A N/A
Use case for project Page 16 of 44
Indian Institute of Information Technology & Management
4.0 Loan Verification Use Case Template
Use Case ID: Use Case Name: Created By: Date Created: 4.0 Loan Verification Arti Omar 31-10-2011 Last Updated By: N/A Date Last N/A Updated:
Actors: Lenders (Normal/Supervisory) Trigger: Lenders are asked to give loan verification to bank admin/underwriter Description: In order to verify loan and to save result for underwriting Preconditions: Loan application documents should be saved with key , LAN should be known to lenders Post-conditions: Loan verified, loan verification status is updated, forward to underwriter Normal Flow: 4.0 fetching loan documents, sending request to CIBIL for credit score checking Alternative Flows: N/A Exceptions: N/A Includes: Credit score checking done by CIBIL by sending online request Priority: System should run key, system should follow rules for verification Frequency of Use: One time use on daily basis for single loan application Business Rules: N/A Special Requirements: Reusability, throughput, stress handling Assumptions: Rules are predefined for verification Notes and Issues: TBD
Use case for project Page 17 of 44
Indian Institute of Information Technology & Management
1.
Use Case Identification 1.1. ? 4.0 1.2. Use Case Name Use Case ID
? Loan verification 1.3. Use Case History
1.3.1 Created By ? Arti Omar 1.3.2 Date Created 31-10-2011 1.3.3 Last Updated By N/A 1.3.4 Date Last Updated N/A 2. Use Case Definition 2.1. Actors
1. Normal Lender 2. Supervisory lender 2.2. Trigger
Lenders are asked to give loan application verification to bank admin/underwriter.
Use case for project Page 18 of 44
Indian Institute of Information Technology & Management
2.3.
Description
In order to validate information have been provided by customer and to get customer credit rating loan application are verified by lenders. 2.4. Preconditions
1. All the loan applications should have documents saved in document management system with key as . 2. Documents are easily accessible to lenders 3. should be known to lenders. 4. Customer should be registered with valid customer ID. 5. CIBIL accessibility. 2.5. Post-conditions
1. Loan application will be verified by performing listed task I. Asset/liability test II. Address verification test III. Information Validation IV. Credit Score checking 2. If all conditions are true make loan verification status 1 other wise 0. 3. Loan status is updated. 4. All verification results are saved in the system. 2.6. ? Normal Flow
How do lenders (Normal and Supervisory lender) accomplish the task stated in Loan Verification use case?
Use case for project Page 19 of 44
Indian Institute of Information Technology & Management
As applications are assigned to lenders according to business rules, lenders will perform their task by taking loan information, personal information and all that from LOS to verify them. This function is done by step by step is given below. [1] Open assigned loan application detail in LOS. [2] Verify person authorization by using documents. [3] Analyze assets/liability status of consumer by using documents [4] Address verification by using documents. [5] Other information validation. [6] Verify credit score by sending online request to CIBIL with in LOS [7] Repeat the process if loan verification status is 0. [8] Forward loan application with all the information recorded and documents attached. After each verification, make corresponding status flag equals to 1or 0. 1 if given information is verified, 0 if it is not. 2.7. N/A 2.8. N/A 2.9. Includes Exceptions Alternative Flows
Credit score checking done by lenders comes in includes for that they need external actor who will provide response for credit score checking. Under Loan verification online request will be send to CIBIL for credit score checking for particular customer and CIBIL will response for that request. This all will be denoted by 4 here 4 is loan Verification ID and which includes (credit score check) for loan verification.
Use case for project Page 20 of 44
Indian Institute of Information Technology & Management
2.10. Priority 1. Documents are accessible and key is known to lenders 2. Rules for assets /liability analysis 3. Rules for address verification 4. Rules for information validation 5. Update the status of asset/liability, address verification and information validation. 6. Support online request to CIBIL. 7. Connect server to CIBIL data base. 8. Save automatically CIBIL response. 9. Send acknowledgment to CIBIL 2.11. Frequency of Use One time use for single loan application on daily basis 2.12. Business Rules No Normal lender is allowed to have more than 5 open cases at any point of time and no Supervisory lender is allowed to have more than 7 open cases at any point of time. 2.13. Special Requirements 1. Reusability 2. Compatibility 3. Throughput 4. Stress handling
Use case for project Page 21 of 44
Indian Institute of Information Technology & Management
2.14. Assumptions N/A 2.1. Name TBD TBD Revision History Name N/A N/A Date N/A N/A Reason For Changes N/A N/A Version N/A N/A Notes and Issues Due Date Result TBD TBD TBD TBD Issue TBD TBD
Use case for project Page 22 of 44
Indian Institute of Information Technology & Management
5.0 Underwriting Use Case Template
Use Case ID: Use Case Name: Created By: Date Created: 5.0 Underwriting Arti Omar 31-10-2011 Last Updated By: N/A Date Last N/A Updated:
Actors: Trigger: Description: Preconditions:
Post-conditions: Normal Flow: Alternative Flows: Exceptions: Includes: Priority: Frequency of Use: Business Rules: Special Requirements: Assumptions: Notes and Issues:
Underwriter Call for risk evaluation In order to evaluate risk before loan disbursement Updated verification status, CIBIL database accessibility, Forward all attached documents and results for underwriting function Risk is evaluated , report prepared, loan status is updated 5.0 assigned weight, take aggregated, compare, update status N/A N/A N/A System should reflect updated status, accept rules for weight assignment One time use on daily basis N/A Reusability, standardized interface, performance, quick response Rules are predefined for weight allocation TBD
1.
Use Case Identification 1.1. ? 5.0 Use Case ID
Use case for project Page 23 of 44
Indian Institute of Information Technology & Management
1.2.
Use Case Name
? Underwriting 1.3. Use Case History
1.3.1 Created By ? Arti Omar 1.3.2 Date Created 31-10-2011 1.3.3 Last Updated By N/A 1.3.4 Date Last Updated N/A 2. Use Case Definition 2.1. Actors
? Underwriter 2.2. Trigger
Call for risk evaluation when loan verification status is 1. 2.3. Description
In order to perform risk evaluation underwriting function is performed by underwriter. When risk evaluation is done by underwriter now he has the authority to approve loan, reject loan or can place on hold for seeking more information. 2.4. Preconditions
1. Verification flag must be 1.
Use case for project Page 24 of 44
Indian Institute of Information Technology & Management
2. CIBIL must response for the request of credit score checking. 3. Bank should have enough underwriters. 4. One should not have 5 open cases at any point of time for any loan amount. 5. Other important documents and results should be forward to underwriter. 2.5. Post-conditions
1. Risk evaluation is done. 2. Loan status will be updated either loan approved, loan rejected or placed on hold for seeking more information. 3. Result is saved and report is prepared. 2.6. ? Normal Flow
How does Underwriter accomplish the task stated in Underwriting use case? 1. Forward verified loan application with all results and documents attached. 2. Weights are assigned to each entity list in loan verification list for verification. 3. Aggregate value is calculated. 4. Comparison of aggregate value and bench mark value. 5. Loan status is updated to loan approved if aggregate value is greater than bench mark value. 6. Loan status is updated to loan rejected if aggregate value is lesser than bench mark value. 7. Loan status is updated to loan placed on hold for seeking more information aggregate is approximate to bench mark value.
2.7. N/A
Alternative Flows
Use case for project Page 25 of 44
Indian Institute of Information Technology & Management
2.8. N/A 2.9. N/A
Exceptions
Includes
2.10. Priority 1. Forward loan application should contain all results and documents. If it is, make document status is 1. 2. Weight assignment rules 3. Aggregate calculation rule and comparison rule. 4. Updating Loan status. 2.11. Frequency of Use On Daily unit of time, one time use of use case for single loan application. 2.12. Business Rules N/A 2.13. Special Requirements 1. Reusability 2. Standardized interface 3. Reliability 4. Performance 5. Duplication reduce 6. Scalability
Use case for project Page 26 of 44
Indian Institute of Information Technology & Management
2.14. Assumptions 1. Weights are assigned by predefined rules. 2. Some bench mark value for risk evaluation is predefined.
2.1. Name TBD TBD
Notes and Issues Due Date Result TBD TBD TBD TBD Issue TBD TBD
Revision History Name N/A N/A Date N/A N/A Reason For Changes N/A N/A Version N/A N/A
Use case for project Page 27 of 44
Indian Institute of Information Technology & Management
6.0 Issued Draft Use Case Template
Use Case ID: Use Case Name: Created By: Date Created: 6.0 Issued Draft Arti Omar 31-10-2011 Last Updated By: N/A Date Last N/A Updated:
Actors: Trigger: Description: Preconditions: Post-conditions: Normal Flow: Alternative Flows: Exceptions: Includes: Priority: Frequency of Use: Business Rules: Special Requirements: Assumptions: Notes and Issues:
Underwriter Customer make call after loan status is approved For disbursing loan amount and to close loan application Loan status should be approved, customer should agree to take loan Draft is issued, amount is disbursed, loan application is closed 6.0 Draft is made in the name of beneficiary, loan report is updated N/A N/A N/A System should update loan status, send acknowledge to customer, reflect loan amount in customer account One time in month for single loan approval N/A Extensibility, reliability, maintainability, local access to customer N/A TBD
1.
Use Case Identification 1.1. ? 6.0 Use Case ID
Use case for project Page 28 of 44
Indian Institute of Information Technology & Management
1.2.
Use Case Name
? Issued Draft 1.2.1 Created By ? Arti Omar 1.2.2 Date Created 31-10-2011 1.2.3 Last Updated By N/A 1.2.4 Date Last Updated N/A 2. Use Case Definition 2.1. Actors
? Underwriter 2.2. Trigger
? Loan status is approved. ? Draft is made by bank to disburse loan amount. 2.3. Description
For disbursement of loan amount and to close loan application Issued draft use case is defined. 2.4. Preconditions
1. Loan status should be approved. 2. Customer should be agreed to take loan.
Use case for project Page 29 of 44
Indian Institute of Information Technology & Management
2.5.
Post-conditions
1. Draft will be issued. 2. Loan amount will be disbursed. 3. Loan application will be closed. 4. Loan report is updated. 2.6. ? Normal Flow
How does under writer accomplish the task stated in Issued draft use case? 1. Underwriting function is performed. 2. Draft is made in the name of beneficiary as requested on loan application and informed him. 3. Loan status will be updated pending to approve and customer will come to know that his loan application has been approved. 4. Customer will be requested to take draft and loan amount. 5. And after loan disbursal that loan application will be closed.
2.7.
Alternative Flows
1. Underwriting function is performed. 2. Draft is made in the name of beneficiary as requested on loan application and informed him. 3. Loan status will be updated pending to approve and customer will come to know that his loan application has been approved. 4. Customer will be requested to take draft and loan amount. 5. Draft is not taken by customer and loan amount is not disbursed
Use case for project Page 30 of 44
Indian Institute of Information Technology & Management
6. Deal is postponed for near future. 7. Loan status is set to unissued draft. 8. Loan account is closed. 2.8. N/A 2.9. N/A 2.10. Priority 1. System should update underwriting result. 2. System should send acknowledged to customer for loan approval. 3. Reflect the amount in customer account. 2.11. Frequency of Use One time use when loan is approved in monthly unit of time. 2.12. Business Rules N/A 2.13. Special Requirements 1. Reusability 2. Maintainability 3. Extensibility 4. Reliability 5. Enough Memory
Use case for project Page 31 of 44
Exceptions
Includes
Indian Institute of Information Technology & Management
2.14. Assumptions N/A 2.1. Name TBD TBD Revision History Name N/A N/A Date N/A N/A Reason For Changes N/A N/A Version N/A N/A Notes and Issues Due Date Result TBD TBD TBD TBD Issue TBD TBD
Use case for project Page 32 of 44
Indian Institute of Information Technology & Management
7.0 Loan Track Use Case Template
Use Case ID: Use Case Name: Created By: Date Created: 7.0 Loan Track Arti Omar 31-10-2011 Last Updated By: N/A Date Last N/A Updated:
Actors: Trigger: Description: Preconditions: Post-conditions: Normal Flow: Alternative Flows: Exceptions: Includes: Priority: Frequency of Use: Business Rules: Special Requirements: Assumptions: Notes and Issues:
Customer LAN is assigned to customer In order to check current loan status Customer should be registered, Reliable information should be entered, LAN should be assigned Customer can track loan at any point of time 7.0 LAN assignment, login into system, LAN accepted, Status is tracked 7.1 LAN not accepted, enter customer ID, resend LAN, relogin, LAN accepted, status is tracked N/A N/A System should upload loan form, save loan information, generate random LAN, send acknowledgement Max. 3 times in a day N/A Consistency, reusability, loose_coupling, reliability, security N/A TBD
1.
Use Case Identification 1.1. ? 7.0 Use Case ID
Use case for project Page 33 of 44
Indian Institute of Information Technology & Management
1.2.
Use Case Name
? Loan Track 1.3. Use Case History
1.3.1 Created By Supply the name of the person who initially documented this use case. 1.3.2 Date Created Enter the date on which the use case was initially documented. 1.3.3 Last Updated By Supply the name of the person who performed the most recent update to the use case description. 1.3.4 Date Last Updated Enter the date on which the use case was most recently updated. 2. Use Case Definition 2.1. Actors
? Customer 2.2. Trigger
Assignment of LAN for tracking loan information 2.3. Description
For tracking loan at any stage, customers are assigned LAN. For getting loan status information loan tracking done
2.4.
Preconditions
1. Customer should be registered
Use case for project Page 34 of 44
Indian Institute of Information Technology & Management
2. All information provided by customer should be scanned and no missed information form should be accepted by system 3. LAN should be assigned to valid registered customer. 4. Enough memory required in Bank data base to run several loan tracking queries at a time. 2.5. Post-conditions
1. Customer will get to know about loan status. 2.6. ? Normal Flow
How does customer accomplish the task stated in Track loan use case?
1. Entered scanned information into LOS by data entry operator or by customer if it is online application form 2. Generation of a random number by system for that particular customer which is known as LAN (loan application number). 3. By entering LAN one can track loan status.
2.7. N/A 2.8. N/A 2.9. N/A
Alternative Flows
Exceptions
Includes
2.10. Priority 1. Upload Loan form properly.
Use case for project Page 35 of 44
Indian Institute of Information Technology & Management
2. Saved all scanned information from loan application form. 3. Generate random number (LAN) 4. Provide customer registration facility. 5. Make error if wrong logged in. 6. Ask for customer ID for resending new LAN. 7. Validate customer ID from customer data base. 8. Send LAN. 2.11. Frequency of Use Maximum 3 times it is used on daily unit of time. 2.12. Business Rules N/A 2.13. Special Requirements 1. Consistency 2. Reusability 3. Loose_coupling 4. Standardized_interface 5. Extensibility 6. Maintainability 7. Performance 8. Reliability 9. Probability 10. Access locally
Use case for project Page 36 of 44
Indian Institute of Information Technology & Management
11. Replicate on all nodes 12. Duplication reduce 13. Scalability 2.14. Assumptions N/A 2.1. Name TBD TBD Revision History Name N/A N/A Date N/A N/A Reason For Changes N/A N/A Version N/A N/A Notes and Issues Due Date Result TBD TBD TBD TBD Issue TBD TBD
Use case for project Page 37 of 44
Indian Institute of Information Technology & Management
8.0 Fetch Report Use Case Template
Use Case ID: 8.0 Use Case Fetch Report Name: Created By: Arti Omar Date Created: 31-10-2011
Last Updated By: N/A Date Last N/A Updated:
Actors: Bank Administrator Trigger: Call for new loan assignment and number of loan approval Description: In order to know number of loan assignment to different lenders, and to see assigned loan status Preconditions: Report should be prepared, loan status should be approved, Bank admin should be an authorized person Post-conditions: New loan can be assigned to lenders, draft is disbursed to old customer Normal Flow: 8.0 make admin Id, run ID in system, ID accepted, Track report Alternative Flows: N/A Exceptions: N/A Includes: N/A Priority: System should run admin ID, ID update in data base, load report Frequency of Use: Two times in a week Business Rules: N/A Special Requirements: Loose_coupling, Standardized_interface, Extensibility, Maintainability, Performance, Direct collaboration Assumptions: N/A Notes and Issues: TBD
Use case for project Page 38 of 44
Indian Institute of Information Technology & Management
1.
Use Case Identification 1.1. ? 8.0 1.2. Use Case Name Use Case ID
? Fetch report 1.3. Use Case History
1.3.1 Created By ? Arti Omar 1.3.2 Date Created 31-10-2011 1.3.3 Last Updated By N/A 1.3.4 Date Last Updated N/A 2. Use Case Definition 2.1. Actors
? Bank Administrator 2.2. Trigger
? Bank admin make call for new of loan assignment and for approving new loan applications. ? Old Customer call for its pending but finalized loan.
Use case for project Page 39 of 44
Indian Institute of Information Technology & Management
2.3.
Description
In order to konw number and detailed of loan in review stage, approved or declined and also a report for number of cases assigned to different lenders for new loan assignment.
2.4.
Preconditions
1. Bank admin should have unique ID to fetch report. 2. Bank data base should be updated after each use case. 3. Report are made after the loan assignment verification and loan verification and underwriting function. 2.5. Post-conditions
1. He can assign new loan applications according to the lenders status. 2. He can get the information about performance of bank and how many loans have been approved and in pending stage. 3. Old customer will be issued a draft. 2.6. ? Normal Flow
How does Bank administrator accomplish the task stated in Fetch Report use case?
1. Query is run by bank admin in the LOS to see the number of loans and details of loan in different-2 stages. 2. Create Admin ID 3. Run System ID to access report 4. ID accepted by system 5. Track Report having loan ID, type of loan, Status of loan, Corresponding lender.
Use case for project Page 40 of 44
Indian Institute of Information Technology & Management
2.7. N//A 2.8. N/A 2.9. N/A
Alternative Flows
Exceptions
Includes
2.10. Priority System should 1. Run query for Loan status. 2. Run query for number of open case assigned to different-2 lenders. 3. Show Updated Lenders status with lender IDs. 2.11. Frequency of Use Maximum 2 times on weekly unit of time 2.12. Business Rules N/A 2.13. Special Requirements 1. Loose_coupling 2. Standardized_interface 3. Extensibility 4. Maintainability 5. Performance
Use case for project Page 41 of 44
Indian Institute of Information Technology & Management
6. Direct collaboration 7. Utilization minimized 8. Reliability 9. Probability 10. Access locally 11. Replicate on all nodes 12. Duplication reduce 2.14. Assumptions N/A 2.1. Name TBD TBD Revision History Name N/A N/A Date N/A N/A Reason For Changes N/A N/A Version N/A N/A Notes and Issues Due Date Result TBD TBD TBD TBD Issue TBD TBD
Use case for project Page 42 of 44
Indian Institute of Information Technology & Management
Use case for project Page 43 of 44
doc_861716342.docx
Use Case document of LOS
Indian Institute of Information Technology & Management
Use Cases
For
Version 1.0 approved
Prepared by
Arti Omar (IPG_2008108)
ABV-IIITM
31-10-2011
Indian Institute of Information Technology & Management
Use Case List
Primary Actor
Data Entry Operator Bank Administrator Lenders (Normal/Supervisory) CIBIL Underwriter Customer
Use Cases
Enter Application Information Loan Configuration, Loan Assignment, Fetch Report Loan Verification Credit Score checking Underwriting, Issued Draft Track loan
Loan Originating system.simp
Use case for project Page 1 of 44
Indian Institute of Information Technology & Management
1.0 Enter application Information Use Case Template
Use Case ID: Use Case Name: Created By: Date Created: 1 Enter application Information Arti Omar Last Updated By: N/A 31-10-2011 Date Last Updated: N/A Data entry operator/customer Submission of loan application To Scan document and enter in LOS Form Availability, User Authorization, enough memory Information entered, LAN assigned 1.0 submission of form, scanning, entering loan information N/A N/A N/A Form availability, Clear downloading, Send confirmation mail 3 times in a day on daily basis unit of time N/A Consistency, Access locally, Open source N/A TBD
Actors: Trigger: Description: Preconditions: Post-conditions: Normal Flow: Alternative Flows: Exceptions: Includes: Priority: Frequency of Use: Business Rules: Special Requirements: Assumptions: Notes and Issues:
Use case for project Page 2 of 44
Indian Institute of Information Technology & Management
1.
Use Case Identification 1.1. Use Case ID ? 1.0 1.2. Use Case Name. ? Enter Application Information 1.3. Use Case History
1.3.1 Created By ? Arti Omar 1.3.2 Date Created ? 31-10-2011 1.3.3 Last Updated By N/A 1.3.4 Date Last Updated N/A 2. Use Case Definition 2.1. Actors 3.1.1 Data Entry Operator 3.1.2 Customer As mentioned, this case study is divided in two parts at the beginning of the case. If customer fills the loan application form in offline mode then Data Entry Operator will be the first actor who will trigger the event but if customer fills the loan application form in online mode then customer itself will be the first actor who will trigger the event.
Use case for project Page 3 of 44
Indian Institute of Information Technology & Management
2.2.
Trigger
Loan applications are submitted at submission counter. 2.3. Description ? After submission of loan application forms data entry operator will scan all the forms with the documents are attached with them for any missing information. When scanning is done then he will feed all the information has been provided into LOS (loan originating system) in Enter application information use case. 2.4. Preconditions
1. User’s identity has been authenticated. 2. User’s computer has sufficient free memory available to launch task. 3. Form should be available online/offline. 2.5. Post-conditions
1. Loan information has been entered into system 2. Scanned documents are in document management system 3. LAN is assigned to customer 4. Unique document number is assigned to document. 5. After the execution of Enter application information use case, system state will be in partial application state. 6. Send acknowledgment to customer.
2.6. ?
Normal Flow
How does Data Entry Operator accomplish the task stated in Enter Application Information?
Use case for project Page 4 of 44
Indian Institute of Information Technology & Management
1. Submission of application form on the application submission counter. 2. Data entry operator will be responsible for scanning all the applications for any missed information and accordingly 3. Acceptance or rejection of the form. 4. Enter loan information from accepted form. Like type of loan, loan product, personal, address, employment, asset & liability and loan information into the LOS 5. Scanning attached documents and accordingly accepts and rejects them. 6. Assigned document number to accepted form. 7. Generate Loan Application Number (LAN) 8. Save image in document management system with the key as . 2.7. Alternative Flows
1. If form missed in offline mode make a customer entry in entry register before giving form so that customer can be informed for resubmission. 2.8. N/A 2.9. N/A 2.10. Priority 1. Form should be available to customer either online and offline mode. 2. System should have enough memory space. 3. System should send conformation mail to customer with LAN. 4. System should classify different loan products under each loan category.
Use case for project Page 5 of 44
Exceptions
Includes
Indian Institute of Information Technology & Management
5. System should show interest rate fixed tenure and type of interest rate information with loan product. 6. Tight scanning of provided information. 7. Reject false positives. 2.11. Frequency of Use In daily basis this use case can be used by customers at most 3 times. 2.12. Business Rules N/A 2.13. Special Requirements Nonfunctional requirement (NFR) can be stated as soft goal. Under NFR we define 1. Consistency 2. Access Locally 3. Open source system 4. Response time 5. Replicate in all nodes 2.14. Assumptions 1. Server has enough memory 2. Data base has enough capacity
Use case for project Page 6 of 44
Indian Institute of Information Technology & Management
2.15. Notes and Issues Name TBD TBD Due Date Result TBD TBD TBD TBD Issue TBD TBD
Revision History
Name N/A N/A
Date N/A N/A
Reason For Changes N/A N/A
Version N/A N/A
Use case for project Page 7 of 44
Indian Institute of Information Technology & Management
2.0 Loan Configuration Use Case Template
Use Case ID: Use Case Name: Created By: Date Created: 2.0 Loan Configuration Arti Omar 31-10-2011 Last Updated By: N/A Date Last N/A Updated:
Actors: Trigger: Description: Preconditions: Post-conditions: Normal Flow: Alternative Flows: Exceptions: Includes: Priority: Frequency of Use: Business Rules: Special Requirements: Assumptions: Notes and Issues:
Bank Administrator Calling for loan configuration Configured loan application for loan assignment purpose Information should be entered by data operating system/customer Loan application are configured, loan status update 2.0 fetching loan information from LOS, classifying application form N/A N/A N/A System should proper classify loan product, update data base Once in a day on daily basis unit of time N/A Consistency, Maintainability, reliability N/A TBD
1.
Use Case Identification 1.1. Use Case ID ? 2.0 1.2. Use Case Name ? Loan Configuration
Use case for project Page 8 of 44
Indian Institute of Information Technology & Management
1.3.
Use Case History
1.3.1 Created By ? Arti Omar 1.3.2 Date Created ? 31-10-2011 1.3.3 Last Updated By N/A 1.3.4 Date Last Updated N/A 2. Use Case Definition 2.1. Actors
1. Bank Admin 2.2. Trigger
Bank admin calls system for loan configuration 2.3. Description
Configured loan applications are in the system for loan assignment purpose. 2.4. Preconditions
1. All information form application should be entered by Data entry operator/Customer. 2. Admin should have enough memory to launch the task. 2.5. Post-conditions
1. After the execution of loan configuration use case system state will be in Pending state from consumer point of view whereas from bank’s perspective it is Evaluation state.
Use case for project Page 9 of 44
Indian Institute of Information Technology & Management
2. Identifying loan product and creating a loan list 3. All the applications will be divided in two parts, ? Loans beyond 5 lacs. ? Loans lesser than 5 lacs 2.6. ? Normal Flow
How does Bank Administrator accomplish the task stated in Loan Configuration use case? 1. All required information has been entered by data entry operator into LOS 2. Bank admin will run query in the system to get information about the loan request in a specific date under specific loan category, 3. System response for information about all the loan products under specific category. 4. Loans are classified in two parts [1] Loan applications beyond 5 lacs. [2] Loan applications within 5 lacs range
2.7. N/A 2.8. N/A 2.9. N/A
Alternative Flows
Exceptions
Includes
2.10. Priority 1. Entered information should be loaded properly.
Use case for project Page 10 of 44
Indian Institute of Information Technology & Management
2. All types of loan products should be properly classified. 3. Replicate update in all parts. 2.11. Frequency of Use On the daily basis it is used once in a day. 2.12. Business Rules N/A 2.13. Special Requirements 1. Consistency [object] 2. Loose_coupling [objects] 3. Maintainability [system] 4. Reliability 5. Duplication reduce 2.14. Assumptions N/A 2.1. Name TBD TBD Revision History Name N/A N/A Date N/A N/A Reason For Changes N/A N/A Version N/A N/A Notes and Issues Due Date Result TBD TBD TBD TBD Issue TBD TBD
Use case for project Page 11 of 44
Indian Institute of Information Technology & Management
3.0 Loan Assignment Use Case Template
Use Case ID: Use Case Name: Created By: Date Created: 3.0 Loan Assignment Arti Omar 31-10-2011 Last Updated By: N/A Date Last N/A Updated:
Actors: Bank Administrator Trigger: Calling configured loan for assignment Description: To Assign loan application to normal and supervisory lender according to business rules. Preconditions: Valid lenders Ids, No lender should open cases as mentioned in the rule. Post-conditions: Update lender status, prepared report, loan are assigned Normal Flow: 3.0 configured loan application is called, check lender status, assign loan application Alternative Flows: N/A Exceptions: N/A Includes: N/A Priority: System should upload configured loan list, classify loan application according to loan amount, follow round robin process Frequency of Use: Once in week Business Rules: 1. Loan beyond 5 lacs assigned to supervisory lender, 2. loan assignment should follow round robin process 3. Normal lender can have only 5 open cases at any point of time and supervisory lender can have 7 open cases at any point of time. Special Requirements: Consistency, maintainability, reliability Assumptions: Supervisory lenders also have their IDs. Notes and Issues: TBD .
Use case for project Page 12 of 44
Indian Institute of Information Technology & Management
1.
Use Case Identification 1.1. ? 3.0 1.2. Use Case Name Use Case ID
? Loan Assignment 1.3. Use Case History
1.3.1 Created By ? Arti Omar 1.3.2 Date Created 31-10-2011 1.3.3 Last Updated By N/A 1.3.4 Date Last Updated N/A 2. Use Case Definition 2.1. Actors
? Bank Administrator 2.2. Trigger
Calling configured loan for assignment 2.3. Description
Assign loan to Normal and Supervisory lenders as per the Business Rules for loan verification.
Use case for project Page 13 of 44
Indian Institute of Information Technology & Management
2.4.
Preconditions
1. Lenders should have unique IDs 2. Normal lenders should not have more than 5 open cases at any point of time and Supervisory lenders should not have more than 7 open cases at any point of time. 3. Each loan application should contain valid loan ID 4. Loan applications are properly configured with all information and documents. 2.5. Post-conditions
1. After the execution of loan assignment use case loan status will be in Pending state from consumer point of view whereas from bank’s perspective it is Evaluation state. 2. Loan applications are assigned to lenders for verification. 3. Lenders status are update as per the number of open cases are assigned. 4. Report is prepared for numbers of loans are assigned to different lenders. 2.6. ? Normal Flow
How does Bank Administrator accomplish the task stated in Loan Assignment use case? 1. Configured loan applications data base is called. 2. Check loan amount and lender status in parallel. 3. Loan applications beyond 5 lacs are assigned to supervisory have less than 7 open cases at that point of time. 4. Loan applications below 5 lacs are assigned to Normal lenders have less than 5 open cases at that point of time. 5. Loans are assigned to lenders on round robin basis sequential lender IDs.
2.7. N/A
Alternative Flows
Use case for project Page 14 of 44
Indian Institute of Information Technology & Management
2.8. N/A 2.9. N/A
Exceptions
Includes
2.10. Priority 1. Upload configured loan application list 2. Loans beyond 5 lacs make their status 1. 3. Loans below 5 lacs make their status 0. 4. Update lenders status. 5. System should follow round robin process. 6. Assigned IDs to lenders 2.11. Frequency of Use Once in week 2.12. Business Rules There are three business rules for assignment of loan application to lenders. 1. All loan applications beyond 5 lacs can only be assigned to Supervisory lenders. 2. Loan cases will be assigned on round robin basis of sequential Normal Lender IDs. 3. A Normal lender cannot have more than 5 open cases assigned to him at any point of time and a Supervisory lender cannot have more than 7 open cases at any point of time. 2.13. Special Requirements 1. Consistency 2. Performance
Use case for project Page 15 of 44
Indian Institute of Information Technology & Management
3. Maintainability 4. Reliability 5. Security 2.14. Assumptions 1. Assuming Supervisory lenders also have IDs. And loan cases will be assigned on round robin basis of sequential Supervisory lender IDs. 2. Assuming all lenders do not violated the condition at the time of assignment. Like if loan is assigned to Normal lender he does not have more than 5 open cases at any point of time. This condition is applicable with Supervisory lender too. 3. Assuming Bank has enough lenders for loan assignment if not then alternative flow will be applicable. 2.15. Notes and Issues Name TBD TBD Due Date Result TBD TBD TBD TBD Issue TBD TBD
Revision History Name N/A N/A Date N/A N/A Reason For Changes N/A N/A Version N/A N/A
Use case for project Page 16 of 44
Indian Institute of Information Technology & Management
4.0 Loan Verification Use Case Template
Use Case ID: Use Case Name: Created By: Date Created: 4.0 Loan Verification Arti Omar 31-10-2011 Last Updated By: N/A Date Last N/A Updated:
Actors: Lenders (Normal/Supervisory) Trigger: Lenders are asked to give loan verification to bank admin/underwriter Description: In order to verify loan and to save result for underwriting Preconditions: Loan application documents should be saved with key , LAN should be known to lenders Post-conditions: Loan verified, loan verification status is updated, forward to underwriter Normal Flow: 4.0 fetching loan documents, sending request to CIBIL for credit score checking Alternative Flows: N/A Exceptions: N/A Includes: Credit score checking done by CIBIL by sending online request Priority: System should run key, system should follow rules for verification Frequency of Use: One time use on daily basis for single loan application Business Rules: N/A Special Requirements: Reusability, throughput, stress handling Assumptions: Rules are predefined for verification Notes and Issues: TBD
Use case for project Page 17 of 44
Indian Institute of Information Technology & Management
1.
Use Case Identification 1.1. ? 4.0 1.2. Use Case Name Use Case ID
? Loan verification 1.3. Use Case History
1.3.1 Created By ? Arti Omar 1.3.2 Date Created 31-10-2011 1.3.3 Last Updated By N/A 1.3.4 Date Last Updated N/A 2. Use Case Definition 2.1. Actors
1. Normal Lender 2. Supervisory lender 2.2. Trigger
Lenders are asked to give loan application verification to bank admin/underwriter.
Use case for project Page 18 of 44
Indian Institute of Information Technology & Management
2.3.
Description
In order to validate information have been provided by customer and to get customer credit rating loan application are verified by lenders. 2.4. Preconditions
1. All the loan applications should have documents saved in document management system with key as . 2. Documents are easily accessible to lenders 3. should be known to lenders. 4. Customer should be registered with valid customer ID. 5. CIBIL accessibility. 2.5. Post-conditions
1. Loan application will be verified by performing listed task I. Asset/liability test II. Address verification test III. Information Validation IV. Credit Score checking 2. If all conditions are true make loan verification status 1 other wise 0. 3. Loan status is updated. 4. All verification results are saved in the system. 2.6. ? Normal Flow
How do lenders (Normal and Supervisory lender) accomplish the task stated in Loan Verification use case?
Use case for project Page 19 of 44
Indian Institute of Information Technology & Management
As applications are assigned to lenders according to business rules, lenders will perform their task by taking loan information, personal information and all that from LOS to verify them. This function is done by step by step is given below. [1] Open assigned loan application detail in LOS. [2] Verify person authorization by using documents. [3] Analyze assets/liability status of consumer by using documents [4] Address verification by using documents. [5] Other information validation. [6] Verify credit score by sending online request to CIBIL with in LOS [7] Repeat the process if loan verification status is 0. [8] Forward loan application with all the information recorded and documents attached. After each verification, make corresponding status flag equals to 1or 0. 1 if given information is verified, 0 if it is not. 2.7. N/A 2.8. N/A 2.9. Includes Exceptions Alternative Flows
Credit score checking done by lenders comes in includes for that they need external actor who will provide response for credit score checking. Under Loan verification online request will be send to CIBIL for credit score checking for particular customer and CIBIL will response for that request. This all will be denoted by 4 here 4 is loan Verification ID and which includes (credit score check) for loan verification.
Use case for project Page 20 of 44
Indian Institute of Information Technology & Management
2.10. Priority 1. Documents are accessible and key is known to lenders 2. Rules for assets /liability analysis 3. Rules for address verification 4. Rules for information validation 5. Update the status of asset/liability, address verification and information validation. 6. Support online request to CIBIL. 7. Connect server to CIBIL data base. 8. Save automatically CIBIL response. 9. Send acknowledgment to CIBIL 2.11. Frequency of Use One time use for single loan application on daily basis 2.12. Business Rules No Normal lender is allowed to have more than 5 open cases at any point of time and no Supervisory lender is allowed to have more than 7 open cases at any point of time. 2.13. Special Requirements 1. Reusability 2. Compatibility 3. Throughput 4. Stress handling
Use case for project Page 21 of 44
Indian Institute of Information Technology & Management
2.14. Assumptions N/A 2.1. Name TBD TBD Revision History Name N/A N/A Date N/A N/A Reason For Changes N/A N/A Version N/A N/A Notes and Issues Due Date Result TBD TBD TBD TBD Issue TBD TBD
Use case for project Page 22 of 44
Indian Institute of Information Technology & Management
5.0 Underwriting Use Case Template
Use Case ID: Use Case Name: Created By: Date Created: 5.0 Underwriting Arti Omar 31-10-2011 Last Updated By: N/A Date Last N/A Updated:
Actors: Trigger: Description: Preconditions:
Post-conditions: Normal Flow: Alternative Flows: Exceptions: Includes: Priority: Frequency of Use: Business Rules: Special Requirements: Assumptions: Notes and Issues:
Underwriter Call for risk evaluation In order to evaluate risk before loan disbursement Updated verification status, CIBIL database accessibility, Forward all attached documents and results for underwriting function Risk is evaluated , report prepared, loan status is updated 5.0 assigned weight, take aggregated, compare, update status N/A N/A N/A System should reflect updated status, accept rules for weight assignment One time use on daily basis N/A Reusability, standardized interface, performance, quick response Rules are predefined for weight allocation TBD
1.
Use Case Identification 1.1. ? 5.0 Use Case ID
Use case for project Page 23 of 44
Indian Institute of Information Technology & Management
1.2.
Use Case Name
? Underwriting 1.3. Use Case History
1.3.1 Created By ? Arti Omar 1.3.2 Date Created 31-10-2011 1.3.3 Last Updated By N/A 1.3.4 Date Last Updated N/A 2. Use Case Definition 2.1. Actors
? Underwriter 2.2. Trigger
Call for risk evaluation when loan verification status is 1. 2.3. Description
In order to perform risk evaluation underwriting function is performed by underwriter. When risk evaluation is done by underwriter now he has the authority to approve loan, reject loan or can place on hold for seeking more information. 2.4. Preconditions
1. Verification flag must be 1.
Use case for project Page 24 of 44
Indian Institute of Information Technology & Management
2. CIBIL must response for the request of credit score checking. 3. Bank should have enough underwriters. 4. One should not have 5 open cases at any point of time for any loan amount. 5. Other important documents and results should be forward to underwriter. 2.5. Post-conditions
1. Risk evaluation is done. 2. Loan status will be updated either loan approved, loan rejected or placed on hold for seeking more information. 3. Result is saved and report is prepared. 2.6. ? Normal Flow
How does Underwriter accomplish the task stated in Underwriting use case? 1. Forward verified loan application with all results and documents attached. 2. Weights are assigned to each entity list in loan verification list for verification. 3. Aggregate value is calculated. 4. Comparison of aggregate value and bench mark value. 5. Loan status is updated to loan approved if aggregate value is greater than bench mark value. 6. Loan status is updated to loan rejected if aggregate value is lesser than bench mark value. 7. Loan status is updated to loan placed on hold for seeking more information aggregate is approximate to bench mark value.
2.7. N/A
Alternative Flows
Use case for project Page 25 of 44
Indian Institute of Information Technology & Management
2.8. N/A 2.9. N/A
Exceptions
Includes
2.10. Priority 1. Forward loan application should contain all results and documents. If it is, make document status is 1. 2. Weight assignment rules 3. Aggregate calculation rule and comparison rule. 4. Updating Loan status. 2.11. Frequency of Use On Daily unit of time, one time use of use case for single loan application. 2.12. Business Rules N/A 2.13. Special Requirements 1. Reusability 2. Standardized interface 3. Reliability 4. Performance 5. Duplication reduce 6. Scalability
Use case for project Page 26 of 44
Indian Institute of Information Technology & Management
2.14. Assumptions 1. Weights are assigned by predefined rules. 2. Some bench mark value for risk evaluation is predefined.
2.1. Name TBD TBD
Notes and Issues Due Date Result TBD TBD TBD TBD Issue TBD TBD
Revision History Name N/A N/A Date N/A N/A Reason For Changes N/A N/A Version N/A N/A
Use case for project Page 27 of 44
Indian Institute of Information Technology & Management
6.0 Issued Draft Use Case Template
Use Case ID: Use Case Name: Created By: Date Created: 6.0 Issued Draft Arti Omar 31-10-2011 Last Updated By: N/A Date Last N/A Updated:
Actors: Trigger: Description: Preconditions: Post-conditions: Normal Flow: Alternative Flows: Exceptions: Includes: Priority: Frequency of Use: Business Rules: Special Requirements: Assumptions: Notes and Issues:
Underwriter Customer make call after loan status is approved For disbursing loan amount and to close loan application Loan status should be approved, customer should agree to take loan Draft is issued, amount is disbursed, loan application is closed 6.0 Draft is made in the name of beneficiary, loan report is updated N/A N/A N/A System should update loan status, send acknowledge to customer, reflect loan amount in customer account One time in month for single loan approval N/A Extensibility, reliability, maintainability, local access to customer N/A TBD
1.
Use Case Identification 1.1. ? 6.0 Use Case ID
Use case for project Page 28 of 44
Indian Institute of Information Technology & Management
1.2.
Use Case Name
? Issued Draft 1.2.1 Created By ? Arti Omar 1.2.2 Date Created 31-10-2011 1.2.3 Last Updated By N/A 1.2.4 Date Last Updated N/A 2. Use Case Definition 2.1. Actors
? Underwriter 2.2. Trigger
? Loan status is approved. ? Draft is made by bank to disburse loan amount. 2.3. Description
For disbursement of loan amount and to close loan application Issued draft use case is defined. 2.4. Preconditions
1. Loan status should be approved. 2. Customer should be agreed to take loan.
Use case for project Page 29 of 44
Indian Institute of Information Technology & Management
2.5.
Post-conditions
1. Draft will be issued. 2. Loan amount will be disbursed. 3. Loan application will be closed. 4. Loan report is updated. 2.6. ? Normal Flow
How does under writer accomplish the task stated in Issued draft use case? 1. Underwriting function is performed. 2. Draft is made in the name of beneficiary as requested on loan application and informed him. 3. Loan status will be updated pending to approve and customer will come to know that his loan application has been approved. 4. Customer will be requested to take draft and loan amount. 5. And after loan disbursal that loan application will be closed.
2.7.
Alternative Flows
1. Underwriting function is performed. 2. Draft is made in the name of beneficiary as requested on loan application and informed him. 3. Loan status will be updated pending to approve and customer will come to know that his loan application has been approved. 4. Customer will be requested to take draft and loan amount. 5. Draft is not taken by customer and loan amount is not disbursed
Use case for project Page 30 of 44
Indian Institute of Information Technology & Management
6. Deal is postponed for near future. 7. Loan status is set to unissued draft. 8. Loan account is closed. 2.8. N/A 2.9. N/A 2.10. Priority 1. System should update underwriting result. 2. System should send acknowledged to customer for loan approval. 3. Reflect the amount in customer account. 2.11. Frequency of Use One time use when loan is approved in monthly unit of time. 2.12. Business Rules N/A 2.13. Special Requirements 1. Reusability 2. Maintainability 3. Extensibility 4. Reliability 5. Enough Memory
Use case for project Page 31 of 44
Exceptions
Includes
Indian Institute of Information Technology & Management
2.14. Assumptions N/A 2.1. Name TBD TBD Revision History Name N/A N/A Date N/A N/A Reason For Changes N/A N/A Version N/A N/A Notes and Issues Due Date Result TBD TBD TBD TBD Issue TBD TBD
Use case for project Page 32 of 44
Indian Institute of Information Technology & Management
7.0 Loan Track Use Case Template
Use Case ID: Use Case Name: Created By: Date Created: 7.0 Loan Track Arti Omar 31-10-2011 Last Updated By: N/A Date Last N/A Updated:
Actors: Trigger: Description: Preconditions: Post-conditions: Normal Flow: Alternative Flows: Exceptions: Includes: Priority: Frequency of Use: Business Rules: Special Requirements: Assumptions: Notes and Issues:
Customer LAN is assigned to customer In order to check current loan status Customer should be registered, Reliable information should be entered, LAN should be assigned Customer can track loan at any point of time 7.0 LAN assignment, login into system, LAN accepted, Status is tracked 7.1 LAN not accepted, enter customer ID, resend LAN, relogin, LAN accepted, status is tracked N/A N/A System should upload loan form, save loan information, generate random LAN, send acknowledgement Max. 3 times in a day N/A Consistency, reusability, loose_coupling, reliability, security N/A TBD
1.
Use Case Identification 1.1. ? 7.0 Use Case ID
Use case for project Page 33 of 44
Indian Institute of Information Technology & Management
1.2.
Use Case Name
? Loan Track 1.3. Use Case History
1.3.1 Created By Supply the name of the person who initially documented this use case. 1.3.2 Date Created Enter the date on which the use case was initially documented. 1.3.3 Last Updated By Supply the name of the person who performed the most recent update to the use case description. 1.3.4 Date Last Updated Enter the date on which the use case was most recently updated. 2. Use Case Definition 2.1. Actors
? Customer 2.2. Trigger
Assignment of LAN for tracking loan information 2.3. Description
For tracking loan at any stage, customers are assigned LAN. For getting loan status information loan tracking done
2.4.
Preconditions
1. Customer should be registered
Use case for project Page 34 of 44
Indian Institute of Information Technology & Management
2. All information provided by customer should be scanned and no missed information form should be accepted by system 3. LAN should be assigned to valid registered customer. 4. Enough memory required in Bank data base to run several loan tracking queries at a time. 2.5. Post-conditions
1. Customer will get to know about loan status. 2.6. ? Normal Flow
How does customer accomplish the task stated in Track loan use case?
1. Entered scanned information into LOS by data entry operator or by customer if it is online application form 2. Generation of a random number by system for that particular customer which is known as LAN (loan application number). 3. By entering LAN one can track loan status.
2.7. N/A 2.8. N/A 2.9. N/A
Alternative Flows
Exceptions
Includes
2.10. Priority 1. Upload Loan form properly.
Use case for project Page 35 of 44
Indian Institute of Information Technology & Management
2. Saved all scanned information from loan application form. 3. Generate random number (LAN) 4. Provide customer registration facility. 5. Make error if wrong logged in. 6. Ask for customer ID for resending new LAN. 7. Validate customer ID from customer data base. 8. Send LAN. 2.11. Frequency of Use Maximum 3 times it is used on daily unit of time. 2.12. Business Rules N/A 2.13. Special Requirements 1. Consistency 2. Reusability 3. Loose_coupling 4. Standardized_interface 5. Extensibility 6. Maintainability 7. Performance 8. Reliability 9. Probability 10. Access locally
Use case for project Page 36 of 44
Indian Institute of Information Technology & Management
11. Replicate on all nodes 12. Duplication reduce 13. Scalability 2.14. Assumptions N/A 2.1. Name TBD TBD Revision History Name N/A N/A Date N/A N/A Reason For Changes N/A N/A Version N/A N/A Notes and Issues Due Date Result TBD TBD TBD TBD Issue TBD TBD
Use case for project Page 37 of 44
Indian Institute of Information Technology & Management
8.0 Fetch Report Use Case Template
Use Case ID: 8.0 Use Case Fetch Report Name: Created By: Arti Omar Date Created: 31-10-2011
Last Updated By: N/A Date Last N/A Updated:
Actors: Bank Administrator Trigger: Call for new loan assignment and number of loan approval Description: In order to know number of loan assignment to different lenders, and to see assigned loan status Preconditions: Report should be prepared, loan status should be approved, Bank admin should be an authorized person Post-conditions: New loan can be assigned to lenders, draft is disbursed to old customer Normal Flow: 8.0 make admin Id, run ID in system, ID accepted, Track report Alternative Flows: N/A Exceptions: N/A Includes: N/A Priority: System should run admin ID, ID update in data base, load report Frequency of Use: Two times in a week Business Rules: N/A Special Requirements: Loose_coupling, Standardized_interface, Extensibility, Maintainability, Performance, Direct collaboration Assumptions: N/A Notes and Issues: TBD
Use case for project Page 38 of 44
Indian Institute of Information Technology & Management
1.
Use Case Identification 1.1. ? 8.0 1.2. Use Case Name Use Case ID
? Fetch report 1.3. Use Case History
1.3.1 Created By ? Arti Omar 1.3.2 Date Created 31-10-2011 1.3.3 Last Updated By N/A 1.3.4 Date Last Updated N/A 2. Use Case Definition 2.1. Actors
? Bank Administrator 2.2. Trigger
? Bank admin make call for new of loan assignment and for approving new loan applications. ? Old Customer call for its pending but finalized loan.
Use case for project Page 39 of 44
Indian Institute of Information Technology & Management
2.3.
Description
In order to konw number and detailed of loan in review stage, approved or declined and also a report for number of cases assigned to different lenders for new loan assignment.
2.4.
Preconditions
1. Bank admin should have unique ID to fetch report. 2. Bank data base should be updated after each use case. 3. Report are made after the loan assignment verification and loan verification and underwriting function. 2.5. Post-conditions
1. He can assign new loan applications according to the lenders status. 2. He can get the information about performance of bank and how many loans have been approved and in pending stage. 3. Old customer will be issued a draft. 2.6. ? Normal Flow
How does Bank administrator accomplish the task stated in Fetch Report use case?
1. Query is run by bank admin in the LOS to see the number of loans and details of loan in different-2 stages. 2. Create Admin ID 3. Run System ID to access report 4. ID accepted by system 5. Track Report having loan ID, type of loan, Status of loan, Corresponding lender.
Use case for project Page 40 of 44
Indian Institute of Information Technology & Management
2.7. N//A 2.8. N/A 2.9. N/A
Alternative Flows
Exceptions
Includes
2.10. Priority System should 1. Run query for Loan status. 2. Run query for number of open case assigned to different-2 lenders. 3. Show Updated Lenders status with lender IDs. 2.11. Frequency of Use Maximum 2 times on weekly unit of time 2.12. Business Rules N/A 2.13. Special Requirements 1. Loose_coupling 2. Standardized_interface 3. Extensibility 4. Maintainability 5. Performance
Use case for project Page 41 of 44
Indian Institute of Information Technology & Management
6. Direct collaboration 7. Utilization minimized 8. Reliability 9. Probability 10. Access locally 11. Replicate on all nodes 12. Duplication reduce 2.14. Assumptions N/A 2.1. Name TBD TBD Revision History Name N/A N/A Date N/A N/A Reason For Changes N/A N/A Version N/A N/A Notes and Issues Due Date Result TBD TBD TBD TBD Issue TBD TBD
Use case for project Page 42 of 44
Indian Institute of Information Technology & Management
Use case for project Page 43 of 44
doc_861716342.docx