Name: Harish Singh

ID NO: 171080095

SUBJECT: SOFTWARE ANALYSIS

AND DESIGN.

BRANCH: Information technology

ASSIGNMENT NO: 4

LOAN MANAGEMENT SYSTEM

 LOAN MANAGEMENT SYSTEM

USE CASE DIAGRAM:

Following are the Use case Specifications and respective diagrams for
each use case:
1. Registration of
Customer Use
case
Specifications:
1.1. Description :- Register to theSystem.
1.2. Actor :-
Customer.
1.3.Precondition
:- None.
1.4.Basic Flow
Of Event:-

Actor System
1.Click on register button
2. Display Registration Screen

3.Enter name,address,salary,KYC,

Phone no,email id,password.

4.Search data in database.
5.Stores data in database.
6.Redirect to Home page.

1.5. Alternate Flow Of Event:

Actor System
3.1 Invalid Data Entry 3.1.1 Error message takes it back to
Step 3.
 4.1 Email Address Exist 4.1.1 Error message user already
exist and exit.

1.6. Post Condition :- AccountCreated.

1.7. Special Cases :- Response Time is Less than2s.

1.8. Frequency of Usage :- High Frequency and hence thoroughly testedand

implemented.

Activity Diagram:
Sequence Diagram:

State Machine Diagram:

Class Diagram:
2. Login
Use case Specifications:

2.1. Description : This use case let’s the user log into the theiraccount.

2.2.Actor :User

2.3. PreCondition:InternetConnectionshouldbeavailableandthe
user must have registeredbefore.

2.4.Control Flow:

1) BASICFLOW

ACTOR SYSTEM

1.Actor clicks on Login

button

2.System displays Login

screen to actor.

3.Actor enters username and

password and clicks ‘OK’

4.System searches given

username in database and
retrieve actor’s password.

5.System compares the

password and authenticates
the actor.
 6.System displays ‘Login
Successful’ message and
navigate to actor’s page.

2) ALTERNATEFLOW

ACTOR SYSTEM

3.1 Actor enters invalid 3.1.1 System shows error

