Software Requirements Specification

<Organization>
< Project Name>

Software Requirements Specification
<mm dd yyyy>
<Version n.n>
<Security Notice>
Approvals Signature Block
Organization Responsibility Signature Date

Customer /customer representative
Project Manager
Software Quality Assurance Leader
Software Configuration Management
Leader
User Documentation Leader
User Training Leader
The document in this file is adapted from the IEEE standards for Software Project
Requirements Specifications, 830-1998, which conforms to the requirements of
ISO standard 12207 Software Life Cycle Processes. Tailor as appropriate.
Items that are intended to stay in as part of your document are in bold; blue italic
text is used for explanatory information that should be removed when the
template is used.
2 v. 1.4 14 January 2004

Table of Contents
To update Table of Contents first complete the document then click to the left of the index
below and Press F9.
1. INTRODUCTION ...............................................................................................................................5
1.1 PURPOSE ............................................................................................................................................5
1.2 SCOPE ................................................................................................................................................5
1.3 DEFINITIONS, ACRONYMS, AND ABBREVIATIONS................................................................................5
1.4 REFERENCES ......................................................................................................................................5
1.5 OVERVIEW .........................................................................................................................................5
2. OVERALL DESCRIPTION ...............................................................................................................6
2.1 PRODUCT PERSPECTIVE .....................................................................................................................6
2.1.1 System Interfaces.................................................................................................................... 6
2.1.2 User Interfaces........................................................................................................................ 6
2.1.3 Hardware Interfaces................................................................................................................ 6
2.1.4 Software Interfaces ................................................................................................................. 7
2.1.5 Communications Interfaces .................................................................................................... 7
2.1.6 Memory Constraints ............................................................................................................... 7
2.1.7 Operations............................................................................................................................... 7
2.1.8 Site Adaptation Requirements ................................................................................................ 7
2.2 PRODUCT FUNCTIONS ........................................................................................................................7
2.3 USER CHARACTERISTICS ....................................................................................................................7
2.4 CONSTRAINTS ....................................................................................................................................8
2.5 ASSUMPTIONS AND DEPENDENCIES ...................................................................................................8
2.6 APPORTIONING OF REQUIREMENTS ....................................................................................................8
3. SPECIFIC REQUIREMENTS ...........................................................................................................8
3.1 EXTERNAL INTERFACES .....................................................................................................................9
3.2 FUNCTIONS ........................................................................................................................................9
3.3 PERFORMANCE REQUIREMENTS .......................................................................................................10
3.4 LOGICAL DATABASE REQUIREMENTS ..............................................................................................10
3.5 DESIGN CONSTRAINTS .....................................................................................................................11
3.5.1 Standards Compliance. ......................................................................................................... 11
3.6 SOFTWARE SYSTEM ATTRIBUTES.....................................................................................................11
3.6.1 Reliability ............................................................................................................................. 11
3.6.2 Availability ........................................................................................................................... 11
3.6.3 Security................................................................................................................................. 11
3.6.4 Maintainability...................................................................................................................... 12
3.6.5 Portability ............................................................................................................................. 12
3.7 ORGANIZING THE SPECIFIC REQUIREMENTS.....................................................................................13
3.7.1 System Mode ........................................................................................................................ 13
3.7.2 User Class............................................................................................................................. 13
3.7.3 Objects.................................................................................................................................. 13
3.7.4 Use Cases.............................................................................................................................. 13
3.7.5 Feature .................................................................................................................................. 14
3.7.6 Stimulus................................................................................................................................ 14
3.7.7 Response............................................................................................................................... 14
3.7.8 Functional Hierarchy ............................................................................................................ 14
3.8 ADDITIONAL COMMENTS .................................................................................................................14
4. SUPPORTING INFORMATION.....................................................................................................15
3 v. 1.4 14 January 2004

DOCUMENT CONTROL ..........................................................................................................................17

CHANGE HISTORY .........................................................................................................................................17
DOCUMENT STORAGE ....................................................................................................................................17
DOCUMENT OWNER .......................................................................................................................................17
APPENDICES .............................................................................................................................................18
4 v. 1.4 14 January 2004

