1. Sample SRS Document

2. Table of Contents
1). Introduction
1.1 Purpose of this document
1.2 Scope of this Document
1.3 Acronyms
1.4 References
1.5 Intended Audience and Reading Suggestions
1.6 Document Overview
2). Overall description
2.1 Product Perspective
2.2 Product Functions
2.3 User Classes and Characteristics
2.4 Operating Environment
2.5 Design and Implementation Constraints
2.6 User Documentation
2.7 Assumptions and Dependencies
3). External Interface Requirements
3.1 User Interfaces
3.2 Hardware Interfaces
3.3 Software Interfaces
3.4 Communication Interfaces
4). Functional Requirement Specifications (FRS)
4.1 System Features
4.2 Functional Requirements
4.2.1 Front end (Store front) Requirements
4.2.2 Back end (Administrative Tools) Requirements

3. 4.3 Use Cases
4.3.1 Front end (Store front)
4.3.2 Back end (Administrative Tools)
5). Non Funtional Requirements
5.1 Usability Requirements
5.2 Performance Requirements
5.3 Compatibility Requirements
6). Other Requirements
7). Glossary

4. 1). Introduction
1.1 Purpose of this document
The Purpose of this document is to outline the requirements for the eCommerce (Business
to Customer) Product to be developed for IBEE Solutions (P) Ltd.
1.2 Scope of this Document
1.3 Glossary
1.4 References
IBEE solutions PID (Project Initiation Document)
IBEE solutions Project Plan
IBEE Business Requirements
[IEEE] The applicable IEEE standards are published in “IEEE Standards Collection,” 2001
edition.
[Bruade] The principle source of text book material is “Software Engineering: An Object
oriented perspective” by Eric J Bruade.
1.5 Intended Audience and Reading Suggestions
Project Manager, IBEE Solutions Developers, NRSTT (P) Ltd Testers, Marketing Staff,
Business Users and Technical writers
2). Overall description
2.1 Product Perspective
2.2 Product Functions
2.3 User Classes and Characteristics
2.4 Operating Environment
2.5 Design and Implementation Constraints
2.6 User Documentation
2.7 Assumptions and Dependencies

5. 3). External Interface Requirements
3.1 User Interfaces
3.2 Hardware Interfaces
3.3 Software Interfaces
3.4 Communication Interfaces
4). Functional Requirement Specifications (FRS)
4.1 System Features
Front end (customer storefront)
Products Catalog
Customer’s registration
Customer account
Products Search
Advanced Search
Products Comparison
Price list
News
Feedback
Shopping cart
Checking out
Polls
Back end (administrative tools)
Login
Managing products catalog
Adding new categories/subcategories
Viewing/Editing/deleting existing categories
Adding new products
Viewing/Editing/deleting existing product entry
Table of products
Importing products
Exporting products

6. Synchronization tools
Product custom options
Special offers
Discussions
Defining Polls
Adding news
Reports
4.2 Functional Requirements
email4.2.1 Front end (Store front) Requirements
Connecting to Application with Valid URL
U 1.0 User home page-All features availability
U 1.1 Registration
U 1.1.1 Taking Login Name
U 1.1.2 Taking Password
U 1.1.3 Taking confirm Password
U 1.1.4 Selecting salute (Any one)
U 1.1.5 Taking first name
U 1.1.6 Taking middle name
U 1.1.7 Taking last name
U 1.1.8 Taking e-mail in the e-mail format
U 1.1.8 Selecting profession
U 1.1.9 Taking phone number (Mandatory)
U 1.1.10 Taking Fax number
U 1.1.11 Taking date of birth
U 1.1.12 Taking passport number
U 1.1.13 Taking address including city, state zip & country
U 1.1.14 Submitting the form

7. U 1.1.15 Resetting the form
U 1.2 Login
U 1.2.1 Taking user name
U 1.2.2 Taking Password
U 1.2.3 Providing forgot password option
U 1.2.3.1 Submitting e-mail address and getting user info through our mail ID.
U 1.2.4 Submission of the Login
U 1.3 Products Catalog
U 1.3.1 All entered categories and products availability.
U 1.4 Products search
U 1.4.1 Taking input values and finding
U 1.4.2 Displaying results in another screen if not found providing message.
U 1.5 Advanced search
U 1.5.1 Selecting category & taking product name, Taking price range, color etc and finding.
U 1.5.2 Displaying result as per customization of not available providing message.
U 1.6 Products comparison
U 1.6.1 Selecting products for comparison [two or more] and getting comparison.
U 1.7 Shopping Process
U 1.7.1 Browsing through categories, selecting products to buy.
U 1.7.2 Able to view detailed information in the separate screen.
U 1.7.3 Choosing quantity and continue buying

