LMS Case Study Solution 1.0

Table of Contents

Topic Page No.Problem statement 2Requirement analysis 5Use case analysis 6 Use case specification 7

Use case diagram 16 Software requirements specification 17

Functional requirements 19Traceability matrix 26Non functional requirements 26

Sequence diagrams 27E-R diagrams 45Design Element 46Class Diagram 48System Test Cases 49

Problem Statement

‘Scott Bank’ was established in 1985 and has since become a leader in the domain of banking. The bank has decided to automate its home loan system and make it online in order to provide better services to its customers. The Loan Management System (LMS) would serve as a sub-system of the existing online banking system. The Bank aims to overcome external competition by providing its customers a web-enabled, user-friendly service. It allows users of the system to register themselves, and apply for home loans. An Officer can view the loan requests, reject the requests or forward the request to the manger. The Manager can then sanction/reject the loan request.

General users of the site are called Visitors. Visitors can view general information about the bank and the loan procedures that are followed. . When a visitor submits a loan application, the bank executive can contact the visitor and set-up a meeting. During the meeting between , the visitor might decide to avail of the home loan scheme. This discussion could also take place over the phone or by exchange of electronic mails. Thereafter, the Visitor signs up and submits a formal loan application. After signing up the Visitor is identified as a customer, and assigned a customer-id.Each customer can login into the system and view/update his profile, change his password apply for a loan and also view the loan status after he has applied for the same.

Once a customer requests for a loan, the application is forwarded to an Officerwho setups a meeting with the customer. During the meeting all documents are verified and a loan amount decided.. The Officer can hold , reject , or forward the application to the Manager for sanction. The Manager processes a loan request only after an Officer verifies the documents and forwards the request. The loan is sanctioned by the Manager and it is assumed that disbursement is done in one installment.

For every loan applied through the system a LoanApplicationId is generated. The LoanApplicationId is used to track the status of the loan, until the loan is sanctioned.

The customer can view the loan application status and the loan information. After the loan is sanctioned, a LoanId is generated for future reference.A Customer can view the loan amount sanctioned, the interest rate, terms of repayment, tenure of loan, mode of repayment and total interest, using the LoanId. Presently the mode of repayment is through debiting from the Savings Bank Account.

A customer can apply for more than one home loan.

Types of loans: Only Home Loan is being considered for the current development.

Definitions of the terms used in LMS: ● Visitor: Any person who visits the home loan site but is not yet registered.

● Customer: A visitor who is already registered and has a unique CustomerId.

● Officer: A Bank Employee, who is responsible for checking the loan application, verifying the relevant documents and then forwarding the application to the manager.

● Manager: A Bank Employee, who actually sanctions the loan. He can also change the interest rates as per rules.

● CustomerId: Every customer on successful registration is alloted a CustomerId, using which he can login to the system.

● LoanApplicationId: For every Loan Application submitted by a customer a LoanApplicationId is generated which is used to track the status of the loan until it is sanctioned.

● LoanId: When the Manager sanctions a Loan, a Loan Id is generated. This is used to refer to the details of the loan..

● Loan Application Status: Every Loan Application has a number of states. This state identifies the current Loan Application Status. The Loan Application States provided are –

○ 1 - Applied○ 2 - Officer Verified○ 3 - Sanctioned○ 4 - Rejected○ 5 - On Hold (An application can be withheld for subsequent

approval by an Officer until which time the status is withheld).

● Loan Status: After a loan is sanctioned it moves to a state called Active State. Once all the repayments are made it moves to the Closed State.

○ 1 - Active○ 2 - Closed

Business Logic:

1. Criteria for sanctioning:● Any salaried person, self employed professional, business man, and agriculturist.

● Minimum net take home salary of $ 6000/- per month for salaried employees. Annual income of not less than $ 120,000 for businesspersons, self-employed professionals and agriculturists.

● Minimum age for sanctioning a loan to a person is 21 yrs. The maximum age at the time of loan maturity should not exceed 63 yrs.

● The maximum loan amount which can be given to an individual is $ 100,00,000.

● The minimum loan amount which can be given to an individual is $ 100,000.

2. Interest Calculation:● Processing Charge: Nil.

● Rate of Interest (RoI): Flat rates of interest.

● Flat Interest Rate – a fixed interest of 7.5% ( the Manager can change the interest rateas per rules) on the entire Loan Amount Sanctioned.

3. Statement of interest paid and principal repaid.● This statement consists of Principal Amount Sanctioned.

● Total Interest and Principal Repaid.

4. Penal interest: @ 5% on the defaulted amount (where default amount is given in batch mode in a text file/table) and if default is beyond 6 months then legal action commences.

5. Changing Loan Interest Rate: The Manager has the authority to change the interest rate.

6. Reports: The Manger/Officer requires to view different types of reports. The LMS should provide the following reports –

● Customer report consisting of details of all the registered users of the system.

● Loans report consisting of details of all the Loans sanctioned / rejected / with held .

● Defaulter report giving details of all loans and corresponding customers with pending dues.

● Repayment Reports containing details of loans and their respective due dates and balance to be paid.

● Financial report consisting of all loans sanctioned by the bank during a particular period and amount that is credited from EMI’s of all loans sanctioned.

7. Repayment is done by deduction from an Saving Bank A/c in Scott Bank every month.

Assumptions:1. Every customer maintains a savings bank account with the bank.2. The bank has a Home Loan Account to which all the repayments are credited.3. The bank has adequate funds from which it can sanction loans to any number of customers.

Requirement AnalysisObjective: Real world application scenarios are captured as Use Cases. The Use Case diagrams are generated manually or using a tool. Requirement analysis along with the modeling elements forms the basis for the product development. Requirement Analysis provides the overall description of the product, the environment, detailed descriptions of the Use Cases.

Overview ‘Scott Bank’ was established in 1985 and has since become a leader in the domain of banking. The bank has decided to automate its home loan system and make it online in order to provide better services to its customers. This would serve as a sub-system of the existing online banking system. The bank aims to overcome external competition by providing its customers a web-enabled, user-friendly service.