1. INTRODUCTION
The introduction of the SRS should provide an overview of the entire SRS.
<Click Here to Insert Your Text>
1.1 PURPOSE
a) Describe the purpose of the SRS
b) Specify the intended audience for the SRS
1.2 SCOPE
a) Identify the software product(s) to be produced by name (e.g., Host DBMS,
Report Generator, etc.);
b) Explain what the software product(s) will, and, if necessary, will not, do;
c) Describe the application of the software being specified, including relevant
benefits, objectives, and goals
1.3 DEFINITIONS, ACRONYMS, AND ABBREVIATIONS

Provide the definitions of all terms, acronyms, and abbreviations required to properly
interpret the SRS. This information may be provided by reference to one or more
appendices in the SRS or by reference to documents.
Term or Acronym Definition
Table x. Definitions and Acronyms
1.4 REFERENCES
a) Provide a complete list of all documents referenced elsewhere in the SRS
b) Identify each document by title, report number (if applicable), date, and publishing
organization
c) Specify the sources from which the references can be obtained.
This information can be provided by reference to an appendix or to another document.
1.5 OVERVIEW
a) Describe what the rest of the SRS contains
b) Explain how the SRS is organized.
5 v. 1.4 14 January 2004

2. OVERALL DESCRIPTION
Describe background that affects the product and its requirements. This section does not
state specific requirements. Instead, it provides a background for those requirements,
which are defined in section 3, and makes them easier to understand.
2.1 PRODUCT PERSPECTIVE

Describe how this product is related to other products or to a larger system of which it is
a part.
A block diagram showing the major components of the larger system, interconnections,
and external interfaces can be helpful.
The following subsections describe how the software operates inside various constraints.
2.1.1 System Interfaces

List each system interface and identify the functionality of the software to accomplish the
system requirement and the interface description to match the system.
2.1.2 User Interfaces

Specify:
a) The logical characteristics of each interface between the software product and its
users. This includes those configuration characteristics (e.g., required screen formats,
page or window layouts, content of any reports or menus, or availability of
programmable function keys) necessary to accomplish the software requirements.
b) Describe how the interface will appear to the user. This may be a list of do’s and
don’ts on how the system will appear to the user. One example may be a requirement
for the option of long or short error messages. Like all others, these requirements
should be verifiable.
2.1.3 Hardware Interfaces

Specify the logical characteristics of each interface between the software product and the
hardware components of the system. This includes configuration characteristics (number
of ports, instruction sets., etc.). It also covers such matters as what devices are to be
supported, how they are to be supported and protocols.
6 v. 1.4 14 January 2004

2.1.4 Software Interfaces

Specify the use of other required software products and interfaces with other application
systems. For each required software product, include complete name and version
number. For each interface, describe the purpose of that interface software.
2.1.5 Communications Interfaces

Specify the various interfaces to communications such as local network protocols, etc.
2.1.6 Memory Constraints

Specify any applicable characteristics and limits on primary and secondary memory.
2.1.7 Operations
If appropriate, specify the normal and special operations required by the user such as:
a) The various modes of operations in the user organization;
b) Periods of interactive operations and periods of unattended operations;
c) Data processing support functions;
d) Backup and recovery operations.
2.1.8 Site Adaptation Requirements

In this section, describe any requirements for modifications to the site or to the data at
the site, in order to use the product.
2.2 PRODUCT FUNCTIONS

Provide a summary of the major functions that the software will perform. The functions
should be organized in a way that makes the list of functions understandable to the
customer or to anyone else reading the document for the first time. Textual or graphic
methods can be used to show the different functions and their relationships. Such a
diagram is not intended to show a design of a product but simply shows the logical
relationships among variables.
2.3 USER CHARACTERISTICS

Describe general characteristics of the intended users of the product including
educational level, experience, and technical expertise. Do not state specific
requirements but rather provide the reasons why certain specific requirements are later
specified in section 3.
7 v. 1.4 14 January 2004

