Software Requirements Specification

For Software Testing Information visit: www.gcreddy.
net
Software Requirements
Specification
For
IBEEeCom Portal
Version 2.0 approved
IBEE Solutions (P) LTD

April 2008
www.gcreddy.com
Name Role Date

Prepared By Prasanna Yadav System Analyst 19/02/2008
Reviewed By Durga Prasad SA 25/02/2008
Approved By Pravin Ratta Project Manager 04/03/2008
Document History
For QTP Information & Scripts visit: www.gcreddy.com 1

For Software Testing Information visit: www.gcreddy.net
Revision History
Change Brief
Sno Date Version No Page No Mode Description of
(A/M/D) Change
1) 26-04-2008 2.0 17 A Back end use
cases added
2)
A-Added, M-Modified, D-Deleted

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
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

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
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)

o Products Catalog
o Customer’s registration
o Customer account
o Products Search
o Advanced Search
o Products Comparison
o Price list
o News
o Feedback
o Shopping cart
o Checking out
o Polls
Back end (administrative tools)

o Login
o Managing products catalog
o Adding new categories/subcategories
o Viewing/Editing/deleting existing categories
o Adding new products
o Viewing/Editing/deleting existing product entry
o Table of products
o Importing products
o Exporting products
o Synchronization tools

o Product custom options

o Special offers
o Discussions
o Defining Polls
o Adding news
o Reports
4.2 Functional Requirements
4.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
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
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.
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
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.
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.
4.3 Use Cases
*(Introduction
A use case is a methodology used in system analysis to identify, clarify, and organize
system requirements. The use case is made up of a set of possible sequences of
interactions between systems and users in a particular environment and related to a
particular goal. It consists of a group of elements (for example, classes and
interfaces) that can be used together in a way that will have an effect larger than the
sum of the separate elements combined. The use case should contain all system
activities that have significance to the users. A use case can be thought of as a
collection of possible scenarios related to a particular goal, indeed, the use case and
goal are sometimes considered to be synonymous.
A use case (or set of use cases) has these characteristics:
 Organizes functional requirements

 Models the goals of system/actor (user) interactions
 Records paths (called scenarios) from trigger events to goals
 Describes one main flow of events (also called a basic course of action), and
possibly other ones, called exceptional flows of events (also called alternate
courses of action)
 Is multi-level, so that one use case can use the functionality of another one.
Use cases can be employed during several stages of software development, such as
planning system requirements, validating design, testing software, and creating an
outline for online help and user manuals.)*
*(Use Case ID: - Meaningful identification

Use Case version: - Depend upon draft reviewed.
Status: - It depends upon document status

1. Draft represents an incomplete document
2. Draft has been completed and is being reviewed.
3. Approved represents a use case that has been approved by all parties.
4. Rejected represents a Use case that has been rejected.
Title: - The title or name of the Use case (This should be a simple sentence that
describes the use case)
Actors: - An actor is a person or other entity external to the software system being
specified who interacts with the system and performs use cases to accomplish tasks.
Different actors often correspond to different user classes, or roles, identified from
the customer community that will use the product. Name the actor that will be
initiating this use case and any other actors who will participate in completing the
use case.
Normal flow: - This is where the description of our use case goes.

The normal flow should include the most common (or) the most valuable path
through the use case.
Alternative flow: - Document other, legitimate usage scenarios that can take place
within this use case separately in this section. State the alternative flow, and
describe any differences in the sequence of steps that take place.)*
4.3.1 Front end (Store front)
USE Case ID: UC- U-01