Purpose The objectives of this system are:● To automate the Loan Management System (LMS), thereby making it more user-

friendly and simple so that customers can apply for a home loan online

● To provide services to users from across the globe.

The intended users of the application are:● Visitors to the site.

● Home Loan Customers of the bank.

● Officer of the bank.

● Manager of the bank.

Scope LMS enables:● Visitors to the site to view general information about the loan schemes offered

by the bank and to register online.● Home Loan Customers to apply for home loans, check loan application status

and to maintain their profile.● The Officer to forward, reject or put an application on hold.

● The Manager to sanction or reject a loan application and to maintain a rate of interest.

The system implements role based login functionality for Home Loan Customer, Officer & Manager.

User Characteristics The user should be proficient in the use of the English language.The user is not required to have any technical expertise.The user is required to have a basic knowledge of internet.

General Constraints Considering login scope of the system:

● Password should be at least 6 characters long and should contain at least one numeric and one special character like @,#,$,%,& etc.,

● The Home Loan Customer, Officer and Manager will have their own role based login id.

Assumptions, Dependencies and Risks

● The user should have a SB account in the bank before applying for a loan.

● A Home Loan Customer has his/her unique customer id and password, r

● Database security must be ensured.

● The system is dependent on the bank’s existing ‘SB account’ database for loan repayment.

Use Case Analysis

Use Cases Look-up Table

This table gives a consolidated view of the use cases. Detailed descriptions of each of the use cases are given in the Use Case Specification section following this table.

S. No.

Use Case ID Use Case Name

1 LMS-UGI01 View General Information2 LMS-UCE02 Calculate EMI3 LMS-USU03 Signup4 LMS-URL04 Login5 LMS-UAL05 Apply For Loan6 LMS-UAS06 View Loan Application Status7 LMS-UMP07 Maintain Customer Profile8 LMS-UVA08 View Loan Applications9 LMS-UPA09 Process Loan Application10 LMS-UMI10 Maintain Interest Rate11 LMS-UVR11 View Reports12 LMS-ULR12 Repay Loan

Use Cases Specification

Use Case ID:

LMS-UGI01

Use Case Name:

View General InformationDescription: This use case allows a user to browse through the various loan schemes offered by

the bank and the eligibility criteria associated with the different schemes such as age limit, total income and profession.

Actors: Visitor, Home Loan Customer, Officer, Manager.Preconditions: None.Post conditions: If the use case was successful, the actor gets to view the general information

regarding the loan schemes offered by the bank. Else the system state remains unchanged.

Frequency of Use: 500 per day.Normal Course of Events: This use case starts when the actor wishes to view the information regarding the

loans offered by the bank.1. The actor chooses to view the loan schemes.2. The system displays the details about the various loan schemes offered by the bank such as:

● Loan amount

● Tenure of loan

● Rate of interest

● Mode of repayment and the eligibility criteria associated with the loan schemes.

Alternative Courses: None.Associated Use case diagrams Refer LMS-Model-1.1.5.mdl (Rational Rose file).Exceptions: The following exceptions could occur:

1. Network connection failure. 2. Database connection failure.Appropriate error messages will be displayed.

Includes: None.Special Requirements: None.Assumptions: The system updates the details associated with the loan schemes as per existing

rules of the bank.Notes and Issues: None.

Use Case ID:

LMS-UCE02

Use Case Name:

Calculate EMIDescription: This use case allows a user to calculate the probable instalment amount for a

particular loan based on the rate of interest, tenure of loan and the loan amount.Actors: Visitor, Home Loan Customer, Officer, ManagerPreconditions: None.Post conditions: If the use case was successful, the actor gets to know the equated monthly

instalments for the given inputs. Otherwise the system state is unchanged.Frequency of Use: 400 per day.Normal Course of Events: 1. The actor selects to view the EMI calculator.

2. The system requests the actor to enter the loan amount, rate of interest and tenure of loan.3. The actor enters the required details.4. The system processes the data and displays the calculated EMI.

Business Logic:The EMI is calculated with a monthly reducing balance rate system, using the following formula: EMI = p*r*(((1+r)^n)/(((1+r)^n)-1)) P = Principal r = rate of Interest. If the rate is say 10% per annum then r = 10 /(100*12) n = Term duration. if the repayment is 20 Years then n will be 12* 20

For a loan of 100000.00 at 10.25% rate of interest and 20 years repayment period the EMI will be

EMI=100000*(10.25/1200)*(((1+(10.25/1200))^240)/ ((1+(10.25/1200))^240)-1)

EMI =$ 982.00Alternative Courses: Invalid Format or Insufficient Information

If in the Normal Course Of Events, the data entered is incomplete or incorrect, the system displays an error message. The actor can then choose to either input the required data or cancel the EMI calculation, at which point the use case ends.

Associated Use case diagrams Refer LMS-Model-1.1.5.mdl (Rational Rose file).Exceptions: The following exceptions could occur:


Includes: None.Special Requirements: None.Assumptions: None.Notes and Issues: None.

Use Case ID:

LMS-USU03

Use Case Name:

SignupDescription: This use case allows a Bank Customer to register with the Loan Management

System (LMS). Once the registration is complete, the Bank Customer becomes a Home Loan Customer. A customer id and password are generated and displayed to the Home Loan Customer with which he/she can login, apply for a loan and access services offered by the system.

Actors: Bank CustomerPreconditions: The Bank Customer should hold a savings bank (SB) account in the bank, in

order for this use case to begin.Post conditions: If the use case was successful, the Bank Customer is registered with the LMS.

Otherwise, the system state is unchanged.Frequency of Use: 250 per day.

Normal Course of Events: This use case starts when the Bank Customer wishes to register with the LMS to apply for a loan. 1. The Bank Customer selects to register with the LMS. 2. The system requests that the Bank Customer enter the registration details such as:

● Personal details

● Contact details

● Employment details

● SB account details 3. The Bank Customer enters the necessary registration details. 4. The system generates and displays a customer id and default password which can be changed later.