2.4 CONSTRAINTS
Provide a general description of any other items that will limit the design and
implementation options. These can include:
a) Regulatory policies
b) Hardware limitations (for example, signal timing requirements)
c) Interface to other applications
d) Parallel operation
e) Audit functions
f) Control functions
g) Higher-order language requirements
h) Reliability requirements
i) Criticality of the application
j) Safety and security considerations
2.5 ASSUMPTIONS AND DEPENDENCIES

List each of the factors that affect the requirements stated in the SRS. These factors are
not design constraints on the software but are, rather, any changes to them that can
affect the requirements in the SRS. For example, an assumption might be that a specific
operating system will be available on the hardware designated for the software product.
2.6 APPORTIONING OF REQUIREMENTS

Identify requirements that may be delayed until future versions of the system.
3. SPECIFIC REQUIREMENTS
This section contains all the software requirements at a level of detail sufficient to enable
designers to design a system to satisfy those requirements, and testers to test that the
system satisfies those requirements. Throughout this section, each stated requirement
should be externally perceivable by users, operators, or other external systems. These
requirements should include at a minimum a description of every input (stimulus) into the
system, every output (response) from the system and all functions performed by the
system in response to an input or in support of an output. As this is often the largest and
most important part of the SRS, the following principles apply:
a) Specific requirements should be stated with all the characteristics of a good SRS
• correct
• unambiguous
• complete
• consistent
• ranked for importance and/or stability
• verifiable
8 v. 1.4 14 January 2004

• modifiable
• traceable.
1. Specific requirements should be cross-referenced to earlier documents that relate.
2. All requirements should be uniquely identifiable.
3. Careful attention should be given to organizing the requirements to maximize
readability.
Before examining specific ways of organizing the requirements it is helpful to understand

the various items that comprise requirements as described in the following subsections.
When using use-case modeling, these requirements are captured in the use cases and the
applicable supplementary specifications.
3.1 EXTERNAL INTERFACES

Provide a detailed description of all inputs into and outputs from the software system.
This section complements the interface descriptions in section 2 but does not repeat
information there.
Include appropriate elements of both content and format as follows:
a) Name of item
b) Description of purpose
c) Source of input or destination of output
d) Valid range, accuracy and/or tolerance
e) Units of measure
f) Timing
g) Relationships to other inputs/outputs
h) Screen formats/organization
i) Window formats/organization
j) Data formats
k) Command formats
l) End messages
3.2 FUNCTIONS
Functional requirements define the fundamental actions that must take place in the
software in accepting and processing the inputs and in processing and generating the
outputs. These are generally listed as “shall” statements starting with “The system
shall…”.
These include:
a) Validity checks on the inputs
b) Exact sequence of operations
c) Responses to abnormal situation, including
• Overflow
• Communication facilities
• Error handling and recovery
9 v. 1.4 14 January 2004

d) Effect of parameters
e) Relationship of outputs to inputs, including
• Input/Output sequences
• Formulas for input to output conversion
It may be appropriate to partition the functional requirements into subfunctions or

subprocesses. This does not imply that the software design will also be partitioned that
way.
3.3 PERFORMANCE REQUIREMENTS

Specify both the static and the dynamic numerical requirements placed on the software
or on human interaction with the software, as a whole. Static numerical requirements
may include:
(a) The number of terminals to be supported
(b) The number of simultaneous users to be supported
(c) Amount and type of information to be handled
Static numerical requirements are sometimes identified under a separate section entitled
capacity.
Dynamic numerical requirements may include, for example, the numbers of transactions
and tasks and the amount of data to be processed within certain time periods for both
normal and peak workload conditions.
All of these requirements should be stated in measurable terms, such as

95% of the transactions shall be processed in less than 1 s
Note: Numerical limits applied to one specific function are normally specified as part of
the processing subparagraph description of that function.
3.4 LOGICAL DATABASE REQUIREMENTS

Specify the logical requirements for any information that is to be placed into a database.
This may include:
a) Types of information used by various functions
b) Frequency of use
c) Accessing capabilities
d) Data entities and their relationships
e) Integrity constraints
f) Data retention requirements
10 v. 1.4 14 January 2004

3.5 DESIGN CONSTRAINTS

Specify design constraints that can be imposed by other standards, hardware limitations,
etc.
3.5.1 Standards Compliance.

