SE201

SOFTWARE REQUIREMENT SPECIFICATION (SRS) FALL2021

2021

SOFTWARE
REQUIREMENT
SPECIFICATION (SRS)
SYSTEM NAME

LIST OF AUTHORS’ NAME

[Type the company name]
ITEM NUMBER VERSION NUMBER (Example
To be submitted SRSSE201
to the SYS NAME 2021
Software i
VERSION Engineering
Requirement 1.0)
 SE201
SOFTWARE REQUIREMENT SPECIFICATION (SRS) FALL2021

DOCUMENT APPROVAL
Name Date

Authenticated by:

_______________________

Project Manager

Approved by:

_______________________

Client

Software :
Archiving Place :
Copies Available :

ITEM NUMBER VERSION NUMBER (Example SRS SYS NAME 2021 VERSION 1.0) ii
 SE201
SOFTWARE REQUIREMENT SPECIFICATION (SRS) FALL2021

TABLE OF CONTENT

DOCUMENT APPROVAL......................................................................................................II
TABLE OF CONTENTS.........................................................................................................III
LIST OF FIGURES................................................................................................................IV
LIST OF TABLES...................................................................................................................V
LIST OF APPENDIXES.........................................................................................................VI
1. INTRODUCTION...........................................................................................................1
1.1 PURPOSE................................................................................................................................1
1.2 SYSTEM IDENTIFICATION.......................................................................................................1
1.3 SYSTEM OVERVIEW................................................................................................................1
1.4 REFERENCES...........................................................................................................................1
1.5 DOCUMENT OVERVIEW.........................................................................................................1
2. PRODUCT DESCRIPTION...............................................................................................2
2.1 PRODUCT PERSPECTIVE..........................................................................................................2
2.2 SYSTEM INTERFACES..............................................................................................................2
2.3 PRODUCT FUNCTIONS...........................................................................................................3
2.4 USER CHARACTERISTICS.........................................................................................................3
2.5 CONSTRAINTS........................................................................................................................3
2.6 ASSUMPTIONS AND DEPENDENCIES......................................................................................3
3. SPECIFIC REQUIREMENTS............................................................................................4
3.1 SOFTWARE PRODUCT FEATURES...........................................................................................4
3.1.1 USE CASE NAME.............................................................................................................4
3.2 EXTERNAL INTERFACE REQUIREMENTS.................................................................................4
3.2.1 USER INTERFACES..........................................................................................................4
3.2.2 HARDWARE INTERFACES...............................................................................................4
3.2.3 SOFTWARE INTERFACES................................................................................................4
3.3 REQUIREMENTS TRACEBILITY................................................................................................4
4. ACRONYMS AND ABBREVIATION.................................................................................6

ITEM NUMBER VERSION NUMBER (Example SRS SYS NAME 2021 VERSION 1.0) iii
 SE201
SOFTWARE REQUIREMENT SPECIFICATION (SRS) FALL2021

LIST OF FIGURES

No table of figures entries found.

ITEM NUMBER VERSION NUMBER (Example SRS SYS NAME 2021 VERSION 1.0) iv
 SE201
SOFTWARE REQUIREMENT SPECIFICATION (SRS) FALL2021

LIST OF TABLES

ITEM NUMBER VERSION NUMBER (Example SRS SYS NAME 2021 VERSION 1.0) v
 SE201
SOFTWARE REQUIREMENT SPECIFICATION (SRS) FALL2021

LIST OF APPENDIXES

ITEM NUMBER VERSION NUMBER (Example SRS SYS NAME 2021 VERSION 1.0) vi
1. INTRODUCTION

This section should describe the project and the software product being to be built.

1.1 PURPOSE
The Software Requirements Specification (SRS) specifies requirements for a Computer
Software Configuration and the methods to be used to ensure that each requirement
has been met.

1.2 SYSTEM IDENTIFICATION

1.3 SYSTEM OVERVIEW

1.4 REFERENCES
This section shall list the number, title, revision, and date of all documents referenced
in this specification. This section shall also identify the source for all documents not
available through normal Government stocking activities.

1.5 DOCUMENT OVERVIEW

This paragraph shall summarize the purpose and the contents of this document and
describe any security or privacy considerations associated with its use.
2. PRODUCT DESCRIPTION

2.1 Product Perspective

This subsection of the SRS should put the product into perspective with other related
products. If the product is independent and totally self-contained, it should be so
stated here. If the SRS defines a product that is a component of a larger system, as
frequently occurs, then this subsection should relate the requirements of that larger
system to functionality of the software and should identify interfaces between that
system and the software. This section should represent context diagram for the
systems.

2.2 System Interfaces

This should 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.3 Product Functions

This subsection of the SRS should provide a summary of the major functions that the
software will perform. For example, an SRS for an accounting program may use this
part to address customer account maintenance, customer statement, and invoice
preparation without mentioning the vast amount of detail that each of those
functions requires. This section should represent use case diagram for the systems.

2.4 User Characteristics

This subsection of the SRS should describe those general characteristics of the
intended users of the product including educational level, experience, and technical
expertise.

2.5 Constraints
This subsection of the SRS should provide a general description of any other items
that will limit the developer’s options. These include
o Regulatory policies;
o Hardware limitations (e.g., signal timing requirements);
o Interfaces to other applications;
o Parallel operation;
o Audit functions;
o Control functions;
o Higher-order language requirements;
o Signal handshake protocols (e.g., XON-XOFF, ACK-NACK);
o Reliability requirements;
o Criticality of the application;
o Safety and security considerations.
2.6 Assumptions and Dependencies
This subsection of the SRS should 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 may be that a specific operating system will be available on
the hardware designated for the software product. If, in fact, the operating system is
not available, the SRS would then have to change accordingly.
3. SPECIFIC REQUIREMENTS
This section of the SRS should contain all of the software requirements to 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, every 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.

3.1 Software Product Features

3.1.1 Use Case Name

Figure 3.1 Use Case Name - Diagram

Table 3.1 Use Case Name

Use Case ID
Brief Description
Actor
Pre-Conditions
Basic Flow
Alternative Flow
Exception Flow
Post-Conditions
Rules
Constraints
Activity Diagram Refer Appendix
A-1 : Sequence Diagram

3.1.2 Use Case Name

 Figure 3.2 Use Case Name-Diagram

Table 3.2 Use Case Name

Use Case ID
Brief Description
Actor
Pre-Conditions
Basic Flow
Alternative Flow
Exception Flow
Post-Conditions
Rules
Constraints
Activity Diagram Refer Appendix
A-2 :Sequence Diagram

3.2 External Interface Requirements

This should be a detailed description of all inputs into and outputs from the software system.
3.2.1 User Interfaces
 Figure 3.3 Dialogue Diagram

Table 3.3 User Interfaces Description

User Interface Name Description User Interface Layout

or Number

Login interface User shall key-in their user ID Refer Appendix B.1
and password

Refer Appendix B.2

3.2.2 Hardware Interface

Not Applicable.

3.2.3 Software Interface

3.3 Requirements Traceability

This section shall contain:
a. List of requirements. You are suggested to write in a table the list of requirements.
b. Your table contains requirement ID, requirement details statement, and
requirement sources.
4. ACRONYMS AND ABBREVIATION
This subsection should 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 appendixes in the SRS or by reference to other documents.
 APPENDIX A

Sequence Diagram
i

APPENDIX B

User Interfaces