Software Requirements Specification for CPSI Page 1

1. Introduction
‘Customized portal for stock investor’ is a useful portal for the small stock investors. User can
make their account. Reports can be generated on user demand. Overall market statistics can be
viewed.

1.1 Purpose
1.1.1 Problem Statement

Nowadays there is a lot of competition in market for investors and businessmen but when it comes to face
difficulties small investors are among the most affected. As they are not well aware of the prices of stock,
market rates, competitors, profit/loss chance, highest bidders, lowest bidders, new investment opportunities
etc. This causes them to lose their money without any backup plan.

1.1.2 Problem Solution

We are going to introduce the “Customized Portal for Stock Investor” which can help small investors
with their difficulties and help them invest their money after judging the market according to the
opportunities. This portal will allow them to view current market rates, profit, loss, competitors, stock
etc.

1.2 Scope
Customized investment portal will provide small investors a variety of options. They can cope with
their difficulties of inexperience as this system will provide them a platform to view and analyze
market rates and do investments accordingly. Static data from stock markets shall be provided through
which small investors can judge market situation and can know about their competitors. They can
track the market prices, stock prices, availability and unavailability of stocks, profit/loss chances can
be guessed as all the market related activities shall be shown to them. High market value stocks and
company with high shares in the market are to be displaced in the top. Profit shall be shown as green
arrow pointing upwards while loss shall be shown as red arrow pointing downwards. Data shall be
manipulated as new investors come in the market and effect the stock rates and market prices.
Investors shall be successful in investing their money with confidence. Investments shall be done
manually according to investor’s interest.

1.2.1 Modules
1.2.1.1 Admin Panel
Admin is only required for maintaining the system as following.

 Add new company

Admin can add new company by keeping in mind the listed company in the PSX.

 Remove company
Once the company is shut down, removed from the PSX admin can remove it from the listed
company.
Software Requirements Specification for CPSI Page 2

 Update data
Admin can update data on regular basis from the PSX which shall be in raw form initially
i.e. .lis files.

 Generate Daily Report

Admin can generate daily report based upon the market behavior and save it in the system.

1.2.1.2 User Panel

In this system user shall be stock investor who can be facilitated as following

 Account Management
All the management related to a user profile shall be handled.

 Add Invested Stocks

User can add invested stocks with the help of built in form which will help trace
profit/loss according to the market behavior.

 Update profile
The user will update the personal details & their investments

 Add company to profile

The user will add a new company to his profile dashboard.

 Remove company from profile

The user will remove the company from his profile dashboard.

 Reports

 Generate Report
All the reports related to a particular user shall be generated i.e. daily, weekly,
monthly, quarterly, bi-annually, annually.

 Print Report
User can print a specific report directly from the system.

 Save Report
User can save a particular report in their account.

 Download Report
User can download any report which is saved previously in the system or is
generated.

 Delete Report
User can delete any report saved in the system.

 View Report
Software Requirements Specification for CPSI Page 3

User can view a particular report from different reports in the system.

1.2.1.3 Guest Panel

In this system, guest is facilitated as following

 Sign Up
Guest can sign up whenever needed

 View Daily Report

Guest can view daily reports which are previously generated and saved in the system by the admin.

1.3 Definitions, Acronyms and Abbreviations

1.3.1 Abbreviations

CPSI: Customized Portal for Stock Investor

SRS: Software Requirements Specification
UC: Use case
PSX: Pakistan stock exchange

2. Use Case(s)

2.1 Use Case Diagram

2.1.1 Guest
Software Requirements Specification for CPSI Page 4

2.1.2 Admin
Software Requirements Specification for CPSI Page 5
Software Requirements Specification for CPSI Page 6

2.1.3 User
Software Requirements Specification for CPSI Page 7

2.2 Use Cases Table

UC-No Primary Use Cases

Actor
UC-1 Guest Sign Up

UC-2 Admin, User Sign in

UC-3 Admin, User Sign out

UC-4 Admin Update data

UC-5 Admin Add new Company

UC-6 Admin Remove Company

UC-7 User Update Profile

UC-8 User Search Company

UC-9 User Add company to profile

UC-10 User Remove company from profile

UC-11 User View Personal investments

UC-12 User, Admin Generate Daily report

UC-13 User Generate Weekly report

UC-14 User Generate Monthly report

UC-15 User Generate Quarterly report