Specify the requirements derived from existing standards or regulations. They might
include:
a) Report format
b) Data naming
c) Accounting procedures
d) Audit Tracing
For example, this could specify the requirement for software to trace processing activity.
Such traces are needed for some applications to meet minimum regulatory or financial
standards. An audit trace requirement may, for example, state that all changes to a
payroll database must be recorded in a trace file with before and after values.
3.6 SOFTWARE SYSTEM ATTRIBUTES

There are a number of attributes of software that can serve as requirements. It is
important that required attributes be specified so that their achievement can be
objectively verified. The following items provide a partial list of examples.
3.6.1 Reliability
Specify the factors required to establish the required reliability of the software system at
time of delivery.
3.6.2 Availability
Specify the factors required to guarantee a defined availability level for the entire system
such as checkpoint, recovery, and restart.
3.6.3 Security
Specify the factors that would protect the software from accidental or malicious access,
use, modification, destruction, or disclosure. Specific requirements in this area could
include the need to
a) Utilize certain cryptographic techniques
b) Keep specific log or history data sets
c) Assign certain functions to different modules
d) Restrict communications between some areas of the program
11 v. 1.4 14 January 2004

e) Check data integrity for critical variables

3.6.4 Maintainability
Specify attributes of software that relate to the ease of maintenance of the software itself.
There may be some requirement for certain modularity, interfaces, complexity, etc.
Requirements should not be placed here just because they are thought to be good design
practices.
3.6.5 Portability
Specify attributes of software that relate to the ease of porting the software to other host
machines and/or operating systems. This may include
a) Percentage of components with host-dependent code
b) Percentage of code that is host dependent
c) Use of a proven portable language
d) Use of a particular compiler or language subset
e) Use of a particular operating system.
Once the relevant characteristics are selected, a subsection should be written for each,
explaining the rationale for including this characteristic and how it will be tested and
measured. A chart like this might be used to identify the key characteristics (rating them
High, Medium, or Low), or ranking them in order of importance (1, 2, 3, etc.).
ID Characteristic Rank
1 Correctness
2 Efficiency
3 Flexibility
etc.
Definitions of the quality characteristics follow.

• Correctness - extent to which program satisfies specifications, fulfills user’s
mission objectives
• Efficiency - amount of computing resources and code required to perform
function
• Flexibility - effort needed to modify operational program
• Integrity/Security - factors that protect the software from accidental or
malicious access, use, modification, destruction, or disclosure
• Interoperability - effort needed to couple one system with another
• Maintainability - ease of maintenance of the software itself
• Portability - ease of porting the software to another host
• Reliability - factors required to establish the required reliability of the
system
12 v. 1.4 14 January 2004

• Reusability - extent to which it can be reused in another application

• Testability - effort needed to test to ensure performs as intended
• Usability - effort required to learn, operate, prepare input, interpret output
• Availability - factors required to guarantee a defined availability level for
the system
3.7 ORGANIZING THE SPECIFIC REQUIREMENTS

For anything but trivial systems the detailed requirements tend to be extensive. For this
reason, it is recommended that careful consideration be given to organizing these in a
manner optimal for understanding. There is no one optimal organization for all systems.
Different classes of systems lend themselves to different organizations of requirements in
section 3. Some of these organizations are described in the following subsections.
3.7.1 System Mode

Some systems behave quite differently depending on the mode of operation. For example,
a control system may have different sets of functions depending on its mode: training,
normal, or emergency. When organizing by mode there are two possible outlines (see
Appendices). The choice depends on whether interfaces and performance are dependent
on mode.
3.7.2 User Class

Some systems provide different sets of functions to different classes of users. For example,
an elevator control system presents different capabilities to passengers, maintenance
workers, and fire fighters.
3.7.3 Objects
Objects are real-world entities that have a counterpart within the system. For example,
in a patient monitoring system, objects would include patients, sensors, nurses, rooms,
physicians, medicines, etc. Associated with each object is a set of attributes (of that
object) and functions (performed by that object). These functions are also called services,
methods, or processes. Note that sets of objects may share attributes and services. These
are grouped together as classes.
3.7.4 Use Cases

