1. System Modeling Assessment & Roadmap Joint OMG/INCOSE Working Group
Systems Engineering Model Construction
Focus Area
Introduction
September, 2015
Collaborate
Analyze
Integrate
System
Model
Manage
Transform
Construct
Exchange
Visualize
Ron Williamson
11/8/2018

2. System Modeling Assessment & Roadmap Joint OMG/INCOSE Working Group
Objectives:
Assess effectiveness of system modeling with SysML in support of MBSE Adoption and Use
Develop a preliminary System Modeling Roadmap to improve effectiveness
Use the Roadmap to influence the SysML specification, tool vendor implementations, related standards efforts, and industry collaborations
Scope:
SysML modeling language and tools
Modeling languages and tools that support use of SysML (e.g. constraint language, transformations)
Reuse libraries (e.g., models, practices, ..)
Integrations with other engineering models and tools
Focus Areas:
Systems Engineering Use Cases
System Engineering Concept Model
SysML v2/MBSE Capabilities including Model Construction, Model Visualization, Model Analysis, Model Management, Model Interoperability,
Members:
IBM, EADS, LMC, NASA/JPL, Raytheon, John Deere and Various Consultants
11/8/2018

3. MBSE Capability: Construct Model
Task objective
Elaborate concepts, requirements, and metrics for effective model construction that support the next generation system modeling language (SysML v2)
Use Cases
Systems engineers and other discipline engineers contribute to the development and update of the system model throughout the lifecycle to support system specification, design, analysis, and verification activities
MoE
Ability to efficiently and intuitively construct models
High Level Intent/Driving Requirement:  
The next-generation modeling language and tools must enable much more intuitive and efficient model construction.
It often requires several clicks to capture a core concept in a model.
More streamlined and efficient user interfaces could reduce the time and effort to build and maintain a model.
The ability to repeat common modeling patterns with reduced user input (e.g., table-based entry) is another capability to increase modeling productivity and understanding.
11/8/2018

4. MBE To-Be State Source: NDIA MBE Final Report dated February 2011
Hardware Models Q
SET
CLR S R
System Models
Component Models ò G ( s ) U
Analysis Models
Operational Models
Component Models
System Models ò G ( s ) U
Analysis Models
Operational Models
Configuration Management
Program
Management
Test
Manufacturing
Hardware
Systems
Customer
Logistics
Software
System Models
Operational Models
The MBE to-be state leverages MBE across the acquisition life cycle to enhance affordability, shorten delivery time, and reduce risk. In the to-be state, the models become an integral part of the technical baseline, and evolve throughout the programs life cycle. The current state is characterized by gaps between domain silos and lifecycle development phase hand-offs that are often the source of errors until later in the development process when they are more expensive to fix.  The future state of MBE seeks to reduce these errors though seamless integration of model data across domains and across the lifecycle by aligning shared model properties and assumptions. Different engineering disciplines concurrently operate on different facets of the system and/or product design, such that the impact of a change in one model can be readily assessed in another model. Engineering and programmatic knowledge is shared through a common technical baseline. The models developed by each discipline evolve in maturity throughout the life cycle, and are not thrown away and redeveloped as the program transitions from one phase of development to another. This includes the up-front mission analysis models, the system requirements and architecture models, the detailed hardware and software design models, and the detailed simulation models used to assess and verify all aspects of the system as it evolves. Early validation of requirements including those for manufacturing and support, and efficient development of a fully integrated technical baseline result in significant improvement to the development process.
The collaborative foundation provides a means to share the information from the model registry across the extended enterprise of customers, teammates and suppliers. The foundation includes the modeling standards that enable information exchange, the model registry that enables ready access to the different models, and a trusted environment which enforces protection of intellectual property and secure access to sensitive and classified data. The collaborative environment also enables reuse from one program to another to enable sharing across a family of products and system of systems.
The MBE to-be state includes a workforce that is skilled in the use of the matured modeling methods and tools, an infrastructure that supports this capability, and policies that enable it.
MBE Enhances Affordability,
Shortens Delivery and Reduces Risk Across the Acquisition Life Cycle
Needs
Current Capabilities
Budget/Schedule

5. Systems Modeling Environment Conceptual Architecture - Construct Model
Initial Scope

