Systems Engineering Concept Model (SECM) OMG Technical Conference, La Jolla CA, 12/10/2015 System Modeling Assessment & Roadmap WG John Watson

Overview Background SECM Approach SECM – 2015 Reference Model SECM – SysML V2 RFP

Resources - SECM Team Contributors Yves Bernard Roger Burkhart Sandy Friedenthal Chas Galey Rick Steiner John Watson Systems Engineering Concept Model Wiki Tools MagicDraw Modeling Tool Teamwork Server Team collaboration tool Server and licenses provided by No Magic

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 SysML V2 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 MoE The SysML V2 RFP requirements are clear and concise, and reflect the core Systems Engineering concepts and vernacular High Level Intent/Driving Requirement:   (R1) 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 SysML derive from the original Systems Engineering Conceptual Model, jointly developed by the INCOSE/OMG/AP233 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. Derive the requirements from well established SE references

Systems Engineering Concept Model (SECM) Approach INCOSE Systems Engineering Handbook V4 SEBoK V 0.5 Model V 1.4 ISO/ IEC/IEEE 15288: 2015 SECM – 2015 Industry Reference SysML V2 Services Requirements Other OMG Specs Other Industry Ontologies SECM - SysML V2 RFP SysML V2 RFP SysML V2 Spec SysML V2 Meta-model Service Spec To date most of the work has been done in the Industry Reference Model SECM – 2003 Industry Reference * UML 4SE RFP SysML V1.X Spec * Joint INCOSE/AP233/OMG, Led by Dave Oliver

Systems Engineering Concept Model 2015 Industry Reference

SECM – 2015 Industry Reference The intent of this model is to capture Systems Engineering domain concepts based on well-established industry references. The three primary industry references used as source material include; SEBoK Version 1.4 ISO/IEC/IEEE 15288:2015 INCOSE Systems Engineering Handbook, Version 4 Utilize a limited set of UML constructs. The intent is to keep the modeling as simple as possible to make it easy to read, to quickly understand, and to avoid implying more than intended. This model will attempt to faithfully capture the SE concepts as they are presented in the three industry references

SECM - 2015 Industry Reference 200+ Concept Terms have been captured and defined in the model 12 Concept Diagrams have been created and reviewed 2 additional Concept Diagrams are Under Construction HTML Model Extracts are available on the SECM Wiki

List of Diagrams Available Today System Hierarchy Disciplines System Architecture Generic Life Cycle Model Environment Life Cycle Configuration Management Requirement Traceability System Thinking – Principles SE Processes Architecture Models SEBoK Structure

Principle - a fundamental truth or proposition

Systems Engineering Concept Model SysML V2 RFP

SECM - SysML V2 RFP The intent is to derive a set of requirements that will be incorporated in the SysML V2 RFP. In this model we are not limited to just established industry published concepts. We are also able to include additional forward thinking and field proven concepts. This model will also utilize a limited set of UML constructs Work on this model will not wait until the SECM 2015 Industry Reference is complete As concepts are completed in the SECM 2015 Industry Reference, work will commence in this model

SECM - SysML V2 RFP Properties will be the first concept examined 1st Step – Integrate Input from sources SECM – 2015 Industry Reference UML for SE RFP - Section 6.5.3, Properties Scan SysML RTF Issues Then, request Input from other Industry Ontologies

Property Comments (1 – 10) 01-Goal: Property concepts should support seamless integration of SysML v2 models with analysis models 02-Determine whether each of the following capabilities should apply to property, property type, value, something else, or not at all 03-Support for property assignment for element, function/behavior, event (i.e., change event), condition 04-Support for grouping properties based on domain criteria (e.g., electrical vs mechanical vs thermal properties) 05-Support for property primitive types (e.g. integer, real, Boolean, string, complex, enumeration) 06-Support for units, quantity kinds, system of units, and system of quantity kinds 07-Support for specifying a range of valid values (e.g. knob position is 0-360 degrees) 08-Support for properties that are constant, constant over the execution time, and variable (refer to Modelica) 09-Support for properties that are a function of time (e.g., state variables) 10-Support for initial conditions 01, 07,

Property Comments (11 – 20) 11-Support for time as a property, including time durations, and time events 12-Support for time continuous and time discrete valued properties 13-Support for state dependent property values 14-Support for properties that are a function of other properties (e.g., parametric relationships) 15-Support for scalar, vector, and tensor properties 16-Support for matrices and arrays (e.g., engine temperature as a function to time from startup, and location on engine. Each row represents an increment of time, and each column represents an engine location.) 17-Support for ordering properties 18-Support for comparison operators (e.g., <, =, >) 19-Support for logical/Boolean operators (e.g. AND, OR, NOT, ..) 20-Support for different expression languages 13, 15, 16, 17,

Property Comments (21 – 30) 21-Support for declarative and procedural expressions 22-Support for dependent versus independent variables versus derived properties (inputs and outputs of analysis) 23-Support for referring to a particular property of an element, function or event in an expression (e.g., element reference) 24-Support for probability distributions on property values. A) unit to unit distribution B) distribution of an individual unit over time and other conditions (e.g., temperature) 25-Support for over-riding property values (e.g., redefinition) 26-Support for subsetting properties 27-Support for technical measures (e.g., TPM. KPP, MOP and MOE), including support for capturing threshold, planned values, achieve to date values, milestones and tolerance bands 28-Ability to designate properties as-specified, as-designed, as-manufactured, as-fielded (was Source in v1 RFP) 29-Support for UPDM concept of measurement 30-Support for identifying the source of a property 22, 27, 28,

Property Comments (31 – 39) 31-Support for a property referencing a set of values (e.g. table, plot) 32-Support for referring to and establishing relationships to deeply nested properties 33-Support for visualizing complex property values and relationships (e.g. plots, tables) 34-Support for linking property, units, values, .. to text 35-What is the impact of property based requirements on the property concepts? 36-Should a property be reusable or just its type (e.g., mass vs. kilograms) 37-To what extent do the SysML v1 language concepts of property, value type, instance specifications, slots, value specifications, and default values support these property concepts? 38-Clarify the relationship of physical property to quantity kind? Should a library of physical properties be provided as noted in Wikipedia at: https://en.wikipedia.org/wiki/Physical_property 39-Support for time units (ontology) - calendar time 31,

Questions?

Backup

Systems Engineering Concepts (v0.5)