Technical Certifications Table 2.2-1 summarizes the system-level technical certifications which must be obtained during program’s life-cycle. Certification PMO Team/PoC Activities to Obtain Certification1 Certification Authority Expected Certification Date Defense Business System (DBS) Certification and approval ?Q FY? Cybersecurity Risk Management Framework (RMF) Assessment and Authorization Respond to security controls in Enterprise Mission Assurance Support Service (eMASS) Designated Authorizing Official (AO) ?Q FY? Interoperability and Supportability (I&S) Certification See ?Q FY? Release Turn-In Certification See and [insert program name] Program Manager ?Q FY? Title Act (CCA) See Component Information Officer (CIO) also by Department of Defense (DoD) CIO) ?Q FY? Table 2.2-1 Certification Requirements [mandated]
Functional team membership (to include all design consideration areas from Section 4.6) IPT products (e.g., updated baselines, risks, etc.) IPT-specific metrics Note: Make sure that the IPTs in the figure above match the IPTs in the table below! Expectation: Program personnel should integrate SE activities with all appropriate functional and stakeholder organizations. In addition, IPTs should include personnel responsible for each of the design consideration in Section 4.6, Table 4.6-1.
Team Name Chairperson Team Membership (by Function or Organization) Team Role, Responsibility, and Authority Products and Metrics SE IPT Lead SE Program Office Platform Lead Mission Equipment Lead Weapons Lead Test Manager LSW Lead Production/Quality Manager Safety Lead Interoperability Rep. R&M Lead PEO and PM Service Representative OSD SE Key Subcontractor or Suppliers Role: IPT Purpose Responsibilities: Integrate all technical efforts Team Member Responsibilities Cost, Performance, Schedule Scope, Boundaries of IPT Responsibilities Schedule and frequency of meetings Date of signed IPT charter and signatory Products: SE Plan/ SE Plan Updates IMP/IMS Input Specifications Metrics: -Cost -Performance -Schedule XXX IPT XXX Lead Program Office Lead SE Mission Equipment Lead Weapons Lead Test Manager SW Lead R&M Lead Production/Quality Manager Safety Lead Interoperability Rep. Key Subcontractor or Suppliers Role: IPT Purpose Responsibilities: Integrate all technical efforts Team Member Responsibilities Cost, Performance, Schedule Scope, Boundaries of IPT Responsibilities Schedule and frequency of meetings Date of signed IPT charter and signatory Products: Specification input SE Plan input TES/TEMP input AS input Metrics: Technical Performance Measure (TPM) 1 TPM 2 Table 3.4.4-2 IPT Team Details [mandated unless charters are submitted, sample]
Mapping Key Design Considerations into Contracts Name (Reference) Cognizant PMO Org Certification Documentation (hot link) Contractual Requirements (CDRL #) Description/Comments (COTS) Completed ASR Checklist, TDS (MS A) Completed of Code Estimating Form, Completed Lines of Code Estimating Template, Title 40/CCA Compliance and Confirmation, Transition Plan (MS A, B, & C) Completed Requirements Change Form Template, Completed RTM, Completed Supplementary Specifications Peer Review Checklist, GRS, LCMP (MS B & C) Completed CDR Checklist, Implementation Plan (MS C) The Alternative System Review (ASR) checks for a risk assessment of the inclusion of COTS in the program. The Technology Development Strategy (TDS) may consider COTS as a rationale for implementing a single-step-to-full-capability strategy. COTS is also a consideration when developing the AS portion of the LCMP. Maximum use of COTS is required for Title 40/CCA compliance and confirmation. The GRS documents assumptions made regarding the availability and capability of COTS components. The peer review of the Supplementary Specification checks for consideration of COTS items. The Critical Design Review (CDR) checks for adequate preparations for the configuration of COTS items. COTS is included when estimating software costs and counting source lines of code (SLOC). The RTM includes traceability to/from COTS code. New or updated COTS packages are considered when documenting requirements changes. The Implementation Plan documents the installation of COTS support software for the operating environment.
Memorandum; ITR (MS C) Two roles, Information System Security Manager (ISSM) and Information System Security Officer (ISSO) are assigned to specifically address IA duties. The ISSM also participates in requirements analysis, the Integrated Test Team (ITT), the PDR, the CDR, the Design Review, and the TRR I. The ISP describes Cybersecurity compliance. A ISSM No Impact Security Memorandum is included in the release package submitted during TRR I. Reliability and Maintainability (R&M) LCMP (MS A, B, & C) Completed SRR Checklist (MS B) A Reliability, Availability, and Maintainability (RAM) strategy is included in the LCMP, and the SRR checks for system compliance with RAM requirements. SE Tradeoff Analysis for Affordability LCMP (MS B) The LCMP discusses how tradeoffs between cost and performance will be encouraged and the government‘s role in managing the trade space. Software [Insert program name] is a software-only system. Spectrum Management ISP, LCMP (MS A, B, & C) CDD, TEMP (MS B & C) Spectrum supportability is addressed in the CDD and LCMP, and is included as a critical operational effectiveness and suitability parameter in the TEMP. Frequency spectrum dependencies are described in the ISP. Standardization LCMP (MS A, B, & C) Applicable International Standardization Agreements are identified in the LCMP. Survivability TES (MS A) LCMP, 40/CCA Compliance and Confirmation Survivability is addressed in the CDD, GRS, LCMP, and TES. Survivability is also a factor in Title 40/CCA compliance.