username/password. and redirects to step 3 in the
basic flow (Three times and
exits use case

4.1 Username not available

in database.

4.1.1 System displays error

‘Invalid User’ ,exits use
case.

5.1 Invalid Password 5.1.1 System displays error

‘Invalid Password’ and
redirect to step 3 and exits
the usecase.

2.5. Post Condition : User gets logged into the system if

theentered credentials werecorrect

2.6. Special Specifications:

- Response Time : Should not be less than 3seconds.

 - Throughput : Concurrent 100 transactionsrequired.

2.7.Other Specifications:

-Frequency Of Usage is high so the component needs to be

developed properly and tested with 100% accuracy.

- Complexity : Medium.

Activity Diagram:
 Sequence
Diagram:

State Machine
Diagram:
Class Diagram:
3.Apply for Loan
Use case Specifications:

3.1 Description – Actor can apply forloan.

3.2 Actors –Customer

3.3 Pre-Condition – Customer must be successfully logged into thesystem.

3.4 Basic Flow ofinteraction–

Actor System

1 Actor will click on apply for

loan

2 System displays apply for loan page

and requests type of loan

3 Selects type of loan. Clicks

next.

4 Processes input and requests amount

of loan

5 Inputs amount. Clicks next.

6 Processes input and displays the

various repayment schedule options

7 Selects feasible repayment

schedule and clicks next
 8 Processes input and displays all
entered details and request user/
actor for confirmation

9 Clicks on confirm button

System displays confirmation

message “Applied for loan”

3.5 Alternate or Exceptional flow–

Actor System

1 User clicks on edit button System redirects to step (2) basic

flow

3.6 Post-condition – Redirects to Uploaddocuments

3.7 Special Conditions–

Response time must be less than 3 seconds.

Concurrent 100 processes can be performed

3.8 Other Specifications

– Frequency of

usage:Moderate

Complexity:Easy
Activity Diagram:
Sequence Diagram:

State Machine Diagram : Not Applicable.

Class Diagram:
6. CalculateEMI

Use case Specifications:

6.1 Description – For calculation of EMI according to loan type andperiod

6.2 Actors –Customer
6.3 Pre-Condition – Customer must be loggedin
6.4 Basic Flow ofinteraction–
Actor System
1 Clicks on calculate EMI
2 Generates input screen for loan type
and period
3 User inputs loan type and period

4 Checks validity of input

5 Fetches interest rates from database

6 Calculates EMI
7 Displays calculated EMI

6.5 Alternate or Exceptional flow–

Actor System

3.1 User inputs invalid loan Display invalid loan type or period, redirect
type or period to point 3 in basic flow

6.6 Post-condition – Redirects to apply forloan

6.7 Special Conditions–

 Response time must be less than 2 seconds.

6.8 Other Specifications

– Frequency of
usage:Moderate
Complexity:Easy

Activity Diagram:
Sequence Diagram:
Class Diagram:
7. EMIPAYMENT
Use case Specifications:

7.1 Description–
ForpayingmonthlyEMIofloantakenbyECSmodeorby depositing a
post-datedcheque.

7.2 Actors –Customer

7.3 Pre-Condition–
EMIshouldalreadyhavebeencalculatedandcustomer should be
loggedin.

7.4 Basic Flow ofinteraction–

Actor System
1 User clicks on EMI payment
button.
2 Displays payment due(EMI + penalty,
if any) and input screen for selecting
between “ECS mode” and “post-dated
cheque”
3 User chooses the type of mode.

4 System navigates user to another

website.
5 User clicks on pay EMI button.

6 Displays message: Payment done

successfully.
7.5 Alternate or Exceptional flow–

Actor System

4.1 Poor network Display poor connectivity, redirect to point 2

connectivity during in Basic Flow
payment
5.1 EMI Payment is not done System calculates penalty and displays
within 15 days. message: Pay EMI and penalty within next 10
days

7.6 Post-condition – Payment done isrecorded.

7.7 SpecialConditions–
IfbydoingtheEMIpayment,thecompleteloanispaid off, close the loan
account and give back the mortgagedocuments.

7.8 Other Specifications–

Frequency of usage: High
Complexity: Hard as payment completion is a difficult process.
Activity Diagram:
Sequence Diagram:
Class Diagram:
8. CUSTOMER

REPORT Use

caseSpecification

s:

8.1 Description:Thisusecasehelpstheusertodownloadandviewcusto
mer reports

8.2 Actors:Customer

8.3 Pre-
Conditions:Theusermustbeloggedintothesystemandthereshouldbe
an active internetconnection.

8.4 Basic flow ofInteractions:

Actor System
1.User clicks on the “Get Reports”
button.
2.System displays a list of all the possible
reports that can be generated
A. Paymentreport
B. Income TaxReport
3.User clicks on the desired option.
4.System generates the report and
displays it on the screen with a
“Download” button.
5.User clicks on the “Download”
button.
6.System opens the file manager and asks
for the location.
7.User selects the location and clicks
on the “OK” button.
8.System downloads the file on the
computer and displays the home page.

8.5 Alternate flow ofinteractions:

Actor System
5.1. User clicks on the “Back” button. 5.1.1. Join step 2 in basic flow.
4.1. Database connectivity is lost
4.1.1 System will display message
“Database error occurred”.
4.1.2. System exits the use-case
8.1. Internet connectivity is lost
8.1.1 System will display message
“Internet connectivity lost”.
8.1.2. Join step 4 in basic flow
8.2. There is insufficient storage.
8.2.1 System will display message
“Insufficient storage”.
8.2.2. Join step 4 in basic flow

8.6 Post Conditions: The user has successfully downloaded or viewedreports

8.7 SpecialConditions:
1. The system should respond to the user within 2 seconds of therequest.
2. At the same time 100 users can access the use casesimultaneously.

8.8 OtherSpecifications:
 ● Frequency:Moderate
● Complexity:Simple
Activity Diagram:
Sequence Diagram:
State Machine Diagram:
Class Diagram:
9.Part Payment

of Loan Use

caseSpecificat

ions:

1.1 Use-CaseDescription:
The use case is used for part payment of the applicant’s loan.

1.2 Actors:
Applicant

1.3 Pre-condition
1. The loan should beapproved.
2. The user must be loggedin.
3. User must have an unpaidloan.

1.4 Basic Flow ofInteraction:

Actor System
1.Clicks on Part Payment
option.

2.Displays Part Payment page.

3. Selects amount to be
paid
4. Check if applicant has sufficient bankbalance
to pay givenamount.

5. The transaction is successfully carriedout.

6. Display success message alongwith
outstanding loanamount.

7. Click on ‘Done’ button

1.5 Alternative or Exception Flow ofInteraction:

4.1 User does not have sufficient balance to pay theamount:

4.1.1 Display Insufficient Balance message, go back to previousscreen.
4.2 Amount selected is greater than outstanding loanamount:
4.2.1 Display Amount Invalid message and go back to previousscreen.
5.1 Transaction failure:
5.1.2 Display Transaction Failed message and go back toprevious
screen.

1.6 PostCondition
1. System displays message of success orfailure
2. ApplicantselectsbetweenreducingEMIamountorreducingrepay
ment period.

1.7 SpecialConditions:
1. The response time should be less than10sec.
2. The transactions should beconcurrent

1.8 OtherSpec
ification:
Complexity-
Low
Frequency-
Moderate
Activity Diagram:
Sequence Diagram:
State Machine Diagram:

Class Diagram:
10. Disburse Loan

Use case Specifications:

10.1 Use-
CaseDescription:Theusecaseisusedtodisburseloantoloan
applicant’saccount

10.2 Actors:BankOfficer

10.3 Pre-condition:The loan should beapproved

10.4 Basic Flow ofInteraction:

Bank Officer System

1.Clicks on Disburse Loan 2.Displays Loan Id page

3.Enters Loan Id 4.Fetch details of

applicant and loan

5.Clicks on Proceed Loan 6.Transfers money to

loan applicant’s account

10.5 Alternative or Exception Flow ofInteraction:

Bank Officer System

5.Clicks on Cancel Payment button 6.Payment process is

cancelled and is
 redirected to loan ID
page

10.6 Post Condition:System displays message of success orfailure

10.7 Special Conditions:The response time should be less than10sec.

10.8 OtherSpec

ification:

Complexity-

Low Frequency-

Moderate

ActivityDiagra

m:
Sequence Diagram:

State Machine Diagram:

Class Diagram:
11. CloseLoan

Use case Specifications:

11.1 Description – It is used for closing an OpenLoan.

11. 2 Actors – Admin

11.3 Pre-Condition – The admin should be logged in to thesystem.

11.4 Basic Flow ofInteraction–

Actor System
1. Actor clicks on Close Loan 2. System displays the user details
button. form.
3. Actor enters the user details and 4.1 System checks the details.
clicks on Check details.
4.2 System checks if all EMIs are
paid.
4.3 System closes the loan.

11. 5Alternate or Exceptional Flow–

Actor System

Invalid user. System redirects to the user login

page.
Improper user details entered. System redirects to the user details
page.
All EMIs are not paid. System prints this message and
redirects to the homepage.

11.6 Post-Condition–
Theloanisclosedandthehomepageisdisplayedtothe actor.
11.7 SpecialConditions–
TheresponsetimefortheSystemtocheckdetailsand EMI should not
exceed 3minutes.

11.8 OtherSpecifications–
Theloanholder(user)shouldcontacttheadminfor closing the loan.
Without the intervention of the admin, an user cannot close
his/herloan.

Activity Diagram:
Sequence Diagram:

State Machine Diagram:

Class Diagram:
12. Change InterestRate
Use case Specifications:

12.1. Use Case Description:

The interest rate on our loan can change due to some regulatory
changes in government policy or bank policy. Then, the bank can
use this option to change interest rate. The bank employee will
enter the new interest rate, if that interest rate is valid, then it will
be updated in the database and displayed to user. Otherwise, the
error message will be displayed.

12.2 Actor : Bankemployee.

12.3 Pre-Condition:
The employee of bank should be logged in and should have proper internet
connection.

12.4 Basic Flow ofInteraction

Actor System
4.1) The user clicks on change interest
rate button ( CIR button ) .
4.2) System will display the Change
interest rate screen.
4.3) The user will enter new interest
rate and clicks on the submit button.
4.4) System validates the new interest
rate given by the user. If the new interest
rate is valid, then it is stored in the
databse.
4.5) System will display the new
updated interest rate to the user.
12.5 Alternate Flow ofCondition:

Actor System
5.1) The user enters invalid new interest
rate in the change interest rate column or
leaves that column empty.
5.2) System redirects the user to step 4.3
of the basic flow.
5.1) Database connectivity is lost.
5.1.1)System will display message
“Database error occurred.”
5.1.2)System redirects to step 4.3 of basic
flow.
5.1) Internet connectivity is lost.
5.1.1) System will display message
“internet connectivity is lost.
5.1.2) System redirects to step 4.3 of
basic flow.

12.6 Post-Condition:
The user has successfully changed the interest rate.

12.7 Special Condition:

Number of concurrent users : Only single user must access the use
case at that time.

12.8 Others Specification:none.

Activity Diagram:
Sequence Diagram:

State Machine Diagram:

Class Diagram:
PACKAGING AND LAYERING DIAGRAM: