Software Requirements Specification

-  model text

Foreword

The Software Requirements specification (SRS) specifies the requirements for a Computer Software Configuration Item (CSCI) and the methods to be used to ensure that each requirement has been met. Requirements pertinent to the CSCIs external interfaces may be presented in the SRS or in one or more interface requirements specifications (IRSs) and referenced from the SSS.

SOFTWARE REQUIREMENTS SPECIFICATION

FOR THE

SPEED CONTROLLER

CONTRACT NO.

CDRL SEQUENCE NO.

Prepared for:

Prepared by:

This document contains No. of pages pages

insert here a distribution statement
(i)

REVIEW AND HISTORY PAGE


CONTENTS

Insert the "Table of Contents" here.

Consult DI-IPSC-81433 and 'Documentation Standard' when preparing this document. 


1. SCOPE

1.1 Identification.

Identify the system and the software to which this document applies, including, as applicable, identification number(s), title(s), abbreviation(s), version number(s), and release number(s).

1.2 System overview.

State the purpose of the system or subsystem to which this document applies.

1.3 Document overview.

Summarize the purpose and contents of this document.
This document comprises of six sections: Describe any security or privacy considerations associated with its use.

2. REFERENCED DOCUMENTS

2.1 Project documents.

Identify the project management system documents here.

2.1 Other documents.

2.1 Precedence.

2.1 Source of documents.

3. REQUIREMENTS

This section shall be divided into paragraphs to specify the CSCI requirements, that is, those characteristics of the CSCI that are conditions for its acceptance. CSCI requirements are software requirements generated to satisfy the system requirements allocated to this CSCI. Each requirement shall be assigned a project-unique identifier to support testing and traceability and shall be stated in such a way that an objective test can be defined for it.

3.1 Required states and modes.

3.2 CSCI capability requirements.

3.3 CSCI external interface requirements.

3.4 CSCI internal interface requirements.

3.5 CSCI internal data requirements.

3.6 Adaptation requirements.

3.7 Safety requirements.

3.8 Security and privacy requirements.

3.9 CSCI environment requirements.

3.10 Computer resource requirements.

3.11 Software quality factors.

3.12 Design and implementation constraints.

3.13 Personnel requirements.

3.14 Training-related requirements.

3.15 Logistics-related requirements.

3.16 Other requirements.

3.17 Packaging requirements.

3.18 Precedence and criticality requirements.

4. QUALIFICATION PROVISIONS

5. REQUIREMENTS TRACEABILITY

6. NOTES

This section contains information of a general or explanatory nature that may be helpful, but is not mandatory.

6.1 Intended use.

This Software Requirements specification shall ...

6.2 Definitions used in this document.

Insert here an alphabetic list of definitions and their source if different from the declared sources specified in the 'Documentation standard'.

6.3 Abbreviations used in this document.

Insert here an alphabetic list of the abbreviations and acronyms if not identified in the declared sources specified in the 'Documentation Standard'.

6.4 Changes from previous issue.

Will be "not applicable" for the initial issue.

Revisions shall identify the method used to identify changes from the previous issue. 


This page is under construction



Back to Home page MANAGING STANDARDS Home page

Please send any beneficial comments or identification of errors using the following form to: kenr@wysywig.airtime.co.uk

Copyright © by Ken Rigby 1996, 1997, 1998 -- 2003