Alternative Courses: Invalid Format or Insufficient InformationIf in the Normal Course Of Events, the Bank Customer has not specified sufficient and/or valid details to register, the system will display an error message. The Bank Customer can either enter the missing information or cancel the sign-up, at which point the use case ends.


1. Network connection failure. 2. Database Connection failure.Appropriate error messages will be displayed.

Includes: None.Special Requirements: None.Assumptions: The Bank Customer is not an existing Home Loan Customer.Notes and Issues: None.

Use Case ID:

LMS-URL04

Use Case Name:

Login

Description: This use case describes how a user logs onto the Loan Management System (LMS)

Actors: Home Loan Customer, Officer, ManagerPreconditions: None.Post conditions: If the use case was successful, the actor is now logged onto the system. If not,

the system state is unchanged.Frequency of Use: 500 per day.Normal Course of Events: This use case starts when the actor wishes to log onto the LMS.

1. The system requests that the actor enters his/her id and password. 2. The actor enters his/her id and password. 3. The system validates the id and password and logs the actor onto the system. 4. Based on the login details entered by the actor, the system displays the corresponding actor’s user interface.

Alternative Courses: Invalid Id/PasswordIf in the Normal Course Of Events, the actor enters an invalid id and/or password, the system displays an error message. The actor will have an option to either provide valid id and password, or cancel the login, at which point the use case ends.



Includes: None.Special Requirements: Security check should be implemented to ensure that only the authorized

actors are able to view their user interface.Assumptions: None.Notes and Issues: None.

Use Case ID:

LMS-UAL05

Use Case Name:

Apply for Loan

Description: This use case allows a Home Loan Customer to apply for a home loan. A loan application id is generated and displayed to the Home Loan Customer.

Actors: Home Loan Customer.Preconditions: Home Loan Customer is logged onto the system, before this use case begins.Post conditions: If the use case was successful, a loan application id is generated and updated

in the system. Otherwise the system state is unchanged.Frequency of Use: 50 per day.Normal Course of Events: This use case starts when the actor wishes to apply for a home loan.

1. The system requests the Home Loan Customer to enter the loan application details.2. The Home Loan Customer enters the necessary details such as

● Loan amount

● Tenure

● Interest rate

● Property value

● Mode of repayment 3. The system validates the entered data. 4. A loan application id is generated, updated in the system and displayed to the Home Loan Customer.

Business Logic: The minimum limit for any loan is Rupees One Lakh and the maximum limit is Rupees One Crore.

Alternative Courses: Invalid Format or Insufficient InformationIf in the Normal Course Of Events, the Home Loan Customer has not specified sufficient and/or valid details to apply for loan, the system will display an error message. The Home Loan Customer can either enter the missing information or cancel the operation, at which point the use case ends.



Includes: None.

Special Requirements: None.Assumptions: A Home Loan Customer can apply for more than one home loan.

Notes and Issues: None.

Use Case ID:

LMS-UAS06

Use Case Name: View Loan Application Status

Description: This use case allows a Home Loan Customer to view his/her loan application status.

Actors: Home Loan CustomerPreconditions: The Home Loan Customer must be logged onto the system before this use case

begins.

Post conditions: The system state is unchanged by this use case.Frequency of Use: 500Normal Course of Events: This use case starts when a Home Loan Customer wishes to view his/her loan

application status 1. The Home Loan Customer requests to view the status of his/her loan applications. 2. The system retrieves and displays the loan application status for the loans applied by the Home Loan Customer.The status of the application can be one of these:

a. Under Processingb. On hold c. Sanctionedd. Rejected

3. When the Home Loan Customer indicates that he/she is done viewing the loan application status, the use case terminates.

Alternative Courses: No Status Information AvailableIf in the Normal Course of Events, the system cannot find any loan application status information for the Home Loan Customer, a message is displayed. Once the Home Loan Customer acknowledges the message, the use case terminates.




Use Case ID:

LMS-UMP07

Use Case Name:

Maintain Customer Profile

Description: This use case allows user to view profile, edit profile and change password.

Actors: Home Loan CustomerPreconditions: Home Loan Customer is logged onto the system, before this use case begins.Post conditions: If the use case was successful, any changes carried out by the Home Loan

Customer are updated. Otherwise, the system state is unchanged.Frequency of Use: 150 per day.Normal Course of Events: This use case starts when the Home Loan Customer wishes to view profile, edit

profile or change password.1. The system requests the Home Loan Customer to specify the function

he/she would like to perform (view profile, edit profile, or change password).

2. Once the Home Loan Customer provides the requested information, one of the sub flows is executed.

2.1. View Home Loan Customer profile. 2.2. Update Home Loan Customer profile. The Home Loan Customer can update the following details:

● Contact details

● Mailing details

● Employment details 2.3. Change password.

3. The system updates the Home Loan Customer profile and/or password in the system.

Alternative Courses: Invalid Format or Insufficient Information

If in the Update Home Loan Customer profile sub flow, the Home Loan Customer updates his/her profile incorrectly or incompletely the system will display an error message. The Home Loan Customer can either enter the missing information or cancel the operation, at which point the use case ends. Password MismatchIf in the Change Password sub flow, the new password and confirm new password are not the same, the system will display an error message. The Home Loan Customer can either enter the required information or cancel the operation, at which point the use case ends.




Use Case ID:

LMS-UVA08

Use Case Name: View Loan Applications

Description: This use case allows the user to view the loan applications. This includes viewing new applications, applications on hold and verified applications.

Actors: OfficerPreconditions: The Officer must be logged onto the system before this use case begins.

Post conditions: The system state is unchanged by this use case.Frequency of Use: 100 per day.Normal Course of Events: This use case starts when the Officer wishes to view the loan applications.

1. The system requests the Officer to specify the kind of application (either new applications, applications on hold or verified applications) he/she would like to view. 2. The system retrieves and displays the loan applications requested by the Officer. 3. When the Officer indicates that he/she is done viewing the applications, the use case terminates