USE Case 1.0
Version:
Status: 2
Release: 1.0
Author: Prasanna Yadav and Sridhar Bale Rao
Use Case Title: Customer’s Registration
Actors: Guest Users
Preconditions: Connecting to IBEEeCom portal- Front End (Customer Store
Front) by providing valid URL
Selecting the ‘Register’ option from the Front End (Customer
Store Front) Home Page.
Normal Flow: System: Displays registration form
Guest User: Enters login, password, confirm password
Selects salute(either Mr or Ms or Mrs)
Enters first name , middle name ,last name and
email
Selects “subscribes for news letter”, Selects
profession
Enters phone number, fax number, date of
birth, passport number.
Enters address details(address1,address2,
address3,city,state
and Zip)
Selects Country
Submits form
System: Verifies login information and displays an error
message
If password and confirm password are not same
Verifies general information and displays an error
message if all mandatory fields are not filled, it also displays
error message if email, date of birth fields are not in standard
format
Verifies address details and displays an error message if any
mandatory field is not filled
Sends registered details to the database and gives
acknowledgement
Alternative Flows: System: Displays registration form
Guest User: Enters login, password, confirm password

Enters first name , middle name ,last name and

email
Selects profession
Enters phone number, date of birth.
Enters address details(address1,address2,
address3,city,state
and Zip)
Selects Country
Submits form
message
If password and confirm password are not same
Verifies general information and displays an error
message if all mandatory fields are not filled, it also displays
error message if email, date of birth fields are not in standard
format
Verifies address details and displays an error message if any
mandatory field is not filled
Sends registered details to the database and gives
acknowledgement
Business Rules: Guest user has to enter all mandatory fields,
should maintain standard formats for emaild, date of birth.

USE Case 1.0
Version:
Status: 2
Release: 1.0
Use Case Title: Customer account
Actors: Registered Users
Normal Flow: System: Displays the Front End (Customer Store Front) Home
page
Registered User: Enters login, password and submits
message
If user name and/or password are incorrect.
Registered user: Selects forgot password option if he/she
forgot
the password
System: Provides email address submission option in separate
window
Registered user: Submits emaild and get his/her login
information
Through mail.
Alternative Flows:
Business Rules: Registered user must enter valid user name and password


USE Case 1.0
Version:
Status: 2
Release: 1.0
Use Case Title: Products catalog
Actors: Guest and Registered Users
page
Guest/Registered User: Selects categories from category
block/ Selects from home page
System: Displays all products under selected category

Guest/Registered user: Views displayed products information
Alternative Flows: Through search or Advanced search guest/registered user can

get products info
Business Rules: Guest/Registered user should select one item at a time

USE Case 1.0
Version:
Status: 2
Release: 1.0
Use Case Title: Products search
page
Guest/Registered User: Enters data in search field and finds
System: Displays search related info if available otherwise it

shows message
Alternative Flows: Browsing through catalog or advanced search user can get info
Business Rules: Guest/Registered user should select one item at a time

USE Case 1.0

Version:
Status: 2
Release: 1.0
Use Case Title: Advanced search
Preconditions: Connecting to IBEEeCom portal - Front End (Customer Store
Selecting advanced search option from the Front End (Customer
Store Front) Home page
Normal Flow: System: Displays advanced search window
Guest/Registered User: Selects category, enters name, enter
price range, color and finds
shows message
Alternative Flows: 1.System: Displays advanced search window

Guest/Registered User: Selects category, enters name and
finds
shows message
2.Browsing through catalog or searching guest/registered user

can get info
Business Rules:

USE Case 1.0
Version:
Status: 2
Release: 1.0
Use Case Title: Price list
Selecting price list option from the Front End (Customer Store
Front) Home page
Normal Flow: System: Displays available products price list
Guest/Registered User: Views the price list
Alternative Flows:
Business Rules:

USE Case 1.0

Version:
Status: 2
Release: 1.0
Use Case Title: News
page
Guest/Registered User: selects one news item from the news
block
System: Displays detailed info of the selected news item
Alternative Flows:
Business Rules: Guest/registered user can select one news item at a time

USE Case 1.0
Version:
Status: 2
Release: 1.0
Use Case Title: Feed back
Front) by providing valid URL and selecting feedback option
Normal Flow: 1.System: Displays feedback screen
Guest/Registered User: Enters product name, name, email,
message, comments about the product and selects rank of the
product and submits the details.
System: Sends submitted details to the database and provides
acknowledgement.
2. Guest/registered user: Resets details after filling one or

more fields.
System: Clears the entered data.
Alternative Flows:
Business Rules: Guest/Registered User has to enter all mandatory fields and
should fill email field in the standard format.

