Software Requirements Specification Template

Only available on StudyMode
  • Topic: Requirements analysis, Software Requirements Specification, Software requirements
  • Pages : 11 (1662 words )
  • Download(s) : 390
  • Published : November 17, 2012
Open Document
Text Preview
Software Requirements Specification Template
CptS 322—Software Engineering
9 February 2005

The following annotated template shall be used to complete the Software Requirements Specification (SRS) assignment of WSU-TC CptS 322. The instructor must approve any modifications to the overall structure of this document.

Template Usage:
Text contained within angle brackets (‘’) shall be replaced by your project-specific information and/or details. For example, will be replaced with either ‘Smart Home’ or ‘Sensor Network’.

Italicized text is included to briefly annotate the purpose of each section within this template. This text should not appear in the final version of your submitted SRS.

This cover page is not a part of the final template and should be removed before your SRS is submitted.

Acknowledgements:
Sections of this document are based upon the IEEE Guide to Software Requirements Specification (ANSI/IEEE Std. 830-1984). The SRS templates of Dr. Orest Pilskalns (WSU, Vancover) and Jack Hagemeister (WSU, Pullman) have also be used as guides in developing this template for the WSU-TC Spring 2005 CptS 322 course.

Software Requirements Specification

Lead Software Engineer

Prepared for
WSU-TC CptS 322—Software Engineering Principles I
Instructor: A. David McKinnon, Ph.D.
Spring 2005

Revision History

|Date |Description |Author |Comments | | | | | | | | | | | | | | | | | | | | |

Document Approval

The following Software Requirements Specification has been accepted and approved by the following: |Signature |Printed Name |Title |Date | | | |Lead Software Eng. | | | |A. David McKinnon |Instructor, CptS 322 | | | | | | |

Table of Contents

Revision Historyii

Document Approvalii

1. Introduction1

1.1 Purpose1
1.2 Scope1
1.3 Definitions, Acronyms, and Abbreviations1
1.4 References1
1.5 Overview1

2. General Description2

2.1 Product Perspective2
2.2 Product Functions2
2.3 User Characteristics2
2.4 General Constraints2
2.5 Assumptions and Dependencies2

3. Specific Requirements2

3.1 External Interface Requirements3
3.1.1 User Interfaces3
3.1.2 Hardware Interfaces3
3.1.3 Software Interfaces3
3.1.4 Communications Interfaces3
3.2 Functional Requirements3
3.2.1 3
3.2.2 3
3.3 Use Cases3
3.3.1 Use Case #13
3.3.2 Use Case #23
3.4 Classes / Objects3
3.4.1 3
3.4.2 3
3.5 Non-Functional Requirements4
3.5.1 Performance4
3.5.2 Reliability4
3.5.3 Availability4
3.5.4 Security4
3.5.5 Maintainability4
3.5.6 Portability4
3.6 Inverse Requirements4
3.7 Design Constraints4
3.8 Logical Database Requirements4
3.9 Other Requirements4

4. Analysis Models4

4.1 Sequence Diagrams5
4.3 Data Flow Diagrams (DFD)5
4.2 State-Transition...
tracking img