UC-16 User Generate Bi-Annually report

UC-17 User Generate Annually report

UC-18 User Save report

UC-19 User Print report

UC-20 User Download Report

Software Requirements Specification for CPSI Page 8

UC-21 User Delete Report

UC-22 Guest, User View Report

UC-23 User Add invested stocks

2.3 Use Case Description

Use Case UC-01

ID:
Use Case Sign up
Name:
Actors: Guest
Description: In sign up, guest can sign up to use site as a registered user.
Trigger: Guest will click on ‘Sign Up’ button.
Preconditions: Guest must have unique name and password
Post conditions: 1. Guest will sign in to account
2. Guest will use a site as a registered user
Normal Flow: 1. The Guest browses the website.
2. The Guest clicks signup button.
3. A form appears on browser.
4. The Guest enters username.
5. The Guest enters password.
6. The User re-enters password.
7. The Guest enters Email address
8. Guest clicks “Sign Up” button.
9. System displays confirmation message “You have Signed
Up successfully”.
Alternative N/A
Flows:
Exceptions: 7a In case re-entered password does not match with already entered
password
1. Warning message shall be shown to the Guest
2. Guest re-enters password.
Use case resumes at the step 8 of the use case.

8a In case email already exists.

1. The system displays message “email already exist”.
2. The Guest re-enters email.
The flow will resume from step 8 of normal flow.
Software Requirements Specification for CPSI Page 9

6a If Guest enters invalid password

1. Warning message shall be shown to the Guest.
2. Guest re-enters the password
Use case resumes at the step 7 of the use case
Includes: N/A
Assumptions: Internet connection is available
Guest can understand English
Notes and Password should be at least 8 characters long
Issues:

Use Case UC-02

ID:
Use Case Sign In
Name:
Actors: User, Admin
Description: This use case authenticates the user.
Trigger: User clicks on the ‘Sign In’ button.
Preconditions: User is already registered.
Post conditions: User logged in successfully.
Normal Flow: 1. The user browses the website.
2. The user clicks on the login button.
3. System displays a login form.
4. User enters the Username.
5. User enters the Password.
6. The System validates the Username and Password
7. User logged in to the system successfully.
Alternative N/A
Flows:
Software Requirements Specification for CPSI Page 10

Exceptions: 4a If the username is incorrect

1. The system displays an error message.
2. The user re-enters the username.
Use Case resumes on the step 5 of the Normal Flow

5a If the Password is Incorrect

1. The system displays an error message.
2. The user Re-enter password.
Use Case resumes on the step 6 of the Normal Flow

6a User account does not exit.

1. System display a message “User account does not found.”
2. Use case ends.
Includes: UC-01
Assumptions: 1. Internet Availability
2. Knowhow of system

Notes and N/A

Issues:

Use Case UC-03

ID:
Use Case Sign Out
Name:
Actors: User, Admin
Description: In sign out , user will signed out from the site
Trigger: User will click on ‘Sign Out’ button.
Preconditions: 1. User must be registered.
2. User must be logged in to site.

Post conditions: 1. User will sign out from the site

2. User will not be able to use as a registered users privileges.
Normal Flow: 1. User will click on “sign out” option
2. User will move to the homepage.
Alternative N/A
Flows:
Exceptions: N/A
Includes: UC-02
Assumptions: N/A
Notes and N/A
Issues:
Software Requirements Specification for CPSI Page 11

Use Case UC-04

ID:
Use Case Update data
Name:
Actors: Admin
Description: Admin will update the system with new data.
Trigger: When admin clicks the ‘Update data’ button
Pre-conditions: Admin must have the data file in the .LIS format from the PSX
website.

Post-conditions: The data is updated in the system.

Normal Flow: 1. Admin clicks the “update data” button.
2. Admin selects the data file.
3. Admin uploads the .lis file.
4. The data is updated.
Alternative N/A
Flows:

Exceptions:
2a Format not supported e.g. other than .lis file
1. Admin is prompted to select the file again

Use case resumes on the step 3 of normal flow

Includes: UC-02
Assumptions: N/A
Notes and Only one file can be uploaded at a time.
Issues:

Use Case UC-05

ID:
Use Case Add new Company
Name:
Actors: Admin
Description: Admin will add a new company to the stock market company index
list.
Trigger: When admin clicks on ‘add new company’
Preconditions: Admin shall be Signed In
Post conditions: A new company is added and listed in the index.
Software Requirements Specification for CPSI Page 12