Alternative Courses: Requested Information UnavailableIf in the Normal Course of Events, the system cannot find any loan applications, a message is displayed. Once the Officer acknowledges the message, the use case terminates.




Use Case ID:

LMS-UPA09

Use Case Name:

Process Loan Applications

Description: This use case allows the user to process loan application in the loan management system. The loan application can be forwarded, sanctioned, rejected or kept on hold. The action is recorded by changing the status of the loan application appropriately.

Actors: Officer, Manager Preconditions: The Home Loan Customer submits loan application before this use case begins.Post conditions: If the use case was successful, the status of the loan application is updated in

the system. Otherwise, the system state is unchanged.Frequency of Use: 50 per day.Normal Course of Events: This use case starts when the officer wishes to forward the loan application to

the manager or reject the loan application or put it on hold

1. The system requests the Officer to specify the function to perform(either forward, reject loan application or put it on hold)

2. Once the Officer provides the requested information, one of the sub flows is executed.

1. 2.1. Forward the loan application to Manager 2.1.1. The system requests the Manager to specify the function to perform(either sanction or reject the loan application) 2.1.2. Once the Manager provides the requested information, one of the sub flows is executed.

2.1.2.1. Sanction loan. The system generates a loan id and updates

it in the system. 2.1.2.2. Reject loan

The loan application is rejected and its status is updated in the system.

2.2 Reject the loan application

The loan application is rejected and its status is updated in the system.

1. Put the loan application on hold The loan application is put on hold and its status is updated in the system.

Alternative Courses: NoneAssociated Use case diagrams Refer LMS-Model-1.1.5.mdl (Rational Rose file).Exceptions: The following exceptions could occur:


Includes: View Loan ApplicationSpecial Requirements: NoneAssumptions: Home Loan Customer is not notified by mail. The Home Loan Customer is

expected to check his status on the web.Notes and Issues: Officer/Manager will be responsible for any issues arising out of the use case.

Use Case ID:

LMS-UMI10

Use Case Name:

Maintain Interest RateDescription: This use case allows a Manager to maintain home loan interest rates. This

includes specifying new interest rates and changing existing interest rates for various home loan schemes.

Actors: Manager

Preconditions: The Manager must be logged onto the system before this use case begins.

Post conditions: If the use case was successful, the new interest rate is updated in the system. Otherwise, the system state is unchanged.

Frequency of Use: 2 per year.

Normal Course of Events: This use case starts when a Manager wishes to specify or change interest rate for a verified loan application.

1. The Manager specifies or changes the interest rate.2. The System updates the changes implemented by the Manager.

Alternative Courses: NoneAssociated Use case diagrams Refer LMS-Model-1.1.5.mdl (Rational Rose file).Exceptions: The following exceptions could occur:


Includes: NoneSpecial Requirements: NoneAssumptions: NoneNotes and Issues: None

Use Case ID:

LMS-UVR11

Use Case Name: View Reports

Description: This use case allows the user to view the reports on Home Loan Customer details, loan sanction details, loan repayment details and the defaulter details

Actors: Officer, Manager

Preconditions: The actor must be logged onto the system before this use case begins.

Post conditions: The system state is unchanged by this use case

Frequency of Use: 100 times per day.

Normal Course of Events: This use case starts when the actor wishes to view reports related to the Loan Management system.

1. The actor requests the system for the required report.2. The system retrieves and displays the report requested

by the actor.3. When the actor indicates that he/she is done viewing the

report, the use case terminates

Alternative Courses: Requested Report Not AvailableIf in the Normal Course of Events, the system cannot find any report requested by the actor, a message is displayed. Once the actor acknowledges the message, the use case terminates.

Associated Use case diagrams Refer LMS-Model-1.1.5.mdl (Rational Rose file).

Exceptions: The following exceptions could occur: 1. Network connection failure. 2. Database connection failure.Appropriate error messages will be displayed.


Use Case ID:

LMS-ULR12

Use Case Name:

Repay Loan

Description: This use case allows the user to initiate the process of loan repayment by debiting the EMI amount from the SB account of the Home Loan Customer.

Actors: OfficerPreconditions: The Officer is logged onto the system, before this use case begins.Post conditions: If the use case was successful, the EMI amount is debited from the Home Loan

Customer’s SB account.Frequency of Use: 50 per day.Normal Course of Events: This use case starts when the Officer wishes to initiate repayment process.

1. The Officer requests the system to provide the details of the loans for which repayment process has to be executed.

2. The system gets the list of all loans that are due for repayment and starts the repayment process.

3. The system updates the SB account of the loan considered in one of the following ways:

1. The balance is sufficient, system debits the SB account towards EMI and interest payment.2. The balance is insufficient; the system calculates the penalty and updates

the information.

Alternative Courses: If in the Normal Course Of Events, if there are no loans returned by the system then the use case terminates.




Actor Responsibility Matrix

Sl No

Responsibilities Actor 1 Actor 2 Actor 3 Actor 4

1. View General Information

Visitor Home Loan Customer

Officer Manager

2. Calculate EMI Visitor Home Loan Customer

Officer Manager

3. Signup Visitor

4. Login Home Loan Customer

Officer Manager

5. Apply For Loan Home Loan Customer

6. View Loan Application Status

Home Loan Customer

7. Maintain Customer Profile

Home Loan Customer

8. View Loan Applications

Officer

9. Process Loan Applications

Officer

10. Maintain Interest Rate

Manager

11. View Reports Officer Manager

12. Repay Loan Officer

Use case diagram

Software Requirements Specification

System Perspective The system being developed is a new, self contained product, which will be integrated with the existing core banking system. It has six major modules: Signup, Login, Apply for loan, Loan application processing, Loan repayment and Reports generation.

Product Functions The system will provide the following functions:

● General information: Any Visitor to the site can view general information about the various loan schemes offered by the bank. It helps the visitors to know about the approximate EMI for any given loan amount, thus enabling them to take informed decisions.

