Description
SRS document of LOS
Indian Institute of Information Technology & Management
Software Requirements Specification
For
Version 1.0 approved Prepared by Arti Omar (IPG_2008108) ABV-IIITM 1-11-2011
Software Requirements Specification for
Page ii
Table of Contents
1. Introduction................................................................................................................................1
1.1Purpose ................................................................................................................................................ 1 1.2Intended Audience and Reading Suggestions...................................................................................... 1 1.3Project Scope........................................................................................................................................ 1 Product scope focus on the following component: client, server, and database......................................1 1. 4 References....................................................................................................................................... 2
2. Overall Description....................................................................................................................3
2.1 Product Perspective......................................................................................................................... 2.2 Product Features............................................................................................................................. 2.3Access Control (CRUD Matrix).......................................................................................................... 2.4Operating Environment........................................................................................................................ 2.4.4Assumptions and Dependencies....................................................................................................... 3 3 4 5 6
3. UML Diagrams...........................................................................................................................7
3.1Activity Diagram.................................................................................................................................. 7 3.2Class Diagrams.................................................................................................................................... 9 3.3 State Chart Diagrams................................................................................................................... 10 3.4Sequence Diagrams............................................................................................................................ 11 3.5Collaboration Diagrams..................................................................................................................... 12 3.6Component Diagrams........................................................................................................................ 13 3.7Deployment Diagrams....................................................................................................................... 14
4 External Interface Requirements............................................................................... 15 4.1 User Interfaces....................................................................................................................... 15
5Other Nonfunctional Requirements...................................................................................................... 5.1 Performance Requirements.............................................................................................................. 5.2Safety Requirements.......................................................................................................................... 5.3Security Requirements....................................................................................................................... 16 16 16 17
6 Other Requirements................................................................................................................. 18
Revision History
Name N/A N/A Date N/A N/A Reason For Changes N/A N/A Version N/A N/A
Software Requirement Specification for of 20
Page ii
Indian Institute of Information Technology & Management
1.
1.1
Introduction
Purpose
Proposed Software Requirement document is for Loan Originating System. Approved version of SRS is 1.0. Loan Originating System is the system will be used to originate consumer loans in IIITM campus. 1.1.1 The product shall provide a platform upon which multiple users can fill online form, multiple data entry operator can update information and multiple users can track their loan information and create account. 1.1.2 This Software Requirements Specification document shall be intended for internal developer reference. 1.1.3 Credit rating support system -Process for accessing credit rating ratings from CIBIL data base 1.1.4 server 1.1.5 Server – the application that manages customer statistics 1.1.6 Keep-Alive Time Interval – the maximum amount of time negotiated at client authentication that may pass without communication between a client and its server before the server begins transmitting the ping message. Client – the end-user application necessary for interacting with the main loan data base
1.2
Intended Audience and Reading Suggestions
TBD
1.3
Project Scope
Product scope focus on the following component: client, server, and database. 1.3.1 loan feedback. 1.3.2 Server shall communicate with client the client application to provide updates, form provide guidelines for filling the form, For scanning and saving documents, for LAN generation and assignment and Re assignment of LAN if incase user has missed his LAN. The client application shall provide the user with an interactive interface for accessing application form, for entering loan information, for tracking loan status, for loan process
1.3.3 Product shall provide web-based loan originating environment.
Software Requirement Specification for 20 Page 1 of
Indian Institute of Information Technology & Management
1.3.4 Web forms filled out and saved by the applicant on the web site, that are then sent to or retrieved by (ostensibly securely) the financial institution 1.3.5 True web applications with interfaces to a loan origination system on the back end. Many of the early solutions had a lot of the same problems as general forms (bad work flows, trying to handle all manner of loan types in one form) 1.3.6 Wizard-style applications that are very intuitive and don't ask superfluous questions. 1.3.7 Product shall classify type of loan products with attached interest rate information. 1.3.8 Product shall update all information after each step from end user point of view. 1.3.9 Product should notify all the errors and relevant guidelines for that. 1.3.10 Product shall fulfill current security requirement (Multi-factor authentication). 1.3.11 Get current credit-report. 1.3.12 Prequalify (auto-decision) the application and return a quick response to the applicant
1. 4
N/A
References
Software Requirement Specification for 20
Page 2 of
Indian Institute of Information Technology & Management
2. Overall Description
This SRS contains all of the requirements needed to implement this system and its dependencies. This document shall be formatted so that requirements are prioritized by system components.
2.1
Product Perspective
2.1.1. The product shall be fully independent and self-contained.
2.2
Product Features
2.2.1. This product shall, at a minimum, operate using the following three components. Extensibility to these components as well as additional components not listed here will be allowed: 2.2.1.1. Client application: • • • • • • The client shall display the status of loan, and send the server commands. It will display loan application form at customer end. It will provide LAN and other user guidelines to fill the application form. It will display updated loan information regarding type of new loan product, new interest schemes, etc. It will provide a good interface between customer and server. It will provide search option on screen so that a user can search the loan product with appropriate key wards and get all the information regarding the product. Client application will support communication protocol between client and server application. 2.2.1.2. Server application: • • • • • • The server shall process all of the logics and rules. It will support communication protocol among client application and data base application. It will automatically filter all the redundant information. It will quickly response to customer queries. It will update all the loan information in loan account. It will update the status flag of loan status.
Page 3 of
Software Requirement Specification for 20
Indian Institute of Information Technology & Management
• • • • • •
It will discard irrelevant client message which is not define under communication protocol. It will automatically generate random loan ID (LAN) to customer after submitting and scanning correct loan information. It will save the customer documents in the data base and run them when they will be called. It will send request for credit rating save the result. It will run the bank admin queries and configured the loan applications accordingly. It will process risk evaluation rules. 2.2.1.3. Database application: The database shall store
• • • • • • • • • • • • • •
Consumer loan application information, Loan documents, Login information, Consumer record, Loan information, Product type, Product updates, Loan interest type information, Lenders information, Loan assignment information And credit rating score. Easy interaction with server application and client application. Support server queries. Support key wards also to run queries.
2.3
Access Control (CRUD Matrix)
Entity Process Customer Data Entry Operator Bank Administrator Lenders Underwriter CIBIL
Software Requirement Specification for 20
Page 4 of
Indian Institute of Information Technology & Management
Fill loan application
CRU
R
R
R
R
Receive loan application Process loan application Configure loan application Verify loan application Process of risk evaluation Maintain loan account Maintain loan Product Loan reporting process Loan assignment report process Terminate loan application Credit Score Checking Loan status
R CRU C R R R
R R R R R -
R R CRU R R RU CRU R CU D R CRU
R R CRU R R R CUR R R RU
R R R CRU U R UR D R CUR CUR -
2.4
Operating Environment
2.4.1 Hardware Interfaces Hardware Interfaces shall be left to the user to acquire (i.e. Internet Access, Server, etc.)
2.4.2 Software Interfaces 2.4.2.1 2.4.2.2 2.4.2.3 2.4.2.4 2.4.2.5 2.4.2.3 Developers shall use SQL for the database. Developers shall use Google Code for tracking development, files, and bugs. Server software shall run on Windows OS (Version XP or later) as a service. The client application shall run on Windows OS (Version XP or later). The client application may also support platforms other than windows. Application shall check for updates on the server as initiated.
2.4.3 Communication Interfaces
Software Requirement Specification for 20 Page 5 of
Indian Institute of Information Technology & Management
2.4.3.1 2.4.3.2 2.4.3.3
XML shall be used to communicate message between the server and client The server will directly communicate with the database. Client/Server message shall be defined by the system communication protocol.
application.
2.4.4
Assumptions and Dependencies
At this phase there are no known system constraints. Only system shall be constraints by hardware compatibilities. 2.4.4.1 • • • • Dependencies This product shall require a TCP/IP network to function Server should always connect with CIBIL data base server. This product shall require communication protocol between loan data base server and CIBIL data base server. CIBIL response on each request shall be automatically saved in Administrator side.
Software Requirement Specification for 20
Page 6 of
Indian Institute of Information Technology & Management
3.
3.1
UML Diagrams
Activity Diagram
Activity Diagram
Software Requirement Specification for 20 Page 7 of
Indian Institute of Information Technology & Management
Swim lane Diagram
Software Requirement Specification for 20
Page 8 of
Indian Institute of Information Technology & Management
3.2
Class Diagrams
Software Requirement Specification for 20
Page 9 of
Indian Institute of Information Technology & Management
3.3
State Chart Diagrams
Software Requirement Specification for 20
Page 10 of
Indian Institute of Information Technology & Management
3.4
Sequence Diagrams
Software Requirement Specification for 20
Page 11 of
Indian Institute of Information Technology & Management
3.5
Collaboration Diagrams
Software Requirement Specification for 20
Page 12 of
Indian Institute of Information Technology & Management
3.6
Component Diagrams
Software Requirement Specification for 20
Page 13 of
Indian Institute of Information Technology & Management
3.7
Deployment Diagrams
Software Requirement Specification for 20
Page 14 of
Indian Institute of Information Technology & Management
4 4.1
External Interface Requirements User Interfaces
4.1.1 The user should be allowed to use client application to access server. 4.1.2 Users should be allowed to download application form from a website. 4.1.3 Users should be allowed to use application which will save settings with login information. 4.1.4 Users are allowed to click on application form in order to fill the form according to their requirements. 4.1.5 User should be allowed to access loan status data base after login by LAN 4.1.6 Administrator should be able to configure the application form. 4.1.7 System should respond user after each step of loan application submission. 4.1.8 System should send acknowledgement to user after loan application submission 4.1.9 Users should be able to resubmit loan application or update to the previous loan
application form.
Software Requirement Specification for 20
Page 15 of
Indian Institute of Information Technology & Management
5
Other Nonfunctional Requirements
5.1 Performance Requirements
5.1.1 Stress Requirements System must be able to support at least 15 end users accessing loan form, loan information, status record and loan application documents for loan processing simultaneously. 5.1.2 Response time Requirements Maximum time take by the system will be 3-5 seconds. 5.1.3 Throughput Requirements Maximum 15 number of transactions per unit of time that the system must be process 5.1.4 Server Application should respond to all protocol-defined communication from its authenticated client applications. 5.1.5 Client application should respond to all protocol-defined communication from its connected server application. 5.1.6 Server application should handle all protocol-defined communications in order they were received from its authenticated end users.
5.2
Safety Requirements
5.2.1 The system should constrained by the hardware compatibilities of the server, so that loan application shall safely submitted and bank admin can safely access all the data base and restore the results. 5.2.2 Notify any error occurred in between the process. Discard that data and do not replicate that result in server data base.
Software Requirement Specification for 20
Page 16 of
Indian Institute of Information Technology & Management
5.2.3 Maintain a backup file of data and asked for deletion.
5.3
Security Requirements
5.3.1 Customer Authorization Customer should registered first before applying for loan. Without registration customer will not be allowed to submit application form.
5.3.2 Customer Authentication Customer will be authenticated by employing LAN provided by system. Without LAN he is not allowed to track loan status.
5.3.3 Admin Authorization Only authorized persons of bank can make change in customer and loan application data base as well loan information data base.
Software Requirement Specification for 20
Page 17 of
Indian Institute of Information Technology & Management
6 Other Requirements
6.1 Usability Requirements System must confirm to usability guidelines are provided. 6.2 Volume and Storage Requirements First iteration of the system must support a volume of 500 customers and 25000 loan applications in a year 6.3 Configuration Requirements PC-compatible, Windows XP/Vista/7
Appendix A: Glossary TBD
Software Requirement Specification for 20
Page 18 of
doc_522743905.doc
SRS document of LOS
Indian Institute of Information Technology & Management
Software Requirements Specification
For
Version 1.0 approved Prepared by Arti Omar (IPG_2008108) ABV-IIITM 1-11-2011
Software Requirements Specification for
Page ii
Table of Contents
1. Introduction................................................................................................................................1
1.1Purpose ................................................................................................................................................ 1 1.2Intended Audience and Reading Suggestions...................................................................................... 1 1.3Project Scope........................................................................................................................................ 1 Product scope focus on the following component: client, server, and database......................................1 1. 4 References....................................................................................................................................... 2
2. Overall Description....................................................................................................................3
2.1 Product Perspective......................................................................................................................... 2.2 Product Features............................................................................................................................. 2.3Access Control (CRUD Matrix).......................................................................................................... 2.4Operating Environment........................................................................................................................ 2.4.4Assumptions and Dependencies....................................................................................................... 3 3 4 5 6
3. UML Diagrams...........................................................................................................................7
3.1Activity Diagram.................................................................................................................................. 7 3.2Class Diagrams.................................................................................................................................... 9 3.3 State Chart Diagrams................................................................................................................... 10 3.4Sequence Diagrams............................................................................................................................ 11 3.5Collaboration Diagrams..................................................................................................................... 12 3.6Component Diagrams........................................................................................................................ 13 3.7Deployment Diagrams....................................................................................................................... 14
4 External Interface Requirements............................................................................... 15 4.1 User Interfaces....................................................................................................................... 15
5Other Nonfunctional Requirements...................................................................................................... 5.1 Performance Requirements.............................................................................................................. 5.2Safety Requirements.......................................................................................................................... 5.3Security Requirements....................................................................................................................... 16 16 16 17
6 Other Requirements................................................................................................................. 18
Revision History
Name N/A N/A Date N/A N/A Reason For Changes N/A N/A Version N/A N/A
Software Requirement Specification for of 20
Page ii
Indian Institute of Information Technology & Management
1.
1.1
Introduction
Purpose
Proposed Software Requirement document is for Loan Originating System. Approved version of SRS is 1.0. Loan Originating System is the system will be used to originate consumer loans in IIITM campus. 1.1.1 The product shall provide a platform upon which multiple users can fill online form, multiple data entry operator can update information and multiple users can track their loan information and create account. 1.1.2 This Software Requirements Specification document shall be intended for internal developer reference. 1.1.3 Credit rating support system -Process for accessing credit rating ratings from CIBIL data base 1.1.4 server 1.1.5 Server – the application that manages customer statistics 1.1.6 Keep-Alive Time Interval – the maximum amount of time negotiated at client authentication that may pass without communication between a client and its server before the server begins transmitting the ping message. Client – the end-user application necessary for interacting with the main loan data base
1.2
Intended Audience and Reading Suggestions
TBD
1.3
Project Scope
Product scope focus on the following component: client, server, and database. 1.3.1 loan feedback. 1.3.2 Server shall communicate with client the client application to provide updates, form provide guidelines for filling the form, For scanning and saving documents, for LAN generation and assignment and Re assignment of LAN if incase user has missed his LAN. The client application shall provide the user with an interactive interface for accessing application form, for entering loan information, for tracking loan status, for loan process
1.3.3 Product shall provide web-based loan originating environment.
Software Requirement Specification for 20 Page 1 of
Indian Institute of Information Technology & Management
1.3.4 Web forms filled out and saved by the applicant on the web site, that are then sent to or retrieved by (ostensibly securely) the financial institution 1.3.5 True web applications with interfaces to a loan origination system on the back end. Many of the early solutions had a lot of the same problems as general forms (bad work flows, trying to handle all manner of loan types in one form) 1.3.6 Wizard-style applications that are very intuitive and don't ask superfluous questions. 1.3.7 Product shall classify type of loan products with attached interest rate information. 1.3.8 Product shall update all information after each step from end user point of view. 1.3.9 Product should notify all the errors and relevant guidelines for that. 1.3.10 Product shall fulfill current security requirement (Multi-factor authentication). 1.3.11 Get current credit-report. 1.3.12 Prequalify (auto-decision) the application and return a quick response to the applicant
1. 4
N/A
References
Software Requirement Specification for 20
Page 2 of
Indian Institute of Information Technology & Management
2. Overall Description
This SRS contains all of the requirements needed to implement this system and its dependencies. This document shall be formatted so that requirements are prioritized by system components.
2.1
Product Perspective
2.1.1. The product shall be fully independent and self-contained.
2.2
Product Features
2.2.1. This product shall, at a minimum, operate using the following three components. Extensibility to these components as well as additional components not listed here will be allowed: 2.2.1.1. Client application: • • • • • • The client shall display the status of loan, and send the server commands. It will display loan application form at customer end. It will provide LAN and other user guidelines to fill the application form. It will display updated loan information regarding type of new loan product, new interest schemes, etc. It will provide a good interface between customer and server. It will provide search option on screen so that a user can search the loan product with appropriate key wards and get all the information regarding the product. Client application will support communication protocol between client and server application. 2.2.1.2. Server application: • • • • • • The server shall process all of the logics and rules. It will support communication protocol among client application and data base application. It will automatically filter all the redundant information. It will quickly response to customer queries. It will update all the loan information in loan account. It will update the status flag of loan status.
Page 3 of
Software Requirement Specification for 20
Indian Institute of Information Technology & Management
• • • • • •
It will discard irrelevant client message which is not define under communication protocol. It will automatically generate random loan ID (LAN) to customer after submitting and scanning correct loan information. It will save the customer documents in the data base and run them when they will be called. It will send request for credit rating save the result. It will run the bank admin queries and configured the loan applications accordingly. It will process risk evaluation rules. 2.2.1.3. Database application: The database shall store
• • • • • • • • • • • • • •
Consumer loan application information, Loan documents, Login information, Consumer record, Loan information, Product type, Product updates, Loan interest type information, Lenders information, Loan assignment information And credit rating score. Easy interaction with server application and client application. Support server queries. Support key wards also to run queries.
2.3
Access Control (CRUD Matrix)
Entity Process Customer Data Entry Operator Bank Administrator Lenders Underwriter CIBIL
Software Requirement Specification for 20
Page 4 of
Indian Institute of Information Technology & Management
Fill loan application
CRU
R
R
R
R
Receive loan application Process loan application Configure loan application Verify loan application Process of risk evaluation Maintain loan account Maintain loan Product Loan reporting process Loan assignment report process Terminate loan application Credit Score Checking Loan status
R CRU C R R R
R R R R R -
R R CRU R R RU CRU R CU D R CRU
R R CRU R R R CUR R R RU
R R R CRU U R UR D R CUR CUR -
2.4
Operating Environment
2.4.1 Hardware Interfaces Hardware Interfaces shall be left to the user to acquire (i.e. Internet Access, Server, etc.)
2.4.2 Software Interfaces 2.4.2.1 2.4.2.2 2.4.2.3 2.4.2.4 2.4.2.5 2.4.2.3 Developers shall use SQL for the database. Developers shall use Google Code for tracking development, files, and bugs. Server software shall run on Windows OS (Version XP or later) as a service. The client application shall run on Windows OS (Version XP or later). The client application may also support platforms other than windows. Application shall check for updates on the server as initiated.
2.4.3 Communication Interfaces
Software Requirement Specification for 20 Page 5 of
Indian Institute of Information Technology & Management
2.4.3.1 2.4.3.2 2.4.3.3
XML shall be used to communicate message between the server and client The server will directly communicate with the database. Client/Server message shall be defined by the system communication protocol.
application.
2.4.4
Assumptions and Dependencies
At this phase there are no known system constraints. Only system shall be constraints by hardware compatibilities. 2.4.4.1 • • • • Dependencies This product shall require a TCP/IP network to function Server should always connect with CIBIL data base server. This product shall require communication protocol between loan data base server and CIBIL data base server. CIBIL response on each request shall be automatically saved in Administrator side.
Software Requirement Specification for 20
Page 6 of
Indian Institute of Information Technology & Management
3.
3.1
UML Diagrams
Activity Diagram
Activity Diagram
Software Requirement Specification for 20 Page 7 of
Indian Institute of Information Technology & Management
Swim lane Diagram
Software Requirement Specification for 20
Page 8 of
Indian Institute of Information Technology & Management
3.2
Class Diagrams
Software Requirement Specification for 20
Page 9 of
Indian Institute of Information Technology & Management
3.3
State Chart Diagrams
Software Requirement Specification for 20
Page 10 of
Indian Institute of Information Technology & Management
3.4
Sequence Diagrams
Software Requirement Specification for 20
Page 11 of
Indian Institute of Information Technology & Management
3.5
Collaboration Diagrams
Software Requirement Specification for 20
Page 12 of
Indian Institute of Information Technology & Management
3.6
Component Diagrams
Software Requirement Specification for 20
Page 13 of
Indian Institute of Information Technology & Management
3.7
Deployment Diagrams
Software Requirement Specification for 20
Page 14 of
Indian Institute of Information Technology & Management
4 4.1
External Interface Requirements User Interfaces
4.1.1 The user should be allowed to use client application to access server. 4.1.2 Users should be allowed to download application form from a website. 4.1.3 Users should be allowed to use application which will save settings with login information. 4.1.4 Users are allowed to click on application form in order to fill the form according to their requirements. 4.1.5 User should be allowed to access loan status data base after login by LAN 4.1.6 Administrator should be able to configure the application form. 4.1.7 System should respond user after each step of loan application submission. 4.1.8 System should send acknowledgement to user after loan application submission 4.1.9 Users should be able to resubmit loan application or update to the previous loan
application form.
Software Requirement Specification for 20
Page 15 of
Indian Institute of Information Technology & Management
5
Other Nonfunctional Requirements
5.1 Performance Requirements
5.1.1 Stress Requirements System must be able to support at least 15 end users accessing loan form, loan information, status record and loan application documents for loan processing simultaneously. 5.1.2 Response time Requirements Maximum time take by the system will be 3-5 seconds. 5.1.3 Throughput Requirements Maximum 15 number of transactions per unit of time that the system must be process 5.1.4 Server Application should respond to all protocol-defined communication from its authenticated client applications. 5.1.5 Client application should respond to all protocol-defined communication from its connected server application. 5.1.6 Server application should handle all protocol-defined communications in order they were received from its authenticated end users.
5.2
Safety Requirements
5.2.1 The system should constrained by the hardware compatibilities of the server, so that loan application shall safely submitted and bank admin can safely access all the data base and restore the results. 5.2.2 Notify any error occurred in between the process. Discard that data and do not replicate that result in server data base.
Software Requirement Specification for 20
Page 16 of
Indian Institute of Information Technology & Management
5.2.3 Maintain a backup file of data and asked for deletion.
5.3
Security Requirements
5.3.1 Customer Authorization Customer should registered first before applying for loan. Without registration customer will not be allowed to submit application form.
5.3.2 Customer Authentication Customer will be authenticated by employing LAN provided by system. Without LAN he is not allowed to track loan status.
5.3.3 Admin Authorization Only authorized persons of bank can make change in customer and loan application data base as well loan information data base.
Software Requirement Specification for 20
Page 17 of
Indian Institute of Information Technology & Management
6 Other Requirements
6.1 Usability Requirements System must confirm to usability guidelines are provided. 6.2 Volume and Storage Requirements First iteration of the system must support a volume of 500 customers and 25000 loan applications in a year 6.3 Configuration Requirements PC-compatible, Windows XP/Vista/7
Appendix A: Glossary TBD
Software Requirement Specification for 20
Page 18 of
doc_522743905.doc