Normal Flow: 1. Admin clicks the Add New company button.

2. A new form shall be opened.
3. Admin enters the company name.
4. Admin enters the company symbol.
5. Admin press enter.
6. New company is added

Alternative N/A
Flows:

Exceptions:

3a The company name already exists.

1. The system displays an error message.
2. The users re-enters the company name.
Use case resumes on the step 4 of the normal flow.

4a The company symbol already exists.

1. The system displays an error message.
2. The users re-enters the company symbol.
Use case resumes on the step 5 of the normal flow
Includes: UC-02
Assumptions: The company is already registered in the PSX.
Notes and N/A
Issues:

Use Case UC-06

ID:
Use Case Remove Company
Name:
Actors: Admin
Description: Admin will remove the company from the list.
Trigger: ‘Remove company’ button is pressed.
Preconditions: Admin is signed in to the system.
Post conditions: The company shall be removed from the list.
Normal Flow: 1. The admin will click on the remove company button.
2. A list of companies shall be shown to the admin.
3. Admin will select the company to remove from the given list.
4. Admin will click the delete button.
Alternative N/A
Flows:
Software Requirements Specification for CPSI Page 13

Exceptions: N/A

Includes: UC-02
Assumptions: The company shut down its operations and is no longer trading its
stocks in the market.
Notes and N/A
Issues:

Use Case UC-07

ID:
Use Case Update Profile
Name:
Actors: User
Description: The user will update the personal details & their investments
Trigger: User clicks the ‘Update profile’ button.
Preconditions: User should be signed In.
Post conditions: The profile shall be updated.
Normal Flow: 1. The user clicks on the update profile button.
2. The editable profile form shall be shown to the user.
3. The user will update the fields.
4. User will press the confirm button.
Alternative N/A
Flows:

Exceptions: 3a If the Password is Incorrect

1. The system displays an error message.
2. The user Re-enters password.
Use Case resumes on the step 4 of the Normal Flow

Includes: UC-02
Assumptions: N/A
Notes and N/A
Issues:

Use Case UC-08

ID:
Use Case Search Company
Name:
Actors: User
Software Requirements Specification for CPSI Page 14

Description: The user will search for a particular company from a list of companies.
Trigger: User clicks on the ‘search company’ button
Preconditions: User must be signed in.
Post conditions: The particular company is found and it is shown to the user.
Normal Flow: 1. The user clicks on the search button.
2. A search box is displayed.
3. The user enters the company name and press enter.
4. The company is shown.
Alternative N/A
Flows:

Exceptions: 3a The company name is not found.

1. The user is prompted that the company is not in the list.
2. The user is asked to reenter the company name.
Use case resumes to the step 3 of the normal flow.
Includes: UC-02
Special N/A
Requirements:
Assumptions: N/A
Notes and N/A
Issues:

Use Case UC-09

ID:
Use Case Add Company to profile
Name:
Actors: User
Description: The user will add a new company to his profile dashboard.
Trigger: ‘Add company’ button is pressed.
Preconditions: The User must be signed in.
Post conditions: A new company is added to the profile dashboard.
Normal Flow: 1. The user clicks the add company button.
2. The list of companies is shown.
3. User selects the particular company.
4. User clicks the add button.
5. The company is added to the profile dashboard.
Alternative 3a User searches the company.
Flows: 1. The user clicks the search button
2. The search box is shown.
3. User enters the name and press enter.
4. The company is shown.
Use case resumes at step 4 of the normal flow.
Software Requirements Specification for CPSI Page 15

Exceptions: 3a,
3a The company name is not found.
1. The user is prompted that the company is not in the list.
2. The user is asked to reenter the company name.
Use case resumes to the step 3 of the alternative flow.

Includes: UC-02
Special N/A
Requirements:
Assumptions: N/A
Notes and N/A
Issues:

Use Case UC-10

