SlideShare a Scribd company logo
1 of 16
Software Requirement
Specification
For Interest Rate Management System

Submitted By:Sharad Srivastava
12810076
MBA (2012-2014)
DoMS, IIT Roorkee
Contents
1.

Introduction......................................................................................................................................... 4
1.1 Purpose ........................................................................................................................................... 4
1.2 Scope............................................................................................................................................... 4
1.3 Definitions, Acronym, Abbreviation .............................................................................................. 5

2.

Overall Description ............................................................................................................................. 6
2.1 Product Perspective......................................................................................................................... 6
2.1.1 System Interface ...................................................................................................................... 6
2.1.2 User Interface ........................................................................................................................... 7
2.1.3 Hardware Interface .................................................................................................................. 8
2.1.4 Software Interface .................................................................................................................... 8
2.1.5 Memory Constaints .................................................................................................................. 9
2.1.6 Communication Interface......................................................................................................... 9
2.1.7 Operations ................................................................................................................................ 9
2.1.8 Site Adaptation Requirement ................................................................................................... 9
2.2 Product Function ............................................................................................................................. 9
2.3 User Characteristics ...................................................................................................................... 10
2.4 Contraints ...................................................................................................................................... 10
2.5 Assumptions and Dependencies ................................................................................................... 10
2.6 Apportioning of Requirement ....................................................................................................... 10

3.

Specific Requirements ...................................................................................................................... 11
3.1 External Interface Requirements .................................................................................................. 11
3.1.1 User Interface ......................................................................................................................... 11
3.2 System Product Feature ................................................................................................................ 12
3.2.1 Loan Information Management ............................................................................................. 12
3.2.2 Interest Rate Information Maintenance ................................................................................. 12
3.2.3 Report Generation .................................................................................................................. 13
3.2.4 User Account Information Maintenance ................................................................................ 14
3.3 Performance Requirement ............................................................................................................ 15
3.4 Design Constraints ........................................................................................................................ 15
2|Page
3.5 Software System Attributes .......................................................................................................... 15
3.5.1 Security .................................................................................................................................. 15
3.5.2 Maintainability ....................................................................................................................... 15
3.5.3 Portability............................................................................................................................... 15
3.6 Logical Database Requirement ..................................................................................................... 16

3|Page
1. Introduction
In 2009, during the time of recession and financial sector was feeling the heat, a big consolidation took
place in the sector. One of the leading investment banks Citibank sold 51% share of its Global wealth
Management division, called Smith Barney, to Morgan Stanley. The remaining 49% would be with Citi
group and the joint venture would be known as Morgan Stanley Smith Barney (MSSB). As of now, Citi
has its own MIS and reporting system for variable loan products which Morgan Stanley does not have.
Since business processes are not the same in two groups, there is a need to develop a new system to
perform variable interest rate lending products reporting. The new system will be known as “Interest rate
Management System” or IRMS.
This document tries to define the overall software requirements for „Interest Rate Management System‟.
It aims to define the requirements exhaustively and accurately. The final product will be having only
features/functionalities mentioned in this document and assumptions for any additional
functionality/feature should not be made by any of the parties involved in
developing/testing/implementing/using this product. In this case it is required to have some additional
features, a formal change request will need to be raised and subsequently a new release of this document
and/or product will be produced as per the agreement.

1.1 Purpose
This specification document describes the capabilities that will be provided by the software application
„Interest Rate Management System‟. It also clearly mentions the various required constraints by which
the system will abide. The intended audiences for this document are the development team, testing team
and end-users (financial advisor in this case) of this product.

1.2 Scope
The software product „Interest Rate Management System‟ will be an MIS and reporting application. The
application will be used for managing the activities of library of Morgan Stanley Smith Barney. The
application will manage the information of various clients and investors that have relationships with the
investment bank, their wealth and assets, various lending product information, past association/track
record, assigned investment banker/financial advisor‟s details and the net revenue generated. Printable
reports regarding list of clients, investment bankers, historical data and other relevant details will be
generated. The system will serve as MIS and reporting tool where rates are variable in nature.

4|Page
1.3 Definitions, Acronym, Abbreviation
MSSB:
IRMS:
FA:
User:
LIBOR:
DBA:
IBM DB2:
ASP:
IIS:
RAM:

Morgan Stanley Smith Barney
Interest Rate Management System
Financial Advisor
The login id having some or all access to the system
London Inter-Bank Offered Rate
Database Administrator
Relational database developed by IBM
Active Server Pages (a web page formatted on server and delivered to browser)
Internet Information Services
Random Access Memory

5|Page
2. Overall Description
2.1 Product Perspective
The software product will be a web based system which would run on an intranet. It will also be
connected to the outside world through a secured channel to gather real time data on interest rates.
Internally, it would interact with several other systems to receive and disseminate data.

2.1.1 System Interface
The Interest Rate Management System would need to interact with a variety of systems to facilitate the
function. It will talk to following systems:
The new system will interact, through the internet, to the external world. The base interest rates
(LIBOR rates) are determined on a daily basis and released by Reuters. Hence the IRMS will
fetch these daily feeds for its reporting purpose.
The new system will take inputs from another system for client details and stores the same. Since
IRMS is only a reporting tool, it does not have visibility to the new clients or changes in existing
data. Such details will be taken from other internal systems every day.
The job of IRMS is to serve as an MIS tool only. It does not process the loans or other
6|Page
computations. For this purpose it submits data to other sub-systems. Any loans will be saved in
IRMS first before any further processing.

2.1.2 User Interface
The Interest Rate Management System will have a user friendly and menu based interface. Following
screens will be provided:
A Login screen for entering the username, password and role (Administrator, Financial Advisor,
Management) will be provided. Access to different screens will be based upon the role of the
user.
There will be a screen which will list all borrower‟s data falling into a particular region,
associated with a particular FA or from the same branch. The screen would give details like
Loan No., Borrower Name, Address, Branch, FA, Loan Amount, Interest Rate, Interest Amount,
Loan Issue Date, Next Installment Due Date and Loan status (active, pending, approved,
rejected, cancelled or expired).
The above list will have the Borrower name as a hyperlink. By clicking on the same, a new
screen will appear with will list out the past record for the same recipient. The screen will have
details like Loan No., Borrower Name, Address, Branch, FA, Loan Amount, Interest Rate, Issue
Date and Loan Status.
There will be a standalone screen which would display all lending products offered by MSSB.
The screen will have details like Loan Product, Base rate, Spread (Premium) and Total Charged
Rate. This base rate gets updated daily, based on Reuters input.
There will be a search screen which will have the Loan No., Name, Branch, FA, Issue Date, Due
Date, Loan Product, Loan status and fields. The fields will alone or with combination of other
fields will be used to search a particular account or a set of accounts.
There will be a screen which will facilitate the addition of new records. This screen is supposed
to be used on the ad - face basis (actual updating will happen through a daily batch process).
Only administrators will be able to perform this function.
A separate screen would provide functionality to modify or delete an existing record. As
mentioned above, only administrators will have authority to perform this function.
One screen would be accessible to administrators only and contain audit information (changes
done in the database).
The following reports (only on demand basis) will be generated by this system:
A report containing a list of all borrowers falling into a particular region, associated with a
particular FA or from the same branch will be created. Reports can also be generated on other
fields such as Loan issued on a specific date, for a definite installment date, accounts pertaining
to same lending products and so on.
A report containing historical records of any particular beneficiary for limited or all time period,
7|Page
will be generated.
A report containing a list of accounts in a desired time period along with their loan amounts will
be created.
A list showing the trend of rates (as determined by Reuters) for any one or all products for the
past six months will be published.
A report showing new added loan accounts in a given time period will be published.

