INCOSE Presentation San Francisco Chapter 13 October 2009 Mapping CMMI to Systems Engineering

1. INCOSE PresentationSan Francisco Chapter13 October 2009 Mapping CMMI to Systems Engineering Adrienne Friedman

2. Mapping the Capability Maturity Model Integration (CMMI) for Development, V 1.2toSystem EngineeringRequirements

3. Agenda • Working definitions • What is the CMMI? • What is INCOSE? • What is Systems Engineering? • CMMI Process categories • CMMI-DEV V1.2 Process Areas Handout • INCOSE Process Categories • INCOSE Handbook 3.1 SE Overview • CMMI Requirements Management (REQM) compared to INCOSE Requirements Analysis • CMMI Requirements Development (RD) compared to INCOSE Requirements Definition • Stakeholder benefits: Requirements • Summary

4. What is the CMMI? • CMMI is a process improvement approach that provides organizations with the essential elements of effective processes that ultimately improve their performance. • CMMI can be used to guide process improvement across a project, a division, or an entire organization. • Integrates traditionally separate organizational functions • Sets process improvement goals and priorities • Provide guidance for quality processes • Provides a point of reference for appraising current processes.

5. Purpose of INCOSE • To define the discipline and practice of Systems Engineering (SE) for student and practicing professional alike • To provide an authoritative reference to understand the discipline of SE in terms of content and practice

6. Definition of Systems Engineering • Systems engineering is a discipline that concentrates on the design and application of the whole (system) as distinct from the parts. It involves looking at a problem in its entirety, taking into account all the facets and all the variables and relating the social to the technical aspect. (Ramo) • Systems engineering is an iterative process of top-down synthesis, development, and operation of a real-world system that satisfies, in a near optimal manner, the full range of requirements for the system. (Eisner) • Systems engineering is an interdisciplinary approach and means to enable the realization of successful systems. (INCOSE) Systems’ thinking focuses on awareness of wholes and how the parts within those wholes interrelate.

7. PROCESS MANAGEMENT (PCM) SUPPORT (SUP) PROJECT MANAGEMENT (PJM) ENGINEERING (ENG) CMMI Process categories

8. Presentation focus area CMMI-DEV V1.2 Process Areas by Category

9. PROCESS MANAGEMENT (PCM) SUPPORT (SUP) PROJECT MANAGEMENT (PJM) ENGINEERING (ENG) INCOSE SE Process categories Enterprise Processes Agreement Processes PROJECT Processes Technical Processes

10. Enterprise Environment Enterprise Environment Planning Planning Assessment Assessment Control Control Management Management Configuration Configuration Information Information Investment Investment Decision Decision - - making making Risk Management Risk Management Management Management Management Management Management Management System Life Cycle Processes Management Resource Resource Stakeholder Stakeholder Requirements Requirements Management Management Architectural Design Architectural Design Requirements Requirements Analysis Analysis Definition Definition Quality Quality Management Management Implementation Implementation Integration Integration Verification Verification Transition Transition Validation Validation Operation Operation Maintenance Maintenance Disposal INCOSE Handbook SE Overview ENTERPRISE PROJECT PROCESSES PROCESSES Enterprise Environment Control Planning Assessment Assessment Control Planning Management Management Configuration Configuration Information Information Risk Management Investment Investment Decision Decision - - making Making Risk Management Management Management Management Management Management Management System Life Cycle System Life Cycle Process TECHNICAL PROCESSES Processes Processes Guidelines Management Management Resource Resource Stakeholder Stakeholder Architectural Design Requirements Requirements Management Management Architectural Design Requirements Requirements Analysis Analysis Definition Definition Quality Quality Management Management Implementation Implementation Integration Integration AGREEMENT Verification Verification Transition Transition Validation Validation PROCESSES Acquisition Acquisition Maintenance Operation Operation Maintenance Supply Supply Disposal Disposal Figure 1-1 System Life Cycle Processes Overview per ISO/IEC 15288 Presentation Focus Area

11. Presentation Focus Engineering portion of CMMI Systems Engineering approach to Requirements Management and Requirements Development Systems Engineering CMMI Process AreasCMMI Engineering • Requirements Management (REQM) • Requirements Development (RD) • Technical Solution (TS) ENGINEERING (ENG) • Product Integration (PI) • Verification (VER) • Validation (VAL) => <=