ID:
Use Case Remove Company from profile
Name:
Actors: User
Description: The user will remove the company from his profile dashboard.
Trigger: ‘Remove company’ button is pressed.
Preconditions: The User must be signed in.
Post conditions: A company is removed from the profile dashboard.
Normal Flow: 1. The user clicks the remove button.
2. The list of companies is shown.
3. User selects the particular company.
4. User clicks the remove button.
5. The company is removed from the profile dashboard.
Alternative 3a User searches the company.
Flows: 1. The user clicks the search button
2. The search box is shown.
3. User enters the name and press enter.
4. The company is shown.
Use case resumes at step 4 of the normal flow.
Exceptions: 3a The company name is not found.
1. The user is prompted that the company is not in the list.
2. The user is asked to reenter the company name.
Use case resumes to the step 3 of the normal flow.

Includes: UC-02, UC-09

Software Requirements Specification for CPSI Page 16

Assumptions: N/A
Notes and N/A
Issues:

Use Case UC-11

ID:
Use Case View Personal Investments
Name:
Actors: User
Description: All the investments done by a particular user up till now shall be
displayed.
Trigger: Click the personal investments tab
Preconditions: 1. User must be signed In
2. User must have previously invested in some company.

Post conditions: A summary of the investments shall be shown.

Normal Flow: 1. The user opens his profile.
2. The user opens his investment dashboard
3. The user clicks the Summary tab.
4. A complete summary of the investments shall be shown.
Alternative N/A
Flows:

Exceptions: N/A
Includes: UC-02
Assumptions: N/A
Notes and N/A
Issues:

Use Case UC-12

ID:
Use Case Generate Daily Report
Name:
Actors: User, Admin
Description: A daily report shall be generated according to the market proceeding.
Trigger: User clicks the ‘generate daily report’ button.
Preconditions: 1. User must be signed in.
2. A time frame of 24 hours must be passed since the last report
has been generated.
Post conditions: A report in shall be generated.
Software Requirements Specification for CPSI Page 17

Normal Flow: 1. The user opens his profile.

2. The user opens his dashboard
3. The user clicks the Reports tab.
4. The user clicks the daily Report button.
5. A report shall be generated.
Alternative N/A
Flows:

Exceptions: 4a A time of 24 hours is not passed.

1. User shall be prompted to wait until the next report generation
time occurs.
Use case ends.

Includes: UC-02
Assumptions:
Notes and N/A
Issues:

Use Case UC-13

ID:
Use Case Generate Weekly Report
Name:
Actors: User
Description: A weekly report shall be generated according to the market proceeding.
Trigger: User clicks the ‘generate weekly report’ button.
Preconditions: 1. User must be signed in.
2. A time frame of 7 days must be passed since the last report has
been generated.
Post conditions: A report in shall be generated.
Normal Flow: 1. The user opens his profile.
2. The user opens his dashboard
3. The user clicks the Reports tab.
4. The user clicks the weekly Report button.
5. A report shall be generated.
Alternative N/A
Flows:
Software Requirements Specification for CPSI Page 18

Exceptions: 4a A time of 7 days is not passed.

1. User shall be prompted to wait until the next report generation
time occurs.
Use case ends.

Includes: UC-02
Assumptions:
Notes and N/A
Issues:

Use Case UC-14

ID:
Use Case Generate Monthly Report
Name:
Actors: User
Description: A monthly report shall be generated according to the market
proceeding.
Trigger: User clicks the ‘generate monthly report’ button.
Preconditions: 1. User must be signed in.
2. A time frame of 30 days must be passed since the last report
has been generated.
Post conditions: A report in shall be generated.
Normal Flow: 1. The user opens his profile.
2. The user opens his dashboard
3. The user clicks the Reports tab.
4. The user clicks the monthly Report button.
5. A report shall be generated.
Alternative N/A
Flows:

Exceptions: 4a A time of 30 days is not passed.

1. User shall be prompted to wait until the next report generation
time occurs.
Use case ends.

Includes: UC-02
Assumptions:
Software Requirements Specification for CPSI Page 19

Notes and N/A

Issues:

Use Case UC-15

ID:
Use Case Generate Quarterly Report
Name:
Actors: User
Description: A quarterly report shall be generated according to the market
proceeding.
Trigger: User clicks the ‘generate quarterly report’ button.
Preconditions: 1. User must be signed in.
2. A time frame of 3 months must be passed since the last report
has been generated.
Post conditions: A report in shall be generated.
Normal Flow: 1. The user opens his profile.
2. The user opens his dashboard
3. The user clicks the Reports tab.
4. The user clicks the quarterly Report button.
5. A report shall be generated.
Alternative N/A
Flows:

Exceptions: 4a A time of 3 months is not passed.

