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

PAGE PAGE 1 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 West Long Branch Table of Contents TOC \o 1-3 1. Scope 3 1.1. Identification 3 1.2. System Overview 3 1.3. Document Overview 3 2. Referenced Documents 3 3. Requirements Summary 3 3.1. Background, Objectives, and Scope 4 3.2. Operational Policies and Constraints 4 3.3. Description of Current System or Situation 5 3.4. Users or Involved Personnel 5 3.4.1 Configuration Requirements 6 3.5. Software Configuration Management Criteria 6 4. Justification 9 4.1 Assumptions and Constraints 9 4.2 Additional Items for consideration: 9 5. Notes 10  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 docum