Use cases detail the interactions between actors and the system for each major functional
requirement. They may be represented in UML or in a variety of text formats.
13 v. 1.4 14 January 2004

3.7.5 Feature
A feature is an externally desired service by the system that may require a sequence of
inputs to effect the desired result. For example, in a telephone system, features include
local call, call forwarding, and conference call. Each feature is generally described in as
sequence of stimulus-response pairs.
3.7.6 Stimulus
Some systems can be best organized by describing their functions in terms of stimuli. For
example, the functions of an automatic aircraft landing system may be organized into
sections for loss of power, wind shear, sudden change in roll, vertical velocity excessive,
etc.
3.7.7 Response
Some systems can be best organized by describing their functions in support of the
generation of a response. For example, the functions of a personnel system may be
organized into sections corresponding to all functions associated with generating
paychecks, all functions associated with generating a current list of employees, etc.
3.7.8 Functional Hierarchy

When none of the above organizational schemes prove helpful, the overall functionality
can be organized into a hierarchy of functions organized by either common inputs,
common outputs, or common internal data access. Data flow diagrams and data
dictionaries can be used to show the relationships between and among the functions and
data.
3.8 ADDITIONAL COMMENTS

Whenever a new SRS is contemplated, more than one of the organizational techniques
given in 3.7 may be appropriate. In such cases, organize the specific requirements for
multiple hierarchies tailored to the specific needs of the system under specification. Any
additional requirements may be put in a separate section at the end of the SRS.
There are many notations, methods, and automated support tools available to aid in the
documentation of requirements. For the most part, their usefulness is a function of
organization. For example, when organizing by mode, finite state machines or state
charts may prove helpful; when organizing by object, object-oriented analysis may prove
helpful; when organizing by feature, stimulus-response sequences may prove helpful;
when organizing by functional hierarchy, data flow diagrams and data dictionaries may
prove helpful.
14 v. 1.4 14 January 2004

In any of the outlines below, those sections called “Functional Requirement i” may be
described in native language, in pseudocode, in a system definition language, or in four
subsections titled: Introduction, Inputs, Processing, Outputs.
4. SUPPORTING INFORMATION.
The supporting information makes the SRS easier to use. It includes:
a) Table of Contents at the front of the document
b) Index
c) Appendices
The Appendices are not always considered part of the actual requirements specification
and are not always necessary. They may include:
(a) Sample I/O formats, descriptions of cost analysis studies, results of user surveys;
(b) Supporting or background information that can help the readers of the SRS;
(c) A description of the problems to be solved by the software;
(d) Special packaging instructions for the code and the media to meet security,
export, initial loading, or other requirements.
When Appendices are included, the SRS should explicitly state whether or not the
Appendices are to be considered part of the requirements.
Tables on the following pages provide alternate ways to structure section 3 on the
specific requirements.
15 v. 1.4 14 January 2004

16 v. 1.4 14 January 2004

DOCUMENT CONTROL
CHANGE HISTORY
Release
Revision Description [list of changed pages and reason for change]
Date
DOCUMENT STORAGE
This document was created using <> . The file is stored <file location> .
DOCUMENT OWNER
<> is responsible for developing and maintaining this document.
17 v. 1.4 14 January 2004

APPENDICES
A.1 Outline for SRS Section 3: Organized by mode: Version 1
3 Specific Requirements
3.1 External interface requirements
3.1.1 User interfaces
3.1.2 Hardware interfaces
3.1.3 Software interfaces
3.1.4 Communications interfaces
3.2 Functional requirements
3.2.1 Mode 1
3.2.1.1 Functional requirement 1.1
.....
3.2.1.n Functional requirement 1.n
3.2.2 Mode 2
.....
3.2.m Mode m
3.2.m.1 Functional requirement m.1
.....
3.2.m.n Functional requirement m.n
3.3 Performance Requirements
3.4 Design Constraints
3.5 Software system attributes
3.6 Other requirements
18 v. 1.4 14 January 2004