1. User shall be prompted to wait until the next report generation
time occurs.
Use case ends.

Includes: UC-02
Assumptions:
Notes and N/A
Issues:

Use Case UC-16

ID:
Use Case Generate Bi-Annually Report
Name:
Actors: User
Description: A bi-annually report shall be generated according to the market
proceeding.
Trigger: User clicks the ‘generate bi-annually report’ button.
Software Requirements Specification for CPSI Page 20

Preconditions: 1. User must be signed in.

2. A time frame of 6 months must be passed since the last report has
been generated.
Post conditions: A report in shall be generated.
Normal Flow: 1. The user opens his profile.
2. The user opens his dashboard
3. The user clicks the Reports tab.
4. The user clicks the bi-annually Report button.
5. A report shall be generated.
Alternative N/A
Flows:

Exceptions: 4a A time of 6 months is not passed.

1. User shall be prompted to wait until the next report generation
time occurs.
Use case ends.

Includes: UC-02
Assumptions:
Notes and N/A
Issues:

.
Use Case UC-17
ID:
Use Case Generate Annually Report
Name:
Actors: User
Description: Annually report shall be generated according to the market proceeding.
Trigger: User clicks the ‘generate annually report’ button.
Preconditions: User must be signed in.
A time frame of 12 months must be passed since the last report has
been generated.
Post conditions: A report in shall be generated.
Normal Flow: 1. The user opens his profile.
2. The user opens his dashboard
3. The user clicks the Reports tab.
4. The user clicks the annually Report button.
5. A report shall be generated.
Software Requirements Specification for CPSI Page 21

Alternative N/A
Flows:

Exceptions: 4a A time of 12 months is not passed.

1. User shall be prompted to wait until the next report generation
time occurs.
Use case ends.

Includes: N/A
Assumptions: N/A
Notes and N/A
Issues:

Use Case UC-18

ID:
Use Case Save Report
Name:
Actors: User
Description: The user will save the report that was generated.
Trigger: When ‘Save report’ button is clicked
Preconditions: 1. The user must be signed in.
2. The report must be generated first.

Post conditions: The report shall be saved in the profile of the user.
Normal Flow: 1. The user opens his profile.
2. The user opens his dashboard.
3. The user clicks the Reports tab.
4. The user clicks to generate any type of report.
5. The report is generated
6. The user clicks the ‘Save Report’ button.
7. The report shall be saved in the user profile.
Alternative N/A
Flows:

Exceptions: N/A

Includes: UC-02, UC-12, UC-13, UC-14, UC-15, UC-16, UC-17

Assumptions:
Notes and N/A
Issues:
Software Requirements Specification for CPSI Page 22

Use Case UC-19

ID:
Use Case Print Report
Name:
Actors: User
Description: The user will print the report that was generated or saved.
Trigger: When ‘print report’ button is clicked
Preconditions: 1. The user must be signed in.
2. The report must be generated first.

Post conditions: The report shall be printed.

Normal Flow: 1. The user opens his profile.
2. The user opens his dashboard.
3. The user clicks the Reports tab.
4. The user clicks the ‘Print Report’ button.
5. The report shall be printed.
Alternative N/A
Flows:

Exceptions: 4a Printer not found

1. User shall be prompted to check that printer is attached and try
again.
Use case resumes from step 4 of normal flow.

Includes: UC-02, UC-12, UC-13, UC-14, UC-15, UC-16, UC-17

Assumptions:
Notes and N/A
Issues:

Use Case UC-20

ID:
Use Case Download Report
Name:
Actors: User
Description: The user will download the report that was generated or saved.
Trigger: When ‘download report’ button is clicked
Preconditions: 1. The user must be signed in.
2. The report must be generated first.

Post conditions: The report shall be downloaded.

Software Requirements Specification for CPSI Page 23

Normal Flow: 1. The user opens his profile.

2. The user opens his dashboard.
3. The user clicks the Reports tab.
4. The user clicks the ‘Download Report’ button.
5. The report shall be downloaded.
Alternative N/A
Flows:

Exceptions: N/A

Includes: UC-02, UC-12, UC-13, UC-14, UC-15, UC-16, UC-17, UC-18

Assumptions:
Notes and N/A
Issues:

Use Case UC-21

