Professional Documents
Culture Documents
Homeworkping.com
Homework Help
https://www.homeworkping.com/
Online Tutoring
https://www.homeworkping.com/
This is the software requirements specifications (SRS) document for the NAB
Computers Online Shopping System. In particular, the document details the specifications of
Checkout and Ordering process of the system. The intended audience of the SRS are users,
system administrators and as per request the customer. Also, any future maintenance staff
should be aware of the information contained herein. However, foreknowledge of certain
computer systems and basic knowledge of computers is an asset to understanding the SRS.
Table of Contents
Signature....................................................................................................................................................................................3
Change History..........................................................................................................................................................................4
Preface........................................................................................................................................................................................5
Table of Contents.......................................................................................................................................................................6
List of Figures............................................................................................................................................................................7
List of Tables..............................................................................................................................................................................8
1. Introduction...........................................................................................................................................................................9
1.1. Purpose............................................................................................................................................................................................. 9
1.2. Scope................................................................................................................................................................................................ 9
1.3. Definitions, Acronyms and Abbreviations........................................................................................................................................9
1.4. References...................................................................................................................................................................................... 10
1.5. Overview........................................................................................................................................................................................ 10
2. Overall Description..............................................................................................................................................................11
2.1. Product perspective......................................................................................................................................................................... 11
2.2. Product functions............................................................................................................................................................................ 11
2.3. User characteristics......................................................................................................................................................................... 12
2.4. Constraints..................................................................................................................................................................................... 12
2.5. Assumptions and dependencies......................................................................................................................................................12
3. Specific Requirements ........................................................................................................................................................13
3.1. External interface requirements......................................................................................................................................................13
3.1.1. User interfaces...................................................................................................................................................................... 13
3.1.2. Hardware interfaces.............................................................................................................................................................. 13
3.1.3. Software interfaces................................................................................................................................................................ 13
3.1.4. Communications interfaces...................................................................................................................................................14
3.2. Functional requirements.................................................................................................................................................................14
3.2.1. Use case 1............................................................................................................................................................................. 14
3.2.2. Use case 2............................................................................................................................................................................. 21
3.3. Performance Requirements.............................................................................................................................................................21
3.4. Design constraints......................................................................................................................................................................... 21
3.5. Software system attributes.............................................................................................................................................................. 21
3.6. Other requirements......................................................................................................................................................................... 22
4. Appendixes...........................................................................................................................................................................23
5. Index.....................................................................................................................................................................................24
List of Figures
List of Tables
Software Requirements Specifications Document Version: N.n
Insert Title Here Published Date: DD MMMM YYYY
1. Introduction
1.1. Purpose
The purpose of the document is to collect and analyze all assorted ideas that have come
up to define the system, its requirements with respect to consumers. In short, the purpose of
this SRS document is to provide a detailed overview of our software product, its parameters
and goals. This document describes the project's target audience and its user interface,
hardware and software requirements. It defines how our client, team and audience see the
product and its functionality.
1.2. Scope
NAB Computers Online Shopping System is designed to provide quality service to the
customers and to allow new online store owners a quick and easy means to setup and
perform sales and other core business over the internet. The system requires Internet
connection and has to be designed with a database capable of maintaining inventory details
up-to-date. All payments will be through cash during the delivery or shipping of items.
Inventory – Merchandise that is purchased and/or produced and stored for eventual sale
transmitted information.
Page 9 of 24
Software Requirements Specifications Document Version: N.n
Insert Title Here Published Date: DD MMMM YYYY
Ethernet – a family of frame – based computer networking technologies for Local Area Net
works.
MySQL – is a RDBMS based on SQL, which is used for adding, removing, and modifying
information in the database.
XAMPP -
1.4. References
IEEE. IEEE Std 830-1998 IEEE Recommended Practice for Software Requirements
Specifications
1.5. Overview
Page 10 of 24
Software Requirements Specifications Document Version: N.n
Insert Title Here Published Date: DD MMMM YYYY
2. Overall Description
The product is a web-based system that allows the customer to shop virtually using the
Internet and allow customers to buy the items of their desire from the store. It is aimed
towards the vendors who want to reach out to the maximum cross-section of customer and
common people who can be potential customer. It should be user-friendly, ‘quick to learn’ and
reliable application for the above purpose.
Customer module
Administrator module
- Any visitor is allowed to browse through the product list, their prices and bidding
procedures.
Account Management (AM): AM allows users to create, edit, and view accounts information. It
also allows the user to log-in/out of the system.
Search Engine (SE): SE is the tool that assists the user in finding a specific item in the
database. It can receive search criteria, find search criteria, and return
the results of the search.
Product Management (PM): PM allows administrator to manage the product line shown on
the web site.
Shopping Cart (SC): SC is temporary storage for customers shopping on the web. Items from
the inventory can be reserved in a virtual cart until the customer decides
to purchase them.
Page 11 of 24
Software Requirements Specifications Document Version: N.n
Insert Title Here Published Date: DD MMMM YYYY
Purchasing and Payment (PP): PP is used to approve and transfer payment from buyers
when purchasing items in the cart.
There are following types of users in the NAB Computers Online Shopping System.
Administrators: The administrators have complete control over all the activities that can be
performed.
Customers: They are the registered members of the online store website. They can view
the list of products and purchase items.
2.4. Constraints
- The main constraint here would be the checking the genuineness of the buyer,
which is not always possible. There can be security risks involved.
Page 12 of 24
Software Requirements Specifications Document Version: N.n
Insert Title Here Published Date: DD MMMM YYYY
3. Specific Requirements
The user interface shall be web-based, allowing users to remotely access the system
via several applications. Users will be able to use the software through applications such as
Microsoft Internet Explorer, Mozilla, et al. Each part of the user interface intends to be as user
friendly as possible. The fonts and buttons used will be intended to be very fast and easy to
load on web pages. The pages will be kept light in space so that it won’t take a long time for
the page to load. The starting page will be a home page regarding the store and a number of
buttons with the specific category of the products sold. The customer will be given an option
to search a product or a category through the search engine provided in the website. In
adding product to his/her cart, the customer will only have to drag the desired product to be
purchased and drop it to the cart. While in removing the product, he/she will select the item in
the cart, and specify quantity of items to be removed and clicks the button ‘Remove Item’.
There will be buttons added for the managing of accounts of the customer and the
administrator.
Since the application must run over the internet, all the hardware shall require to connect
internet will be hardware interface for the system. As for e.g. Modem, WAN – LAN, Ethernet
Cross-Cable.
During our system development, we have to design both static and dynamic website
interfaces, create website functions and a database system, edit photos and pictures, and
print out reports, so its has a set of software requirements.
Page 13 of 24
Software Requirements Specifications Document Version: N.n
Insert Title Here Published Date: DD MMMM YYYY
The system shall use the HTTP protocol for communication over the internet.
Steps:
Page 14 of 24
Software Requirements Specifications Document Version: N.n
Insert Title Here Published Date: DD MMMM YYYY
Steps:
Steps:
Steps:
1. Customer clicks the button or link to initiate the process to edit the account.
2. System displays the account home page to the Customer.
3. Customer clicks the button or link in order to edit the account details.
4. System verifies the changes.
5. System stores new account information.
Page 15 of 24
Software Requirements Specifications Document Version: N.n
Insert Title Here Published Date: DD MMMM YYYY
Steps:
Page 16 of 24
Software Requirements Specifications Document Version: N.n
Insert Title Here Published Date: DD MMMM YYYY
Steps:
1. Customer selects the item in the cart and clicks the button to initiate the deletion of
item(s).
2. System prompts the customer to specify quantity of items to remove from cart.
3. Customer confirms the number of items to remove.
4. System removes the item(s) from the cart.
Page 17 of 24
Software Requirements Specifications Document Version: N.n
Insert Title Here Published Date: DD MMMM YYYY
Administrator
Steps:
Steps:
Page 18 of 24
Software Requirements Specifications Document Version: N.n
Insert Title Here Published Date: DD MMMM YYYY
Steps:
Page 19 of 24
Software Requirements Specifications Document Version: N.n
Insert Title Here Published Date: DD MMMM YYYY
Steps:
1. Administrator clicks the button or link to initiate Update Product Attributes process.
2. System prompts the Administrator to select a product by searching or viewing a list of
products.
3. System displays all of the product attributes and allows Administrator to update the
product name, product id, product description, product price, update the product
image, product availability, and/or the number of items in the inventory.
4. System validates the product information.
5. System updates the product page and product information within the system.
6. System displays the newly updated product page.
Page 20 of 24
Software Requirements Specifications Document Version: N.n
Insert Title Here Published Date: DD MMMM YYYY
Maximum possible quick response to the orders is required, also should provide fast
updation of records. The changes if any made should be reflected automatically in the next
screens.
The design constraints are that the browser at each place may not follow similar screen
resolutions, browsers etc. This can lead to the website not having the impact it is planned to
have.
3.5.1 Security:
The application is password protected and also any updation of new product entries
and order processing is done by only privileged users.
3.5.2 Maintainability:
3.5.3 Reliability:
3.5.4 Portability
Page 21 of 24
Software Requirements Specifications Document Version: N.n
Insert Title Here Published Date: DD MMMM YYYY
Page 22 of 24
Software Requirements Specifications Document Version: N.n
Insert Title Here Published Date: DD MMMM YYYY
4. Appendixes
Page 23 of 24
Software Requirements Specifications Document Version: N.n
Insert Title Here Published Date: DD MMMM YYYY
5. Index
Page 24 of 24