Outline for SRS Section 3: Organized by mode: Version 2
3.1 Functional Requirements
3.1.1 Mode 1
3.1.1.1 External interfaces
3.1.1.1 User interfaces
3.1.1.2 Hardware interfaces
3.1.1.3 Software interfaces
3.1.1.4 Communications interfaces
3.1.1.2 Functional Requirement
3.1.1.2.1 Functional requirement 1
.....
3.1.1.2.n Functional requirement n
3.1.1.3 Performance
3.1.2 Mode 2
.....
3.1.m Mode m
3.2 Design constraints
19 v. 1.4 14 January 2004

Outline for SRS Section 3: Organized by user class
3.2.1 User class 1
.....
3.2.2 User class 2
.....
3.2.m User class m

.....
20 v. 1.4 14 January 2004

Outline for SRS Section 3: Organized by object
3.2 Classes/Objects
3.2.1 Class/Object 1
3.2.1.1 Attributes (direct or inherited)
3.2.1.1.1 Attribute 1
.....
3.2.1.1.n Attribute n
3.2.1.2 Functions (services, methods, direct or inherited)

3.2.1.2.1 Functional requirement 1.1
.....
3.2.1.2.m Functional requirement 1.m
3.2.1.3 Messages (communications received or sent)
3.2.2 Class/Object 2
.....
3.2.p Class/Object p
21 v. 1.4 14 January 2004

Outline for SRS Section 3: Organized by use case
An alternative to embedding the use cases in line with the functional requirements (as
shown below) is to provide the use cases separately from the SRS and refer to the use
case name or ID for each functional requirement in the SRS.
3.2 Functional Requirements
3.1.1.2 Functional Requirement
Use case for functional requirement 1
.....
Use case for functional requirement n
22 v. 1.4 14 January 2004

Outline for SRS Section 3: Organized by feature
3.3 System features
3.2.1 System Feature 1
3.2.1.1 Introduction/Purpose of feature
3.2.1.2 Stimulus/Response sequence
3.2.1.3 Associated functional requirements
.....
3.2.2 System Feature 2
.....
3.2.m System Feature m
.....
23 v. 1.4 14 January 2004

Outline for SRS Section 3: Organized by stimulus
3.2.1 Stimulus 1
.....
3.2.2 Stimulus 2
.....
3.2.m Stimulus m
.....
24 v. 1.4 14 January 2004

Outline for SRS Section 3: Organized by response
3.2.1 Response 1
.....
3.2.2 Response 2
.....
3.2.m Response m
.....
25 v. 1.4 14 January 2004

Outline for SRS Section 3: Organized by functional hierarchy
3.2.1 Information flows
3.2.1.1 Data flow diagram 1
3.2.1.1.1 Data entities
3.2.1.1.2 Pertinent processes
3.2.1.1.3 Topology
3.2.1.2 Data flow diagram 2
3.2.1.2.1 Data entities
3.2.1.2.2 Pertinent processes
3.2.1.2.3 Topology
.....
3.2.1.n Data flow diagram n
3.2.1.n.1 Data entities
3.2.1.n.2 Pertinent processes
3.2.1.n.3 Topology
3.2.2 Process descriptions
3.2.2.1 Process 1
3.2.2.1.1 Input data entities
3.2.2.1.2 Algorithm or formula of process
3.2.2.1.3 Affected data entities
3.2.2.2 Process 2
3.2.2.2.1 Input data entities
3.2.2.2.2 Algorithm or formula of process
3.2.2.2.3 Affected data entities
.….
3.2.2.m Process m
3.2.2.m.1 Input data entities
3.2.2.m.2 Algorithm or formula of process
3.2.2.m.3 Affected data entities
3.2.3 Data construct specifications
3.2.3.1 Construct 1
3.2.3.1.1 Record type
3.2.3.1.2 Constituent fields
3.2.3.2 Construct 2
3.2.3.2.1 Record type
3.2.3.2.2 Constituent fields
…..
26 v. 1.4 14 January 2004