● Signup: It allows a Bank Customer to register with the Loan Management System (LMS). Once the registration is complete, the Bank Customer becomes a Home Loan Customer.

● Login: The Login module implements role based login functionality for Home Loan Customer, Officer & Manager.

● Loan application processing: This module includes Officer responsibilities which deal with the evaluation of the loan application and forwarding the application to the Manager or rejecting it. It also includes Manager functionalities which deal with sanction/rejection of loan application.

● Loan repayment: This module handles online repayment process and

viewing repayment details by the Home Loan Customer.

● Reports generation: This module deals with generation of various reports on

customer details, loan sanction details, loan repayment details and the

defaulter details. The reports will be generated for a period with specified start

and end dates.

User Characteristics ● The user should be proficient in English language.

● The user is not required to have any technical expertise.

● The user is required to have a basic knowledge of internet.

The various user roles in the system are:Visitor: Any person who visits the bank’s web site and navigates to the Loan Management System (LMS).

Home Loan Customer: Any bank customer who registers with the LMS would become a home loan customer. Such a customer must hold an SB account with Scott Bank. Officer: An authorized employee of the bank who verifies a loan application and either forwards, rejects the loan application or puts it on hold.

Manager: An authorized employee of the bank who sanctions or rejects a loan and maintains the rate of interest.

Operating Environment Target Environment

Server Side :

Hardware : Pentium processor PC with 128 MB RAM and 10GB HDD or moreOperating system : Windows NTDatabase : Microsoft SQL ServerWeb Server : Microsoft Internet Information Server.

Client Side :Operating system : Windows 9X and above, LINUX.Hardware : Pentium processor PC with minimum 128MB RAMWeb browser : Internet Explorer 5.0 or above

Design and Implementation Constraints

● This software will be developed as an online system and will be integrated with existing online core banking system.

● Design will be done using OOAD methodology.

● The system will be developed using the naming standards of the software development.

● The naming conventions will be retained across all modules.

Assumptions ● Only Visitor, Home Loan Customer, Officer and Manager are the categories of users.

● Only the details of the last update would be stored in the database for each record.

● Every Home Loan Customer has a valid savings bank account within the bank.

● The bank employees cannot apply for a loan under this scheme.

● The bank has a Home Loan Account to which all the repayments are credited.

● The bank has unlimited bank balance from which it can sanction money to any number of customers.

User Interfaces● Login page/Home page

● EMI calculation page

● Registration page

● View profile page

● Edit profile page

● Change password page

● New loan application page

● Generating loan application id page

● View loan application status page

● View/Forward/Reject loan application page

● Sanction/Reject loan page

● View loan details page

Functional Requirements

System Features

System Feature ID:

LMS-UGI01-SF01

System Feature Name:

Display General Information

Description: This system feature allows a user to browse through the various loan schemes offered by the bank and the eligibility criteria associated with the different schemes such as age limits, total income and profession.

Classes: LMSHomePage,

LMSGeneralInformationPage

Sequence diagrams, collaboration diagrams, state transitions:

View General information

- Basic Flow

Operations: The user selects to view the information regarding the loans offered by the bank.The requested details are displayed to the user.Requirement ID

Requirement Description

REQ-1 To display the loan schemes and the associated eligibility criteria on request by the user for these pages.

System Feature ID:

LMS-UCE02-SF02


EMI Calculation

Description: This system feature allows a user to calculate the probable installment amount for a particular loan, based on the rate of interest, tenure of loan and the loan

amount.

Refer LMS-UCE02 for further details

Classes: CalculateEMIForm, EMICalculator, CalculateEMIInfo, EMIPage


Calculator EMI Sequence Diagrams

- Basic Flow

Operations: When a user clicks on EMI calculator link, the EMI calculation page is displayed to the user.This page requests the loan amount, tenure and rate of interest. If incorrect data are entered then the system displays appropriate error messages.If data are correct, system calculates the EMI and displays it to the user.

Requirement ID


REQ-1 To accept tenure, rate of interest and loan amount details.

REQ-2 To validate the details entered.

REQ-3 To calculate EMI based on the details.

REQ-4 To display the calculated EMI amount.

REQ-5 To display proper error messages when required.

System Feature ID:

LMS-USU03-SF03

System Feat

ure Name:

Signup

Description: This system feature allows a Bank Customer to register with the Loan Management System (LMS). Once the registration is complete, the Bank Customer becomes a Home Loan Customer. A customer id and password are generated and displayed to the Home Loan Customer, with which he/she can login, apply for a loan and access services offered by the system.

Refer LMS-USU03 for further details.

Classes: SignUpForm, SignUpController, LoginInfo, CustomerInfo, SignUpSuccesfulPage


Signup Sequence Diagram

- Basic Flow

Operations: Bank Customer browses through the home page and navigates to the registration form. After the Bank Customer submits the

necessary details, the system will validate the data.If the data are valid, system displays a customer id using which the user can logon to the system.Requirement ID


REQ-1 To accept the user information.

REQ-2 To validate the user information.

REQ-3 To generate a unique customer id.

REQ-4 To display proper messages when required.

System Feature ID:

LMS-URL04-SF04


Role Based Login

Description: This system feature enables a user to log onto the system.

Refer LMS-URL04 for further details.

Classes: LoginForm, LoginInfo, LoginValidator, CustomerPage, OfficerPage, ManagerPage, LoginErrorPage


Role Based Login Sequence Diagrams

- Basic Flow

Operations: The user id and password are entered in login screen.If the user id is invalid, the system will throw an error message “User Id doesn’t exist, please reenter the User Id.”If the password entered is invalid, the system will throw an error

message “password entered is wrong, please reenter the password”. If the user id and password are valid, the system will display the corresponding actor’s user interface.Requirement ID Requirement Description

REQ-1 To accept user id and password.

REQ-2 To validate the id and password entered by the user.

REQ-3 To provide access to users (Customer/Officer/Manager) with their respective interfaces.


System Feature ID:

LMS-UAL05-SF05


Apply for LoanDescription: This system

