计算机软件需求规格说明方法资源-CSDN下载

需积分: 9 28 浏览量 2019-01-01 22:44:37 上传评论收藏 63KB PDF 举报

资源推荐

资源详情

资源评论

DATA ITEM DESCRIPTION

Form Approved

OMB NO.0704-0188

Public reporting burden for collection of this information is estimated to average 110 hours per response, including the time for reviewing instructions, searching existing data sources,

gathering and maintaining the data needed and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this

collection of information, including suggestions for reducing this burden to Washington Headquarters Services, Directorate of Operations and Reports, 1215 Jefferson Davis Highway, Suite

1204, Arlington, VA 22202-4302, and to the Office of Management and Budget, Paperwork Reduction Project (0704-0188), Washington , DC 20503.

1. TITLE

SOFTWARE REQUIREMENTS SPECIFICATION (SRS)

2. IDENTIFICATION NUMBER

DI-IPSC-81433

3. DESCRIPTION/PURPOSE

3.1 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 pertaining to the CSCI’s external interfaces may be presented in the SRS or in one or more

Interface Requirements Specifications (IRSs) (DI-IPSC-81434) referenced from the SRS.

3.2 The SRS, possibly supplemented by IRSs, is used as the basis for design and qualification testing of a

CSCI.

4. APPROVAL DATE

(YYMMDD)

941205

5. OFFICE OF PRIMARY RESPONSIBILITY

6a. DTIC

APPLICABLE

6b. GIDEP

APPLICABLE

7. APPLICATION/INTERRELATIONSHIP

7.1 This Data Item Description (DID) contains the format and content preparation instructions for the data

product generated by specific and discrete task requirements as delineated in the contract.

7.2 This DID is used when the developer is tasked to define and record the software requirements to be met by

a CSCI.

7.3 Requirements pertaining to CSCI interfaces may be presented in the SRS or in IRSs.

7.4 The Contract Data Requirements List (CDRL) (DD 1423) should specify whether deliverable data are to be

delivered on paper or electronic media; are to be in a given electronic form (such as ASCII, CALS, or compatible

with a specified word processor or other support software); may be delivered in developer format rather than in

the format specified herein; and may reside in a computer-aided software engineering (CASE) or other

automated tool rather than in the form of a traditional document.

7.5 This DID supersedes DI-MCCR-80025A and DI-MCCR-80301.

8. APPROVAL LIMITATION

Limited Approval from 12/5/94 through 12/5/96

9a. APPLICABLE FORMS 9b. AMSC NUMBER

N7076

10. PREPARATION INSTRUCTIONS

10.1 General instructions.

a. Automated techniques. Use of automated techniques is encouraged. The term "document" in this DID

means a collection of data regardless of its medium.

b. Alternate presentation styles. Diagrams, tables, matrices, and other presentation styles are acceptable

substitutes for text when data required by this DID can be made more readable using these styles.

(Continued on Page 2)

11. DISTRIBUTION STATEMENT

DISTRIBUTION STATEMENT A. Approved for public release; distribution is unlimited.

DD Form 1664, APR 89

Previous editions are obsolete

Page 1 of 10 Pages

135/123

Software Requirements Specification (SRS) (PDF version) DI-IPSC-81433

10. PREPARATION INSTRUCTIONS -- 10.1 General Instructions (continued)

c. Title page or identifier with signature blocks

. The document shall include a title page

containing, as applicable: document number; volume number; version/revision indicator;

security markings or other restrictions on the handling of the document; date; document

title; name, abbreviation, and any other identifier for the system, subsystem, or item to

which the document applies; contract number; CDRL item number; organization for which

the document has been prepared; name and address of the preparing organization;

distribution statement; and signature blocks for the developer representative authorized

to release the document, the acquirer representative authorized to approve the document,

and the dates of release/approval. For data in a database or other alternative form, this

information shall be included on external and internal labels or by equivalent identification

methods.

d. Table of contents

. The document shall contain a table of contents providing the number,

title, and page number of each titled paragraph, figure, table, and appendix. For data in

a database or other alternative form, this information shall consist of an internal or external

table of contents containing pointers to, or instructions for accessing, each paragraph,

figure, table, and appendix or their equivalents.

e. Page numbering/labeling

. Each page shall contain a unique page number and display the

document number, including version, volume, and date, as applicable. For data in a

database or other alternative form, files, screens, or other entities shall be assigned

names or numbers in such a way that desired data can be indexed and accessed.

f. Response to tailoring instructions

. If a paragraph is tailored out of this DID, the resulting

document shall contain the corresponding paragraph number and title, followed by "This

paragraph has been tailored out." For data in a database or other alternative form, this

representation need occur only in the table of contents or equivalent.

g. Multiple paragraphs and subparagraphs

. Any section, paragraph, or subparagraph in this

DID may be written as multiple paragraphs or subparagraphs to enhance readability.

h. Standard data descriptions

. If a data description required by this DID has been published

in a standard data element dictionary specified in the contract, reference to an entry in

that dictionary is preferred over including the description itself.

i. Substitution of existing documents

. Commercial or other existing documents may be

substituted for all or part of the document if they contain the required data.

10.2 Content requirements

. Content requirements begin on the following page. The numbers

shown designate the paragraph numbers to be used in the document. Each such number is

understood to have the prefix "10.2" within this DID. For example, the paragraph numbered 1.1

is understood to be paragraph 10.2.1.1 within this DID.

剩余9页未读，继续阅读

评论收藏

内容反馈

was4444

粉丝: 0

软件需求规格说明

示例：软件需求规格说明书

软件需求规格说明书

软件需求规格说明编写指南(438B).doc

软件需求规格说明书模板(SRS)

软件需求规格说明书(SRS)

软件需求规格说明书模板.doc

计算机软件需求规格说明规范

软件需求规格说明书模板

软件开发+需求说明+软件需求规格说明说+软件需求设计+需求说明+软件需求说明文档(范本模板)

05软件需求规格说明书评审.pdf

软件需求规格说明书模板(超详细).doc

软件需求规格说明书模板（通用版）

软件需求规格说明1

计算机软件需求规格说明规范（国家标准）

软件需求规格说明书SRS模板.doc

软件需求规格说明书模板(超详细.zip程序开发文档软件开发文技术档下载

Vue相关踩坑之路

用SpriteKit打造iOS游戏

最新资源