3.2.3.p Construct p
3.2.3.p.1 Record type
3.2.3.p.2 Constituent fields
3.2.4 Data dictionary
3.2.4.1 Data element 1
3.2.4.1.1 Name
3.2.4.1.2 Representation
3.2.4.1.3 Units/Format
3.2.4.1.4 Precision/Accuracy
3.2.4.1.5 Range
3.2.4.2 Data element 2
3.2.4.2.1 Name
3.2.4.2.2 Representation
3.2.4.2.3 Units/Format
3.2.4.2.4 Precision/Accuracy
3.2.4.2.5 Range
…..
3.2.4.q Data element q
3.2.4.q.1 Name
3.2.4.q.2 Representation
3.2.4.q.3 Units/Format
3.2.4.q.4 Precision/Accuracy
3.2.4.q.5 Range
27 v. 1.4 14 January 2004

Outline for SRS Section 3: Showing multiple organizations
3.2.1 User class 1
3.2.1.1 Feature 1.1
3.2.1.1.1 Introduction/Purpose of feature
3.2.1.1.2 Stimulus/Response sequence
3.2.1.1.3 Associated functional requirements
3.2.1.2 Feature 1.2
3.2.1.2.1 Introduction/Purpose of feature
3.2.1.2.2 Stimulus/Response sequence
3.2.1.2.3 Associated functional requirements
…..
3.2.1.m Feature 1.m
3.2.1.m.1 Introduction/Purpose of feature
3.2.1.m.2 Stimulus/Response sequence
3.2.1.m.3 Associated functional requirements
3.2.2 User class 2
.....
3.2.n User class n
.....
28 v. 1.4 14 January 2004

Software Requirements Specification

Uploaded by

Copyright:

Available Formats

Software Requirements Specification

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Software Requirements Specification

Uploaded by

Copyright:

Available Formats

<Organization>

< Project Name>

Approvals Signature Block

Organization Responsibility Signature Date

2 v. 1.4 14 January 2004

3 v. 1.4 14 January 2004

DOCUMENT CONTROL ..........................................................................................................................17

4 v. 1.4 14 January 2004

1.3 DEFINITIONS, ACRONYMS, AND ABBREVIATIONS

Term or Acronym Definition

Table x. Definitions and Acronyms

5 v. 1.4 14 January 2004

2.1 PRODUCT PERSPECTIVE

2.1.1 System Interfaces

2.1.2 User Interfaces

2.1.3 Hardware Interfaces

6 v. 1.4 14 January 2004

2.1.4 Software Interfaces

2.1.5 Communications Interfaces

2.1.6 Memory Constraints

2.1.8 Site Adaptation Requirements

2.2 PRODUCT FUNCTIONS

2.3 USER CHARACTERISTICS

7 v. 1.4 14 January 2004

2.5 ASSUMPTIONS AND DEPENDENCIES

2.6 APPORTIONING OF REQUIREMENTS

8 v. 1.4 14 January 2004

Before examining specific ways of organizing the requirements it is helpful to understand

3.1 EXTERNAL INTERFACES

9 v. 1.4 14 January 2004

It may be appropriate to partition the functional requirements into subfunctions or

3.3 PERFORMANCE REQUIREMENTS

All of these requirements should be stated in measurable terms, such as

3.4 LOGICAL DATABASE REQUIREMENTS

10 v. 1.4 14 January 2004

3.5 DESIGN CONSTRAINTS

3.5.1 Standards Compliance.

3.6 SOFTWARE SYSTEM ATTRIBUTES

11 v. 1.4 14 January 2004

e) Check data integrity for critical variables

Definitions of the quality characteristics follow.

12 v. 1.4 14 January 2004

• Reusability - extent to which it can be reused in another application

3.7 ORGANIZING THE SPECIFIC REQUIREMENTS

3.7.1 System Mode

3.7.2 User Class

3.7.4 Use Cases

13 v. 1.4 14 January 2004

3.7.8 Functional Hierarchy

3.8 ADDITIONAL COMMENTS

14 v. 1.4 14 January 2004

<Click Here to Insert Your Text>

15 v. 1.4 14 January 2004

16 v. 1.4 14 January 2004

17 v. 1.4 14 January 2004

18 v. 1.4 14 January 2004

Outline for SRS Section 3: Organized by mode: Version 2

19 v. 1.4 14 January 2004

Outline for SRS Section 3: Organized by user class