Sample SRS documentation
Page 1 of 6
Software Requirements Specification (SRS)
For
E-commerce Software of Marvel Electronics
Table of Contents
1. Introduction
1.1 Purpose
1.2 Scope
1.3 Definitions, Acronyms, and Abbreviations
2. Overall Description of the software
3.1 Functional Requirement
3.1.1 Sell Configured to Ordered Products.
3.1.2 Provide comprehensive product details.
3.1.3 Detailed product Categorizations
3.1.4 Provide Search facility.
3.1.5 Maintain customer profile.
3.1.6 Provide personalized profile
3.1.7 Provide Customer Support.
3.1.8 Email confirmation.
3.1.9 Detailed invoice for customer.
3.1.10 Provide shopping cart facility.
3.1.11 Provide multiple shipping methods.
3.1.12 Online tracking of shipments
3.1.13 Provide online Tax Calculations
3.1.14 Allow multiple payment methods.
3.1.15 Allow online change or cancellation of order.
3.1.16 Allow Online Product reviews and ratings
3.2 Non-functional requirement Usability
3.2.1 Usability
3.2.2 Reliability and Availability
3.2.3 Performance
3.2.4 Security
3.2.5 Supportability
3.3 Constraints
3.4 Conclusion
Software Requirements Specification
1. Introduction
The aim of this Software Requirement Specification (SRS) document is to gather and analyze and
give an in-depth insight of the complete Marvel Electronics and Home Entertainment software
system by defining the problem statement in detail. Nevertheless, it also concentrates on the
capabilities required by stakeholders and their needs while defining high-level product features.
The detailed requirements of the Marvel Electronics and Home Entertainment are provided in
this document.
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. Also, we shall predict and sort out
how we hope this product will be used in order to gain a better understanding of the project, outline
concepts that may be developed later, and document ideas that are being considered, but may be
discarded as the product develops.
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. Nonetheless, it helps any designer and developer to assist in
software delivery lifecycle (SDLC) processes.
1.2 Scope
Primarily, the scope pertains to the E-Store product features for making Marvel Electronics and
Home Entertainment project live. It focuses on the company, the stakeholders and applications,
which allow for online sales, distribution and marketing of electronics.
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 in-house and commercial software products. The standard can
be used to create software requirements specifications directly or can be used as a model for
defining a organization or project specific standard. It does not identify any specific method,
nomenclature or tool for preparing an SRS.
1.3 Definitions, Acronyms, and Abbreviations
| Configuration | It means a product which is available / Selected from a catalogue can be customized. |
| FAQ | Frequently Asked Questions |
| CRM | Customer Relationship Management |
| RAID 5 | Redundant Array of Inexpensive Disk/Drives |
2. Overall Description
This document contains the problem statement that the current system is facing which is hampering
the growth opportunities of the company. It further contains a list of the stakeholders and users of
the proposed solution. It also illustrates the needs and wants of the stakeholders that were identified
in the brainstorming exercise as part of the requirements workshop. It further lists and briefly
describes the major features and a brief description of each of the proposed system.
The following SRS contains the detail product perspective from different stakeholders. It provides
the detail product functions of E-Store with user characteristics permitted constraints, assumptions
and dependencies and requirements subsets.
3. Functional Requirements
(Explain what you mean by functional requirement with example – make one paragraph)
3.1.1 Sell Configured to Ordered Products.
3.1.1.1 The system shall display all the products that can be configured.
3.1.1.2 The system shall allow user to select the product to configure.
3.1.1.3 The system shall display all the available components of the product to configure
3.1.1.4 The system shall enable user to add one or more component to the configuration.
3.1.1.5 The system shall notify the user about any conflict in the current configuration.
3.1.1.6 The system shall allow user to confirm the completion of current configuration
3.1.2 Provide comprehensive product details.
3.1.2.1 The system shall display detailed information of the selected products.
3.1.2.2 The system shall provide browsing options to see product details.
3.1.3 Provide Search facility.
3.1.3.1 The system shall enable user to enter the search text on the screen.
3.1.3.2 The system shall enable user to select multiple options on the screen to search.
3.1.3.3 The system shall display only 10 matching result on the current screen.
3.1.3.4 The system shall enable user to navigate between the search results.
3.1.4 Email confirmation.
3.1.4.1 The system shall maintain customer email information as a required part of customer
profile.
3.14.2 The system shall send an order confirmation to the user through email.
3.1.5 Detailed invoice for customer.
3.15.1 The system shall display detailed invoice for current order once it is confirmed.
3.15.2 The system shall optionally allow user to print the invoice.
3.1.6 Provide shopping cart facility.
3.16.1 The system shall provide shopping cart during online purchase.
3.16.2 The system shall allow user to add/remove products in the shopping cart.
3.1.7 Online tracking of shipments
3.1.7.1 The system shall allow user to enter the order information for tracking.
3.17.2 The system shall display the current tracking information about the order.
3.2 Non-functional requirement
(Explain what you mean by non functional requirement with example – make one paragraph)
3.2.1 Usability through Graphical User Interface
• The system shall provide a uniform look and feel between all the web pages.
• The system shall provide a digital image for each product in the product catalog.
• The system shall provide use of icons and toolbars.
3.2.2 Reliability & Availability
• The system shall provide storage of all databases on redundant computers with automatic
switchover.
• The system shall provide for replication of databases to off-site storage locations.
• The system shall provide RAID V Disk Stripping on all database storage disks.
• The system shall provide a contractual agreement with an internet service provider for T3
access with 99.9999% availability.
• The system shall provide a contractual agreement with an internet service provider who can
provide 99.999% availability through their network facilities onto the internet.
3.2.3 Performance
• The product shall be based on web and has to be run from a web server.
• The product shall take initial load time depending on internet connection strength which also
depends on the media from which the product is run.
• The performance shall depend upon hardware components of the client/customer.
3.2.4 Security
• The system shall use secure sockets in all transactions that include any confidential customer
information.
• The system shall automatically log out all customers after a period of inactivity.
• The system shall confirm all transactions with the customer’s web browser.
• The system shall not leave any cookies on the customer’s computer containing the user’s
password.
• The system shall not leave any cookies on the customer’s computer containing any of the user’s
confidential information.
• The system’s back-end servers shall never display a customer’s password. The customer’s
password may be reset but never shown.
• The system’s back-end servers shall only be accessible to authenticated administrators.
• The system’s back-end databases shall be encrypted.
3.3 Constraints
(Explain what you mean by constraints with example – make one paragraph)
• The system shall be built using a standard web page development tool that conforms to either
IBM’s CUA standards or Microsoft’s GUI standards.
• There are no memory requirements
• The computers must be equipped with web browsers such as Internet explorer.
• The product must be stored in such a way that allows the client easy access to it.
• Response time for loading the product should take no longer than five minutes.
• A general knowledge of basic computer skills is required to use the product
3.4 Conclusion
……………………………………………………..
The post Software Requirements Specification (SRS) appeared first on My Assignment Online.