Systems Engineering Concept Model SECM Update Status 06232016

Systems Engineering Concept Model (SECM) Update Status 06/23/2016 John Watson

System Engineering Concept Model Agenda Overview Resources and Goals SECM High Level Approach SECM Model High Level Organization Status SECM Industry Reference Model SECM – Sys. ML V 2 RFP Approach Interface Concepts SE Needs Interface Core Team (Marc Sarrel, JPL) 2

Resources - SECM Team Contributors Yves Bernard Roger Burkhart Sandy Friedenthal Chas Galey Rick Steiner John Watson Meet Weekly, Tuesday’s 11 AM ET Systems Engineering Concept Model Wiki Tools Magic. Draw Modeling Tool Teamwork Server Team collaboration tool Server and licenses provided by No Magic 3

SECM-Domain Goals and Overview Task objective Derive a data model that captures the core Systems Engineering concepts and vernacular Derive the system modeling language requirements that will be used in the Sys. ML V 2 RFP Use Cases Systems engineers and other discipline engineers contribute to the development and maintenance of a system model throughout the lifecycle to support the system specification, design, analysis, and verification activities Mo. E The Sys. ML V 2 RFP requirements are clear and concise, and reflect the core Systems Engineering concepts and vernacular High Level Intent/Driving Requirement: (R 1) The next-generation modeling language must express the core systems engineering concepts. This requires definition of a robust data model that reflects these concepts. The requirements that drove Sys. ML derive from the original Systems Engineering Conceptual Model, jointly developed by the INCOSE/OMG/AP 233 WG requirements team. Modifications and refinements to this model will occur in light of lessons learned over the last several years, and as necessary to express the core systems engineering concepts. 4

Systems Engineering Concept Model (SECM) Approach INCOSE Systems Engineering Handbook V 4 ISO/ IEC/IEEE 15288: 2015 V 1. 5 SECM – 2015 Industry Reference Other Industry Ontologies SECM – 2003 Industry Reference * SECM - Sys. ML V 2 RFP Sys. ML V 2 Service Requirements Other OMG Specs Sys. ML V 2 Spec Sys. ML V 2 RFP Meta-model Profile Libraries Concrete Syntax Standardized API Reference Model UML 4 SE RFP * Joint INCOSE/AP 233/OMG, Led by Dave Oliver Sys. ML V 1. X Spec User Interface Guidelines 5

SECM Model High Level Organization

SECM - Industry Reference 7

SECM: 2015 Industry References Primary – SEBo. K V 1. 6 INCOSE SE Handbook, 4 th Edition ISO/IEC/IEEE 15288 Status 246 Concept Terms have been captured and defined in the model 30 Concept Diagrams and Tables HTML Model Extracts are available on the Wiki 8

Core SEBo. K Concepts 9

SECM – Sys. ML V 2 RFP 10

“SECM – Sys. ML V 2 RFP” Topic Approach SECM – 2015 Industry Reference SE Needs Model Related Papers Produce “SE Needs” Other Industry Ontologies Example Models Topic Expert Core Team Refine with Top Industry Experts Requirements & Concepts SE Needs Document SECM - Sys. ML V 2 RFP UML 4 SE RFP 11

Topic Core Teams Properties and Expression Core Team Launched 22 January 2016 “SE Needs” resources provided; Interface Core Team Launched 27 May 2016 “SE Needs” resources provided; Concept Model Diagrams SE Needs Document Extension Wiki from the SECM Wiki Their status being provided today Potential Future Topics Requirements and Verification Function and Structure Behavior Variants Libraries 12

SECM – SE Interface Needs 13

Interface Needs Deliverables All deliverables available on the SECM Wiki Interface Needs Word Document Interface Needs Modeling Artifacts SECM Web Publisher Report, zip file download, snapshot on 6 June 2016 - Interface Needs Complete Concepts Diagram Concept Definitions Examples Interface Needs Model Diagrams Review Slides Other useful references

Interface Needs Concepts 15

Interface Core Team Status Marc Sarrel, JPL

Backup 17

Conclusions SECM Industry Reference Provides a solid anchor to SE Vernacular More will be added as needed SECM – Sys. ML V 2 RFP Selecting Topics, deriving needs, create expert topic teams Properties and Expression and Interface Core Teams Launched Started Requirements Needs Modeling Potential Future topics Function and Structure Behavior Variants 18