Srs Template-Ieee Modified

Software Requirements Specification for
A2Z online Super Store
Version 1.0 approved
Software Requirements Specification for A2Z Online Super Store
Table of Contents
1. Introduction..............................................................................................................................1
1.1 Purpose.......................................................................................................................................1
1.2 Document Conventions..............................................................................................................1
1.3 Intended Audience and Reading Suggestions.............................................................................2
1.4 Product Scope.............................................................................................................................2
1.5 References..................................................................................................................................2
2. Overall Description..................................................................................................................3
2.1 Product Perspective....................................................................................................................3
2.2 Product Functions.......................................................................................................................3
2.3 User Classes and Characteristics................................................................................................3
2.4 Operating Environment..............................................................................................................4
2.5 Design and Implementation Constraints.....................................................................................4
2.6 User Documentation...................................................................................................................5
2.7 Assumptions and Dependencies.................................................................................................5
3. External Interface Requirements...........................................................................................5
3.1 User Interfaces............................................................................................................................5
3.2 Hardware Interfaces...................................................................................................................5
3.3 Software Interfaces.....................................................................................................................6
3.4 Communications Interfaces........................................................................................................6
4. System Features.......................................................................................................................7
4.1 Purchasing module.....................................................................................................................7
4.1.1 Description and Priority.........................................................................................................7
4.1.2 Functional Requirements........................................................................................................7
4.1.3 Interaction Matrix..................................................................................................................8
4.1.4 Priority Table.......................................................................................................................12
4.1.5 Traceability Matrix...............................................................................................................12
4.1.6 Checklist Items.....................................................................................................................13
4.2 Login Module............................................................................................................................13
4.2.1 Description and Priority........................................................................................................13
4.2.2 Functional Requirements......................................................................................................14
4.3 Customers’ Registration Module...............................................................................................14
4.4 Information Module..................................................................................................................14
5. Other Nonfunctional Requirements....................................................................................15
5.1 Performance Requirements.......................................................................................................15
5.2 Availability Requirements........................................................................................................15
5.3 Security Requirements..............................................................................................................15
5.4 Reliability Requirements..........................................................................................................16
6. Other requirements...................................................................................................................16
1
1. Introduction
Online shopping allows you to browse through endless possibilities, and even offers merchandise
that's unavailable in stores. If you're searching for a product that may not be distributed locally,
you're sure to find what you're looking for on the internet. What's even more useful is the ability to
compare items, similar or not, online. You can search through multiple stores at the same time,
comparing material quality, sizes and pricing simultaneously. Shopping via the internet eliminates the
need to sift through a store's products with potential buys like pants, shirts, belts and shoes all slung
over one arm. Online shopping also eliminates the catchy, yet irritating music, as well as the
hundreds, if not thousands, of other like-minded individuals who seem to have decided to shop on
the same day.
1.1 Purpose
The purpose of the project is to come up with electronic commerce system that is simple and secure
for users. The system will provide means by which clients can view products browse for
information about the products and then order or buy products online. The system will be able to
manage customers’ data, data about products in store and transaction made by the customers.
Management will be able to add, edit and view the products in the store, also administrator of the
system can view transaction made edit and even remove the transaction from the ecommerce
management system. Customers’ information will be kept confidential by system and online
administrator can view them.
1.2 Document Conventions
We have used IEEE SRS template to documents product requirements. We have used “Times New
Roman” as font style with font size 18 for main headings and 14 for subheadings and for normal
2
text it is 12 .Priorities for higher-level requirements are assumed to be inherited by detailed

requirements.
1.3 Intended Audience and Reading Suggestions
This document is intended for developers, project managers, marketing staff, users, testers,
contractors and documentation writers .SRS contains information about the web application to be
developed and requirements for its development .For main module of our product (i.e. web
application to be developed) this documents contain the requirements traceability matrix as well as
checklist items and interaction matrix. For reading purpose SRS sections are organized in following
order:
 Introduction
 Overall description
 External Interface Requirements
 System Features
 Other Non-Functional Requirements
 Other Requirements