USE Case 1.0
Version:
Status: 2
Release: 1.0
Use Case Title: Shopping cart


Selecting a product from catalog/ search/ advanced search
Normal Flow: System: Displays product info
Guest/Registered User: Selects Add option
System: Adds product to the cart
Guest/registered user: Selects quantity option and modifies
quantity and update
System: Updates total cost
Guest/registered user: Chooses checkout option
System: Asks login info and also provides create account
facility.
Registered user: Enters login info
Guest User: Selects create account option
Alternative Flows: System: Displays product info

Guest/Registered User: Selects Add option
System: Adds product to the cart
Guest/registered user: Selects quantity option and modifies
quantity and update
System: Updates total cost
Guest/registered user: Selects close option
System: Closes the cart window and allows user to buy another
product.
Guest/registered user: Selects another product
System: Adds another product to the cart
Guest/registered user: Selects remove option in the cart
System: Removes selected product from the cart
Guest/registered user: Chooses checkout option
System: Asks login info and also provides create account
facility.
Registered user: Enters login info
Guest User: Selects create account option
Business Rules: Customer has to select minimum one product as well as
quantity.
There is no limitation for selecting maximum products and
quantity w.r.t availability.

USE Case 1.0
Version:
Status: 2
Release: 1.0
Use Case Title: Polls


Normal Flow: System: Displays home page
Guest/Registered User: Selects one option in poll block and
votes.
System: Receives the vote and provides up-to-date poll results.
Alternative Flows: System: Displays the Front End (Customer Store Front) Home
page
Guest/Registered User: Selects one option second time in poll
block in the same session.
System: Rejects the vote and provides message.
Business Rules: Guest/Registered User can vote one time per session.
4.3.2 Back end (Administrative Tools)
USE Case ID: UC- Ad-01

USE Case 1.0
Version:
Status: 2
Release: 1.0
Author: Prasanna Yadav and Lavanya
Use Case Title: Admin Login Operation
Actors: Admin User
Preconditions: Connecting to IBEEeCom portal - Back End (Admin Interface) by
providing valid URL
Normal Flow: System: Displays the Admin Login page
Admin User: Enters User ID, password and submits
System: Verifies login information and Provides Admin Home
Page, if Login Details are Correct.
Alternative Flows: System: Displays the Admin Login page

Admin User: Enters User ID, password and submits
System: Verifies login information and Provides an error
Message if login Details are incorrect
Business Rules: Admin User has to give Valid User ID and password for Logging;
if any one is incorrect login operation won’t be performed.

USE Case 1.0
Version:
Status: 2
Release: 1.0
Use Case Title: Adding new categories/subcategories
Actors: Admin User

providing valid URL (Admin login Page displays)

Entering Valid User ID and Password (Admin Home page
Displays)
Selecting ‘Catalog’ option in the Admin Home page
Selecting ‘Categories’ Option in the ‘Catalog’ menu
Normal Flow: System: Displays the ‘All Categories’ Page

Admin User: Selects ‘Add New Category’ option
System: Displays ‘Add New Category’ form
Admin User: enters parent, Category Name, sort order,
attaching logo by browsing.
Enters meta keywords, meta description and description(HTML)
and saves.
System: saves the details into the database

Alternative Flows: 1.System: Displays the ‘All Categories’ Page
Admin User: Selects ‘Add New Category’ option
Admin User: enters parent, Category Name, sort order
Selecting parameters like color, weight, dimensions etc…
Attaching logo by browsing.
Enters meta keywords, meta description and description(HTML)
and saves.
System: saves the details into the database
2. System: Displays the ‘All Categories’ Page

Admin User: cancels the form (without entering any data, after
entering some data and entering full data)
System: closes the form
Business Rules:

USE Case 1.0
Version:
Status: 2
Release: 1.0
Use Case Title: Viewing/Editing/deleting existing categories
Actors: Admin User
Displays)
Selecting ‘Categories’ Option in the ‘Catalog’ menu
Normal Flow: System: Displays the ‘All Categories’ Page
Admin User: selects Viewing/Editing/deleting option
System: displays selected category details(view).
displays selected category details for editing(editing).
Displays confirmation message for deleting(deleting)
Admin User: views and close(view)
Edits intended details and saves(editing)

