IEEE/EIA 12207, Software Life Cycle Processes Air Force Weapon System Software Management Guidebook Process areas and associated definitions were developed to best meet AF SE needs and are in alignment with current DoD and AF guidance as summarized in the table below: AF SEAM Defense Acquisition Guide AFI 63-101/20-101 Requirements Reqts Analysis, Reqts Mgmt, Stakeholder Reqts Definition Reqt Dev & Mgmt, & Architecture Design Architectural Design, Integration & Interface Mgmt Design & Interface Mgmt Verification & Validation Verification & Validation Test & Evaluation, Verification & Validation Manufacturing Implementation Design Transition, Fielding, & Sustainment Transition Design Project Planning Technical Planning Planning Configuration Management CM, Data Mgmt, Technical Data Mgmt Configuration Mgmt, Data Mgmt Risk Management Risk Mgmt Integrated Risk Management Technical Mgmt & Control (PMC) Technical Assessment Technical Reviews & Measurements Decision Analysis Decision Analysis Decision Analysis Terminology In general, this model uses the terminology used within the CMMI framework. References to CMMI and AF SEAM terminology should be understood in both the acquisition and the process improvement contexts. The term “project” denotes a managed set of interrelated resources that delivers one or more products to a customer or end-user. In this document, a “project” could refer to an entire acquisition program or, perhaps, a major subset of an acquisition program. The scope of the term is tailored to
the specific acquisition. The term “organization” is typically used to denote an administrative structure in which people collectively manage one or more projects. The term “acquirer” refers to the organization responsible for acquisition of the product or component. This is typically the Government and might include both the project or program office and sponsoring office. It can also apply recursively down the supply-chain (i.e., the integrator fulfills an acquirer role when working with sub- tiers in the supply-chain) The term “integrator” refers to the organization performing the work of product integration (e.g., the prime contractor). The term “supplier” refers to all organizations in the supply-chain including the integrator and other organizations responsible for providing a subassembly, component or part of the product. The term “work product” is any artifact produced by a process. The term “product” denotes a tangible output or service that is a result of a process and that is intended for delivery to a customer or end user. A product is a work product that is delivered to the customer. The term “establishing” includes changing documenting and providing a description. The term “maintaining” includes changing documentation as necessary. The term “system” is not used in the CMMI framework or in the AF SEAM process areas except in the general sense (e.g., systems engineering). The term “systems engineering” includes software engineering. The term “stakeholder” refers to a person, group, or organization that affects or can be affected by an organization’s actions. Readers should decide how these terms apply to their environment. AF SEAM Assessment Process The below diagram describes the overall AF SEAM assessment process. The following paragraphs summarize what occurs during each phase of the process.
Typical Work Products Configuration Management Plan Configuration Items (list, table, spreadsheet etc.) Reference Material AFI 33-114 (Software Management) AFI 63-101/20-101 (5.2.1.6) MIL-HDBK-61A (SE) Other Considerations Examples of work products that may be a part of a configuration item include process descriptions, requirements, design details, verification methods and procedures, source code and tools. Other documents, such as interface definitions and test results, may also be included. CMG2P2: Establish and maintain configuration and change management systems. Description The configuration and change management system enables the disciplined management and control of changes to the product and related work products. Typical Work Products Configuration management system with controlled work products Configuration management system access control procedure Change request database Reference Material AFI 63-101/20-101 (5.2.1.6) AFI 33-114 (Software Management) MIL-HDBK-61A (SE) Other Considerations The configuration management system includes the storage media, the procedures, and the tools for accessing the configuration system. It also includes the storage media, the procedures, and the tools for recording and accessing change requests. The system should be able to retrieve documentation of any baseline and status of all CM actions. The Chief Engineer is responsible for maintaining a strategy for technical baseline management. CMG2P3: Create or release technical baselines. Description Ensure that all baselines established are created from configuration items described within the configuration management system, documented, authorized and released in accordance with CM plans. Typical Work Products Description of Baselines
Engineering change proposals Contract change proposals Trade Studies Reference Material is no material at this time Other Considerations Corrective action should be determined in sufficient time to properly resolve the issue. TMCG4P2: Establish and maintain a deficiency reporting system Description A deficiency reporting information system is established and maintained that includes deficiency identification, root analysis, and corrective action mechanisms. Establish and maintain criteria, processes, and procedures for determination and disposition of nonconforming products to prevent their unintended use or delivery. Typical Work Products Deficiency Reports Deficiency reporting system Corrective Action reports Reference Material T.O. 00-35D-54 AFI 21-104 AFI 21-118 AFI 63-501 AFI 63-101/20-101 Other Considerations An automated defect reporting/tracking system can enhance timely analysis of problem areas and verification of effectiveness of action taken to correct problems. A corrective action team should be established to ensure adequate attention to the causes of defects. Verification and Validation (V) The purpose of Verification is to ensure that work products meet their specified requirements. The purpose of Validation is to demonstrate that a product or product component fulfills its intended use when placed in its intended environment. Verification and validation methods (e.g., peer reviews, modeling and simulation) can be applied to work products (e.g., designs and prototypes) as well as to the product and product components. The work products should be selected based on which are the best predictors of how well the delivered end product and product components will satisfy user needs.
to ensure compliance to applicable standards. The suppliers typically use peer reviews internally on selected interim work products during development, but the acquirer should not rely solely on these results. Peer reviews within a project should include "independent" participants from other organizations not directly connected to the material being reviewed. VG3: Work products are verified VG3P1: Perform verification on the selected work products Description Verify work products, using approved methods and procedures, to promote early detection of problems, timely removal of defects, and reduce cost. Conduct Functional Configuration Audits (FCA) to verify the actual performance meets specification requirements. Verify that interfaces conform to established standards, agreements and specifications, and lower level designs are consistent with top-level designs. Implement pedigree checks and/or test item configuration auditing for important test events. Typical Work Products FCA results Findings Action items Test report Reference Material There is no material at this time. Other Considerations Document and manage the results of verification as an element of the project data management effort. Conduct analysis to identify trends, process improvement opportunities and potential risks. VG3P2: Initiate and document corrective actions Description Track corrective actions until subsequent verification activities confirm compliance with requirements. Typical Work Products Action item list DRs Test report Reference Material There is no material at this time. Considerations Data on verification and corrective actions should be available to the acquirer and suppliers organizations as well as to other appropriate stakeholders.