SOFTWARE REQUIREMENT SPECIFICATION

Software Requirement Specification (SRS) for
Personal Investment Management System
(PIMS)
1. Introduction
1.1 Purpose:
Personal Investment Management System (PIMS) is intended to help the user
keep account of his/her money invested in institutions such as Banks and Share
Market.
This document is meant to delineate the features of PIMS, so as to serve as a
guide to the developers on one hand and a software validation document for the
prospective client on the other.
1.2 Scope:
We describe what features are in the scope of the software and what are not in
the scope of the software to be developed.
In Scope:
a. Managing investment of a single user, which would include maintaining
bookkeeping information about entities like Portfolio, Security, and
Transaction.
b. Computation of Net-Worth and Rate of Investment (ROI) of the Investor.
c. Giving alerts to the user, if he requests for one.
d. Downloading the current prices of shares from the web.
e. User authentication.
Out of Scope:
a. Features for actual purchasing and selling of securities. That is, actually
buying and selling of shares/securities is done outside PIMS.
b. Tax computations for gains/losses.
c. Any market related prediction.
1.3 Definitions, Acronyms, and Abbreviations:
Acronyms and Abbreviations:
a. PIMS: Personal Investment Management System.
b. SRS: Software Requirements Specification.
c. WWW: World Wide Web.
d. GUI: Graphical User Interface.
e. ROI: Rate of Investment.
2
Definitions:
a. Transaction: A real event that involves flow of personal money. In the context
of shares, it is buying/selling a group of shares of the same company, and in
context of Bank it is deposit/withdrawal of money to/from one’s account.
b. Security: A set of all transactions pertaining to a company share or a bank
account.
c. Portfolio: A set of Securities.
d. Net-Worth: The sum total of all the money of the investor in form of shares
and bank balances.
e. ROI: The interest that user gets on a particular investment. In the context of a
bank account it is the annual interest and in case of a company share it is
defined as given in appendix A:
1.4 References:
Appendix A: Formula for ROI calculation for shares.
Appendix B: Formula for Net-Worth calculation.
Appendix C: User Screens.
1.5 Overview:
The rest of this SRS is organized as follows: Section 2 gives an overall description
of the software. It gives what level of proficiency is expected of the user, some
general constraints while making the software and some assumptions and
dependencies that are assumed. Section 3 gives specific requirements which the
software is expected to deliver. Functional requirements are given by various use
cases. Some performance requirements and design constraints are also given.
Section 4 gives some possible future extensions of the system. Finally the
appendices in Section 5 describe respectively the formula for ROI calculation for
shares and user screen.
2. Overall Description:
2.1 Product Perspective:
PIMS is aimed toward a person who has considerable number of investments in
stock market and banks, and so needs software assistance for book keeping and
computations regarding the investments. PIMS should be user-friendly, ‘quick to
learn’ and reliable software for the above purpose.
PIMS is intended to be a stand-alone product and should not depend on the
availability of other software. It should run on both UNIX and Windows based
platform.
2.2 Product Functions:
PIMS should support the following use cases:
3
Class of use cases Use cases Description of use cases
Use case related to
Installation
Installation Creates and initializes working files.
Use cases related to Login Login into PIMS
system authorization Change Password Change PIMS password
Create portfolio Creates a new portfolio
Rename portfolio Rename an existing portfolio
Use cases related to
portfolios
Delete portfolio Delete an existing portfolio
Create security Creates a new security in a given
portfolio
Rename security Renames an existing security
Use cases related to
securities
Delete security Deletes an existing security
Add transaction Add a transaction to a security
Edit transaction Edit an existing transaction
Use cases related to
transactions
Delete transaction Delete an existing transaction
Display investment Display information of the entire
investment
Display portfolio Display information about a given
portfolio
Use cases related to
Information display
Display security Display information about a given
security
Compute net-worth Compute net-worth of
investment/portfolio/security
Use cases related to
computations
Compute ROI Compute ROI of a given security
Get current share price Download the current share price
from the net
Use cases related to share
prices
Edit share price Edit the price of a share already
present in the list
Set alerts Set alert giving date and details
Show alerts Show all the pending alerts
Use cases related to alerts
Delete alerts Delete an already set alert
2.3 User Characteristics:
a. The user should be familiar with the Investment Management related
terminology like Portfolio/Security/Transaction.
b. The user should know the details of a transaction.
2.4 Principal Actors:
The two principal actors in PIMS are “user” and “system”.
2.5 General Constraints:
a. For full working PIMS requires Internet connection.
b. PIMS is single-user software.
2.6 Assumptions and Dependencies:
4
a. Full working of PIMS is dependent on the availability of Internet connection.
b. The downloading of share prices in PIMS is customized to
www.indiainfoline.com. PIMS would not work for any other website.
c. The company shares registered in the National Stock Exchange (NSE) are
only considered by PIMS.
3 Specific Requirements:
3.1 Functional Requirements:
We describe the functional requirements by giving various use cases.
Use case related to installation:
Use Case 1: Installation
Primary Actor: User
Pre Condition: Internet connection available.
Main Scenario :
1. User initiates PIMS installation program.
2. System asks the user for the home directory in which all the working
files will be created. User is also asked for the initial login and
password.
3. User specifies the home directory and login/password.
4. System creates the working files in the specified home directory.
Working files contain:
a. Authorization information.
b. List of company names.
c. Current share prices.
d. Investment structure.
5. System downloads the list of companies (registered in NSE, from
www.indiainfoline.com) and the current share prices. It initializes the
files containing the list of companies and the current share prices with
the downloaded data.
Alternate Scenario:
5(a). Network failure.
5(a)1. Installation aborted.
Use cases related to system authorization:
Use Case 2: Login
Primary Actor: User
Pre Condition: Nil
Main Scenario :
1. Start the application. User prompted for login and password.
2. User gives the login and password.
3. System does authentication.
4. Main screen is displayed.
Alternate Scenario :
4(a). Authorization fails
4(a)1. Prompt the user that he typed the wrong password
5
4(a)2. Allow him to re-enter the password. Give him 3 chances.
Use Case 3: Change Password
Primary Actor: User
Pre Condition: User logged in
Main Scenario :
1. User initiates the password change command.
2. User is prompted for old password, new password and confirm new
password.
3. User gives the old password, new password and confirm new
password.
4. System does authentication.
5. New password is registered with the system.
Alternate Scenario :
4(a). Authorization fails
4(a)1. Prompt the user that he typed the wrong password
4(a)2. Allow him to re-enter the password. Give him 3 chances.
4(b). New password and confirm new password do not match.
4(b)1. Allow him to re-enter the attributes. Give 3 chances.
Use cases related to portfolios:
Use Case 4: Create Portfolio
Primary Actor: User
Pre Condition: User logged in.
Main Scenario:
1. User initiates the “create portfolio” functionality.
2. System asks the user for the portfolio name.
3. User enters the portfolio name.
4. An empty portfolio is created.
Alternate Scenario:
4(a). Portfolio with the same name exists.
4(a)1. System asks the user for a different name.
4(a)2. User enters a different name.
4(a)3. Empty portfolio gets created.
Use Case 5: Rename portfolio.
Primary Actor: User
Pre-Condition: User logged in.
Main Scenario :
1. User initiates the “rename portfolio” functionality.
2. System asks for the portfolio to be renamed and the new name.
3. User enters the new name.
4. Portfolio is renamed.
Alternate Scenario:
4(a). The portfolio whose name is supposed to change does not exist.
4(a)1. Renaming fails, the error message is displayed.
4(b). Portfolio with the same new name exists