|
DATA ITEM DESCRIPTION |
Form Approved OMB No. 0704-0188 |
|||||
|
1. TITLE SOFTWARE REQUIREMENTS SPECIFICATION |
1. IDENTIFICATION NUMBER DI-MCCR-80025A |
|||||
|
3. DESCRIPTION, PURPOSE 3.1 The Software Requirements Specification (SRS specifies the engineering and qualification requirements for a Computer Software Configuration Item (CSCI). 3.2 The SRS is used by the contractor as the basis for the design and formal testing of a CSCI. (continued on page 2) |
||||||
|
4. APPROVAL DATE (YYMMDD) 880229 |
5. OFFICE OF PRIMARY RESPONSIBILITY (OPR) E C |
6a. DTIC APPLICABLE |
6b. GIDEP APPLICABLE |
|||
|
7. APPLICATION/INTERRELATIONSHIP 7.1 This Data Item Description (DID) contains the format and content preparation instructions for data generated under the work tasks described by paragraphs 4.2.10, 5.1.2.3, 5.1.3, 5.2.2.1 and 5.2.3 of DOD-STD-2167A, 3.4.2 and 3.4.7.1 of MIL-STD-483, and 3.1.3.2.5.1 of MIL-STD-490. 7.2 The Contract Data Requirements List should specify whether this document is to be prepared and delivered on bound 8-1/2 by 11 inch bond paper or electronic media. If electronic media is selected, the precise format must be specified. (continued on page 2) |
||||||
|
8. APPROVAL LIMITATION |
9a. APPLICABLE FORMS |
9b. AMSC NUMBER N4340 |
||||
|
10. PREPARATION INSTRUCTIONS 10.1 Content and format instructions. Production of this document using automated techniques is encouraged. Specific content and format instructions for this document are identified below. a. Response to tailoring instructions. In the event that a paragraph or subparagraph has been tailored out, a statement to that effect shall be added directly following the heading of each such (sub)paragraph. If a paragraph and all of its subparagraphs are tailored out, only the highest level paragraph heading need be included. b. Use of alternate presentation styles. Charts, tables, matrices, or other presentation styles are acceptable when the information required by the paragraphs and subparagraphs of this DID can be made more readable. c. Page numbering. Each page prior to Section 1 shall be numbered in lower-case Roman numerals beginning with page ii for the Table of Contents. Each page starting from Section 1 to the beginning of the appendixes shall be consecutively numbered in Arabic numerals. If the document is divided into volumes, each such volume shall restart the page numbering sequence. (continued on page 2) |
||||||
|
11. DISTRIBUTION STATEMENT DISTRIBUTION STATEMENT A. Approved for public release; distribution is unlimited |
||||||
3. DESCRIPTION/PURPOSE (continued)
3.3 The SRS specifies the requirements allocated to a CSCI and enables the Government to assess whether the completed CSCI complies with those requirements. Upon Government approval and authentication, the SRS becomes part of the Allocated Baseline.
7. APPLICATION/INTERRELATIONSHIP (continued)
7.3 The SRS is used to provide the detailed requirements for a CSCI specified in the System/Segment Specification, DI-CMAN-80008A, or Configuration Item Development Specification, DI-E-3102A.
7.4 The SRS may be used to specify requirements for an elaborate database, such as a relational data base. Requirements for such a database shall be specified in terms of a capability for which input and output requirements are to be interpreted as the database contents requirements. When a database is shared by CSCIs, the requirements for the database shall be documented in one SRS and referenced in the SRSs of the sharing CSCIs. Any CSCI unique data element requirements for a database shall be documented in the SRS for that CSCI.
7.5 This DID supersedes DI-MCCR-80025 dated 4 June 1985.
10. PREPARATION INSTRUCTIONS (continued)
d. Document control numbers. For hard copy formats, this document may be printed on one or both sides of each page (single-sided/double-sided). All printed pages shall contain the document control number and the date of the document centered at the top of the page. Document control numbers shall include revision and volume identification as applicable.
e. Multiple (sub)paragraphs. All paragraphs and subparagraphs starting with the phrase "This (sub)paragraph shall..." may be written as multiple subparagraphs to enhance readability. These subparagraphs shall be numbered sequentially.
f. Identifiers. The letter "X" serves as an identifier for a series of descriptions. For example, the subparagraphs describing by 10.1.5.2.1 shall be structured as follows:
3.2.1 (Name and identifier of the first capability)
3.2.2 (Name and identifier of the second capability
3.2.3 etc.
g. Document structure. This document shall consist of the following:
(1) Cover
(2) Title page
(3) Table of contents
(4) Scope
(5) Applicable documents
(6) Engineering requirements
(7) Qualification requirements
(8) Preparation for delivery
[9] Notes
(10) Appendixes.
10. PREPARATION INSTRUCTIONS (continued)
10.1.1 Title page. The title page shall contain the information identified below in the indicated format:
[Document control number and date: Volume x of y (if multi-volume]
[Rev. indicator: date of Rev.]
SOFTWARE REQUIREMENTS SPECIFICATION
FOR THE
[CSCI NAME]
OF
[SYSTEM NAME]
CONTRACT NO. [contract number]
CDRL SEQUENCE NO. [CDRL number]
Prepared for:
[Contracting Agency Name, department code]
Prepared by:
[contractor name and address]
Authenticated by Approved by
Date Date
10.1.2 Table of contents. This document shall contain a table of contents listing the title and page number of each titled paragraph and subparagraph. The table of contents shall then list the title and page number of each figure, table, and appendix, in that order.
10.1.3 Scope. This section shall be numbered 1 and shall be divided into the following paragraphs.
10.1.3.1 Identification. This paragraph shall be numbered 1.1 and shall contain the approved identification number, title and, if applicable, abbreviation of the system and the CSCI to which this SRS applies.
10.1.3.2 CSCI overview. This paragraph shall be numbered 1.2 and shall briefly state the purpose of the system and shall identify and describe the role, within the system, of the CSCI to which this SRS applies.
10.1.3.3 Document overview. This paragraph shall be numbered 1.3 and shall summarize the purpose and contents of this document.
10.1.4 Applicable documents. This section shall be numbered 2 and shall be divided into the following paragraphs.
10.1.4.1 Government documents. This paragraph shall be numbered 2.1 and shall begin with one of the following two paragraphs: (1) "The following documents of the exact issue shown form a part of this specification to the extent specified herein. In the event of conflict between the documents referenced herein and the contents of this specification, the contents of this specification shall be considered a superseding requirement." (2) "The following documents of the exact issue shown form a part of this specification to the extent specified herein. In the event of conflict between the documents referenced herein and the contents of this specification, the contents of this specification shall be considered a superseding requirement, except for specification (enter number of next higher tiered specification) listed below." The following paragraph shall appear at the conclusion of the list of documents: "Copies of specifications, standards, drawings, and publications required by suppliers in connection with specified procurement functions should be obtained from the contracting agency or as directed by the contracting officer." Government documents shall be listed by document number and title in the following order:
SPECIFICATIONS
Federal
Military
Other Government Agency
STANDARDS
Federal
Military
Other Government Agency
DRAWINGS:
(Where detailed drawings referred to in a specification are listed on an assembly drawing, it is only necessary to list the assembly drawing.)
OTHER PUBLICATIONS:
Manuals
Regulations
Handbooks
Bulletins
etc.
10.1.4.2 Non-Government documents. This paragraph shall be numbered 2.2 and shall begin with the following paragraph: "The following documents of the exact issue shown form a part of this specification to the extent specified herein. In the event of conflict between the documents referenced herein and the contents of this specification, the contents of this specification shall be considered a superseding requirement." The source for all documents not available through normal Government stocking activities shall be listed. The following paragraph shall be placed at the conclusion of the list when applicable: "Technical society and technical association specifications and standards are generally available for reference from libraries. They are also distributed among technical groups and using Federal Agencies." Non-Government documents shall be listed by document number and title in the following order:
SPECIFICATIONS
STANDARDS
DRAWINGS
OTHER PUBLICATIONS
10.1.5 Engineering requirements. This section shall be numbered 3 and shall be divided into the following paragraphs and subparagraphs to specify the engineering requirements necessary to ensure proper development of the CSCI. Requirements to be included herein shall be allocate or derived from requirements established by the applicable SSS, PIDS, OR CIDS.
10.1.5.1 CSCI external interface requirements. This paragraph shall be numbered 3.1 and shall identify the external interfaces of the CSCI. An external interface diagram similar to Figure 1 may be used to aid in this description. Each external interface shall be identified by name and project-unique identifier and a brief description of each interface shall be provided. Any identifying documentation, such as an Interface Control Document or Interface Requirements Specification, shall be referenced for each interface.
10.1.5.2 CSCI capability requirements. This paragraph shall be numbered 3.2 and shall identify, in the subparagraphs that follow, all of the capability requirements that the CSCI must satisfy. If the system of which the CSCI is a part can exist in various system states and modes as documented in the system specification, this paragraph shall identify each such state and mode and shall correlate each CSCI capability to those states and modes. A table may be used to depict this correlation.
10.1.5.2.1 (Capability name and project-unique identifier). This subparagraph shall be numbered 3.2.X (beginning with 3.2.1), shall identify the CSCI capability by name and project-unique identifier and shall state the purpose of the capability and its performance in measurable terms. This subparagraph shall identify and state the purpose of each input and output associated with the capability. This subparagraph shall identify the allocated or derived requirements that the capability satisfies or partially satisfies. If the capability can be more clearly specified by decomposing it in constituent capabilities, the requirements for each constituent capability shall be provided as one or more subparagraphs. Each constituent capability shall be assigned a project-unique identifier that is derived from the identifier of the parent capability.
10.1.5.3 CSCI internal interfaces. This paragraph shall be numbered 3.3 and shall identify the interfaces between the capabilities identified above. Each internal interface shall be identified by name and project-unique identifier and a brief description of each interface shall be provided, including a summary of the information transmitted over the interface. Internal interface diagrams depicting data flow, control flow, and other relevant information may be used to aid in this description.
10.1.5.4 CSCI data element requirements. This paragraph shall be numbered 3.4 and shall specify the information identified below, as applicable.
a. For data elements internal to the CSCI:
(1) Assign a project-unique identifier to the data element
(2) Provide a brief description of the data element
(3) Identify the units of measure required for the data element, such as seconds, meters, kilohertz, etc.
(4) Identify the limit/range of values required for the data element (for constants provide the actual value)
(5) Identify the accuracy required for the data element
(6) Identify the precision or resolution required for the data element in terms of significant digits
(7) For data elements of the CSCI's internal interfaces:
• Identify the interface by name and project-unique identifier
• Identify the source capability of the data element by name and project-unique identifier
• Identify the destination capability of the data element by name and project-unique identifier
b. For data elements of the CSCI's external interfaces:
(1) Identify the data elements by project-unique identifier
(2) Identify the interface by name and project-unique identifier
(3) Identify the source or destination capability, as applicable, by name and project-unique identifier.
(4) Reference the Interface Requirements Specification in which the interface is specified.
10.1.5.5 Adaptation requirements. This paragraph shall be numbered 3.5 and shall be divided into the following subparagraphs to specify the requirements for adapting the CSCI to site-unique conditions and to changes in the system environment.
10.1.5.5.1 Installation-dependent data. This subparagraph shall be numbered 3.5.1 and shall describe the site-unique data required by each installation. Examples of such data re: site latitude and longitude, radar ranges and areas of coverage, and prescribed safety limits. In addition, this subparagraph shall identify the CSCI capabilities in which these data are used.
10.1.5.5.2 Operational parameters. This subparagraph shall be numbered 3.5.2 and shall describe parameters required by the CSCI that may vary within a specified range according to operational needs. Examples of such data are: allowable trajectory deviations, navigation set mode numbers, airplane performance characteristics, interaction/isolation of sorties, missile performance characteristics. This subparagraph shall identify the CSCI capabilities in which these data are used.
10.1.5.6 Sizing and timing requirements. This paragraph shall be numbered 3.6 and shall specify the amount and, if applicable, location of internal and auxiliary memory and the amount of processing time allocated to the CSCI. This paragraph shall specify the resources required of both memory and the central processing unit (CPU) for the CSCI.
10.1.5.7 Safety requirements. This paragraph shall be numbered 3.7 and shall specify safety requirements that are applicable to the design of the CSCI, with respect to potential hazards to personnel, property, and the physical environment.
10.1.5.8 Security requirements. This paragraph shall be numbered 3.8 and shall specify security requirements that are applicable to the design of the CSCI, with respect to potential compromise of sensitive data.
10.1.5.9 Design constraints. This paragraph shall be numbered 3.9 and shall specify other requirements that constrain the CSCI design, such as the use of a particular processing configuration, etc.
10.1.5.10 Software quality factors. This paragraph shall be numbered 3.10 and shall be divided into subparagraphs, as appropriate, to specify each software quality factor identified in the contract or derived from a higher level specification. For each quality factor required, the method of compliance shall be specified along with the requirements for that factor.
10.1.5.11 Human performance/human engineering requirements. This paragraph shall be numbered 3.11 and shall specify the applicable human factors engineering requirements for the CSCI. These requirements shall include, as applicable, considerations for:
a. Human information processing capabilities and limitations
b. Foreseeable human errors under both normal and extreme conditions
c. Implications for the total system environment (include training, support, and operational environment).
10.1.5.12 Requirements traceability. This paragraph shall be numbered 3.12 and shall contain a mapping of the engineering requirements in this specification to the requirements applicable to this CSCI in the SSS, PIDS, or CIDS. This paragraph shall also provide a mapping of the allocation of the CSCI requirements from the SSS, PIDS, or CIDS to the engineering requirements in this specification.
10.1.6 Qualification requirements. This section shall be numbered 4 and shall be divided into the following paragraphs to specify the qualification methods and any special qualification requirements necessary to establish that the CSCI satisfies the requirements of sections 3 and 5.
10.1.6.1 Qualification methods. This paragraph shall be numbered 4.1 and shall specify the qualification methods to be used to ensure that the CSCI requirements of sections 3 and 5 have been satisfied. A table similar to Table I may be used to present this information. Qualification methods include:
a. Demonstration. The operation of the CSCI (or some part of the CSCI) that relies on observable functional operation not requiring the use of elaborate instrumentation or special test equipment.
b. Analysis: The processing of accumulated data obtained from other qualification methods. Examples are interpretation or extrapolation of test data.
c. Inspection. The visual examination of CSCI code, documentation, etc.
d. Test. The execution of software procedures and functions where observed output is compared with expected output.
TABLE I. Example of a qualification cross-reference table.
• QUALIFICATION METHOD
A — ANALYSIS
D — DEMONSTRATION
I — INSPECTION
T — TEST
** QUALIFICATION LEVEL
1 — CONFIGURATION ITEM
2 — SYSTEM INTEGRATION
3 — SYSTEM
4 — SYSTEM INSTALLATION
10.1.6.2 Special qualification requirements. This paragraph shall be numbered 4.2 and shall be divided into appropriate subparagraphs to specify special requirements associated with qualification of the CSCI. This paragraph shall identify and describe, if applicable, special tools, techniques (e.g., test formulas, algorithms), procedures, facilities, and acceptance limits. For each special test, the following information shall be specified:
a. A project-unique identifier for the test
b. The paragraph number(s) of the capability requirement(s) to which the test applies.
c. A description of the test, such as peak-load stress test for 24 hr. duration
d. The level of the test (CSU, CSC, CSCI, segment, or system level)
10.1.7 Preparation for delivery. This section shall be numbered 5 and shall specify the type and characteristics of the delivery media for the CSCI (e.g., 8 track magnetic tape 1600 BPI, 150 megabyte disk). In addition, this section shall specify the labeling, packaging, handling, and classification marking requirements for the media, including the CSCI name and project-unique identifier. Any unique delivery requirements shall also be specified in this section.
10.1.8 Notes. This section shall be numbered 6 and shall contain any general information that aids in understanding this specification, (i.e., background information, glossary, formula deviations). This section shall include an alphabetical listing of all acronyms, abbreviations, and their meanings as used in this document.
10.1.8 Appendixes. Appendixes may be used to provide information published separately for convenience in document maintenance (e.g. charts, classified data). As applicable, each appendix shall be referenced in the main body of the document where the data would normally have been provided. Appendixes may be bound as separate documents for ease in handling. Appendixes shall be lettered alphabetically (A, B, etc.), and the paragraphs within each appendix be numbered as multiples of 10 (e.g., Appendix A, paragraph 10, 10.1, 10.2, 20, 20.1, 20.1, etc.). Pages within each appendix shall be numbered alpha-numerically as follows: Appendix A pages shall be numbered A-1, A-2, A-3, etc. Appendix B pages shall be numbered B-1, B-2, B-3, etc.