某公司SCM供应链管理(英文版)

Software Configuration Management

(SCM)

Document Number: [nn]

Date: Day, Month Day, Year

[Project Name]

[Author 1]

[Author 2 - if none, leave blank line]

[Author 3 - if none, leave blank line]

[Author 4 - if none, leave blank line]

Professor [Name]

Software Engineering Department

Monmouth University

West Long Branch, NJ 07764-1898

Table of Contents

1. SCOPE 4

1.1.I DENTIFICATION 4 1.

2.S YSTEM O VERVIEW 4 1.

3.D OCUMENT O VERVIEW 4

2. REFERENCED DOCUMENTS 5

3. REQUIREMENTS SUMMARY 5

3.1.B ACKGROUND,O BJECTIVES, AND S COPE 5 3.2.O PERATIONAL P OLICIES AND C ONSTRAINTS 6 3.3.D ESCRIPTION OF C URRENT S YSTEM OR S ITUATION 6 3.

4.U SERS OR I NVOLVED P ERSONNEL7 3.4.1C ONFIGURATION R EQUIREMENTS8 3.

5.S OFTWARE C ONFIGURATION M ANAGEMENT C RITERIA9

4. JUSTIFICATION 12

4.1A SSUMPTIONS AND C ONSTRAINTS12 4.2A DDITIONAL I TEMS FOR CONSIDERATION: 12

5. NOTES 13

1 Scope

[This section shall be divided into the following paragraphs.]

1.1 Identification

[This paragraph shall contain a full identification of 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

[This paragraph shall briefly state the purpose of the system and the software to which this document applies. It shall describe the general nature of the system and software; summarize the history of 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

[This paragraph shall summarize the purpose and contents of this document and shall describe any security or privacy considerations associated with its use.]

2 Referenced Documents

[This section shall list the number, title, revision, and date of all documents referenced in this specification. This section shall also identify the source for all documents.]

3 Requirements Summary

[This section shall be divided into the following paragraphs to describe the risk management requirements as it currently exists.]

3.1 Background, Objectives, and Scope

[This paragraph shall describe the background, mission or objectives, and scope of the product or situation.]

[Example: Requirements regarding software configuration management (SCM) cover a broad arena. SCM is considered one of the integral processes that support the other activities in the standard. The developer's approach, described in the project's SDP, is to address all applicable contract clauses for SCM including:

Configuration identification

Configuration control

Configuration status accounting