E-Learning Project Software Requirements Specification Version
E-Learning Project Software Requirements Specification Version
E-Learning Project Software Requirements Specification Version
Revision History
Date Version Description Author
Table of Contents
1. Introduction 4
1.1 Purpose 4
1.2 Scope 4
1.3 Definitions, Acronyms, and Abbreviations 5
1.4 References 5
1.5 Overview 5
2. Overall Description 5
3. Specific Requirements 6
3.1 Functionality 6
3.1.1 User Registration 6
3.1.2 User Login 6
3.1.3 Course Details 6
3.1.4 Enrollment 6
3.2 Usability 7
3.2.1 Graphical User Interface 7
3.2.2 Accessibility 7
3.2.3 User Interfaces 7
3.2.4 Hardware Interfaces 7
The introduction of the Software Requirements Specification (SRS) provides an overview of the
entire SRS with purpose, scope, definitions, acronyms, abbreviations, references and overview of
the SRS. The aim of this 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.
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
1.4 References
The references are:
1.5 Overview
The remaining sections of this document provide a general description, including characteristics
of the users of this project, the product's hardware, and the functional and data requirements of
the product. General description of the project is discussed in section 2 of this document.
Section 3 gives the functional requirements, data requirements and constraints and assumptions
made while designing the E-Store. It also gives the user viewpoint of product. Section 3 also
gives the specific requirements of the product. Section 3 also discusses the external interface
requirements and gives detailed description of functional requirements. Section 4 is for
supporting information.
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. Specific Requirements
3.1 Functionality
Introduction –
This subsection contains the requirements for the e-store. These requirements are organized by
the features discussed in the vision document. Features from vision documents are then refined
into use case diagrams and to sequence diagram to best capture the functional requirements of
the system. All these functional requirements can be traced using tractability matrix.
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.6The system shall allow user to update the configuration to resolve conflict in the current
configuration.
3.1.1.7 The system shall allow user to confirm the completion of current configuration
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.4 Enrollment
The system shall enable user to enter the search text on the screen.
The system shall enable user to select multiple options on the screen to search.
The system shall display all the matching products based on the search
The system shall display only 10 matching result on the current screen.
The system shall enable user to navigate between the search results.
The system shall notify the user when no matching product is found on the search.
3.2 Usability
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.
3.2.2 Accessibility
The user interface for the software shall be compatible to any browser such as Internet
Explorer, Mozilla or Netscape Navigator by which user can access to the system.
The user interface shall be implemented using any tool or software package like Java
Applet, MS Front Page, EJB etc.
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.