ID:
Use Case Delete Report
Name:
Actors: User
Description: The user will delete the report that was generated and saved.
Trigger: When ‘Delete report’ button is clicked
Preconditions: 1. The user must be signed in.
2. The report must be generated first.

Post conditions: The report shall be deleted.

Normal Flow: 1. The user opens his profile.
2. The user opens his dashboard.
3. The user clicks the Reports tab.
4. The user clicks the Delete Report button.
5. The report shall be deleted.
Alternative N/A
Flows:
Software Requirements Specification for CPSI Page 24

Exceptions: 4a Conformation dialogue box is shown

1. User has to press ‘Yes’ for deleting the report.
2. User has to press ‘No’ for going back.
Use case resumes from step 4

Includes: UC-02, UC-12, UC-13, UC-14, UC-15, UC-16, UC-17, UC-18

Assumptions:
Notes and N/A
Issues:

Use Case UC-22

ID:
Use Case View Report
Name:
Actors: User
Description: The user will view the report that was generated and saved.
Trigger: When View report button is clicked
Preconditions: 1. The user must be signed in.
2. The report must be generated first.

Post conditions: The report shall be viewed.

Normal Flow: 1. The user opens his profile.
2. The user opens his dashboard.
3. The user clicks the Reports tab.
4. The user clicks the View Report button.
5. The report shall be viewed.
Alternative N/A
Flows:

Exceptions: N/A

Includes: UC-02, UC-12, UC-13, UC-14, UC-15, UC-16, UC-17, UC-18

Assumptions:
Notes and N/A
Issues:

Use Case UC-23

ID:
Software Requirements Specification for CPSI Page 25

Use Case Add invested stocks

Name:
Actors: User
Description: The user will add the information about the stocks that they have
invested in the particular company.
Trigger: When the user clicks the Add Stocks button.
Preconditions: The user must be signed in
Post conditions: The stocks info related to a particular user shall be added in the profile.
Normal Flow: 1. The user opens his profile.
2. The user opens his dashboard.
3. The user clicks the Investments tab.
4. The user clicks the Add Stocks button.
5. A form shall be viewed.
6. The user will enter the name of the company.
7. The user will enter the amount of stocks invested from drop
down menu.
8. The user will enter the price (in rupees) at which stocks are
purchased.
9. The user will enter the date of investment from drop down
menu.
10. User will click the Save button to add the information.

Alternative
Flows:
6a. User selects the company from the list.
1. User selects the particular company.
2. User clicks the add button.
3. The company is added to the form
Use case resume on step 7 of the normal flow.

Exceptions: 6a The company name does not exists.

1. The system displays a warning message.
2. The users re-enters the company name.
Use case resumes on the step 7 of the normal flow.

Includes: N/A
Assumptions:
Notes and N/A
Issues:
Software Requirements Specification for CPSI Page 26

3. Specific Requirements

3.1 Functionality
3.1.1 Add new company

Identifier FR-01
Title Add new company
Requirement The admin shall be able to add a new company in the system which shall
be present in the PSX.
Source Supervisor
Rationale Keeping the company updated.
Restrictions and Risk The admin cannot add a duplicate company.
Dependencies FR-02
Priority High

3.1.2 Remove company

Identifier FR-02
Title Remove company
Requirement The admin shall be able to remove a company from the system which is
shut down.
Source Supervisor
Rationale Keeping the company updated.
Restrictions and Risk The admin may remove active company.
Dependencies N/A
Priority High

3.1.3 Update data

Identifier FR -03
Title Update data
Requirement The admin shall be able to update data on daily basis with the help of .lis
files taken from PSX website.
Source Supervisor
Rationale Keeping the overall system up to date.
Restrictions and Risk Format of the files to be uploaded should be .lis.
Dependencies N/A
Priority High

3.1.4 Generate daily report

Identifier FR -04
Title Generate daily report
Requirement The admin/user shall be able to generate daily report according to market
statistics.
Source Supervisor
Rationale To help guests analyze the market.
Software Requirements Specification for CPSI Page 27

Restrictions and Risk 24 hours should pass before generating new report.
Dependencies N/A
Priority High

3.1.5 Sign in

Identifier FR -05
Title Sign in
Requirement User shall sign in before using the system.
Source Supervisor
Rationale To help users login to system.
Restrictions and Risk User shall press ‘sign in’ to perform the action.
Dependencies FR-08
Priority High

3.1.6 Insert username