Confirms deleting
System: closes the window(view)
Saves the modified details to the database(editing)
Deletes the category(deleting)
Alternative Flows:
Business Rules: Admin user can select one category at a time.

USE Case 1.0
Version:
Status: 2
Release: 1.0
Use Case Title: Adding new products
Actors: Admin User
Displays)
Selecting ‘Products’ Option in the ‘Catalog’ menu
Normal Flow: System: Displays the All Products page

Admin User: Selects ‘Add New Product’ option in the All
Products page.
Admin User: selects parent, enters product name and product
code, selects tax class, enters sort order, price(number only),
list price, In stock, shipping freight, weight, minimum order
quantity and description(HTML) and saves.
System: Saves the details into the database and provides ACK.
Alternative Flows: 1.System: Displays the All Products page

Admin User: Selects ‘Add New Product’ option in the All
Products page.
Admin User: selects parent, enters product name and product
code, selects tax class, enters sort order, price(number only),
list price, In stock, shipping freight, weight, minimum order
quantity.
Selects product configuration and enters color, dimension,
weight etc… details.
Selects product picture gallery and attaches picture, thumbnail,
enlarged picture by browsing.
2. System: Displays the All Products Page

Admin User: cancels the form (without entering any data, after

entering some data and entering full data)

System: closes the form
Business Rules:

USE Case 1.0
Version:
Status: 2
Release: 1.0
Use Case Title: Viewing/Editing/deleting existing product entry
Actors: Admin User
Displays)
Selecting ‘Products’ Option in the ‘Catalog’ menu
Normal Flow: System: Displays the All Products page

Admin User: Selects ‘Viewing/Editing/deleting option in the All
Products page.
System: displays selected product details in the separate
window (view).
displays selected product details for editing in the separate
window (editing).
Displays confirmation message for deleting(deleting)
Admin User: views and close(view)
Edits intended details and saves(editing)
Confirms deleting
System: closes the window(view)
Saves the modified details to the database(editing)
Deletes the product(deleting)
Alternative Flows:
Business Rules:

USE Case 1.0
Version:
Status: 2
Release: 1.0
Use Case Title: Importing products
Actors: Admin User


Displays)
Selecting ‘Catalog’ option in the Admin Home Page
Selecting Import Excel option In the Catalog menu.
Normal Flow: System: Displays the Import Excel Page
Admin User: Specifies Excel sheet path through ‘Browse’ option
and Submits.
System: Imports products from CSV (Excel sheet) file
Alternative Flows:
Business Rules: Admin User can Import One file at a time

USE Case 1.0
Version:
Status: 2
Release: 1.0
Use Case Title: Exporting products
Actors: Admin User
Displays)
Selecting ‘Catalog’ option in the Admin Home Page
Selecting export Excel option In the Catalog menu.
Normal Flow: System: Displays the Export Excel Page
Admin User: Exports Products
Alternative Flows:
Business Rules:

USE Case 1.0
Version:
Status: 2
Release: 1.0
Use Case Title: Special offers
Actors: Admin User
Displays)
Selecting ‘Special offers’ Option in the ‘Catalog’ menu
Normal Flow: System: Displays the Special offers page

Admin User: Selects Add new offer option
System: provides Add new offers page

Admin User: Selects product, enters product price ,discount

and saves
System: Saves the details into database
Alternative Flows: 1.System: Displays the Special offers page

Admin User: Selects Add new offer option
System: provides Add new offers page
Admin User: Selects product, enters product price ,discount,
selects Buy one get one free and saves
System: Saves the details into database
2. System: Displays the Special offers page

Admin User: cancels the form without filling any data, after
filling some data and after filling full data.
System: Closes the page.
Business Rules: Admin User