feature provides facility for the Home Loan Customer to apply for a home loan. Refer LMS-UAL05 for further details

Classes: LoanApplicationPage, LoanApplicationController, LoanApplicationInfo, LoanApplicationSuccessfulPage


Apply loan Sequence Diagrams

- Basic Flow

Operations: The Home Loan Customer enters all the necessary details in the form to apply for a loan with the system.If the details entered are valid, the loan application is submitted to the

system.If the mandatory data is not entered, appropriate error messages are displayed.Requirement ID


REQ-1 To accept the loan application details: Loan type, property value, loan amount, loan tenure, repayment mode.

REQ-2 To validate the entered details.

REQ-3 To generate loan application id.

REQ-4 To update the loan application status as ‘Applied'.


System Feature ID:

LMS-UAS06-SF06


Display Loan Application StatusDescription: This system

feature allows the Home Loan Customer to view his/her loan application status. Refer LMS-UAS06 for further details

Classes: LoanApplicationStatusPage, LoanApplicationController, LoanApplciationinfo, LoanInfo, StatusPage


Display Loan Application Status Sequence Diagrams

- Basic Flow

Operations: If no status information is available, the system will display an appropriate message. Requirement ID Requirement Description

REQ-1 To accept the “View Loan Application Status” request from the Home Loan Customer.

REQ-2 To display the set of loan applications applied by the Home Loan Customer and the corresponding status of the applications.


System Feature ID:

LMS-UMP07-SF07


View Customer Profile

Description: This system feature provides facility for the Home Loan Customer to view his/her personal details.

Refer LMS-UMP07 for further details.

Classes: CustomerProfilePage, CustomerInfo, SuccessfulPage

Sequence diagrams, collaboration diagrams, State Transitions:

View Customer Profile Sequence Diagrams: - Basic Flow

Operations: The Home Loan Customer request to view his/her profile.The system displays the profile of the user.

Requirement ID


REQ-1 To accept the request of the Home Loan Customer to view the profile.

REQ-2 To display the profile of the Home Loan Customer.


System Feature ID:

LMS-UMP07-SF08


Edit Customer Profile

Description: This system feature provides facility for the Home Loan Customer

to edit his/her personal details.




Edit Customer Profile Sequence Diagrams

- Basic Flow

Operations: The Home Loan Customer requests to edit his/her profile.The system displays the profile of the user.The Home Loan Customer edits the profile and submits it to the system. If incorrect details are entered the system displays appropriate messages.Requirement ID


REQ-1 To accept the request of the Home Loan Customer to edit the profile.

REQ-2 To display the profile of the Home Loan Customer.

REQ-3 To accept the changes made by the user and update it in the system.


System Feature ID:

LMS-UMP07-SF09


Change Password

Description: This system feature provides facility for the Home Loan

Customer to change his/her password.




Change Password Sequence Diagrams: - Basic Flow

Operations: The Home Loan Customer requests to change his/her password.The Home Loan Customer modifies the password and submits to the system.

The system validates the current password, most recent password and the old password.The changed password is updated in the system. Requirement ID


REQ-1 To accept the request of the Home Loan Customer to change the password.

REQ-2 To accept the new password.

REQ-3 To validate the current password, most recent password and the old password.

REQ-4 To update the changed password in the system.

REQ-5 To display appropriate error messages when required.

System Feature ID:

LMS-UVA08-SF10


Display New Application

Description: This system feature allows the Officer/Manager to view the new loan applications submitted by the Home Loan Customers who have applied for a loan.

Refer LMS-UVA08 for further details.

Classes: LoanApplicationcontroller,

LoanApplicationInfo, ApplicationListPage

Sequence diagrams,Collaboration diagrams,State Transitions:

View New Loan Applications Sequence Diagrams

- Basic Flow

Operations: The system will provide the Officer/Manager with the list of new loan applications, applied by the Home Loan Customers.If no new applications are available, the system will display an appropriate message. Requirement ID Requirement Description

REQ-1 To accept the “View New Loan Applications” request from the Officer/Manager.

REQ-2 To display all the new loan applications applied by the Home Loan Customers.


System Feature ID:

LMS-UVA08-SF11


Display Applications On Hold

Description: This system feature allows the Officer/Manager to view the loan applications submitted by the Home Loan Customers which have been put on hold by the Officer.

Refer LMS-UC-08 for further details.

Classes: LoanApplicationcontroller, LoanApplicationInfo, ApplicationListPage

State Transitions: View Applications On Hold Sequence Diagrams

- Basic Flow

Operations: The system will provide the Officer/Manager with the list of loan

applications that have been put on hold by the Officer.If no applications are on hold, the system will display an appropriate error message. Requirement ID Requirement Description

REQ-1 To accept the “View On Hold Loan Applications” request from the Officer/Manager.

REQ-2 To display all the loan applications those are kept on hold by the Officer.


System Feature ID:

LMS-UVA08-SF12


Display Verified Applications

Description: This system feature allows the Officer/Manager to view the loan applications submitted by the Home Loan Customers which have been verified by the Officer.

Refer LMS-UVA08 for further details.

Classes: LoanApplicationcontroller, LoanApplicationInfo, ApplicationListPage

State Transitions: View Verified Loan Applications Sequence Diagrams

- Basic Flow

Operations: The system will provide the Officer/Manager with the list of loan applications that have been verified by the Officer.If no verified applications are available, the system will display an appropriate message. Requirement ID Requirement Description

REQ-1 To accept the “View Verified Loan Applications” request from the Officer/Manager.

REQ-2 To display all the verified loan applications applied by the Home Loan Customers and verified by the Officer.


System Feature ID:

LMS-UPA09-SF13

System Feature Name: Forward/Reject/Hold Loan Applications

Description: This feature enables the Officer to view and forward/reject a loan application or to put the application on hold.

Refer LMS-UPA09 for further details

Classes: LaonApplciationDocumentsPage, LoanSanctionPage, LoanInfo, LoanApplicationInfo, LoanController, LoanApplicationController, LoanForwardedPage, LoanWithHeldPage, LoanRejectedPage, LoanSanctionedPage, LoanRejectedPage