1.4 Product Scope
Primarily, the scope pertains to the online super store features for making project live. It focuses on
the admin for modifications and manager for managing the products, special offers on store and
customer’s registration and customer for making purchases as well as registering itself to avail
special offers and to get information about store.
This SRS is also aimed at specifying requirements of software to be developed but it can also be
applied to assist in the selection of inhouse and commercial software products. The standard can be
used to create software requirements specifications directly or can be used as a model for defining
an organization or project specific standard. It does not identify any specific method, nomenclature
or tool for preparing an SRS.
3
1.5 References
The references are:
 A2Z Online Super Store System Use case Diagram
 A2Z Online Super Store System Sequence diagram
 A2Z Online Super Store System ERDiagram
 A2Z Online Super Store System Class Diagram
 A2Z Online Super Store System Activity Diagram
 A2Z Online Super Store System Test cases
All the references will be attached later.
2. Overall Description
2.1 Product Perspective
Our product that is A2Z Online Super Store is a self-contained product. It is going to replace the
traditional commerce with e-commerce for A2Z Super Store.
2.2 Product Functions
 Our system will allow different customers to buy products online.

 It will have a login module for administrator to access and then modify the system, for
manager to manage information and details and for registered customers it will provide
access to the special offers so that they can avail them.
 It will show news related to the new or special offers, arrival of new products etc.
 It will allow customers’ registration so that they will enjoy some special offers available only
to the registered customers.
4
 It will also allow user to get information about our store’s background, contact