8. U 1.7.4 Updating quantity and removing requirements.
U 1.8 Checking out (completing transaction by providing
payment option)
U 1.9 Voting for poll
U 1.9.1 Selecting one option, voting and getting the pole results
(we can vote one time per session only)
U 1.10 Viewing news
U 1.10.1 Selecting displayed news item and getting that news.
U 1.11 Feed back
U 1.11.1 Taking information like product name, name, e-mail, message and submitting.
U 1.11.2 Input data resetting facility.
U 1.12 Price list
U 1.12.1 Getting existing products price list in detail.
4.2.2 Back end (Administrative Tools) Requirements
Connecting to Admin interface with valid URL
Ad 1.0 – Login operation [Taking User ID & Password]
Providing forgot password option & sending user information through e-mail.

9. Ad 1.1 – Admin home page – All features availability
Ad 1.2 – Adding new categories
Ad 1.2.1 – Taking category name & sorting order.
Ad 1.2.2 – Customizing attributes like color, weight and etc.
Ad 1.2.3 – Adding image to category
Ad 1.2.4 – Adding description to category through a file.
Ad 1.2.5 – Saving the entered info and resetting the info.
Ad 1.3 – Editing categories
Ad 1.3.1 – Editing category information and saving the information
Ad 1.3.2 – Viewing the category details
Ad 1.3.3 – Deleting the category
Ad 1.4 – Adding new product
Ad 1.4.1 – Selecting category option
Ad 1.4.2 – Taking product name. Code & sort order.
Ad 1.4.3 – Defining price, stock info shipping freight and weight
Ad 1.4.4 – Adding product image
Ad 1.4.5 – Adding description
Ad 1.4.6 – Saving the details and resetting
Ad 1.5 – Editing product
Ad 1.5.1 – Editing product details and saving the details
Ad 1.5.2 – viewing the product
Ad 1.5.3 – Deleting the product

10. Ad 1.6 Importing products
Ad 1.6.1 Importing products from a CSV file and updating the database
Ad 1.7 Exporting products
Ad 1.7.1 Exporting products to a CSV file.
Ad 1.8 Special offers
Ad 1.8.1 Adding special offer defining [missing requirements]
Ad 1.8.2 Viewing & Deleting the special offer details.
Ad 1.9 Orders information
Ad 1.9.1 Searching orders and selecting the various types of orders.
Ad 1.9.2 Retrieving the selected type orders
Ad 1.10 Customers information
Ad 1.10.1 Searching registered customer’s details and finding.
Ad 1.11 Discounts
Ad 1.11.1 Configuring discount system
Ad 1.11.2 Defining discount rates based on order amount & calculations.
Ad 1.12 Adding news
Ad 1.12.1 Adding news – giving priority published date & title.
Ad 1.12.2 Adding image
Ad 1.12.3 Adding description
Ad 1.12.4 Saving the details & resetting the details.

11. Ad 1.12.5 Viewing/Editing/ deleting the news.
Ad 1.13 Adding polls
Ad 1.13.1 Taking poll question
Ad 1.13.2 Answer options each in separate line.
Ad 1.13.3 Saving & resetting the details
Ad 1.14 Reports
Ad 1.14.1 viewing the category reports
Ad 1.15 Synchronization
Ad 1.15.1 Making a backup of products and categories (export database into a SQL file)
Ad 1.15.2 Importing products & categories from SQL file.

12. 5). Non Funtional Requirements
5.1 Usability Requirements
(As it is a Internet Application, must have some usabilty Features. End users of this System
are Unlimited and from Various Skilled groups, so that we can’t restrict them. By providing
some fecilities we have to make them comfortable.)
 Colors what we use in this Web Portal design are must be attractive.
 Fonts that uses for User Interface (Customer Store front) Design are must be in Uniform.
 Easy Navigations are preferable to do any task.
 multiple flows (ways) are preferable to do any task.
 Home page should be Centralized System (Screen/Window) to go to any feature and to get
any result.
 The facility to return to Home page from any page Should available.
 Labels of all Objects in the entire system Must be in Understandable form(Meaningful form).
5.1 Performance Requirements
(Application’s performance not only depends on application design also on Customers
System’s Configuration (both Hardware and Software), Internet Access Speed, networks
and Others)
Even though the performance is not only depends on application design, our application
design and implimentation also responcible for the Performance.
 It has to load, with in the Industry Standard time.
 It has to support up to 2000 Concurrent users.
 It has to update the database in short time in order to reduce the stock verfication
problems.
5.3 Compatibility Requirements
(As it is a Internet Application, it has to support various Hardware configurarions, Softwares
and Network Communications)
It should support all types of Hardware versions, Operating Systems and Browsers
5.3.1 Operating Systems

13. Operating systems -Wndows98 and upper Versions (EX: Win98, windows 2000 prof, XP
Vista and win NT Server,windows 2000 server, 2003 server and windows 2008 server)
Unix and all Unix flavours like LINUX, Solaris etc..
Novell netware
5.3.2 Browsers
IE 5.0 and higher versions , Mozilla Firefox, AOL, Netscape Navigator.
5.3.4 Hardwares
All leading Brands
6). Other Requirements
7). Glossary