Software Requirements Specification
Software Requirements Specification
net
Software Requirements
Specification
For
IBEEeCom Portal
www.gcreddy.com
Document History
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)
Table of Contents
1). Introduction
1.3 Acronyms
1.4 References
7). Glossary
1). Introduction
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.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.
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.14 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.
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.)*
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.)*
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
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
Business Rules: Guest user has to enter all mandatory fields,
should maintain standard formats for emaild, date of birth.
Alternative Flows: Browsing through catalog or advanced search user can get info
Business Rules: Guest/Registered user should select one item at a time
Version:
Status: 2
Release: 1.0
Author: Prasanna Yadav and Sridhar Bale Rao
Use Case Title: Advanced search
Actors: Guest and Registered Users
Preconditions: Connecting to IBEEeCom portal - Front End (Customer Store
Front) by providing valid URL
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
System: Displays search related info if available otherwise it
shows message
Guest/Registered user: Views displayed products information
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.
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.
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.
System: Saves the details into the database and provides ACK.
Business Rules:
Alternative Flows:
Business Rules:
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)
Novell netware
5.3.2 Browsers
5.3.4 Hardwares
7). Glossary