草帘-internat
标准文档
E-Store Project
错误！未指定书签。
Version
<4.0>
文案大全
标准文档
Revision
History
Date
<04/13/14>
<04/15/14>
<04/15/14>
<04/16/07>
Version
<1.0>
<2.0>
<3.0>
<4.0>
Description
SRS 1.0
SRS 2.0
SRS 3.0
SRS 4.0
Author
Group-1
Group-1
Group-1
Group-1
文案大全
标准文档
Table of
Contents
1.
Introduction
5
1.1
Purpose
5
1.2
Scope
5
1.3
Definitions,
Acronyms, and Abbreviations
6
1.4
References
6
1.5
Overview
6
2.
Overall Description
7
3.
Specific Requirements
7
3.1
Functionality
7
3.1.1
Sell
Configured to Ordered Products.
7
3.1.2
Provide
comprehensive product details.
8
3.1.3
Detailed
product Categorizations
8
3.1.4
Provide
Search facility.
8
3.1.5
Maintain
customer profile.
9
3.1.6
Provide
personalized profile
9
3.1.7
Provide
Customer Support.
9
3.1.8
Email
confirmation.
10
3.1.9
Detailed
invoice for customer.
10
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.1.17
Offer
financing options.
3.1.18
Provide detailed sitemap.
3.1.19
Offer
online promotions and rewards.
3.1.20
Online
Purchase of products.
3.2
Usability
12
3.2.1
Graphical
User Interface
12
3.2.2
Accessibility
12
3.3
Reliability &
Availability
13
3.3.1
Back-end
Internal Computers
13
3.3.2
Internet
Service Provider
13
3.4
Performance
12
3.5
Security
13
3.5.1
Data
Transfer
13
3.5.2
Data
Storage
14
3.6
Supportability
13
3.6.1
Configuration Management Tool
13
3.7
Design Constraints
13
3.7.1
Standard
Development Tools
13
3.7.2
Web Based
Product
13
文案大全
10
10
11
10
11
< br>11
11
11
12
11
12
标准文档
3.8
On-line User
Documentation and Help System Requirements
3.9
Purchased
Components
3.10
Interfaces
3.10.1
3.10.2
3.10.3
3.10.4
3.11
Licensing
Requirements
3.12
Legal, Copyright, and Other Notices
3.13
Applicable
Standards
4.
Supporting Information
文案大全
13
13
14
User
Interfaces
14
Hardware Interfaces
14
Software
Interfaces
14
Communications Interfaces
15
15
15
15
15
标准文档
错误！未指定书签。
1.
Introduction
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.
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
Redundant Array
of Inexpensive Disk/Drives
RAID
5
1.4
References
The references are:
?
E-Store
Structural Model
?
E-Store Behavioral Model
?
E-Store NFR
Model
?
Vision
Draft 5
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
The specific
requirements are
–
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
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 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
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
Detailed
product Categorizations
The
system shall display detailed product
categorization to the user.
3.1.4
Provide
Search facility.
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.
文案大全