State Transitions: Forward Loan Applications Sequence Diagram

- Basic FlowReject Loan Applications Sequence Diagrams

- Basic FlowOn Hold Loan Applications Sequence Diagrams

- Basic Flow

Operations: The Officer wishes to forward, reject a loan application or put it on hold. The Officer enters the details such as pan number, property value,The status of the loan application is updated in the system based on the operation (forward/reject/hold) performed by the Officer. Requirement ID Requirement Description

REQ-1 To accept the request of Officer to forward/reject/ a loan application or to put it on hold.

REQ-2 To accept the verified documents details required to process

the loan application such as pan number, property value,REQ-3 To update the status of the loan application in the system

based on the operation performed by the Officer.REQ-4 To display appropriate error messages when required.

System Feature ID:

LMS-UPA09-SF14


Sanction/Reject Loan ApplicationsDescription: This system

feature enables the Manager to view and sanction/reject a loan application verified by the Officer.Refer LMS-UPA09 for further details

Classes: LaonApplicationDocumentsPage, LoanSanctionPage, LoanInfo, LoanApplicationInfo, LoanController, LoanApplicationController, LoanForwardedPage, LoanWithHeldPage, LoanRejectedPage, LoanSanctionedPage,

State Transitions: Sanction Loan Applications Sequence Diagrams

- Basic Flow Reject Loan Applications Sequence Diagrams - Basic Flow

Operations: The Manager wishes to sanction, reject a loan application verified by the Officer. The Manager updates the loan application details such as the loan amount and the loan tenure.The status of the loan application is updated in the system based on the operation (sanction/reject) performed by the Manager. Requirement ID Requirement Description

REQ-1 To accept the request of Manager to sanction/reject a loan application verified by the Officer.

REQ-2 To accept the loan sanctioning details required to process the loan application such as the loan amount and loan tenure.

REQ-3 To update the status of the loan application in the system based on the operation performed by the Manager.


Traceability matrix

Traceability Table ● Traceability of System Features to User Requirements (System Feature ID to Use Case IDs.)

System Feature ID Use Case IdLMS-UGI01-SF01 LMS-UGI01LMS-UCE02-SF02 LMS-UCE02LMS-USU03-SF03 LMS-USU03LMS-URL04-SF04 LMS-URL04LMS-UAL05-SF05 LMS-UAL05LMS-UAS06-SF06 LMS-UAS06LMS-UMP07-SF07 LMS-UMP07

LMS-UMP07-SF08

LMS-UMP07-SF09LMS-UVA08-SF10 LMS-UVA08

LMS-UVA08-SF11

LMS-UVA08-SF12LMS-UPA09-SF13 LMS-UPA09

LMS-UPA09-SF13

Nonfunctional Requirements

Performance Requirements

● The system will be required to undergo testing by operational staff of the Scott bank before being used.

● The system should operate acceptably in the hardware and software configurations where the system is operational. (Refer Operating Environment(Page 7 of this document)

● 50 users can logon to the system at a time.

Safety Requirements This application can not cause any harm/damage/loss of data to the user.

Security Requirements ● The direct access to database is strictly controlled. COMPANY will not be responsible for malfunctioning of the application in case database structures are modified at the customer end.

● Any data which is not entered through the application will not be validated and may cause erroneous results

● Access to the system is authorized to 3 persons (Home Loan Customer, Officer, and Manager) only.

Software Quality Attributes

● This software is made in accordance with the COMPANY Quality.

● The classes developed as part of the application may be used in other similar projects esp. classes like Login, EMICalculator etc.

● This software also provides the capability to integrate with any other components in future.

Business Rules ● For details of functions which can be performed by different roles (user groups) refer User Characteristics.

Sequence Diagrams

1. View Eligibility Sequence Diagram

- Basic Flow

Visitor/Officer/Manager : UserhomePage : LMSHomePagegeneralPage : LMSGeneralInformationPage// User selects 'View General Information' linkDisplay()

2. View EMI Calculator Sequence Diagrams

- Basic Flow

3. Signup Sequence Diagrams

- Basic Flow

4. Role Based Login Sequence Diagrams

● Basic Flow

5. Apply For Loan Sequence Diagrams

● Basic Flow

6. Display Loan Application Status Sequence Diagrams

● Basic Flow

7. View Profile Sequence Diagrams

● Basic Flow

Viewprofilepage : customerCustomerprofile formcustomerprofilecontrollercustomerinfopress viewview profileview informationdisplay successful page

8. Edit Profile Sequence Diagrams

● Basic Flow

9. Change Password Sequence Diagrams

● Basic Flow

successfulpage : customercustomerprofileformcustomerprofilecontroller

customerinfoEnter new password press updateupdate passwordcheck for validityupdate informationdisplay successful page

10. View New Loan Applications Sequence Diagrams

● Basic Flow

11. View OnHold Loan Applications Sequence Diagrams

● Basic Flow

: officerapplicationcontrollerapplciationinfoapplicationlistpageget all OnHold applicationsget all applciations with status as on holddisplay applications list

12. View Verified Loan Applications Sequence Diagrams

● Basic Flow

: officerapplicationcontrollerapplciationinfoapplicationlistpageget all verified applicationsget all applciations with status as verifieddisplay applications list

13. Forward Loan Applications Sequence Diagrams

● Basic Flow

14. On Hold Loan Applications Sequence Diagrams

● Basic Flow

15. Reject Loan Applications Sequence Diagrams

● Basic Flow

15. Sanction Loan Applications Sequence Diagram

● Basic Flow

16. Reject Loan Applications Sequence Diagram

● Basic Flow

Note: E-R Diagram (Under construction, will be reviewed and replaced)

Date of EMIPending amount

RegidO_id

O_NameSanctionsEmailId

Rate of interestReg Id

LoanIdVerifies

OfficerEmp IdNameDOBCheckStatusForwards

Loan

Employee

LoanApplicationApply

Loan id

EMI StatusLoan schemeDuration

Date of Application

PaymentLoan amount

mLoan application ID

1

Checked by

Address

Visitor 1 m

Contact ENameEmailId

Regid

m 11

DesignationName

Is a

Customer

1 m1 m

1

ManagerDOB

Loan Status

EmaiId

Name

Midm 1

Design Element

Design Element ID:

LMS-UAL05 SF05-DE04

Design Element Name:

Apply loanDescription:Note: A bookmark may be introduced here to hyperlink from the corresponding modeling element generated using Rational Rose.

This design element allows the Home Loan Customer to apply for a loan. It captures all loan application related information. This design element also contains the information to generate a loan application id.

For detailed information on this design element look at the design level sequence diagrams.

For more information on this refer to the LMS- UAL05-SF05 of the LMS-SRS.

Classes: <<aspx>>

LMSLoanApplicationPage (UI)<<cs>> LMSLoanApplication (BL)<<cs>> LMSLoanApplicationDA (DA)<<cs>> SqlHelper (DAAB)<<aspx>>

LMSLoanApplicationSuccessPage (UI)<<aspx>>

LMSLoanApplicationErrorPage (UI)

Method Specifications: ● LMSLoanApplicationPage.aspx: This

is an ASPX page inherited from ‘LMSPageBase’ class. This page captures information about loan application like the loan amount, loan tenure, property value, loan type, repayment mode. This page contains a SubmitButton click event which instantiates the Business Logic layer class LMSLoanApplication.cs to pass on the application details to the corresponding method in the LMSLoanApplication.cs class. The event is as follows:

1.

This ev

ent passes the loan application specific inputs provided by the Home Loan Customer to the LMSLoanApplication.cs class in the Business Logic layer.

● LMSLoanApplication: This is a class

in the Business Logic layer, which implements all the loan application related functionalities such as submission of loan application by the Home Loan Customer and viewing of loan applications by the Officer and Manager. This will pass on the application specific details to a corresponding method in the LMSLoanApplicationDA.cs class after performing business rules check, if any. The method

specification in the class, corresponding to this design element is:

1. public int SubmitApplication(int loginId, string loanType, float propertyValue, float loanAmount, float tenure,

string repaymentMode)

● LMSLoanApplicationDA: This is a class in the Data Access layer, required to implement all the loan application related functionalities such as submission of loan application by the Home Loan

Customer and viewing of loan applications by the Officer and Manager and to communicate with the DAAB for database operations. A method in this class calls an appropriate overloaded method in the SqlHelper.cs class for all the database operations. The method specification in the class, corresponding to this design element is:

1.

string loanType, float propertyValue, float lo

anAmount,

float tenure, string repaymentMode)

