Software Product Specification model text

The Software Product Specification (SPS) contains or references the executable software, source files, and software support information, including "as-built" design information and compilation, build, and modification procedures, for a Computer Software Configuration Item (CSCI). See DID fur further instructions.

SOFTWARE PRODUCT SPECIFICATION

FOR THE

SPEED CONTROLLER

CONTRACT NO.

CDRL SEQUENCE NO.

Prepared for:

Prepared by:

This document contains No. of pages pages

REVIEW AND HISTORY PAGE

CONTENTS

Insert the "Table of Contents" here.

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

1. SCOPE

1.1 Identification.

Identify the system and 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 and software to which this document applies. It shall describe the general nature of the system and software; summarize the history of the system development, operation, and maintenance; identify the project sponsor, acquirer, user, developer, and support agencies; identify current and planned operating sites; and list other relevant documents.

1.3 Document overview.

Summarize the purpose and contents of this document.
This document comprises of six sections:

• Scope;
• Referenced documents;
• Requirements;
• Qualification provisions;
• Software support information;
• Requirements traceability;
• Notes.

2. REFERENCED DOCUMENTS

2.1 Project documents.

Identify the project management systems documents here.

2.1 Other documents.

2.1 Precedence.

2.1 Source of documents.

3. REQUIREMENTS

This section shall be divided into paragraphs to achieve delivery of the software and to establish the requirements that another body of software must meet to be considered a valid copy of the CSCI.
NOTE: This section establishes the software itself as the criterion that must be matched for a body of software to be considered a valid copy of the CSCI. The updated software design shall be placed in section 5, not as a requirement, but as information to be used to modify, enhance, or otherwise support the software. If any portion of this specification is placed under acquirer control, it should be limited to Section 3. It is the software itself that establishes the product baseline, not a description of the software's design.

To be continued.

4. QUALIFICATION PROVISIONS

State the method(s) to be used to demonstrate that a given body of software is a valid copy of the CSCI. The information shall be the same as that required in a 'Software Design Description' (SDD), Interface Design Description (IDD), and 'Database Design Description' (DBDD), as applicable.

5. SOFTWARE SUPPORT INFORMATION

5.1 "As-built" software design

This paragraph shall contain, or reference an appendix or other declared deliverable document that contains, information describing the design of the "as-built" CSCI.
To be continued.

6. REQUIREMENTS TRACEABILITY

The following shall be included in this section:

• Traceability from each CSCI source file to the software unit(s) that it implements.
• Traceability from each software unit to the source that implements it.

7. NOTES

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

7.1 Intended use.

This software product specification shall ...

7.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'.

7.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'.

7.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