Preparation of an SRS Document

1.0 Revision History

Version Number Date Author(s) Comments
1.0 2/15/05 Jane Smith Original

2.0 Introduction
2.1 Purpose of this document
This document specifies the software requirements for the XXX system. This
document includes functional and non-functional user requirements, that were gathered in
the requirement analysis phase.
2.2 Scope of this document
The scope of this document includes an overview of the XXX system, detailed
information about the requirements, including functional requirements, interface
requirements, performance requirements, non-functional requirements and additional
constraints of the system.
2.3 Definitions, Acronyms and Abbreviations
• SRS – Software Requirement Specification
• User – a person who will be using the system for its intended purpose
• Will – indicates a prediction or description of intent
• Shall - indicates a binding prediction
• Etc.
2.4 Business Context
The XXX company has as it’s main mission to provide XXXXXX to consumers. The
Mission Statement of the company is:
SSSSS
The goals of the organization are:
SSSSS
2.5 Overview
The remaining part of this document follows the IEEE STD 830-1993 format. Section 3
will cover the product perspective, functions, user characteristics, constraints and
assumptions. Section 4 will cover the functional and non-functional requirements.
Section 5 will cover the operational requirements.

3.0 General Description

3.1 Product Perspective
The system will be developed using XX, XXX, and XXX. (such as VB, HTML and SQL
Server 2000).
3.2 Product Functions
The product developed will provide an easy access to XXXX for consumers to order
products. The major functions of the system are:
• Provide products online to customers
 • Provide payment options
• Etc.

3.3 User characteristics

The users of the system are customers ordering products from their home or office
computer. These users have a basic knowledge of computers, but may need help
navigating through on-line ordering.
3.4 General Constraints
• The cost constraint includes ordering additional hardware to run the new system
• No current web-site
• Security must be upgraded for on-line purchasing
3.5 Assumptions
• The system will run on a XXX platform
• The processor must be XXX
• The hardware for the clients must be provided by the client
• Etc.

4.0 Requirements
4.1 Functional Requirements
The user should be able to order all products on-line through the designed web site; make
a payment (billed); receive an order confirmation and shipping date.
4.1.1 Login by customer
The system should allow the customer to login under a secure system. A new user should
be allowed to enter new information.

4.1.2 Place Order by customer

The system should allow the customer to place an order on-line for the products they
want.
4.1.2.1 Introduction
The system should be able to verify the orders placed and confirm if the order placed is
available in the warehouse.
4.1.2.2 Inputs
• Customer’s list of desired products
• Customer detailed information for ordering and shipping
4.1.2.3 Processing
Customers will be validated upon entering the system. Orders will be verified as to
product number, availability. Orders will be updated into the database. An electronic bill
will be generated for the customer real-time. The customer will be provided different
methods for payment including credit card or on-line check. After accepting payment,
verification of payment will be sent to bank center for processing. After receiving
confirmation, this will be transmitted to customer and date for shipping will be calculated
and displayed.
4.1.2.4 Outputs
The customer is sent a verification of payment and a verification of shipping date.
4.1.3 Order confirmed and billing statement (invoice) processed
4.1.3.1 Introduction
XXX

4.1.3.2 Inputs
XXX
4.1.3.3 Processing
XXX
4.1.3.4 Outputs
XXX

4.2 Interface Requirements

4.2.1 User Interfaces
4.2.1.1 The Home Screen
The home screen will give general information about the company, catalog, help, login
(existing customer), new customer and contact information.
4.2.1.2. Login Screen
This screen will …..
4.2.1.3 Create New Customer Screen
This screen will allow a new customer to create a login and password.
4.2.1.4 Catalog Main Screen
This screen will list the main categories for products.
4.2.1.4.1 First Category Product Screen
This screen lists the products in the first major category.
4.2.1.4.2 Second Category Product Screen
XXX…
4.2.1.5 Etc.

4.2.2 Hardware Interfaces

All necessary hardware interfaces will be provided by the host operating system …

4.2.3 Software Interfaces

The system shall be compatible to work on Internet Explorer or Netscape web browsers.

4.2.4 Communications Interfaces

The system needs to be able to communicate with the bank for verification of funds or
credit card information.

4.3 Performance Requirements

4.3.1 Number of employees
XXX
4.3.2 Number of customers
XXX
4.3.3 Web page response time
XXX
4.4 Design Constraints
4.4.1 Standard Compliance
The IEEE format is used for the technical documentation specification in this document.
4.4.2 Hardware Constraints
The software system runs on Windows….. that requires ….
4.4.3 Software Constraints (limitations)
The system shall meet all performance requirements running on the VB 6.0 application
with Microsoft Access database on the hardware specified in 4.4.2.
4.4.4 Other Constraints
XXX

4.5 Operational and other Requirements

4.5.1 Database
The database platform will be Microsoft Access 2000….
4.5.1.1 Database table retention
The database tables will be kept for ….
4.5.2 Security
XXX
4.5.3 Audit Trail
XXX
4.5.4 Recovery
XXX
4.5.5 System Availability
XXX
4.5.6 Performance
XXX
4.5.7 Capacity
XXX
4.5.8 Reporting
XXX
4.5.9 Portability
XXX
4.5.10 Documentation
XXX