12. CAR 5 • Requirements Management (REQM) • SG1 Requirements are managed and inconsistencies with project plans and work products are identified. OID 5 QPM 4 VAL 3 DAR 3 RSKM 3 OPP 4 VER 3 OT 3 IPM 3 PI 3 PMC 2 OPD 3 SAM 2 RD 3 TS 3 PP2 REQM 2 OPF 3 CM 2 MA 2 PPQA 2 Process Areas and Specific Goals in Engineering Requirements Management (REQM)

13. CMMI Requirements Development (REQM) Controlling changes ensures that project members and customers have a clear and shared understanding of the requirements It is important to identify when requirements volatility occurs so appropriate action can be taken. High volatility makes it difficult for projects to progress. Plans must be adjusted accordingly Bi-directional traceability can cover traces to work products & demonstrates where & how each requirement is met

14. Requirements Analysis Process Controls - Natural and societal laws - Project procedures & processes Outputs Activities Inputs • Functional and non- • functional Requirements - Define functional boundary - Stakeholder requirements - Define performance requirements - System Solution Constraints - Performance Requirements - Identify architectural constraints • Requirements Verification • & Traceability Matrix (RVTM) - Define non-functional requirements - Architectural constraints - Maintain traceability and baseline integrity • Verification strategy • and criteria - Updated RVTM Enablers - Enterprise Infrastructure - Enterprise Policies, Processes, & Standards Figure 4-3 Context Diagram for Requirements Analysis Process 14

15. CAR 5 OID 5 QPM 4 VAL 3 DAR 3 RSKM 3 OPP 4 VER 3 OT 3 IPM 3 PI 3 PMC 2 OPD 3 SAM 2 RD 3 TS 3 PP2 REQM 2 OPF 3 CM 2 MA 2 PPQA 2 Engineering Process Areas and Specific Goals inEngineeringRequirements Development (RD) • Requirements Development (RD) • SG1 Stakeholder needs, expectations, constraints, and interfaces are collected and translated into customer requirements. • SG2 Customer requirements are refined and elaborated to develop product and product-component requirements. • SG3 The requirements are analyzed and validated, and a definition of required functionality is developed.

16. CMMI Requirements Development (RD) Requirements must be analyzed to ensure they are necessary and sufficient. Resulting products must perform in the users environment Customer needs are communicated informally in documents, conversations and meetings and must be translated into agreed upon requirements Product component requirements are developed recursively in parallel with recursive product development

17. Stakeholder Requirements Definition Process Outputs - System solution constraints System solution constraints - - Requirements Verification & Traceability Matrix Traceability Matrix - Validation criteria - - Validation criteria Concept documents - - Concept documents Controls - Agreements - Project procedures & processes Activities - Identify legitimate stakeholders Inputs - Elicit requirements - Define constraints - Stakeholders’ needs - Build scenarios and concept documents - Project Constraints - Resolve requirements problems - Confirm and record requirements - Establish and maintain traceability Enablers - Enterprise Infrastructure - Enterprise Policies, Processes, & Standards Figure 4-2 Context Diagram for Stakeholder Requirements Definition Process 17

18. Dion, DIO1 McConnell, MCC1 Davis, DAV1, Novorita, NOV1 - 66% to 55% • TYPES OF REQ'TS ERRORS • Incorrect fact 49% • Omission 31% • Inconsistency 13% • Ambiguity 5% • Misplaced 2% Hooks, HOO3 • 55% or more of the ... failures discovered by end users and system testers are caused by problems with requirements. The most probable causes are: • Ambiguous words and phrases • Incomplete statements • Inconsistent functions • Untestable functions • Untraceable functions • Undesirable design impositions To fix requirements errors after deployment: 50x to 200x cost factor McConnell, MCC1 Robert M. Poston, Generating Test Cases from Use Cases Automatically Stakeholder benefits: Requirements

19. In conclusion • CMMI is a process improvement model that maps well to current System Engineering processes • It provides a yardstick to ensure that current best practices for SE and for companies as a whole are implemented http://www.sei.cmu.edu/cmmi/tools/dev/index.cfm