2.1.3 Hardware Interface
An extensive network base system as the system will be accessed by over 10000 FAs and
expected concurrent users are in the range of 700-1000.
Screen resolution of minimum 1024 X 768 is required for proper viewing of screens. Higher
resolutions will not be an issue.
User Machine Requirements:
Support for the printing devices is required. Appropriate drivers should be available and
installed. Printers (inkjet/deskjet/dot-matrix etc.) are connected properly for printing reports.
Operating System: Windows 9x/XP or above/MAC/Unix
Processor: Pentium 3.0 GHz or higher
RAM: 512 MB or more
Hard Drive: 10 GB or more
Internet Browser: IE 6.0 or above
Server Machine Requirements:
Operating System: Windows 9x/XP or above
Processor: Pentium 5.0 GHz or higher
RAM: 4 GB or more
Hard Drive: 500 GB or more
Internet Browser: IE 6.0 or above

2.1.4 Software Interface
Any Windows based operating system.
Database: IBM DB2
Application: ASP (Active Server Pages)
Web Server: IIS (Internet Information Services (IIS) is a powerful Web server that provides a
highly reliable, manageable, and scalable Web application infrastructure.
8|Page
2.1.5 Memory Constraints
Minimum memory requirement is 512 MB RAM and 10 GB space on hard disk for smooth running of
this application.

2.1.6 Communication Interface
None

2.1.7 Operations
This product release will not cover any automated housekeeping aspects of the database. The DBA at
the client side (with administrator level authority) will be responsible for manually deleting old/nonrequired data. Database backup and recovery will also have to be handled by the DBA.
However, the system will provide a „Reset System‟ function that will delete (upon confirmation from
the administrator) all the existing information from the database.

2.1.8 Site Adaptation Requirement
The terminal at the client side will have to support the hardware and software interface specified in the
above sections.

2.2 Product Function
The system will allow access only to authorized user with specific roles. Depending upon user‟s role
they will be able to access only specific modules of the system. A summary of the major functions that
the software will perform is mentioned below:
A login facility for enabling only authorized access to the system
Users (with administrator authority) will be able to add/modify/delete information about the
clients.
User (with administrator authority) will be able to reset password and reset whole system.
User (with access level other than administrator) will able to view all desired information but
would not be able to make changes.
User (with access level other than administrator) will be able to generate and print various
reports as listed above.

9|Page
2.3 User Characteristics
Educational Level: all FAs and managements will be having expertise in understanding
financial products. The intended users are CFAs, MBAs, CFPs and so on.
Experience: Should be well versed with financial markets and instruments and also the
information required for maintaining the tables.
Technical Expertise: Should be comfortable using general purpose applications on computer.
Should have exposure to the internet and web browsing.

2.4 Constraints
Due to limited features of the DBMS being used, database auditing will be provided.
Also, as the number of records increase, the system will tend to get slower.
Users will have to implement a security policy to safeguard information from being modified by
unauthorized users.

2.5 Assumptions and Dependencies
The number of records that will be displayed on one screen list will not be changed.
The layout of input as well as output will not be altered.
The system will depend upon inputs from the other system for its daily feed.
The interest rates will have dependencies on the Reuters feed.

2.6 Apportioning of Requirement
Not Required

10 | P a g e
3. Specific Requirements
This is defined as the software requirements to a level of detail sufficient to design.

3.1 External Interface Requirements
3.1.1 User Interface
Login Screen:
This will be the first screen that will be displayed. It will allow user to access based upon the user‟s role.
Various fields allow users access based upon the user‟s role. Various fields are
User ID: Alphanumeric of length up to 10 characters
Role: will have the following values: Administrator, FA, Management
Listing Screen:
This screen would provide functionality for listing out of client information. This screen will be
available to all users. Users have to provide search fields in order to filter the data.
Detail Screen:
This screen would provide historical data of a particular client. The screen is also available to all users.
Reference Screen:
This screen is used to view all loan products on that given day. This screen is also available to all users.
Search screen:
This screen is used for searching a particular client or a set of client based on search criteria. It will be
accessible to all users.
Insert Screen:
This screen is only available to administrators. It will facilitate adding a new record.
Update Screen:
It will be used to modify or delete an existing record and will be accessible to administrators only.
11 | P a g e
Audit Screen:
This screen is used for displaying all changes done in the database by a particular or all administrators. It
will be accessible only to users with administrators authority.

3.2 System Product Feature
3.2.1 Loan Information Management
Description:
The system will maintain information about various loans being issued during different time periods.
The following information would be maintained for the loans:
Loan No., Borrower Name, Address, Branch, FA, Loan Amount, Interest Rate, Interest Amount, Loan
Issue Date, Next Installment Due Date and Loan status

Validity Check:
Only FAs, Management and Administrators will have authorized access.
Each loan will have a unique loan number.
Each loan will have only one lending products in its entire cycle.
Loan No., borrower‟s name, address, branch, loan amount and loan status can not be spaces.

Error Handling/Response to Abnormal Situations:
If any of the above validations/sequencing flow does not hold true, appropriate error messages will be
prompted to the user for doing the needful.

3.2.2 Loan Product Information Maintenance
Description:
The system will maintain information about various lending products that are issued by Reuters. This
information will be backed up for a period of 6 months. Following information will be maintained for
each product:
Loan Product
12 | P a g e
Base rate
Spread (Premium)
Total Charged Rate
Date
The system will allow addition/modification or deletion of the records. This will assist in having only
the offered product information. The changes could only be done by administrators.

Validity Check:
Only FAs, Management and Administrators will have authorized access.
Each loan product will be pegged with at least one base rate.
Loan Product Name, Base Rate, Date, Total Charged Rate could not be spaces.

Error Handling/Response to Abnormal Situations:
If any of the above validations/sequencing flow does not hold true, appropriate error messages will be
prompted to the user for doing the needful.

3.2.3 Report Generation
Loan Information:
This report would give information about the various loans depending upon the search/filter criteria.
Report Format:
Morgan Stanley Smith Barney
Interest Rate Management System
Loan Summary Report
Loan
No.

Name of Address Branch FA Amount
Borrower
of Loan

Interest
Rate

Interest
Amount

Loan
Issue
Date

Due
Date

Status

13 | P a g e
Lending Product Information:
This report would give information about the various products offered depending upon the time period.
Report Format:
Morgan Stanley Smith Barney
Interest Rate Management System
Product Summary Report
Loan Products

Base Rate

Spread

Total Charged Rate

Date

3.2.4 User Account Information Maintenance
Description:
The system will maintain information about various users who would be able to use the system. The
following information would be maintained.
User name
User Id
Password
Role

Validity Check:
Only users with role FA/Administrator and the management will be authorized to access the User
Accounts Information Maintenance Module.
None of the fields (user name, user id, password or role) can be blank.
There should be a unique user id for every user.

Sequencing Information
User Account for a particular user has to be created in order for the system to be accessible to that user.
At system start up, only a default user account for „Administrator‟ would be present in the system.
14 | P a g e
Error Handling/Response to Abnormal Situations:
If any of the above validations/sequencing flow does not hold true, appropriate error messages will be
prompted to the user for doing the needful.

3.3 Performance Requirement
The system should be capable of handling large amount of data. It should be able to run queries
on 1 billion records.
The system should facilitate a total of 15000 user logins.
The system should be able to run for 700-1000 concurrent logins.

3.4 Design Constraints
None

3.5 Software System Attributes
3.5.1 Security
The application will be password protected. Users will have to enter correct username, password and
role in order to access the application. All the external interfaces such as through the internet or with
other system will have an additional middle layer which would act as security firewall.

3.5.2 Maintainability
The system will be designed in a maintainable manner. It will be easy to incorporate new requirements.

3.5.3 Portability
The system will be easily portable to any Windows based system that has MS Office 2007 installed.

15 | P a g e
3.6 Logical Database Requirement
Following information will be placed in the database.
Loan Info: Loan No., Borrower Name, Address, Branch, FA, Loan Amount, Interest Rate,
Interest Amount, Loan Issue Date, Next Installment Due Date and Loan status
Product Info: Loan Product, Base Rate, Spread, Total Charged Rate, Date
User Info: User name, User Id, Password, Role
Audit Info: User Id, Date, Time, Table, Comment

16 | P a g e

More Related Content

What's hot

Synopsis of online student feedback system(cse)
Synopsis of online student feedback system(cse)Synopsis of online student feedback system(cse)
Synopsis of online student feedback system(cse)shindept123
 
Online Banking Project
Online Banking ProjectOnline Banking Project
Online Banking ProjectM.Saber
 
Report of Student management system
Report of Student management systemReport of Student management system
Report of Student management system1amitgupta
 
Train ticket reservation
Train ticket reservationTrain ticket reservation
Train ticket reservationsazzadur rahman
 
SRS for Online Medicine Ordering System
SRS for Online Medicine Ordering SystemSRS for Online Medicine Ordering System
SRS for Online Medicine Ordering SystemUmmeKalsoom11
 
Loan Management System
Loan Management SystemLoan Management System
Loan Management SystemIshita Gupta
 
online-shopping-documentation-srs for TYBSCIT sem 6
 online-shopping-documentation-srs for TYBSCIT sem 6 online-shopping-documentation-srs for TYBSCIT sem 6
online-shopping-documentation-srs for TYBSCIT sem 6YogeshDhamke2
 
Banking system (final)
Banking system (final)Banking system (final)
Banking system (final)prabhjot7777
 
Presentation on Loan Management System
Presentation on Loan Management SystemPresentation on Loan Management System
Presentation on Loan Management SystemRohanRajMudvari
 
Bank management system
Bank management systemBank management system
Bank management systemMahmudul Hasan
 
Online shopping Report
Online shopping ReportOnline shopping Report
Online shopping ReportPragnya Dash
 
Bank management system with java
Bank management system with java Bank management system with java
Bank management system with java Neha Bhagat
 
Online Ticket Reservation System-SRS, ERD, DFD, Structured Charts
Online Ticket Reservation System-SRS, ERD, DFD, Structured ChartsOnline Ticket Reservation System-SRS, ERD, DFD, Structured Charts
Online Ticket Reservation System-SRS, ERD, DFD, Structured Chartsgrandhiprasuna
 
Srs on-railway-reservation-system
Srs on-railway-reservation-systemSrs on-railway-reservation-system
Srs on-railway-reservation-systemRajesh Salla
 
Event Management System
Event Management SystemEvent Management System
Event Management SystemQamber Ali
 
Electronic cash controller
Electronic cash controllerElectronic cash controller
Electronic cash controllersree1185
 
Bank Management System
Bank Management SystemBank Management System
Bank Management SystemHasan Khan
 

What's hot (20)

Synopsis of online student feedback system(cse)
Synopsis of online student feedback system(cse)Synopsis of online student feedback system(cse)
Synopsis of online student feedback system(cse)
 
Online Banking Project
Online Banking ProjectOnline Banking Project
Online Banking Project
 
Report of Student management system
Report of Student management systemReport of Student management system
Report of Student management system
 
Train ticket reservation
Train ticket reservationTrain ticket reservation
Train ticket reservation
 
SRS for Online Medicine Ordering System
SRS for Online Medicine Ordering SystemSRS for Online Medicine Ordering System
SRS for Online Medicine Ordering System
 
Loan Management System
Loan Management SystemLoan Management System
Loan Management System
 
online-shopping-documentation-srs for TYBSCIT sem 6
 online-shopping-documentation-srs for TYBSCIT sem 6 online-shopping-documentation-srs for TYBSCIT sem 6
online-shopping-documentation-srs for TYBSCIT sem 6
 
Banking system (final)
Banking system (final)Banking system (final)
Banking system (final)
 
Presentation on Loan Management System
Presentation on Loan Management SystemPresentation on Loan Management System
Presentation on Loan Management System
 
Hms project report
Hms project reportHms project report
Hms project report
 
Bank management system
Bank management systemBank management system
Bank management system
 
ONLINE STUDENT FEEDBACK SYSTEM
ONLINE STUDENT FEEDBACK SYSTEMONLINE STUDENT FEEDBACK SYSTEM
ONLINE STUDENT FEEDBACK SYSTEM
 
Online shopping Report
Online shopping ReportOnline shopping Report
Online shopping Report
 
Bank management system with java
Bank management system with java Bank management system with java
Bank management system with java
 
Online Ticket Reservation System-SRS, ERD, DFD, Structured Charts
Online Ticket Reservation System-SRS, ERD, DFD, Structured ChartsOnline Ticket Reservation System-SRS, ERD, DFD, Structured Charts
Online Ticket Reservation System-SRS, ERD, DFD, Structured Charts
 
Srs on-railway-reservation-system
Srs on-railway-reservation-systemSrs on-railway-reservation-system
Srs on-railway-reservation-system
 
Event Management System
Event Management SystemEvent Management System
Event Management System
 
Electronic cash controller
Electronic cash controllerElectronic cash controller
Electronic cash controller
 
Bank Management System
Bank Management SystemBank Management System
Bank Management System
 
online banking system
online banking systemonline banking system
online banking system
 

Viewers also liked

Online Loan Management System
Online Loan Management SystemOnline Loan Management System
Online Loan Management SystemSoban Ahmad
 
Loan Management System in Oracle
Loan Management System in OracleLoan Management System in Oracle
Loan Management System in OracleRanojit Banerjee
 
Online Loan Application & Its Verification System
Online Loan Application & Its Verification SystemOnline Loan Application & Its Verification System
Online Loan Application & Its Verification SystemSoban Ahmad
 
SRS document for Hotel Management System
SRS document for Hotel Management SystemSRS document for Hotel Management System
SRS document for Hotel Management SystemCharitha Gamage
 
Software requirements specification of Library Management System
Software requirements specification of Library Management SystemSoftware requirements specification of Library Management System
Software requirements specification of Library Management SystemSoumili Sen
 
Library mangement system project srs documentation.doc
Library mangement system project srs documentation.docLibrary mangement system project srs documentation.doc
Library mangement system project srs documentation.docjimmykhan
 

Viewers also liked (8)

Online Loan Management System
Online Loan Management SystemOnline Loan Management System
Online Loan Management System
 
Loan Management System in Oracle
Loan Management System in OracleLoan Management System in Oracle
Loan Management System in Oracle
 
Srs document
Srs documentSrs document
Srs document
 
Online Loan Application & Its Verification System
Online Loan Application & Its Verification SystemOnline Loan Application & Its Verification System
Online Loan Application & Its Verification System
 
SRS document for Hotel Management System
SRS document for Hotel Management SystemSRS document for Hotel Management System
SRS document for Hotel Management System
 
Bank Management System
Bank Management SystemBank Management System
Bank Management System
 
Software requirements specification of Library Management System
Software requirements specification of Library Management SystemSoftware requirements specification of Library Management System
Software requirements specification of Library Management System
 
Library mangement system project srs documentation.doc
Library mangement system project srs documentation.docLibrary mangement system project srs documentation.doc
Library mangement system project srs documentation.doc
 

Similar to Software Requirement Specification - Interest Rate Management

Finger Gesture Based Rating System
Finger Gesture Based Rating SystemFinger Gesture Based Rating System
Finger Gesture Based Rating SystemIRJET Journal
 
Mobile store management
Mobile store management Mobile store management
Mobile store management Rupendra Verma
 
Artificially Intelligent Investment Risk Calculation system based on Distribu...
Artificially Intelligent Investment Risk Calculation system based on Distribu...Artificially Intelligent Investment Risk Calculation system based on Distribu...
Artificially Intelligent Investment Risk Calculation system based on Distribu...iosrjce
 
E-Commerce Mobile Sale System
E-Commerce Mobile Sale SystemE-Commerce Mobile Sale System
E-Commerce Mobile Sale SystemAbhishek Kumar
 
Identity_Management_Vendor_Evaluation
Identity_Management_Vendor_EvaluationIdentity_Management_Vendor_Evaluation
Identity_Management_Vendor_EvaluationJerry Ruggieri
 
Banking Management System SRS
Banking Management System SRSBanking Management System SRS
Banking Management System SRSMr. Moms
 
Business Information Systems by Patrick Linhart
Business Information Systems by Patrick LinhartBusiness Information Systems by Patrick Linhart
Business Information Systems by Patrick LinhartPatrick Linhart
 
SOFTWARE DESIGN .docx
SOFTWARE DESIGN                                                   .docxSOFTWARE DESIGN                                                   .docx
SOFTWARE DESIGN .docxrronald3
 
Insurance management system
Insurance management systemInsurance management system
Insurance management systemAnu sneha
 
Share market analysis
Share market analysis Share market analysis
Share market analysis shubham patil
 
IS6155 Project Student numbers 90079094 114223513 102859661
IS6155 Project Student numbers 90079094 114223513 102859661IS6155 Project Student numbers 90079094 114223513 102859661
IS6155 Project Student numbers 90079094 114223513 102859661Brendan Mc Sweeney
 
SHAZ micro ERP
SHAZ micro ERP SHAZ micro ERP
SHAZ micro ERP Raj Boruah
 
IM-7ed-Chapter02-done.pdf
IM-7ed-Chapter02-done.pdfIM-7ed-Chapter02-done.pdf
IM-7ed-Chapter02-done.pdfVahid95
 
Payroll Management System SRS
Payroll Management System SRSPayroll Management System SRS
Payroll Management System SRSShubham Modi
 

Similar to Software Requirement Specification - Interest Rate Management (20)

Srs of bms
Srs of bmsSrs of bms
Srs of bms
 
Finger Gesture Based Rating System
Finger Gesture Based Rating SystemFinger Gesture Based Rating System
Finger Gesture Based Rating System
 
Mobile store management
Mobile store management Mobile store management
Mobile store management
 
D017612529
D017612529D017612529
D017612529
 
Artificially Intelligent Investment Risk Calculation system based on Distribu...
Artificially Intelligent Investment Risk Calculation system based on Distribu...Artificially Intelligent Investment Risk Calculation system based on Distribu...
Artificially Intelligent Investment Risk Calculation system based on Distribu...
 
E-Commerce Mobile Sale System
E-Commerce Mobile Sale SystemE-Commerce Mobile Sale System
E-Commerce Mobile Sale System
 
Identity_Management_Vendor_Evaluation
Identity_Management_Vendor_EvaluationIdentity_Management_Vendor_Evaluation
Identity_Management_Vendor_Evaluation
 
Banking Management System SRS
Banking Management System SRSBanking Management System SRS
Banking Management System SRS
 
Business Information Systems by Patrick Linhart
Business Information Systems by Patrick LinhartBusiness Information Systems by Patrick Linhart
Business Information Systems by Patrick Linhart
 
SOFTWARE DESIGN .docx
SOFTWARE DESIGN                                                   .docxSOFTWARE DESIGN                                                   .docx
SOFTWARE DESIGN .docx
 
Insurance management system report on visual basic
Insurance management system report on visual basicInsurance management system report on visual basic
Insurance management system report on visual basic
 
Insurance management system
Insurance management systemInsurance management system
Insurance management system
 
City Without Crime
City Without CrimeCity Without Crime
City Without Crime
 
Share market analysis
Share market analysis Share market analysis
Share market analysis
 
IS6155 Project Student numbers 90079094 114223513 102859661
IS6155 Project Student numbers 90079094 114223513 102859661IS6155 Project Student numbers 90079094 114223513 102859661
IS6155 Project Student numbers 90079094 114223513 102859661
 
How to Choose an Agency Management System
How to Choose an Agency Management SystemHow to Choose an Agency Management System
How to Choose an Agency Management System
 
SHAZ micro ERP
SHAZ micro ERP SHAZ micro ERP
SHAZ micro ERP
 
Defining Enterprise Identity Management
Defining Enterprise Identity ManagementDefining Enterprise Identity Management
Defining Enterprise Identity Management
 
IM-7ed-Chapter02-done.pdf
IM-7ed-Chapter02-done.pdfIM-7ed-Chapter02-done.pdf
IM-7ed-Chapter02-done.pdf
 
Payroll Management System SRS
Payroll Management System SRSPayroll Management System SRS
Payroll Management System SRS
 

More from Sharad Srivastava

Presentation - Sales & Distribution at ITC
Presentation - Sales & Distribution at ITCPresentation - Sales & Distribution at ITC
Presentation - Sales & Distribution at ITCSharad Srivastava
 
Presentation - Scope and Schedule Management of Business Analytics Project
Presentation - Scope and Schedule Management of Business Analytics ProjectPresentation - Scope and Schedule Management of Business Analytics Project
Presentation - Scope and Schedule Management of Business Analytics ProjectSharad Srivastava
 
IT Case Study - SAP CRM in Asian Paints
IT Case Study - SAP CRM in Asian PaintsIT Case Study - SAP CRM in Asian Paints
IT Case Study - SAP CRM in Asian PaintsSharad Srivastava
 
Presentation - Electronic Data Interchange
Presentation - Electronic Data InterchangePresentation - Electronic Data Interchange
Presentation - Electronic Data InterchangeSharad Srivastava
 
Report - Risk Management in Banks
Report - Risk Management in BanksReport - Risk Management in Banks
Report - Risk Management in BanksSharad Srivastava
 
Presentation - Working Capital Management
Presentation - Working Capital ManagementPresentation - Working Capital Management
Presentation - Working Capital ManagementSharad Srivastava
 
Marketing Case Study - Starbucks
Marketing Case Study - StarbucksMarketing Case Study - Starbucks
Marketing Case Study - StarbucksSharad Srivastava
 
Strategy Report - Daurala Sugar Works
Strategy Report - Daurala Sugar WorksStrategy Report - Daurala Sugar Works
Strategy Report - Daurala Sugar WorksSharad Srivastava
 
Presentation - Rational Unified Process
Presentation - Rational Unified ProcessPresentation - Rational Unified Process
Presentation - Rational Unified ProcessSharad Srivastava
 
Term Paper - Quality Assurance in Software Development
Term Paper - Quality Assurance in Software DevelopmentTerm Paper - Quality Assurance in Software Development
Term Paper - Quality Assurance in Software DevelopmentSharad Srivastava
 
Business Case - SCM Implementation
Business Case - SCM ImplementationBusiness Case - SCM Implementation
Business Case - SCM ImplementationSharad Srivastava
 
Presentation - The Negotiable Instruments Act 1881
Presentation - The Negotiable Instruments Act 1881Presentation - The Negotiable Instruments Act 1881
Presentation - The Negotiable Instruments Act 1881Sharad Srivastava
 
Marketing Strategy - Daurala Sugar Works
Marketing Strategy - Daurala Sugar WorksMarketing Strategy - Daurala Sugar Works
Marketing Strategy - Daurala Sugar WorksSharad Srivastava
 
Presentation - Microfinance in India
Presentation - Microfinance in IndiaPresentation - Microfinance in India
Presentation - Microfinance in IndiaSharad Srivastava
 
Report - Colgate Financial Analysis
Report - Colgate Financial AnalysisReport - Colgate Financial Analysis
Report - Colgate Financial AnalysisSharad Srivastava
 
ERP Case Study - Warehouse Management System
ERP Case Study - Warehouse Management SystemERP Case Study - Warehouse Management System
ERP Case Study - Warehouse Management SystemSharad Srivastava
 
Organisation Case Study - Restructuring at Mayekawa
Organisation Case Study - Restructuring at MayekawaOrganisation Case Study - Restructuring at Mayekawa
Organisation Case Study - Restructuring at MayekawaSharad Srivastava
 

More from Sharad Srivastava (20)

Presentation - Sales & Distribution at ITC
Presentation - Sales & Distribution at ITCPresentation - Sales & Distribution at ITC
Presentation - Sales & Distribution at ITC
 
Presentation - Scope and Schedule Management of Business Analytics Project
Presentation - Scope and Schedule Management of Business Analytics ProjectPresentation - Scope and Schedule Management of Business Analytics Project
Presentation - Scope and Schedule Management of Business Analytics Project
 
IT Case Study - SAP CRM in Asian Paints
IT Case Study - SAP CRM in Asian PaintsIT Case Study - SAP CRM in Asian Paints
IT Case Study - SAP CRM in Asian Paints
 
Presentation - Electronic Data Interchange
Presentation - Electronic Data InterchangePresentation - Electronic Data Interchange
Presentation - Electronic Data Interchange
 
Report - Risk Management in Banks
Report - Risk Management in BanksReport - Risk Management in Banks
Report - Risk Management in Banks
 
Report - Monetary Policy
Report - Monetary PolicyReport - Monetary Policy
Report - Monetary Policy
 
Presentation - Working Capital Management
Presentation - Working Capital ManagementPresentation - Working Capital Management
Presentation - Working Capital Management
 
Marketing Case Study - Starbucks
Marketing Case Study - StarbucksMarketing Case Study - Starbucks
Marketing Case Study - Starbucks
 
Strategy Report - Daurala Sugar Works
Strategy Report - Daurala Sugar WorksStrategy Report - Daurala Sugar Works
Strategy Report - Daurala Sugar Works
 
Presentation - Rational Unified Process
Presentation - Rational Unified ProcessPresentation - Rational Unified Process
Presentation - Rational Unified Process
 
Presentation - SERVQUAL
Presentation - SERVQUALPresentation - SERVQUAL
Presentation - SERVQUAL
 
Term Paper - Quality Assurance in Software Development
Term Paper - Quality Assurance in Software DevelopmentTerm Paper - Quality Assurance in Software Development
Term Paper - Quality Assurance in Software Development
 
Business Case - SCM Implementation
Business Case - SCM ImplementationBusiness Case - SCM Implementation
Business Case - SCM Implementation
 
Presentation - The Negotiable Instruments Act 1881
Presentation - The Negotiable Instruments Act 1881Presentation - The Negotiable Instruments Act 1881
Presentation - The Negotiable Instruments Act 1881
 
Marketing Strategy - Daurala Sugar Works
Marketing Strategy - Daurala Sugar WorksMarketing Strategy - Daurala Sugar Works
Marketing Strategy - Daurala Sugar Works
 
Presentation - Microfinance in India
Presentation - Microfinance in IndiaPresentation - Microfinance in India
Presentation - Microfinance in India
 
Report - Colgate Financial Analysis
Report - Colgate Financial AnalysisReport - Colgate Financial Analysis
Report - Colgate Financial Analysis
 
ERP Case Study - Warehouse Management System
ERP Case Study - Warehouse Management SystemERP Case Study - Warehouse Management System
ERP Case Study - Warehouse Management System
 
Organisation Case Study - Restructuring at Mayekawa
Organisation Case Study - Restructuring at MayekawaOrganisation Case Study - Restructuring at Mayekawa
Organisation Case Study - Restructuring at Mayekawa
 
Report - South Africa
Report - South AfricaReport - South Africa
Report - South Africa
 

Recently uploaded

Unraveling Multimodality with Large Language Models.pdf
Unraveling Multimodality with Large Language Models.pdfUnraveling Multimodality with Large Language Models.pdf
Unraveling Multimodality with Large Language Models.pdfAlex Barbosa Coqueiro
 
Developer Data Modeling Mistakes: From Postgres to NoSQL
Developer Data Modeling Mistakes: From Postgres to NoSQLDeveloper Data Modeling Mistakes: From Postgres to NoSQL
Developer Data Modeling Mistakes: From Postgres to NoSQLScyllaDB
 
The Fit for Passkeys for Employee and Consumer Sign-ins: FIDO Paris Seminar.pptx
The Fit for Passkeys for Employee and Consumer Sign-ins: FIDO Paris Seminar.pptxThe Fit for Passkeys for Employee and Consumer Sign-ins: FIDO Paris Seminar.pptx
The Fit for Passkeys for Employee and Consumer Sign-ins: FIDO Paris Seminar.pptxLoriGlavin3
 
Merck Moving Beyond Passwords: FIDO Paris Seminar.pptx
Merck Moving Beyond Passwords: FIDO Paris Seminar.pptxMerck Moving Beyond Passwords: FIDO Paris Seminar.pptx
Merck Moving Beyond Passwords: FIDO Paris Seminar.pptxLoriGlavin3
 
The Role of FIDO in a Cyber Secure Netherlands: FIDO Paris Seminar.pptx
The Role of FIDO in a Cyber Secure Netherlands: FIDO Paris Seminar.pptxThe Role of FIDO in a Cyber Secure Netherlands: FIDO Paris Seminar.pptx
The Role of FIDO in a Cyber Secure Netherlands: FIDO Paris Seminar.pptxLoriGlavin3
 
Use of FIDO in the Payments and Identity Landscape: FIDO Paris Seminar.pptx
Use of FIDO in the Payments and Identity Landscape: FIDO Paris Seminar.pptxUse of FIDO in the Payments and Identity Landscape: FIDO Paris Seminar.pptx
Use of FIDO in the Payments and Identity Landscape: FIDO Paris Seminar.pptxLoriGlavin3
 
The State of Passkeys with FIDO Alliance.pptx
The State of Passkeys with FIDO Alliance.pptxThe State of Passkeys with FIDO Alliance.pptx
The State of Passkeys with FIDO Alliance.pptxLoriGlavin3
 
How AI, OpenAI, and ChatGPT impact business and software.
How AI, OpenAI, and ChatGPT impact business and software.How AI, OpenAI, and ChatGPT impact business and software.
How AI, OpenAI, and ChatGPT impact business and software.Curtis Poe
 
From Family Reminiscence to Scholarly Archive .
From Family Reminiscence to Scholarly Archive .From Family Reminiscence to Scholarly Archive .
From Family Reminiscence to Scholarly Archive .Alan Dix
 
Passkey Providers and Enabling Portability: FIDO Paris Seminar.pptx
Passkey Providers and Enabling Portability: FIDO Paris Seminar.pptxPasskey Providers and Enabling Portability: FIDO Paris Seminar.pptx
Passkey Providers and Enabling Portability: FIDO Paris Seminar.pptxLoriGlavin3
 
unit 4 immunoblotting technique complete.pptx
unit 4 immunoblotting technique complete.pptxunit 4 immunoblotting technique complete.pptx
unit 4 immunoblotting technique complete.pptxBkGupta21
 
Take control of your SAP testing with UiPath Test Suite
Take control of your SAP testing with UiPath Test SuiteTake control of your SAP testing with UiPath Test Suite
Take control of your SAP testing with UiPath Test SuiteDianaGray10
 
What is DBT - The Ultimate Data Build Tool.pdf
What is DBT - The Ultimate Data Build Tool.pdfWhat is DBT - The Ultimate Data Build Tool.pdf
What is DBT - The Ultimate Data Build Tool.pdfMounikaPolabathina
 
Nell’iperspazio con Rocket: il Framework Web di Rust!
Nell’iperspazio con Rocket: il Framework Web di Rust!Nell’iperspazio con Rocket: il Framework Web di Rust!
Nell’iperspazio con Rocket: il Framework Web di Rust!Commit University
 
SAP Build Work Zone - Overview L2-L3.pptx
SAP Build Work Zone - Overview L2-L3.pptxSAP Build Work Zone - Overview L2-L3.pptx
SAP Build Work Zone - Overview L2-L3.pptxNavinnSomaal
 
A Deep Dive on Passkeys: FIDO Paris Seminar.pptx
A Deep Dive on Passkeys: FIDO Paris Seminar.pptxA Deep Dive on Passkeys: FIDO Paris Seminar.pptx
A Deep Dive on Passkeys: FIDO Paris Seminar.pptxLoriGlavin3
 
Moving Beyond Passwords: FIDO Paris Seminar.pdf
Moving Beyond Passwords: FIDO Paris Seminar.pdfMoving Beyond Passwords: FIDO Paris Seminar.pdf
Moving Beyond Passwords: FIDO Paris Seminar.pdfLoriGlavin3
 
Gen AI in Business - Global Trends Report 2024.pdf
Gen AI in Business - Global Trends Report 2024.pdfGen AI in Business - Global Trends Report 2024.pdf
Gen AI in Business - Global Trends Report 2024.pdfAddepto
 
DevEX - reference for building teams, processes, and platforms
DevEX - reference for building teams, processes, and platformsDevEX - reference for building teams, processes, and platforms
DevEX - reference for building teams, processes, and platformsSergiu Bodiu
 

Recently uploaded (20)

Unraveling Multimodality with Large Language Models.pdf
Unraveling Multimodality with Large Language Models.pdfUnraveling Multimodality with Large Language Models.pdf
Unraveling Multimodality with Large Language Models.pdf
 
Developer Data Modeling Mistakes: From Postgres to NoSQL
Developer Data Modeling Mistakes: From Postgres to NoSQLDeveloper Data Modeling Mistakes: From Postgres to NoSQL
Developer Data Modeling Mistakes: From Postgres to NoSQL
 
The Fit for Passkeys for Employee and Consumer Sign-ins: FIDO Paris Seminar.pptx
The Fit for Passkeys for Employee and Consumer Sign-ins: FIDO Paris Seminar.pptxThe Fit for Passkeys for Employee and Consumer Sign-ins: FIDO Paris Seminar.pptx
The Fit for Passkeys for Employee and Consumer Sign-ins: FIDO Paris Seminar.pptx
 
Merck Moving Beyond Passwords: FIDO Paris Seminar.pptx
Merck Moving Beyond Passwords: FIDO Paris Seminar.pptxMerck Moving Beyond Passwords: FIDO Paris Seminar.pptx
Merck Moving Beyond Passwords: FIDO Paris Seminar.pptx
 
The Role of FIDO in a Cyber Secure Netherlands: FIDO Paris Seminar.pptx
The Role of FIDO in a Cyber Secure Netherlands: FIDO Paris Seminar.pptxThe Role of FIDO in a Cyber Secure Netherlands: FIDO Paris Seminar.pptx
The Role of FIDO in a Cyber Secure Netherlands: FIDO Paris Seminar.pptx
 
Use of FIDO in the Payments and Identity Landscape: FIDO Paris Seminar.pptx
Use of FIDO in the Payments and Identity Landscape: FIDO Paris Seminar.pptxUse of FIDO in the Payments and Identity Landscape: FIDO Paris Seminar.pptx
Use of FIDO in the Payments and Identity Landscape: FIDO Paris Seminar.pptx
 
The State of Passkeys with FIDO Alliance.pptx
The State of Passkeys with FIDO Alliance.pptxThe State of Passkeys with FIDO Alliance.pptx
The State of Passkeys with FIDO Alliance.pptx
 
How AI, OpenAI, and ChatGPT impact business and software.
How AI, OpenAI, and ChatGPT impact business and software.How AI, OpenAI, and ChatGPT impact business and software.
How AI, OpenAI, and ChatGPT impact business and software.
 
From Family Reminiscence to Scholarly Archive .
From Family Reminiscence to Scholarly Archive .From Family Reminiscence to Scholarly Archive .
From Family Reminiscence to Scholarly Archive .
 
Passkey Providers and Enabling Portability: FIDO Paris Seminar.pptx
Passkey Providers and Enabling Portability: FIDO Paris Seminar.pptxPasskey Providers and Enabling Portability: FIDO Paris Seminar.pptx
Passkey Providers and Enabling Portability: FIDO Paris Seminar.pptx
 
unit 4 immunoblotting technique complete.pptx
unit 4 immunoblotting technique complete.pptxunit 4 immunoblotting technique complete.pptx
unit 4 immunoblotting technique complete.pptx
 
Take control of your SAP testing with UiPath Test Suite
Take control of your SAP testing with UiPath Test SuiteTake control of your SAP testing with UiPath Test Suite
Take control of your SAP testing with UiPath Test Suite
 
What is DBT - The Ultimate Data Build Tool.pdf
What is DBT - The Ultimate Data Build Tool.pdfWhat is DBT - The Ultimate Data Build Tool.pdf
What is DBT - The Ultimate Data Build Tool.pdf
 
Nell’iperspazio con Rocket: il Framework Web di Rust!
Nell’iperspazio con Rocket: il Framework Web di Rust!Nell’iperspazio con Rocket: il Framework Web di Rust!
Nell’iperspazio con Rocket: il Framework Web di Rust!
 
SAP Build Work Zone - Overview L2-L3.pptx
SAP Build Work Zone - Overview L2-L3.pptxSAP Build Work Zone - Overview L2-L3.pptx
SAP Build Work Zone - Overview L2-L3.pptx
 
A Deep Dive on Passkeys: FIDO Paris Seminar.pptx
A Deep Dive on Passkeys: FIDO Paris Seminar.pptxA Deep Dive on Passkeys: FIDO Paris Seminar.pptx
A Deep Dive on Passkeys: FIDO Paris Seminar.pptx
 
Moving Beyond Passwords: FIDO Paris Seminar.pdf
Moving Beyond Passwords: FIDO Paris Seminar.pdfMoving Beyond Passwords: FIDO Paris Seminar.pdf
Moving Beyond Passwords: FIDO Paris Seminar.pdf
 
Gen AI in Business - Global Trends Report 2024.pdf
Gen AI in Business - Global Trends Report 2024.pdfGen AI in Business - Global Trends Report 2024.pdf
Gen AI in Business - Global Trends Report 2024.pdf
 
DMCC Future of Trade Web3 - Special Edition
DMCC Future of Trade Web3 - Special EditionDMCC Future of Trade Web3 - Special Edition
DMCC Future of Trade Web3 - Special Edition
 
DevEX - reference for building teams, processes, and platforms
DevEX - reference for building teams, processes, and platformsDevEX - reference for building teams, processes, and platforms
DevEX - reference for building teams, processes, and platforms
 

Software Requirement Specification - Interest Rate Management

  • 1. Software Requirement Specification For Interest Rate Management System Submitted By:Sharad Srivastava 12810076 MBA (2012-2014) DoMS, IIT Roorkee
  • 2. Contents 1. Introduction......................................................................................................................................... 4 1.1 Purpose ........................................................................................................................................... 4 1.2 Scope............................................................................................................................................... 4 1.3 Definitions, Acronym, Abbreviation .............................................................................................. 5 2. Overall Description ............................................................................................................................. 6 2.1 Product Perspective......................................................................................................................... 6 2.1.1 System Interface ...................................................................................................................... 6 2.1.2 User Interface ........................................................................................................................... 7 2.1.3 Hardware Interface .................................................................................................................. 8 2.1.4 Software Interface .................................................................................................................... 8 2.1.5 Memory Constaints .................................................................................................................. 9 2.1.6 Communication Interface......................................................................................................... 9 2.1.7 Operations ................................................................................................................................ 9 2.1.8 Site Adaptation Requirement ................................................................................................... 9 2.2 Product Function ............................................................................................................................. 9 2.3 User Characteristics ...................................................................................................................... 10 2.4 Contraints ...................................................................................................................................... 10 2.5 Assumptions and Dependencies ................................................................................................... 10 2.6 Apportioning of Requirement ....................................................................................................... 10 3. Specific Requirements ...................................................................................................................... 11 3.1 External Interface Requirements .................................................................................................. 11 3.1.1 User Interface ......................................................................................................................... 11 3.2 System Product Feature ................................................................................................................ 12 3.2.1 Loan Information Management ............................................................................................. 12 3.2.2 Interest Rate Information Maintenance ................................................................................. 12 3.2.3 Report Generation .................................................................................................................. 13 3.2.4 User Account Information Maintenance ................................................................................ 14 3.3 Performance Requirement ............................................................................................................ 15 3.4 Design Constraints ........................................................................................................................ 15 2|Page
  • 3. 3.5 Software System Attributes .......................................................................................................... 15 3.5.1 Security .................................................................................................................................. 15 3.5.2 Maintainability ....................................................................................................................... 15 3.5.3 Portability............................................................................................................................... 15 3.6 Logical Database Requirement ..................................................................................................... 16 3|Page
  • 4. 1. Introduction In 2009, during the time of recession and financial sector was feeling the heat, a big consolidation took place in the sector. One of the leading investment banks Citibank sold 51% share of its Global wealth Management division, called Smith Barney, to Morgan Stanley. The remaining 49% would be with Citi group and the joint venture would be known as Morgan Stanley Smith Barney (MSSB). As of now, Citi has its own MIS and reporting system for variable loan products which Morgan Stanley does not have. Since business processes are not the same in two groups, there is a need to develop a new system to perform variable interest rate lending products reporting. The new system will be known as “Interest rate Management System” or IRMS. This document tries to define the overall software requirements for „Interest Rate Management System‟. It aims to define the requirements exhaustively and accurately. The final product will be having only features/functionalities mentioned in this document and assumptions for any additional functionality/feature should not be made by any of the parties involved in developing/testing/implementing/using this product. In this case it is required to have some additional features, a formal change request will need to be raised and subsequently a new release of this document and/or product will be produced as per the agreement. 1.1 Purpose This specification document describes the capabilities that will be provided by the software application „Interest Rate Management System‟. It also clearly mentions the various required constraints by which the system will abide. The intended audiences for this document are the development team, testing team and end-users (financial advisor in this case) of this product. 1.2 Scope The software product „Interest Rate Management System‟ will be an MIS and reporting application. The application will be used for managing the activities of library of Morgan Stanley Smith Barney. The application will manage the information of various clients and investors that have relationships with the investment bank, their wealth and assets, various lending product information, past association/track record, assigned investment banker/financial advisor‟s details and the net revenue generated. Printable reports regarding list of clients, investment bankers, historical data and other relevant details will be generated. The system will serve as MIS and reporting tool where rates are variable in nature. 4|Page
  • 5. 1.3 Definitions, Acronym, Abbreviation MSSB: IRMS: FA: User: LIBOR: DBA: IBM DB2: ASP: IIS: RAM: Morgan Stanley Smith Barney Interest Rate Management System Financial Advisor The login id having some or all access to the system London Inter-Bank Offered Rate Database Administrator Relational database developed by IBM Active Server Pages (a web page formatted on server and delivered to browser) Internet Information Services Random Access Memory 5|Page
  • 6. 2. Overall Description 2.1 Product Perspective The software product will be a web based system which would run on an intranet. It will also be connected to the outside world through a secured channel to gather real time data on interest rates. Internally, it would interact with several other systems to receive and disseminate data. 2.1.1 System Interface The Interest Rate Management System would need to interact with a variety of systems to facilitate the function. It will talk to following systems: The new system will interact, through the internet, to the external world. The base interest rates (LIBOR rates) are determined on a daily basis and released by Reuters. Hence the IRMS will fetch these daily feeds for its reporting purpose. The new system will take inputs from another system for client details and stores the same. Since IRMS is only a reporting tool, it does not have visibility to the new clients or changes in existing data. Such details will be taken from other internal systems every day. The job of IRMS is to serve as an MIS tool only. It does not process the loans or other 6|Page
  • 7. computations. For this purpose it submits data to other sub-systems. Any loans will be saved in IRMS first before any further processing. 2.1.2 User Interface The Interest Rate Management System will have a user friendly and menu based interface. Following screens will be provided: A Login screen for entering the username, password and role (Administrator, Financial Advisor, Management) will be provided. Access to different screens will be based upon the role of the user. There will be a screen which will list all borrower‟s data falling into a particular region, associated with a particular FA or from the same branch. The screen would give details like Loan No., Borrower Name, Address, Branch, FA, Loan Amount, Interest Rate, Interest Amount, Loan Issue Date, Next Installment Due Date and Loan status (active, pending, approved, rejected, cancelled or expired). The above list will have the Borrower name as a hyperlink. By clicking on the same, a new screen will appear with will list out the past record for the same recipient. The screen will have details like Loan No., Borrower Name, Address, Branch, FA, Loan Amount, Interest Rate, Issue Date and Loan Status. There will be a standalone screen which would display all lending products offered by MSSB. The screen will have details like Loan Product, Base rate, Spread (Premium) and Total Charged Rate. This base rate gets updated daily, based on Reuters input. There will be a search screen which will have the Loan No., Name, Branch, FA, Issue Date, Due Date, Loan Product, Loan status and fields. The fields will alone or with combination of other fields will be used to search a particular account or a set of accounts. There will be a screen which will facilitate the addition of new records. This screen is supposed to be used on the ad - face basis (actual updating will happen through a daily batch process). Only administrators will be able to perform this function. A separate screen would provide functionality to modify or delete an existing record. As mentioned above, only administrators will have authority to perform this function. One screen would be accessible to administrators only and contain audit information (changes done in the database). The following reports (only on demand basis) will be generated by this system: A report containing a list of all borrowers falling into a particular region, associated with a particular FA or from the same branch will be created. Reports can also be generated on other fields such as Loan issued on a specific date, for a definite installment date, accounts pertaining to same lending products and so on. A report containing historical records of any particular beneficiary for limited or all time period, 7|Page
  • 8. will be generated. A report containing a list of accounts in a desired time period along with their loan amounts will be created. A list showing the trend of rates (as determined by Reuters) for any one or all products for the past six months will be published. A report showing new added loan accounts in a given time period will be published. 2.1.3 Hardware Interface An extensive network base system as the system will be accessed by over 10000 FAs and expected concurrent users are in the range of 700-1000. Screen resolution of minimum 1024 X 768 is required for proper viewing of screens. Higher resolutions will not be an issue. User Machine Requirements: Support for the printing devices is required. Appropriate drivers should be available and installed. Printers (inkjet/deskjet/dot-matrix etc.) are connected properly for printing reports. Operating System: Windows 9x/XP or above/MAC/Unix Processor: Pentium 3.0 GHz or higher RAM: 512 MB or more Hard Drive: 10 GB or more Internet Browser: IE 6.0 or above Server Machine Requirements: Operating System: Windows 9x/XP or above Processor: Pentium 5.0 GHz or higher RAM: 4 GB or more Hard Drive: 500 GB or more Internet Browser: IE 6.0 or above 2.1.4 Software Interface Any Windows based operating system. Database: IBM DB2 Application: ASP (Active Server Pages) Web Server: IIS (Internet Information Services (IIS) is a powerful Web server that provides a highly reliable, manageable, and scalable Web application infrastructure. 8|Page
  • 9. 2.1.5 Memory Constraints Minimum memory requirement is 512 MB RAM and 10 GB space on hard disk for smooth running of this application. 2.1.6 Communication Interface None 2.1.7 Operations This product release will not cover any automated housekeeping aspects of the database. The DBA at the client side (with administrator level authority) will be responsible for manually deleting old/nonrequired data. Database backup and recovery will also have to be handled by the DBA. However, the system will provide a „Reset System‟ function that will delete (upon confirmation from the administrator) all the existing information from the database. 2.1.8 Site Adaptation Requirement The terminal at the client side will have to support the hardware and software interface specified in the above sections. 2.2 Product Function The system will allow access only to authorized user with specific roles. Depending upon user‟s role they will be able to access only specific modules of the system. A summary of the major functions that the software will perform is mentioned below: A login facility for enabling only authorized access to the system Users (with administrator authority) will be able to add/modify/delete information about the clients. User (with administrator authority) will be able to reset password and reset whole system. User (with access level other than administrator) will able to view all desired information but would not be able to make changes. User (with access level other than administrator) will be able to generate and print various reports as listed above. 9|Page
  • 10. 2.3 User Characteristics Educational Level: all FAs and managements will be having expertise in understanding financial products. The intended users are CFAs, MBAs, CFPs and so on. Experience: Should be well versed with financial markets and instruments and also the information required for maintaining the tables. Technical Expertise: Should be comfortable using general purpose applications on computer. Should have exposure to the internet and web browsing. 2.4 Constraints Due to limited features of the DBMS being used, database auditing will be provided. Also, as the number of records increase, the system will tend to get slower. Users will have to implement a security policy to safeguard information from being modified by unauthorized users. 2.5 Assumptions and Dependencies The number of records that will be displayed on one screen list will not be changed. The layout of input as well as output will not be altered. The system will depend upon inputs from the other system for its daily feed. The interest rates will have dependencies on the Reuters feed. 2.6 Apportioning of Requirement Not Required 10 | P a g e
  • 11. 3. Specific Requirements This is defined as the software requirements to a level of detail sufficient to design. 3.1 External Interface Requirements 3.1.1 User Interface Login Screen: This will be the first screen that will be displayed. It will allow user to access based upon the user‟s role. Various fields allow users access based upon the user‟s role. Various fields are User ID: Alphanumeric of length up to 10 characters Role: will have the following values: Administrator, FA, Management Listing Screen: This screen would provide functionality for listing out of client information. This screen will be available to all users. Users have to provide search fields in order to filter the data. Detail Screen: This screen would provide historical data of a particular client. The screen is also available to all users. Reference Screen: This screen is used to view all loan products on that given day. This screen is also available to all users. Search screen: This screen is used for searching a particular client or a set of client based on search criteria. It will be accessible to all users. Insert Screen: This screen is only available to administrators. It will facilitate adding a new record. Update Screen: It will be used to modify or delete an existing record and will be accessible to administrators only. 11 | P a g e
  • 12. Audit Screen: This screen is used for displaying all changes done in the database by a particular or all administrators. It will be accessible only to users with administrators authority. 3.2 System Product Feature 3.2.1 Loan Information Management Description: The system will maintain information about various loans being issued during different time periods. The following information would be maintained for the loans: Loan No., Borrower Name, Address, Branch, FA, Loan Amount, Interest Rate, Interest Amount, Loan Issue Date, Next Installment Due Date and Loan status Validity Check: Only FAs, Management and Administrators will have authorized access. Each loan will have a unique loan number. Each loan will have only one lending products in its entire cycle. Loan No., borrower‟s name, address, branch, loan amount and loan status can not be spaces. Error Handling/Response to Abnormal Situations: If any of the above validations/sequencing flow does not hold true, appropriate error messages will be prompted to the user for doing the needful. 3.2.2 Loan Product Information Maintenance Description: The system will maintain information about various lending products that are issued by Reuters. This information will be backed up for a period of 6 months. Following information will be maintained for each product: Loan Product 12 | P a g e
  • 13. Base rate Spread (Premium) Total Charged Rate Date The system will allow addition/modification or deletion of the records. This will assist in having only the offered product information. The changes could only be done by administrators. Validity Check: Only FAs, Management and Administrators will have authorized access. Each loan product will be pegged with at least one base rate. Loan Product Name, Base Rate, Date, Total Charged Rate could not be spaces. Error Handling/Response to Abnormal Situations: If any of the above validations/sequencing flow does not hold true, appropriate error messages will be prompted to the user for doing the needful. 3.2.3 Report Generation Loan Information: This report would give information about the various loans depending upon the search/filter criteria. Report Format: Morgan Stanley Smith Barney Interest Rate Management System Loan Summary Report Loan No. Name of Address Branch FA Amount Borrower of Loan Interest Rate Interest Amount Loan Issue Date Due Date Status 13 | P a g e
  • 14. Lending Product Information: This report would give information about the various products offered depending upon the time period. Report Format: Morgan Stanley Smith Barney Interest Rate Management System Product Summary Report Loan Products Base Rate Spread Total Charged Rate Date 3.2.4 User Account Information Maintenance Description: The system will maintain information about various users who would be able to use the system. The following information would be maintained. User name User Id Password Role Validity Check: Only users with role FA/Administrator and the management will be authorized to access the User Accounts Information Maintenance Module. None of the fields (user name, user id, password or role) can be blank. There should be a unique user id for every user. Sequencing Information User Account for a particular user has to be created in order for the system to be accessible to that user. At system start up, only a default user account for „Administrator‟ would be present in the system. 14 | P a g e
  • 15. Error Handling/Response to Abnormal Situations: If any of the above validations/sequencing flow does not hold true, appropriate error messages will be prompted to the user for doing the needful. 3.3 Performance Requirement The system should be capable of handling large amount of data. It should be able to run queries on 1 billion records. The system should facilitate a total of 15000 user logins. The system should be able to run for 700-1000 concurrent logins. 3.4 Design Constraints None 3.5 Software System Attributes 3.5.1 Security The application will be password protected. Users will have to enter correct username, password and role in order to access the application. All the external interfaces such as through the internet or with other system will have an additional middle layer which would act as security firewall. 3.5.2 Maintainability The system will be designed in a maintainable manner. It will be easy to incorporate new requirements. 3.5.3 Portability The system will be easily portable to any Windows based system that has MS Office 2007 installed. 15 | P a g e
  • 16. 3.6 Logical Database Requirement Following information will be placed in the database. Loan Info: Loan No., Borrower Name, Address, Branch, FA, Loan Amount, Interest Rate, Interest Amount, Loan Issue Date, Next Installment Due Date and Loan status Product Info: Loan Product, Base Rate, Spread, Total Charged Rate, Date User Info: User name, User Id, Password, Role Audit Info: User Id, Date, Time, Table, Comment 16 | P a g e