Loan management system

User Requirements Document

Version 1.0
Version History
Version Date Changes Made Done By Remarks
No

Introduction
This section mainly briefs about who is the customer and what is customer business and the
problems customer is facing in the existing business. It also gives information on business aspects
considered for automation, goals of the project.

Target audience
List the target audience meant for this document

About Customer
Provide details about the customer business and the problems customer is experiencing in the
existing business, which led him for going for this automation project.

Project Objectives
Provide details about goals of the project or things to be achieved by implementing this project in
customer business.

Scope
Identify the areas considered for automation in customer business as part of this project and areas
not considered.

Definitions
Term Definition
ATM Automatic Teller Machine

References
Provide information about documents, discussions, telecons and standards referred in creating this
requirements document

Assumptions
List the assumptions taken while preparing this requirements document

Environment
This section provides information about environment required to implement and operate this
application. It also identifies the minimum knowledge required for the users to operate the software
created as part of this project
Implementation environment

Hardware Environment
Identify the configuration of server required to host this application, in terms of processor capacity,
RAM, LAN card speed, Router, HDD capacity.....

Software Environment
Identify the software required to implement the application developed in terms of operating system,
front end, browsers, drivers, database….

User characteristics
List the minimum knowledge and skill the users need to have to operate this application

Constraints of the customers

List the conditions of the customer for accepting this application.

Functional Requirements
This section will list all the functional requirements of the application being developed and their
operating specification

Requirements lookup table

S.No Requirement Requirement Source Stable Priorit Need Verifiable(y
ID Name (customer/vendor) (Y/N) y /n)

1 TRS-Us-01 registration user y high Essential y

2 TRS-US-02 Search movie user y high Essential y
3 TRS-US-03 Choose theatre user y high Essential y

4 TRS-US-04 Book ticket user y high Essential y

5 TRS-US-05 Ticket cancelled admin y high Essential y

6 TRS-UR06 Manage admin y high Essential Y

theatres
7 TRS-US-07 Manage movies admin y high Essential Y

8 TRS-US-08 View admin Y high Essential Y

reservation
reports

Requirement description

Requirement ID TRS-US-01
Title Registration
Description The purpose of this use case is providing registration for the
customer
Actor Customer
Input Name, search movie,bookticket
Behavior • store all the details in application
• generate id and password
Output Ticket booked or ticket cancelled
Pre condition NA
Post condition Email id and password to the customer
SMS id and password to the customer
Exceptions if there is any problem in storing details or generating id and
password display error message
Use case diagram

Registration
customer

Special instructions  seat number should be given

Requirement ID TRS-US-02
Title Search movie
Description The purpose of this use case is providing information about
theatre
Actor User
Input Choose theatre
Behavior • retrieve the details from the application
• display to the user
Output K search found
Pre condition NA
Post condition NA
Exceptions If there is any problem in retrieving information ,he can say
directly
Use case diagram

Issue the ticket

Ticket
issuer
Special instructions NA

Requirement ID TRS-US-03
Title Book ticket
Description The purpose of this use case is applying for the loan
Actor Customer
Input Book ticket
Behavior • store the details in application
• generate application id
Output Received or cancelled
Pre condition customer should be logged in
Post condition information to the customer
Exceptions If there is a problem in storing information or generating
application id he can say directly
Use case diagram

Takes the ticket

customer

Special instructions The format for generating application id is

<book ticket>
Requirement ID TRS-US-04
Title Trs
Description The purpose of this use case is processing the loan application
Actor officer
Input Cancel ticket
Behavior • retrieve the details from the application
• officer verifies the details
• forwards it to manager if the details are approved
• Manager verifies the details
• approves or rejects loan
Output acknowledgement message
Pre condition officer and manager should be logged in
Post condition SMS and email whether the loan is accepted or not
Exceptions If there is a problem in retrieving information display error
message
Use case diagram

process ticket
officer

Special instructions NA

Requirement ID TRS-TS-05
Title Trs
Description The purpose of this use case is managing interest rate
Actor Manage theatre
Input loan id ,new interest rate, effective date
Behavior • retrieve the interest rate from the application
• modify the interest rate, effective date
• on confirmation update the details

Output Search found

Pre condition manager should be logged in
Post condition Email and SMS new interest rate and the effective date to the
customer

Exceptions if there is any problem in retrieving details or updating details

display error message
Use case diagram

manage loans
manager

Special instructions NA

Requirement ID TRS-US-06
Title manage loans
Description The purpose of this use case is managing the loans
Actor manager
Input loan id, loan name, loan information, loan type
Behavior if loan creation
• store all the details in application
• generate loan id
if loan modification
• retrieve the details of the loan
• modify the details
• on confirmation update the details
if loan deletion
• retrieve the details of the loan
• on confirmation delete the loan
if view details
• retrieve the details of the loan
• view the details
Output acknowledgement message
Pre condition manager should be logged in
Post condition NA
Exceptions if there is any problem in processing display error message
Use case diagram

manage loans
manager

Special instructions NA

Requirement ID TRS-US-07
Title Trs
Description The purpose of this use case is managing the loan types
information
Actor manager
Input Manage movies
Behavior if loan type creation
• store all the details in application
• generate loan type id
if loan type modification
• retrieve the details of the loan type
• modify the details
• on confirmation update the details
if loan type deletion
• retrieve the details of the loan type
• on confirmation delete the loan type
if view details
• retrieve the details of the loan type
• view the details
Output Search found
Pre condition manager should be logged in
Post condition NA
Exceptions if there is any problem in processing display error message
Use case diagram

manage loan types

manager

Special instructions NA

Requirement ID TRS-US-08
Title Trs
Description The purpose of this use case is generating reports
Actor Officer
Input View yes reports
Behavior • retrieve all the loans taken by the customer
• generate reports
Output reports
Pre condition officer should be logged in
Post condition Email reports to the customer
Exceptions if there is any problem in retrieving details display error message
Use case diagram

generate reports
officer

Special instructions NA