This method calls the ‘ExecuteNonQuery’ method in the SQLHelper class to execute a stored procedure to insert the loan application in to the database.

● SQLHelper.cs: This is a part of the DAAB. The DAAB consists of a single .NET-based assembly, which contains all of the functionality necessary to perform the most common data access tasks against a Microsoft SQL

Server 2000 database and hence reduces the amount of custom code one needs to write. The SqlHelper class is intended to encapsulate high performance, scalable best practices for common uses of SqlClient. The method in the class, corresponding to this design element is:

1.

connectionString, string spName,

params object []

parameterValues)

This method executes a command that does not return any rows. This method will thus execute a stored procedure to insert the loan application details submitted by the Home Loan Customer.

● LMSLoanApplicationSuccessPage.aspx: This is an ASPX page inherited from ‘LMSPageBase’ class. This is displayed when the loan application submission process is successful.

● LMSLoanApplicationErrorPage: This is an

ASPX page inherited from ‘LMSPageBase’ class. This is displayed when the loan application submission process fails due to the database connection failure.

Class Diagram

System Test Cases

LMS-UTC 01: This test case checks the View General Information functionality.

Observed Behavior *

S.No

Data Input Expected Behavior Run 1 Run 2 Run 3

(P/F) H/M/L (P/F) H/M/L (P/F) H/M/L

1. Home Loan Schemes link in the LMSHomePageCategories is clicked.

LMSHomeLoanSchemesPage is displayed.

2. Home Loan Schemes link in the LMSHomePageCategories is clicked.

If any exception occurs, LMSErrorPage is displayed.

3. Eligibility Schemes link in the LMSHomePageCategories is clicked.

LMSEligibilityPage is displayed.

4. Eligibility Schemes link in the LMSHomePageCategories is clicked.


5. EMI Calculator link in the LMSHomePageCategories is clicked.

LMSEMICalculatorPage is displayed.

6. EMI Calculator link in the LMSHomePageCategories is clicked.


LMS-UTC 02: This test case checks the Signup functionality.

Observed

Behavior *

S.No



1. New User Signup link in the LMSHomePage is clicked

LMSSignUpPage is displayed.

2. All the required fields in the LMSSignUpPage are filled in and the Submit button is clicked

SignUpSuccessFullPage is displayed with the system generated CustomerId.

3. The required fields are not filled in and the Create Account button is clicked.

Appropriate error messages are displayed.

4. All the required fields in LMSSignUpPage are filled in and the Create Account button is clicked.


LMS-UTC 03: This test case checks the Login functionality.

Observed Behavior *

S.No



7. User Id and Password are not entered and Submit button is clicked.

LMSLoginErrorPage is displayed.

8. Valid User Id and Password are entered and Submit button is clicked.

The home page for the corresponding user is displayed.

9. Invalid User Id and Password are entered and Submit button is clicked.

LMSLoginErrorPage is displayed.

10. Valid User Id and Password are entered and Submit button is clicked.


*: P - Expected and observed behavior are same. F - Expected and observed behavior are different. This is classified as a defect. H - High severity defect (System crash / Incorrect data which impacts other regions / etc.) M - Medium severity defect (Execution can continue / Incorrect data which does not impact other regions / etc.) L - Low severity defect (Aesthetics / Message wording / Menu options / Wrong alarms / Help problems / etc.)

UI Screens

Under Construction and review