6. MBSE Capability: Construct Model
More Detailed Requirements:
Model Changes (includes a change to a model element or change to a reference to an external model element or other data item, or possibly to a change in metadata)
Create new elements or references
Update existing elements or references
Delete existing elements or references
Create Variants of elements or element configurations
Type of Data Input
Manual entry
Graphical
Text/structure text
Tabular/forms based
Automated ingest from the following
Another model of same type
Another model of different type
Structured data source (e.g., file, database)
Unstructured document
Linked data via reference
Simple link (e.g., hyper link)
Semantic relationship (e.g. OSLC)
11/8/2018

7. MBSE Capability: Construct Model
More Detailed Requirements (cont):
Construction Operations
Control  access (validate user has data access privileges)
Automated ingest
Select and validate data source
Transform input to match schema
Maintain links/log to external data source
Manual entry
Apply pattern
Apply validation rules and assess
Resolve validation errors
Log changes to model
Capture metadata regarding update (who changed, when, rationale, input source...)
Report differences
Non Functional Requirements
Performance
Security
Extensibility
New technology
New requirements
11/8/2018

8. MBSE Capability: Construct Model
Stakeholders
Customers
Managers
System Engineers
Design
(IV&V)
Specialty / Whole Life
Other Disciplines
Software
Hardware
Mechanical
Electrical
Algorithms
Mission / Business Analysts
Sources
Customer Specifications
Management Cost/Schedule and EVMS
System Level
CONOPS – Operational Scenarios
Specifications: SRD, SSS, ICS, etc.
Software
SRS, CSCI models/specs, UCs
Hardware
HWCI models/specs
Algorithms
Models/specs
11/8/2018

9. System Engineering Model Construction
System Engineering Model Construction Role of the Concept Model, for example
A model is a simplified representation of a system at some particular point in time or space intended to promote understanding of the real system.
As an abstraction of a system, it offers insight about one or more of the system's aspects, such as its function, structure, properties, performance, behavior, or cost.
Source:
Table
VIEW DB
Text
VIEW
System
Requirements
System
Test Cases
Controller/Transform
Table
System
Model
Text
VIEW
System
Interfaces
Controller/
Transform
MODEL
Update 2003
Model with
Latest
Graphic
Table
Text
Model
System
Design
VIEW
Controller/Transform
CONCEPT MODEL
Parse & Transform Using
Concept / Meta model “grammar”
11/8/2018

10. MBSE Capability: Construct Model
Interactive Model Construction
Standard tool HMI with
Model Browser
Model Diagram
Model Tool Palette
Model Library Access
Stereo type extensions
Data types, and units
Patterns (e.g. Frequently used combinations of model elements)
“Batch” Model Construction
Tabular data import
Requirements (ID, Description, attributes….) mapped to Requirement Stereotype
Interfaces (ID, Description, Type, Attributes) mapped to Interface Stereotype
Use Cases (ID, Description, Pre-Condition, Post-Condition, scenario steps,…)
Structured document import
Unstructured text
Structured / Unstructured Graphics and Figures/Images
& Hybrid
11/8/2018

11. Working Group Wiki Page
11/8/2018

12. Working Group Wiki Page
11/8/2018

13. Working Group Wiki Page
11/8/2018

14. MBSE Capability: Construct Model
Dependencies on other MBSE Assessment Capabilities
Concept Model
Understanding the core and extended concept model is a key pre-requisite to both interactive and batch model construction
Includes transformation from tabular, structured text and natural language descriptions to model based representations
SE Use Cases
Consistent with use cases dependent on model construction
Lifecycle aspects of model construction (e.g. concept, architecture, design, implementation, integration, verification, validation phases)
MBSE Usability
Viewpoint/Views for model construction
Pattern: Model-View-Controller
Tabular: e.g. MS Excel as the model view with macro adapters to the system model
Graphical: e.g. MS Visio as the model view with templates and adapters to the system model
3-D Visualization: e.g. STK with adapters linking to the system model
Pattern Libraries: e.g. domain specific system model patterns for all views driven from a common library
Automation Techniques
OSLC, etc.
11/8/2018

15. System Model Construction Current State & Vision
Manual Entry
Rich GUI interface
Semi-Automated
Bulk tabular data input via plug in scripts
Structured document parsing
Requirements Documents “shall” statements
Design Documents
Tool to tool transfer/exchange
Third party support tools
Bridges/Gateways
File based/OSLC based
Repository transfer/exchange
Emerging Vision
Full automation
Sketch interpretation
Concept development support
Structured text interpretation
Based on standardized document templates
Drawing interpretation
Structured graphics
MS Powerpoint graphics
MS Visio graphics
Repository Exchange
Schema based transformation
Tool Exchange
Model Interchange (UML based)
Model Interchange (non UML)
11/8/2018