information(e-mail, phone #/mobile #, Facebook/twitter)
2.3 User Classes and Characteristics
 Administrator can
 Login
 Insert, delete & update products information in database.
 Delete & update registered customer’s information in database.
 Change contents of web application.
 Manager can
 Login
 Manage information and details of products their orders and the registered users.
 Customers can
 View products information as well as other information available on our web
application.
 Order products
 Register themselves.
 Login
2.4 Operating Environment
Our product can be operated on any bowser like Google chrome, Mozilla Firefox, Microsoft Edge
etc. on PC, laptops, and cell phones having operating system that can be anyone of Microsoft
Windows, Mac OS, and Linux etc.
2.5 Design and Implementation Constraints
Development should take place on a laptop or some PC.Tools for development of our product
should be Xampp server and Dreamweaver. For database we use MySQL database from Xampp
server. Database connection string should be saved on a separate file so that whenever or wherever
5
in a file it will be needed it will be simply included in that file. Scripting languages for client side
scripting should be JavaScript and for server side scripting it should be php.Data should be made
secure through encryption or by creating sessions through login module. Our web application
should have attractive and colorful interfaces with a professional look.
2.6 User Documentation
User manual will be provided along with the system that will help the end user (owner) for operating
the system. Some additional documents will also be provided to the help the system owner for
making basic modifications in the system.
2.7 Assumptions and Dependencies
The Customer must have basic knowledge of computers, English Language and e-commerce.
3. External Interface Requirements
3.1 User Interfaces
 Xampp server
 System developers will use it to develop database and then for its testing also for writing
sever side scripts.
 Admin will use it for database management.
 Dreamweaver
 System developers will use it to design html pages, CSS styles for them and to connect
web pages to MySQL database server.
 Browsers
6
 All end users will use them to interact with the system.
3.2 Hardware Interfaces
 Login module
 MySQL database that is saved on some storage e.g hard drive will be accessed,
processed and managed through php along with the use of html tags and JavaScript.
 Purchasing module
 MySQL database that is saved on some storage e.g hard drive will be updated through
php along with the use of html tags and JavaScript.
 Browsing Module
 Data from MySQL database that is saved on some storage e.g hard drive will be
searched through php along with the use of html tags and JavaScript.
 Registration Module
 Data will be entered in MySQL database through php, html tags along with JavaScript
that is will be saved on some storage e.g hard drive.
3.3 Software Interfaces
 Our system is composed of website with dynamic contents and static content.
 Adobe Dreamweaver, Xampp server and browsers (such as Google chrome, Microsoft Edge
etc) will be used by the system.
 Data will be retrieved and submitted to the database through browsers as well as MySQl
itself. Input for database will be products information as well as registered users’
information and the information about users of the system.
 Similarly the output will be same.
 Using dynamic webpages users will login to the system.
7
 Dynamic webpages will be available for browsing.
 On finalizing the purchase order a confirmation message will be displayed and then a page
will be opened that will show order details.
 Using dynamic webpages users will register themselves.
3.4 Communications Interfaces
 Google chrome, Microsoft Edge, Mozilla Firefox etc will be used by user for
communication with the system.
 MySQL database will be assessed through php.
 Modules will communicate with each other through php and html tags.
 The estore system shall use the HTTP protocol for communication over the internet and for
the intranet communication will be through TCP/IP protocol suite.
4. System Features
The system to be developed will allow browsing and then online purchasing of super store items,
login for registered users as well as for admin, manager, registration for unregistered users and
provide information about the store.
4.1 Purchasing module
4.1.1 Description and Priority
This module will calculate bill and display order details and on completion of order making process
this module will send order notification to the manager. Calculations for this module should be
accurate and error free. This module will have highest priority.
8
4.1.2 Functional Requirements
R1: In this module user must enter product id, its quantity and his/her address in three
separate fields labeled as “Product id:”, “Product Quantity:” and “Address: ”
respectively.
R2: On clicking a button named as “make purchase” system must check all the fields that
they are filled or not.
R3: System must show an alert dialog box if fields are missing and then focus on the missing
fields without proceeding further.
R4: On successful data entry in fields system must show a dialog box with order details.
R5: System must calculate bill and display total amount in a field labeled as “Total amount:”
when a button named as “done” is clicked in this module.
R6: System must send order notification to the manager.
4.1.3 Interaction Matrix
R1 R2 R3 R4 R5 R6 R7 R8 R9 R10
R1 0 1 0 0 1 1 1000 0 0 1 1004
R2 1 0 0 1 0 0 0 1 1 0 4
R3 0 0 0 0 1 0 0 1000 1 1 1003
R4 0 1 0 0 1000 1 0 1 1000 1 2004
R5 1 0 1 1000 0 1000 1 0 1000 1000 4003
R6 1 0 0 1 1000 0 0 1 1 0 1004
R7 1000 0 0 0 1 0 0 1000 0 0 2001
R8 0 1 1000 1 0 1 1000 0 1 0 2004
R9 0 1 1 1000 1000 1 0 1 0 0 2004
R10 1 0 1 1 1000 0 0 0 0 0 1003
Requirements R4, R8 & R9 have same sum so
R4: R8:
I O C I O C
4 2 4 4 2 4
R9:
I O C
4 2 4
9
As requirements R4, R8 & R9 have same overlapping no as same conflicting no
so now we will check sub tables.
 R4’s overlapping requirements:
R5: R9:
I O C I O C
3 4 3 4 2 4
Sum of overlapping = 4+2=6
R3: R7:
I O C I O C
6 1 3 7 2 1
R4: R5:
I O C I O C
4 2 4 3 4 3
Sub tables of R4 and R9 have same overlapping and conflicting sum so now we
will check further sub tables.
 R5’s overlapping requirements under R4’s overlapping requirements
R4: R6:
I O C I O C
4 2 4 5 1 4
10
R9: R10:
I O C I O C
4 2 4 6 1 3
Overlapping sum=2+1+2+1=6 Conflicting sum=4+4+4+3=15
 R4’s overlapping requirements
R4: R5:
I O C I O C
4 2 4 3 4 3
Overlapping sum=2+4=6 Conflicting sum=4+3=7
Total sum of R5’s and R9’s sub conflicting/overlapping requirements
 R4’s conflicting/overlapping requirements under R9’s overlapping
requirements
R4: R5:
I O C I O C
4 2 4 3 4 3
 R5’s overlapping requirements under R9’s overlapping requirements
R4: R6:
I O C I O C
4 2 4 5 1 4
R4: R10:
I O C I O C
4 2 4 6 1 3
11
Overlapping sum=6Conflicting
sum=15
Total overlapping requirements sum
By comparison of the values of sum of total overlapping and conflicting we
came to know that R4 and R9 will have same priority and then there came R8.
R6 and R1 have same sum.
 R6’s requirements table :  R1’s requirements table:
I O C I O C
5 1 4 5 1 4
Overlapping and conflicting requirements of both R1 and R6 are same.
 R6’s requirements table :
R5:
I O C
3 4 3
 R1’s requirements table:
R7:
I O C
5 1 4
On comparison of overlapping values of both tables we get that R6 has greater
priority then R1.
R3 and R10 have same sum so
R10’s requirements table:
I O C
12
6 1 3
 R3’s requirements table:
I O C
6 1 3
 R10’s overlapping table:
R5:
I O C
3 4 3
 R10’s overlapping table:
R8:
I O C
4 2 4
On comparison of overlapping values of above tables we came to know that R10
has higher priority than R3.
4.1.4 Priority Table
Requirements Priority
R5 1
R4 & R9 2
R9 3
R7 4
R6 5
R1 6
R10 7
R3 8
R2 9
4.1.5 Traceability Matrix
13
Related to System
Who Relation with Other
Module Requirement Why it Exist? Design, Implementation
suggest? Requirement
and User Doc.
14
To get order
R1 User No Design
details
To check
R2 Designer whether data is No Design & Implementation
complete or not
To inform user
R3 Developer about missing R2 Design & Implementation
fields
To inform user
R4 Developer about details of No Design
their order
User,
For bill
R5 Designer & R3 Design & Implementation
calculation
Developer
To inform
R6 User manager about R5 Implementation
an order
4.1.6 Checklist Items
R1 R2 R3 R4 R5 R6
Business Goals? Y Y Y Y Y Y
Realism Y Y Y Y Y Y
Premature Design N N N N N N
Unnecessary Requirements N N N N N N
Requirement Ambiguity N N N N N N
Combined Requirements Y N Y N Y N
Requirements Testability Y Y Y Y Y Y
Use of nonstandard hardware N N N N N N
15
4.2 Login Module
This module is developed for the admin, manager and customer.Manager

manages orders.Admin will use this module to view,modify,add,delete records.
Customer will use it to enter into his/her registered account for making
discounted purchases.
R7: User have to enter user name and password.

R8: If any of the field is empty on clicking done button then On-Focus
event will be called.And it will focus on the empty text field.
R9: If any of the field is incorrect dialog box will be appeared that notify
about error.User will have to refill the text fields.
R10: If both the fields are correct user will log into the specified account.
4.3 Customers’ Registration Module
This module is developed for the customers.

In this module user have to fill a form and have to pay certain amount to get 20%
discount on each purchase.
R11: User click on Registration button.

R12: Fill the form.
R13: Select payment method.
R14: Press Done button.
16
R15: If any of the field is empty or incorrect on pressing Done button,On-

Focus event will be called.
R16: If every field is filled and is correctly filled then on pressing Done
button,a notification will be send to the Admin
4.4 Information Module
Information module contains information about the store.This is a static webpage.
R17: User click on the Store Details tab.

R18: Get details about the store on clicking Get Details tab.
5. Other Nonfunctional Requirements
5.1 Performance Requirements
It is the system’s ability to meet latency, throughput and resource utilization

requirements.
 All Web pages must download within three seconds during an average
load, and five seconds during a peak load.
 While executing a search, the system must be able to display 20 search

results.
17
5.2 Availability Requirements
6. System is available to users 24/7.
7. In case of a of a hardware failure or database corruption, system should

redirect user to some other specified page.
7.1 Security Requirements
It’s the ability to prevent and/or forbid restricted actions.
 Login page in the system shall authenticate the user.
 User's that are not allowed to view specific areas of the systems will be
redirected to the login page.
7.2 Reliability Requirements
 Because of importance of data the system should be reliable as incorrect

or incomplete data can damage data.
 Reliability can be achieved through backup of database that will be

continuously maintained and updated reflect each change.
8. Other requirements
 System should have a colorful but professional look.

Srs Template-Ieee Modified

Uploaded by

Copyright:

Available Formats

Srs Template-Ieee Modified

Uploaded by

Document Information

Original Description:

Original Title

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

Srs Template-Ieee Modified

Uploaded by

Copyright:

Available Formats

Software Requirements Specification for

A2Z online Super Store

Version 1.0 approved

text it is 12 .Priorities for higher-level requirements are assumed to be inherited by detailed

 Our system will allow different customers to buy products online.

Development should take place on a laptop or some PC.Tools for development of our product

 R4’s conflicting/overlapping requirements under R9’s overlapping

4.2 Login Module

4.2.1 Description and Priority

This module is developed for the admin, manager and customer.Manager

4.2.2 Functional Requirements

R7: User have to enter user name and password.

4.3 Customers’ Registration Module

4.3.1 Description and Priority

This module is developed for the customers.

4.3.2 Functional Requirements

R11: User click on Registration button.

R15: If any of the field is empty or incorrect on pressing Done button,On-

4.4 Information Module

4.4.1 Description and Priority

Information module contains information about the store.This is a static webpage.

4.4.2 Functional Requirements

R17: User click on the Store Details tab.

It is the system’s ability to meet latency, throughput and resource utilization

 While executing a search, the system must be able to display 20 search

6. System is available to users 24/7.

7. In case of a of a hardware failure or database corruption, system should

It’s the ability to prevent and/or forbid restricted actions.

 Login page in the system shall authenticate the user.

 Because of importance of data the system should be reliable as incorrect

 Reliability can be achieved through backup of database that will be

You might also like