Requirements Document

Stock Tracking System

Shridharshan R R
13MSE0163

Requirement types:
1. Stakeholder requirements
2. Features
3. Supplementary requirements
4. Use Case requirements
5. Glossary requirements

1. Stakeholder requirements

User should be able to maintain multiple watch lists.

Keep information about current holdings confidential.
Should be able to get stock alerts even when user is off-line.
User should be able to filter stock scrip based on custom
constraints.
View information such as fundamental and technical analysis about
stocks.
Allow overdrawing in case of emergency.
See currently tending stocks based on the community usage.
Administrator should be able to suspend users based on user
activity.
Administrator should be able to view vital site statistics.
Administrator should be able to deal with different Data providers on
demand.

2. Features

Portfolio manager.
IPO alerts.
Stock reviews.
Watch list with sector-wise grouping.
SMS based alert for offline users.
Advanced querying with SQL like syntax for customized querying.
Trends with sector wise segregation.
Graphical monitoring of site traffic with individual user stats to
detect malicious user activity.
Scale site resources according to user load.

3. Supplementary requirements
Client application should be lightweight, browser friendly.
The application should be always up or uptime should be 100%
during market trading hours.
Funds transfer should be quick.
Information displayed should be real-time or delayed by a maximum
of 2 seconds.
Login using multi factor authentication.
Should be certified by the SEBI
4. Use Case requirements
1)login page should be highly secured
cases:
1) if user enters wrong login id ..prompt the user find his login id by using
account number and otp.
2)if user forgots password
id,accno and otp.

prompt him to set new password by using login

3) if user enters wrong password for a repeated no of times

limited time( ex: 30min).

block login for

2) all the transactions should be done only after a thorough checking of

details.
cases:
1)

if wrong account number .. revert the money back.

2)

if

ifsc code is wrong ..revert the money back.

3) if any network problem occurred during transaction time .. make sure

that server will recheck after some time and based on transaction status
process the request.
4) if money is not transferred but deduction is done from user
account( revert the transaction back).

3) accounts security should be high

cases:
1) if login has been done on a new system for first time . save the
network ip address (or) gps address and send that to users mail id.
2) if not properly logged out send a message to user mobile no to
logout properly. if same thing is going on every time (block it).

5 . glossary:
1)payee: a person or account whose account is going to get credit by
money.
2) actor: a person, software system, or hardware device that interacts with
a system to achieve a useful goal. also called a user role.
3) constraint: a restriction that is imposed on the choices available to the
developer for the design and construction of a product.
4) process: a sequence of activities performed for a given purpose. a
process description is a documented definition of those activities.
5) stakeholder: a person, group, or organization that is actively involved in
a project, is affected by its outcome, or can influence its outcome.
6) user: a customer who will interact with a system either directly or
indirectly (for example, using outputs from the system but not generating
those outputs
personally). also called end user.
7)window: a separate pane or area which contain information refgarding
the searched item.
8)dashboard: a entrance frame where all basic data is available.
9)imps :instant money transfer serice ( instant transfer of money)
10)revert:undoing the transaction.