公司SCM供应链管理22020年4月19日文档仅供参考Software Configuration Management (SCM)Document Number: nnDate: Day, Month Day, YearProject NameAuthor 1Author 2 - if none, leave blank lineAuthor 3 - if none, leave blank lineAuthor 4 - if none, leave blank lineProfessor NameSoftware Engineering Department Monmouth UniversityWest Long Branch, NJ 07764-1898Table of Contents1. SCOPE31.1. Identification31.2. System Overview31.3. Document Overview32. REFERENCED DOCUMENTS33. REQUIREMENTS SUMMARY33.1. Background, Objectives, and Scope43.2. Operational Policies and Constraints43.3. Description of Current System or Situation53.4. Users or Involved Personnel53.4.1 Configuration Requirements63.5. Software Configuration Management Criteria64. JUSTIFICATION94.1 Assumptions and Constraints94.2 Additional Items for consideration:95. NOTES10 1 ScopeThis section shall be divided into the following paragraphs.1.1 IdentificationThis 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 OverviewThis 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 OverviewThis paragraph shall summarize the purpose and contents of this document and shall describe any security or privacy considerations associated with its use.2 Referenced DocumentsThis 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 SummaryThis section shall be divided into the following paragraphs to describe the risk management requirements as it currently exists.3.1 Background, Objectives, and ScopeThis 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 developers approach, described in the projects SDP, is to address all applicable contract clauses for SCM including:Configuration identificationConfiguration controlConfiguration status accountingConfiguration auditsPackaging, storage, handling, and delivery3.2 Operational Policies and ConstraintsThis paragraph shall describe any operational policies and constraints that apply to the current system or situation.Example: SCM activities apply to all software products prepared, modified, and/or used to develop software products as well as to the products under development, modification, reengineering, or reuse. If a system/subsystem or SWI is developed in multiple builds, SCM in each build is to be understood to take place in the context of the software products and controls in place at the start of the build.3.3 Description of Current System or SituationThis paragraph shall provide a description of the current system or situation, identifying differences associated with different states or modes of operation (for example, regular, maintenance, training, degraded, emergency, alternative-site, wartime, peacetime). The distinction between states and modes is arbitrary. A system may be described in terms of states only, modes only, states within modes, modes within states, or any other scheme that is useful. If the system operates without states or modes, this paragraph shall so state, without the need to create artificial distinctions. 3.4 Users or Involved PersonnelThis paragraph shall describe the types of users of the system, or personnel involved in the current situation, including, as applicable, organizational structures, training/skills, responsibilities, activities, and interactions with one another.Example: Developers key activities related to Software configuration management:Describe the approach to be followed for software configuration management, identifying risks/uncertainties and plans for dealing with them. Cover all contractual clauses pertaining to software configuration management.Participate in selecting CSCIs during system (architectural) design. Identify entities to be placed under configuration control. Assign a project-unique identifier to each SWI and each additional entity to be placed under configuration control, including software products to be developed or us