Identifier FR -06
Title Insert username
Requirement User shall insert username in the specified box.
Source Supervisor
Rationale To help users login to system.
Restrictions and Risk User shall click the specified box to perform the action.
Dependencies FR-07
Priority High

3.1.7 Insert password

Identifier FR -07
Title Insert password
Requirement User shall insert password in the specified box.
Source Supervisor
Rationale To help users login to system.
Restrictions and Risk User shall click the specified box to perform the action.
Dependencies FR-05
Priority High

3.1.8 Sign out

Identifier FR -08
Title Sign out
Requirement User can log out from the system
Source Supervisor
Rationale To help users log out from the system.
Restrictions and Risk User shall press ‘sign out’ to perform the action.
Dependencies N/A
Priority Low
Software Requirements Specification for CPSI Page 28

3.1.9 Update profile

Identifier FR -09
Title Update profile
Requirement User shall be able to update the profile.
Source Supervisor
Rationale To help users keep their accounts updated
Restrictions and Risk Wrong input while updating
Dependencies N/A
Priority High

3.1.10 Search company

Identifier FR -10
Title Search company
Requirement User shall be able to search company from list of companies
Source Supervisor
Rationale To help users analyze the company statistics.
Restrictions and Risk Search result not found.
Dependencies N/A
Priority High

3.1.11 Add company to profile

Identifier FR -11
Title Add company to profile
Requirement User shall be able to add a new company to profile dashboard.
Source Supervisor
Rationale To help users manage the company.
Restrictions and Risk Company already exists.
Dependencies N/A
Priority High

3.1.12 Remove company from profile

Identifier FR -12
Title Remove company from profile
Requirement User shall be able to add a new company to profile dashboard.
Source Supervisor
Rationale To help users manage the company.
Restrictions and Risk Active company is removed.
Dependencies FR-11
Priority High

3.1.13 View personal investments

Identifier FR -13
Title View personal investments
Software Requirements Specification for CPSI Page 29

Requirement User shall be able to view all the investments done up till now.
Source Supervisor
Rationale To help users manage the investments.
Restrictions and Risk N/A
Dependencies N/A
Priority High

3.1.14 Generate warning message

Identifier FR -14
Title Generate warning message
Requirement System shall generate warning message when wrong data is inserted or
field is left empty.
Source Supervisor
Rationale To help users identify their mistakes and use system correctly.
Restrictions and Risk N/A
Dependencies N/A
Priority Medium

3.1.15 Sign up

Identifier FR -15
Title Sign up
Requirement Guest shall be able to sign up before using full functionality of the system
Source Supervisor
Rationale To help guest become registered user
Restrictions and Risk N/A
Dependencies FR-05
Priority High

3.1.16 Generate weekly report

Identifier FR -16
Title Generate weekly report
Requirement User shall be able to generate weekly report according to market
proceedings.
Source Supervisor
Rationale To help users know the market statistics
Restrictions and Risk N/A
Dependencies FR-21
Priority High

3.1.17 Generate monthly report

Identifier FR -17
Title Generate monthly report
Requirement User shall be able to generate monthly report according to market
proceedings.
Software Requirements Specification for CPSI Page 30

Source Supervisor
Rationale To help users know the market statistics
Restrictions and Risk N/A
Dependencies FR-21
Priority High

3.1.18 Generate quarterly report

Identifier FR -18
Title Generate quarterly report
Requirement User shall be able to generate quarterly report according to market
proceedings.
Source Supervisor
Rationale To help users know the market statistics
Restrictions and Risk N/A
Dependencies FR-21
Priority High

3.1.19 Generate bi-annually report

Identifier FR -19
Title Generate bi-annually report
Requirement User shall be able to generate bi-annually report according to market
proceedings.
Source Supervisor
Rationale To help users know the market statistics
Restrictions and Risk N/A
Dependencies FR-21
Priority High

3.1.20 Generate annually report

Identifier FR -20
Title Generate annually report
Requirement User shall be able to generate annually report according to market
proceedings.
Source Supervisor
Rationale To help users know the market statistics
Restrictions and Risk N/A
Dependencies FR-21
Priority High

3.1.21 Save report

Identifier FR -21
Title Save report
Requirement User shall be able to save generated report.
Source Supervisor
Software Requirements Specification for CPSI Page 31

Rationale To help users know the market statistics.

