1.2.2 Describe the need to Technical 1.2.2.1 Evaluate technical requirements for convert functional and Requirements affordability, achievability and traceability to Undertand and reference the Concept of behavioral expectations to stakeholder’s requirements, expectations, and Operations (CONOPS). technical requirements perceived constraints. Ensure connectios are made to user requirements (e.g. JCIDS) and mission 1.2.2.2 Validate and base line the technical operation summary/mission profile. requirements. 1.2.2.3 Define the technical problem scope and the related design and product constraints. Ensure the design Reliabiltity Develop and document reliability 1.2.3 1.2.3.1 incorporates reliability, Growth Curves growth expecations. that program planning (and availability and resourcing) is reflective of RAM approach. maintainability requirements 1.2.3.2 Assess reliabiltiy growth progress RAM across the program to support across a system's life cycle versus the RAM-C expectations. RAM-C Report cost and supportability projections for lifetime support. References: DoDI 5000.02, Enclosure 3 DoD RAM-C Report Manual June 2009 1.2.4 Ensure the open Open Systems 1.2.4.1 Define system design to achieve 1. Survey existing and planned modular and systems architecture design Architecture interoperability with existing and planned open systems and lessons learned. is compatible with user Certification DoD/Service/Agency systems. 2. Determine from systems candidates performance, for the system. interoperability, and product SEP 1.2.4.2 Incorporate a in order to optimize the 3. Consider the life-cycle support costs and support requirements and design for effective and efficient product benefits of incorporating the existing desired capabilities. support. LSCP systems. 4. Coordinate design decisions with stakeholders. 5. Document decisions in the LCSP in coordination with the SEP.
1.2.2 Describe the need to convert functional and behavioral expectations to technical requirements Technical Requirements 1.2.2.1 Evaluate technical requirements for affordability, achievability and traceability to stakeholder’s requirements, expectations, and perceived constraints. 1.2.2.2 Validate and base line the technical requirements. 1.2.2.3 Define the technical problem scope and the related design and product constraints. Undertand and reference the Concept of Operations (CONOPS). Ensure connectios are made to user requirements (e.g. JCIDS) and mission operation summary/mission profile. 1.2.3 Ensure the design incorporates reliability, availability and maintainability requirements across a system's life cycle Reliabiltity Growth Curves RAM-C Report 1.2.3.1 Develop and document reliability growth expecations. 1.2.3.2 Assess reliabiltiy growth progress versus the RAM-C expectations. that program planning (and resourcing) is reflective of RAM approach. RAM across the program to support cost and supportability projections for lifetime support. References: DoDI 5000.02, Enclosure 3 DoD RAM-C Report Manual June 2009 1.2.4 Ensure the open systems architecture design is compatible with user performance, interoperability, and product support requirements and desired capabilities. Open Systems Architecture Certification SEP LSCP 1.2.4.1 Define system design to achieve interoperability with existing and planned DoD/Service/Agency systems. 1.2.4.2 Incorporate a in order to optimize the design for effective and efficient product support. 1. Survey existing and planned modular and open systems and lessons learned. 2. Determine from systems candidates for the system. 3. Consider the life-cycle support costs and benefits of incorporating the existing systems. 4. Coordinate design decisions with stakeholders. 5. Document decisions in the LCSP in coordination with the SEP.
DAG%20Chp%201%20PM%20Technical%20Mmgt%20Roles%20Aug%202016.docx