Software Requirements Specification (SRS)
SOFTWARE REQUIREMENTS SPECIFICATION
THE ONLINE RETAILS SUPPLY CHAIN SYSTEM
17 SEPTEMBER 2008
PREPARED FOR
PREPARED BY
SRS – Course Registration System Page 0
Software Requirements Specification (SRS)
CONTENTS
1. INTRODUCTION.................................................................................................... 3
1.1 PURPOSE..................................................ERROR! BOOKMARK NOT DEFINED.
1.2 SCOPE......................................................ERROR! BOOKMARK NOT DEFINED.
1.3 DEFINITIONS, ACRONYMS, AND ABBREVIATIONS..........ERROR! BOOKMARK NOT
DEFINED.
1.4 REFERENCES............................................ERROR! BOOKMARK NOT DEFINED.
1.5 OVERVIEW ..................................................................................................5
2. OVERALL DESCRIPTION....................................................................................... 6
2.1 PRODUCT PERSPECTIVE............................ERROR! BOOKMARK NOT DEFINED.
2.2 PRODUCT FUNCTIONS...............................ERROR! BOOKMARK NOT DEFINED.
2.2.1 Register for Courses.................................Error! Bookmark not defined.
2.2.1 Login.........................................................Error! Bookmark not defined.
2.2.2 Maintain Professor Information.................Error! Bookmark not defined.
2.2.3 Maintain Student Information....................Error! Bookmark not defined.
2.2.4 Close Registration.....................................Error! Bookmark not defined.
2.2.5 Select Courses to Teach...........................Error! Bookmark not defined.
2.2.6 Submit Grades..........................................Error! Bookmark not defined.
2.2.7 View Report Card......................................Error! Bookmark not defined.
2.3 USER CHARACTERISTICS...........................ERROR! BOOKMARK NOT DEFINED.
3. SPECIFIC REQUIREMENTS....................................................................................8
3.1 SOFTWARE PRODUCT FEATURES...............ERROR! BOOKMARK NOT DEFINED.
3.1.1 Register for Courses Use Case XXXXX....Error! Bookmark not defined.
3.1.1.1 Brief Description........................................Error! Bookmark not defined.
3.1.1.2 Flow of Events...........................................Error! Bookmark not defined.
3.1.1.2.1 Basic Flow – Create a Schedule............Error! Bookmark not defined.
3.1.1.2.2 Alternative Flows....................................Error! Bookmark not defined.
3.1.1.2.2.1 Modify a Schedule.................Error! Bookmark not defined.
3.1.1.2.2.2 Delete a Schedule.................Error! Bookmark not defined.
3.1.1.2.2.3 Save a Schedule...................Error! Bookmark not defined.
3.1.1.2.2.4 Add Course Offering..............Error! Bookmark not defined.
3.1.1.2.2.5 Unfulfilled Prerequisites or Course Full......Error! Bookmark
not defined.
3.1.1.2.2.6 No Schedule Found...............Error! Bookmark not defined.
3.1.1.2.2.7 Course Catalog System Unavailable...Error! Bookmark not
defined.
3.1.1.2.2.8 Course Registration Closed. .Error! Bookmark not defined.
3.1.1.3 Special Requirements...............................Error! Bookmark not defined.
3.1.1.4 Preconditions.............................................Error! Bookmark not defined.
3.1.1.5 Postconditions...........................................Error! Bookmark not defined.
3.1.1.6 Extension Points........................................Error! Bookmark not defined.
SRS – Course Registration System Page 1
Software Requirements Specification (SRS)
3.1.1.7 Register for Courses Sequence Diagram. .Error! Bookmark not defined.
3.1.1.8 Register for Courses Activity Diagram......Error! Bookmark not defined.
3.1.2 Login Use Case.........................................Error! Bookmark not defined.
3.1.1.9 Brief Description........................................Error! Bookmark not defined.
3.1.1.10 Flow of Events.........................................Error! Bookmark not defined.
3.1.1.11 Basic Flow - Login...................................Error! Bookmark not defined.
3.1.1.12 Alternative Flows.....................................Error! Bookmark not defined.
3.1.1.13 Special Requirements.............................Error! Bookmark not defined.
3.1.1.14 Preconditions...........................................Error! Bookmark not defined.
3.1.1.15 Postconditions.........................................Error! Bookmark not defined.
3.1.1.16 Extension Points......................................Error! Bookmark not defined.
3.1.1.17 Login Sequence Diagram........................Error! Bookmark not defined.
3.1.1.18 Activity Diagram......................................Error! Bookmark not defined.
:..........................................................................Error! Bookmark not defined.
3.1.3 Use Case Specification 3..........................Error! Bookmark not defined.
3.1.4 Use Case Specification 4..........................Error! Bookmark not defined.
3.1.5 Use Case Specification 5..........................Error! Bookmark not defined.
3.1.n Paste use case specification n..................Error! Bookmark not defined.
3.2 NON FUNCTIONAL REQUIREMENTS...............................................................8
3.2.1 Usability..................................................................................................36
3.2.1.1 Windows Compliance..............................................................................36
3.2.1.2 Designs for Ease-of-Use..........................................................................36
3.2.1.3 Online Help.............................................................................................. 36
3.2.2 Reliability................................................................................................36
3.2.2.1 Availability............................................................................................... 36
3.2.2.2 Mean Time between Failures...................................................................36
3.2.3 Performance...........................................................................................36
3.2.3.1 Simultaneous Users.................................................................................37
3.2.3.2 Database Access Response Time...........................................................37
3.2.3.3 Transaction Response Time....................................................................37
SRS – Course Registration System Page 2
Software Requirements Specification (SRS)
1. INTRODUCTION
1. INTRODUCTION
1.1 Project Purpose, Scope and Objectives
The purpose of the TESCO project is to provide the end users with the most
convenient and compatible tool for the online supply chain retail system to manage the
database of the food stock and its delivery date, its expired date so that the delivered
stock can be delivered just on time.
1.2 Assumptions and Constraints
This SPMP has been drawn up with specific assumptions, dependencies and
constraints in mind. They are, in no particular order or category.
-The user requirement will be incomplete after UR phase
- The project depends on the technology input to make the TESCO transparently
searchable to end users.
-By intellectual property rights or commercial interest.
1.3 Definitions, Acronyms, and Abbreviations
SRS – Course Registration System Page 3
Software Requirements Specification (SRS)
AD Architectural Design
CF Core Facilities
DD Detailed Design
OM Operations and Maintenance
SCIAMACHY Scanning Imaging Absorption SpectrometerAtmosphericCartography
SR Software Requirements
SPMP Software Project Management Plan
SQAP Software Quality Assurance Plan
SSD Software Specification Document
SVVP Software Validation and Verification Plan
SR Software Requirements
TBD To Be Defined
TR Transition phase
UR User Requirements
SRS – Course Registration System Page 4
Software Requirements Specification (SRS)
Overview
SRS – Course Registration System Page 5
Software Requirements Specification (SRS)
2. OVERALL DESCRIPTION
2. OVERALL DESCRIPTION
2.1 Product Perspective
The interface between the product and related system is based on sequence diagram
and activity diagram
2.2 Product Functions
2.2.1 Login
This use case describes how a user logs into the TESCO system
2.2.2 Supplier
This use case allows the supplier to supply the stock to the TESCO system
2.2.3 Tesco Inventory Management
This use case allows to view the current stock, place order and update stock of TESCO
2.2.4 Tesco Account Manager
This use case allows to make payment to the banking system
2.2.5 System Admin
This use case allow to manage user account
2.3 User Characteristics
SRS – Course Registration System Page 6
Software Requirements Specification (SRS)
Educational level
Mostly the staff in the TESCO system can use the online application system and
have certificate on computer application.
Experience
The supplier, the TESCO inventory management, the TESCO account
management, and the System Admin have experience on handling online retail
supply chain system
Technical Experience
System Admin is the one that has many technical experience in the fields of online
application.
SRS – Course Registration System Page 7
Software Requirements Specification (SRS)
3. SPECIFIC REQUIREMENTS
3.1.1 Login
Logi n
user
(from Use-Case Model)
(from Use Case View)
Figure 1: Login Use Case Diagram
3.1.1.1 Brief Description
This use case describes the steps of registration or logging in of TESCO online
retail supply chain system.
3.1.1.2 Flow of Event
The use case begins when user tries to log in TESCO Online Retail Supply
Chain system
3.1.1.2.1 Basic Flow
1. Enter user name and password
2. Press submit button
3. Log in successfully
3.1.1.2.2 Alternative Flow
If the user submits wrong user ID or password, error message will be displayed.
3.1.1.2.3 Precondition
None
SRS – Course Registration System Page 8
Software Requirements Specification (SRS)
3.1.1.2.4 Post Condition
The use case ends when the user ID and password are correct and log in
successfully, so user can log on to the system.
3.1.3.2.5 Sequence Diagram
: form login : login ctr : user : main applicati on
: any user
fill in login form()
get user info(uID,pwd)
send data()
open
Figure 2: Login Sequence Diagram
3.1.3.2.6 Activity Diagram
SRS – Course Registration System Page 9
Software Requirements Specification (SRS)
Start login use case
Fill in login
form
Press the
submit button
Incorrect UID or password Display error
message
Login
successful
End of login use case
Figure 3: Login Activity Diagram
3.1.2 View Current Stock
Logi n
user
(from Use-Case Model)
(from Use Case View)
Figure 4: View current stock use case Diagram
3.1.2.1 Brief Description
This use case describes to the TESCO Inventory manager to know or view their
current available stock to find out what they need to order from their supplier.
3.1.2.2 Flow of Event
The use case begins when TESCO Inventory manager logs in and clicks view
current stock function button.
3.1.2.1.1 Basic Flow
SRS – Course Registration System Page 10
Software Requirements Specification (SRS)
1. View stock on hand
2. Identify shortage of stock
3.1.2.2 Alternative Flow
None
3.1.2.3 Precondition
Before the use case begins the user needs to log in to the system.
3.1.2.4 Post Condition
The use case ends when TESCO Inventory Manager views stock on hand
successfully, so TESCO Inventory Manager can make orders.
3.1.3.2.5 Sequence Diagram
SRS – Course Registration System Page 11
Software Requirements Specification (SRS)
Figure 5: View current stock sequence Diagram
3.1.3.2.6 Activity Diagaram
SRS – Course Registration System Page 12
Software Requirements Specification (SRS)
Figure 6: View current stock activity Diagram
3.1.3 Place Order
SRS – Course Registration System Page 13
Software Requirements Specification (SRS)
Logi n
user
(from Use-Case Model)
(from Use Case View)
Figure 7: Place Order Use Case Diagram
3.1.3.1 Brief Description
This use case allows TESCO Inventory Manager to make orders to their supplier
if there is some shortage to their stock.
3.1.3.2 Flow of Event
This use case begins when TESCO Inventory manager logs in successfully and
presses make order function button.
3.1.3.2.1 Basic Flow
1. View current stock by pressing stock on hand button
2. Place order by clicking order button
3. Confirm the order.
3.1.3.2.2 Alternative Flow
If the user does not place order properly error message will display and highlight
empty field information for placing the order.
3.1.3.2.3 Precondition
Before use case begins the user needs to log in the system
3.1.3.2.4 Post Condition
This use case ends after inventory manager places orders successfully.
3.1.3.2.5 Sequence Diagram
SRS – Course Registration System Page 14
Software Requirements Specification (SRS)
Figure 8: Place Order Sequence Diagram
3.1.3.2.6 Activity Diagram
SRS – Course Registration System Page 15
Software Requirements Specification (SRS)
Figure 9: Place Order Activity Diagram
3.1.4 View Order
View order
SRS – Course Registration SystemSupplier Page 16
(from Use-Case Model)
(from Use Case View)
Software Requirements Specification (SRS)
3.1.4.1 Brief Description
This use case describes the steps for the supplier to view order sent from
Inventory manager.
3.1.4.2 Flow of event
This use-case begins when the supplier logs in to the system and also receives
an order from inventory manager.
3.1.4.2.1 Basic flow
1. Supplier clicks on ViewNewOrders button
2. System displays the orders needed from the supplier.
3.1.4.2.2 Alternate Flow
1. Supplier failed to login error message will be displayed
2. Supplier forgot his password he must contact system admin.
3.1.4.3 Pre-condition
1. Supplier must log in to the system
2. Inventory manager must place an order.
3.1.4.4 Post condition
1. Use case ends when supplier is successfully able to view the order.
3.1.4.5. Sequence Diagram
SRS – Course Registration System Page 17
Software Requirements Specification (SRS)
View menu View order User Item
form form
Supplier
Select viewNewOrder
userID
Get user info.
View list of the new order
3.1.4.6 Activity Diagram
SRS – Course Registration System Page 18
Software Requirements Specification (SRS)
Start view order use
case
Select View New Order
menu
Get user Info
System record
User info
View NewOrder List
End of view order
use case
3.1.5 Process Order
SRS – Course Registration System Page 19
Software Requirements Specification (SRS)
Process order
supplierr
(from Use-Case Model)
(from Use Case View)
3.1.5.1 Brief Description
This use case describes the steps for processing the order
3.1.5.2 Flow of event
This use-case begins when the supplier logs in to the system and views the
order placed .
3.1.5.2.1 Basic flow
1.Supplier check stock needed
2. Supplier check his stock on hand
3. Supplier compare between stock needed and stock in hand
4 . Supplier processes the order.
3.1.5.2.2 Alternate Flow
1. Supplier failed to login error message will be displayed
2. If the supplier fails to process the order , display stock not available.
3.1.5.3 Pre-condition
1. Supplier must log in to the system
2. Supplier must view order placed by inventory manager.
3.1.5.4 Post condition
SRS – Course Registration System Page 20
Software Requirements Specification (SRS)
This Use case ends when supplier is successfully able to process the
order.
3.1.5.5 Sequence Diagram
3.1.5.6 Activity Diagram
SRS – Course Registration System Page 21
Software Requirements Specification (SRS)
Start process order use
case
Select check order
menu
Check order
needed
Check order
In hand
Order needed not
available
Display error
meaasge
Press submit
button
Process Order
End of process order use case
3.1.6 Update Stock
Update stock
SRS – Course Inventory
Registration System
manager Page 22
(from Use-Case Model)
(from Use Case View)
Software Requirements Specification (SRS)
3.1.6.1 Brief Description
This use case describes the steps to update stock in database after it has
been received.
3.1.6.2 Flow of event
This use-case begins when the inventory manager login into the system and
choose . Update stock menu from the system.
3.1.6.2.1 Basic flow
1. Select update stock
2. Fill the update stock form.
3. Submit update form
4. Add new stock record
5. Submit stock record
6. System updated
3.1.6.2.2 Alternate Flow
3.1.6.2.2.1 Delete old stock record
1. Select delete menu
2. Delete old stock record
3. Submit
4. System updated.
3.1.6.2.2.2 Edit stock record
1. Select edit menu
2. Edit new stock record
SRS – Course Registration System Page 23
Software Requirements Specification (SRS)
3. Submit
4. System updated.
3.1.6.3 Pre-condition
1. Supplier must log in to the system
2. Supplier must view order placed by inventory manager.
3.1.6.4 Post condition
1. Use case ends when supplier is successfully able to process the order .
SRS – Course Registration System Page 24
Software Requirements Specification (SRS)
3.1.6.5. Sequence Diagram
SRS – Course Registration System Page 25
Software Requirements Specification (SRS)
3.1.6.6 Activity Diagram
Select del button menu
Delete old stock
record
Select add button
menu
Add new stock
record
Data already exist Display error
message
Press submit
button
System has
been updated
End of update stock
use case
SRS – Course Registration System Page 26
Software Requirements Specification (SRS)
3.1.7 Order status
Order status
(From use case view) (From use case model)
3.1.7.1 Brief Description
This use case checks the order status if the stock is decreased the manager will
place the product in order status that this product will need to be delivered.
3.1.7.2 Flow of Event
This use begins when the manager checks the order status. Manager sets a
point on every product when it reaches that level manager will put order status
mark.
3.1.7.2.1 Basic Flow
1. Check list of orders
2. Select order
3. View the order status.
3.1.7.2.2 Alternative Flow
If the accountant can’t log in or may be forget his password, he or she will
contact the system administrator. In addition if accountant cant view the order
status he or she must also contact the system administrator or check whether
the inventory manager did place order and the supplier did confirm the
availability of that product.
3.1.7.3 Precondition
Account Manger must login. Also before the order status is to view process
order. Account manager will view order status if the supplier confirm the order
3.1.7.4 Post condition
SRS – Course Registration System Page 27
Software Requirements Specification (SRS)
The account manager will make the payment if the supplier confirms the
availability of the product.
3.1.7.5 Sequence Diagram
:Account
Manager
Menu :Order
Form :Order
Status :Order
:User List Status
Form
Select order
status New( User
ID)
getUser
Info(ID)
Select list
Select
Order
View order
status
View Status
3.1.7.6 Activity Diagram
SRS – Course Registration System Page 28
Software Requirements Specification (SRS)
Start login use case
Check list of
orders
Select order
View Order
Status
End of login use case
3.1.8 Make payment
Make payment
(From use case view) (From use case model)
3.1.8.1 Brief Description
Account manager makes sure that the supplier confirmed the availability of the
order then the account manager will make the payment.
3.1.8.2 Flow of events
SRS – Course Registration System Page 29
Software Requirements Specification (SRS)
The use case begins when the process order is confirmed and order status is
available the payment will be made.
3.1.8.2.1 Basic flows
1. Select order
2. Select list of suppliers
3. Select Type of payment
4. Transfer payment to supplier
5. supplier confirm payment
3.1.8.2.2 Alternative flows
Account manager should login in order to view his or her part of the system. In
addition accountant manager should make the payment to the supplier if there is
a problem with system he or she should contact the supplier and arrange
alternative payment option.
3.1.8.3 Precondition
Account manager should confirm order status
3.1.8.4 Post condition
None
3.1.8.5 Sequence Diagram
SRS – Course Registration System Page 30
Software Requirements Specification (SRS)
:Account
Manager
Menu :Payment :list :types
Form Form :user supplies payment :supplier
Select
paymetnt New (user
ID)
getUser info
Make payment Select List
supplies()
Select types()
Transfer
payment()
3.1.8.6 Activity Diagram
SRS – Course Registration System Page 31
Software Requirements Specification (SRS)
Start login use case
Select order
Select list
supplies
Types
payment
Supplier
End of login use case
3.1.9 Manage User Account
Manage user account
(From use case view) (From use case model)
3.1.9.1 Brief Description
System Administrator is responsible for managing the user account.
SRS – Course Registration System Page 32
Software Requirements Specification (SRS)
3.1.9.2 Flow of events
System Administrator will check the system and limited every user activity. Set
what user can view and what user cant view. If user has a problem with system
they will report to the administrator.
3.1.9.2.1 Basic flow
1. click the sign in bottom
2. Sign in successful take the user to the main page.
3. User Edit menu
3.1 Delete
3.2 Change
3.3 Update
3.1.9.2.2 Alternative flow
If password or user name wrong display error message and ask the user to re-
enter it or contact the system administrator.
3.1.9.3 Precondition
User must provide username and password in order to access the system.(Login
form)
3.1.9.4 Post Condition
The use case ends when the username and password are correct and login
session is successful, so user can log on to the system.
3.1.9.5 Sequence Diagram
SRS – Course Registration System Page 33
Software Requirements Specification (SRS)
:
Manageu
ser :login :Main
account : Edit
Form :user Application
Form
Select login
form
New (user
ID) getUser
info(user ID)
Take user to
main
Application()
Edit menu()
3.1.9.6 Activity Diagram
SRS – Course Registration System Page 34
Software Requirements Specification (SRS)
Start login use case
Fill in login
form
Incorrect username or password
Display error
message
Main
Application
Edit
End of login use case
3.2 Non Functional Requirements
Non-functional requirements are requirements that are not directly concerned with
the specific functions delivered by the system.
SRS – Course Registration System Page 35
Software Requirements Specification (SRS)
3.2.1 Usability
Usability is defined as the ease with which a user can learn to operate, prepare
inputs for and interpret outputs of a system or component. This section lists all of
those requirements that relate to or affect the usability of the system.
3.2.1.1 Windows Compliance
The desktop user-interface shall be Windows XP/ Vista compliant, in order
to have a good usability.
3.2.1.2 Designs for Ease-of-Use
The user interface of the Tesco Online Retail Supply Chain System shall
be designed for ease-of use and shall be appropriate for a computer-
literate user community with no additional training on the system.
3.2.1.3 Online Help
Each feature of the Tesco Online Retail Supply Chain System shall have
built-in online help for the user. Online Help shall include step by step
instructions on using the System. Online Help shall include definitions for
terms and acronyms.
3.2.2 Reliability
Reliability is defined as the system can be trusted to do all the instruction well and
user can rely on it.
3.2.2.1 Availability
The Tesco Online Retail Supply Chain System shall be available 24 hour a
day and 7 days a week. This system shall be not more than 3% down
time, in order to have a good reliability.
3.2.2.2 Mean Time between Failures
The Tesco Online Retail Supply Chain System mean time between failures
shall exceed 300 hour.
3.2.3 Performance
Performance is defined as how well the Tesco Online Retail Supply Chain System
performs and fast the system must execute.
SRS – Course Registration System Page 36
Software Requirements Specification (SRS)
3.2.3.1 Simultaneous Users
The Tesco Online Retail Supply Chain System shall support 1500
simultaneous users against the central database at any given time and to
400 simultaneous users against the local servers at any one time.
3.2.3.1 Database Access Response Time
The Tesco Online Retail Supply Chain system shall provide access to the
legacy course catalogue database with no more than 10 second latency.
3.2.3.1 Transaction Response Time
The Tesco Online Retail Supply Chain system must be able to complete
80% of all transactions within 2 minutes. Here when the transaction
response time is short it means the system response time is good or the
system is good.
SRS – Course Registration System Page 37
