Академический Документы
Профессиональный Документы
Культура Документы
Who∗
Contents
1 Introduction 2
1.1 Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.2 Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.3 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
2 Overall Description 3
2.1 Product perspective . . . . . . . . . . . . . . . . . . . . . . . . . 4
2.1.1 System interfaces . . . . . . . . . . . . . . . . . . . . . . . 4
2.1.2 User interfaces . . . . . . . . . . . . . . . . . . . . . . . . 4
2.1.3 Hardware interfaces . . . . . . . . . . . . . . . . . . . . . 4
2.1.4 Software interfaces . . . . . . . . . . . . . . . . . . . . . . 4
2.1.5 Communications interfaces . . . . . . . . . . . . . . . . . 4
2.1.6 Memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
2.1.7 Operations . . . . . . . . . . . . . . . . . . . . . . . . . . 4
2.1.8 Site adaptation requirements . . . . . . . . . . . . . . . . 4
2.2 Product functions . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
2.3 User characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . 4
2.4 Constraints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
2.4.1 Regulatory policies . . . . . . . . . . . . . . . . . . . . . . 5
2.4.2 Hardware limitations . . . . . . . . . . . . . . . . . . . . . 5
2.4.3 Interfaces to other applications . . . . . . . . . . . . . . . 5
∗ Where, email@cpu.org
1
2.4.4 Parallel operations . . . . . . . . . . . . . . . . . . . . . . 5
2.4.5 Audit functions . . . . . . . . . . . . . . . . . . . . . . . . 5
2.4.6 Control functions . . . . . . . . . . . . . . . . . . . . . . . 5
2.4.7 Higher-order language requirements . . . . . . . . . . . . 5
2.4.8 Signal handshake protocols . . . . . . . . . . . . . . . . . 5
2.4.9 Reliability requirements . . . . . . . . . . . . . . . . . . . 5
2.4.10 Criticality of the application . . . . . . . . . . . . . . . . 5
2.4.11 Safety and security considerations . . . . . . . . . . . . . 5
2.5 Assumptions and dependencies . . . . . . . . . . . . . . . . . . . 5
3 Specific Requirements 5
3.1 External interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . 6
3.1.1 User interfaces . . . . . . . . . . . . . . . . . . . . . . . . 6
3.1.2 Hardware interfaces . . . . . . . . . . . . . . . . . . . . . 6
3.1.3 Software interfaces . . . . . . . . . . . . . . . . . . . . . . 6
3.1.4 Communications interfaces . . . . . . . . . . . . . . . . . 6
3.2 System features . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
3.3 Performance requirements . . . . . . . . . . . . . . . . . . . . . . 6
3.4 Design constraints . . . . . . . . . . . . . . . . . . . . . . . . . . 6
3.5 Software system attributes . . . . . . . . . . . . . . . . . . . . . . 6
3.6 Other requirements . . . . . . . . . . . . . . . . . . . . . . . . . . 6
B Change log 6
1 Introduction
[What is this document about, in very general terms.]
This document conforms to the IEEE 830-1998 SRS recommended prac-
tice. Since the recommended practice covers a wide range of possible
projects, some of the information in it is not appropriate for this
part of DODS. Where that is the case, or I think it is the case, I have
marked the section N/A.
Bold face type is used to indicate a word or phrase that may be found
in the glossary.
2
Emphasized text contained in square brackets ([]) is used to indicate
an editorial comment about the information that should be provided
in a part of the SRS.
1.1 Purpose
[Who is this document for?]
1.2 Scope
[What part of the project does this SRS cover.]
1.3 Overview
The remainder of this document is organized as follows:
2 Overall Description
[This section of the SRS should describe the general factors that af-
fect the product and its requirements. This section should not state
specific requirements. Instead, it provides a background for those
requirements, which should be defined in Section 3.]
3
2.1 Product perspective
2.1.1 System interfaces
2.1.6 Memory
2.1.7 Operations
2.4 Constraints
[This section lists any other items that may limit the developer’s op-
tions.]
4
2.4.1 Regulatory policies
3 Specific Requirements
[This section of the SRS lists all of the software requirements to a
level of detail sufficient to enable designers to design a system to sat-
isfy those requirements, and testers to test that the systems satisfies
those requirements. Each separate requirment should be uniquely
numbered.]
5
3.1 External interfaces
3.1.1 User interfaces
B Change log
$Log: SRS-template.tex,v $
Revision 1.4 2000/07/20 21:35:58 jimg
Minor changes
References