USE Case 1.0
Version:
Status: 2
Release: 1.0
Use Case Title: Defining Polls
Actors: Admin User
providing valid URL (Login window displays)
Displays)
Selecting ‘Module’ option in the Home page
Selecting ‘Polls’ option in the Module menu.
Normal Flow: System: Displays the Start New Poll page
Admin User: Enters a poll Question
Enters 3 Answer options each in separate line and Saves the
Details
System: accepts the details and sends for intended Process.
Gives Ack.
Alternative Flows: System: Displays the Start New Poll page
Admin User: Enters some data/all data and Choose Reset
option.
System: Clears the entered data.
Business Rules: Admin User has to type one Question and 3 answer options
(each in separate line).
Admin user can reset the data at any movement before saving
the data.

USE Case 1.0

Version:
Status: 2
Release: 1.0
Use Case Title: Adding news
Actors: Admin User
Displays)
Selecting ‘Module’ option in the Home page
Selecting ‘News’ option in the Module menu.
Normal Flow: System: Displays the Add News page
Admin User: Enters ‘Priority’, ‘Publish Date’ by selecting, and
Enters ‘News Title’.
Attaches ‘Logo’ through ‘Browse’ option and Adding text for
Publication in HTML format
Saves the Details
Alternative Flows: 1)System: Displays the Add News page

Admin User: Enters ‘Priority’, ‘Publish Date’ by selecting and
Enters ‘News Title’.
Attaches ‘Logo’ through ‘Browse’ option and Adding text for
Publication in HTML format
Enters News letter text and selects ‘Send this newsletter to
subscribers’ option.
Saves the Details
2) System: Displays the Add News page

Admin User: choose ‘Cancel’ option
System: Close the Add News page
Business Rules:

USE Case 1.0
Version:
Status: 2
Release: 1.0
Use Case Title: Reports

Actors: Admin User

Preconditions: connecting to IBEEeCom portal - Back End (Admin Interface) by
Displays)
Selecting ‘Reports’ option in the Home page
Selecting ‘Categories Reports/Products Reports’ option in the
Reports menu.
Normal Flow: System: Displays Categories Reports/Products Reports page

Admin User: selects ‘View reports’ option (link)
System: displays Categories Reports/Products Reports in a
separate window
Admin User: views the Report and Close.
Alternative Flows:
Business Rules:

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 freferable to do any task.
 Multiple flows (ways) are freferable to do any task.
 Home page Should be Centralized System (Screen/Window) to go to any
feature and to get any result.
 The fecility to return to Home page from any page Should available.
 Labels of all Objects in the entire system Must be in Understadable
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
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

Software Requirements Specification

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Software Requirements Specification

Uploaded by

Copyright:

Available Formats

For Software Testing Information visit: www.gcreddy.

Version 2.0 approved

IBEE Solutions (P) LTD

Name Role Date

Reviewed By Durga Prasad SA 25/02/2008

Approved By Pravin Ratta Project Manager 04/03/2008

For QTP Information & Scripts visit: www.gcreddy.com 1

A-Added, M-Modified, D-Deleted

For QTP Information & Scripts visit: www.gcreddy.com 2

1.1 Purpose of this document

1.2 Scope of this Document

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

For QTP Information & Scripts visit: www.gcreddy.com 3

4.2.1 Front end (Store front) Requirements

4.2.2 Back end (Administrative Tools) Requirements

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

For QTP Information & Scripts visit: www.gcreddy.com 4

1.1 Purpose of this document

2). Overall description

3). External Interface Requirements

For QTP Information & Scripts visit: www.gcreddy.com 5

3.1 User Interfaces

4). Functional Requirement Specifications (FRS)

4.1 System Features

Front end (customer storefront)

Back end (administrative tools)

For QTP Information & Scripts visit: www.gcreddy.com 6

o Product custom options

4.2 Functional Requirements

4.2.1 Front end (Store front) Requirements

Connecting to Application with Valid URL

U 1.3 Products Catalog

U 1.4 Products search

U 1.5 Advanced search

For QTP Information & Scripts visit: www.gcreddy.com 7

U 1.6 Products comparison

U 1.7 Shopping Process

U 1.8 Checking out (completing transaction by providing

U 1.9 Voting for poll

U 1.10 Viewing news