Restrictions and Risk N/A
Dependencies FR-22, FR-23, FR-24, FR-25
Priority High

3.1.22 Print report

Identifier FR -22
Title Print report
Requirement User shall be able to print generated report.
Source Supervisor
Rationale To help users know the market statistics.
Restrictions and Risk N/A
Dependencies N/A
Priority High

3.1.23 Download report

Identifier FR -23
Title Download report
Requirement User shall be able to download generated report.
Source Supervisor
Rationale To help users know the market statistics.
Restrictions and Risk N/A
Dependencies N/A
Priority High

3.1.24 Delete report

Identifier FR -24
Title Delete report
Requirement User shall be able to delete generated report.
Source Supervisor
Rationale To help users know the market statistics.
Restrictions and Risk N/A
Dependencies N/A
Priority High

3.1.25 View report

Identifier FR -25
Title View report
Requirement User/Guest shall be able to view generated report.
Source Supervisor
Rationale To help users/guests know the market statistics.
Restrictions and Risk N/A
Software Requirements Specification for CPSI Page 32

Dependencies FR-22, FR-23, FR-22, FR-24

Priority High

3.1.26 Add invested stocks

Identifier FR -26
Title Add invested stocks
Requirement User shall be able to add the information about the stocks that they have
invested in the particular company.
Source Supervisor
Rationale To help users add stocks information in the profile
Restrictions and Risk N/A
Dependencies N/A
Priority High

3.1.27 Confirmation dialogue box

Identifier FR -27
Title Confirmation dialogue box
Requirement System shall ask user again before performing ‘Delete’ action.
Source Supervisor
Rationale To help user consider the action once again.
Restrictions and Risk N/A
Dependencies N/A
Priority High

3.1.28 Validate Username

Identifier FR -28
Title Validate Username
Requirement System shall check the username entered by user have no matching entry
in database.
Source Supervisor
Rationale In order to create single account against one Username (email).
Restrictions and Risk N/A
Dependencies FR-5, FR-15
Priority High

3.1.29 Authenticate User

Identifier FR -29
Title Authenticate User
Requirement System shall check the username and password entered by user have no
matching entry in database.
Source Supervisor
Rationale In order to restrict unauthorized users to login to the system.
Software Requirements Specification for CPSI Page 33

Restrictions and Risk N/A

Dependencies FR-5, FR-28, FR-30
Priority High

3.1.30 Validate Password

Identifier FR -30
Title Validate Password
Requirement System shall check the password entered by user matching entry in
database.
Source Supervisor
Rationale In order to authenticate user
Restrictions and Risk N/A
Dependencies FR-5
Priority High

3.2 Non – Functional Requirements

3.2.1 Usability

Identifier NFR1
Title Usability 1
Requirement Because of user friendly interfaces, the user who had already used PSX
shall be able to learn all the functionalities of the system within 10 to 15
minutes of training. While lay user should take 30 minutes of training to
understand the basics of CPSI.

Identifier NFR2
Title Usability 2
Requirement Interface of the system will provide proper help and will maintain
consistency throughout the interface.

Identifier NFR3
Title Usability 3
Requirement Color scheme for the interfaces should be simple and attractive.

3.2.2 Reliability

Identifier NFR1
Title Reliability 1
Requirement System should fulfill 98 out of 100 requests.

Identifier NFR2
Title Reliability 2
Requirement Maximum down time of system shall not be more than 5 minutes per day.
Software Requirements Specification for CPSI Page 34

3.2.3 Performance

Identifier NFR1
Title Performance 1
Requirement Average time to upload data file which will be of same size shall be 10 to
15 seconds depending on the internet connection.

Identifier NFR2
Title Performance 2
Requirement Average time to generate a daily report should be 5 seconds.
Average time to generate a weekly report should be 10 seconds.
Average time to generate a monthly report should be 15 seconds.
Average time to generate a quarterly report should be 20 seconds.
Average time to generate a bi-annually report should be 25 seconds
Average time to generate a annually report should be 30 seconds.

Identifier NFR3
Title Performance 3
Requirement Average time to open a saved report should be maximum 2 to 3 seconds.

4. User Interfaces
Software Requirements Specification for CPSI Page 35

Home
Software Requirements Specification for CPSI Page 36

Profile
Software Requirements Specification for CPSI Page 37

Sector Overview
Software Requirements Specification for CPSI Page 38

5. Project Gantt chart