Model Based Systems Engineering Design and Analysis (APPEL-vMBSE3)

Upon completion of this course, participants will be able to:

• Describe the organization and major processes that comprise the NASA Systems Engineering (SE) "engine"
• Define Model-Based Systems Engineering (MBSE) as a practice and discipline
• Identify various MBSE tools in current use around the industry
• Define the purpose of modeling languages
• Recognize and name SysML as well as other commonly used systems engineering diagrams and artifacts
• Explain the systems engineering framework that comprises the NASA Systems Engineering "engine" and how we use it to develop technical baselines throughout the lifecycle
• Discuss and give examples for the application of MBSE across the lifecycle, from goals, objectives and ConOps through verification planning
• Explain the uses for each SysML diagrams as well as diagrams used by other languages and modeling approaches (i.e. LML, DoDAF, IDEF)
• Compare and contrast the different modeling languages and explain their application
• Generalize the organization (schema) used by MBSE tools
• List model-based systems engineering (MBSE) tools, contrast them with model-based engineering tools, and explain how they can be used to capture, connect, communicate, collaborate, control and cycle the systems engineering effort
• Discuss the value proposition for MBSE within the project context
• List model-based systems engineering (MBSE) tools, contrast them with model-based engineering tools, and explain how they can be used to capture, connect, communicate, collaborate, control and cycle the systems engineering effort
• Summarize specific examples, usage extent and lessons learned from MBSE application to NASA and other programs
• Demonstrate an understanding of basic SysML syntax
• Simulate system behavior given a fully populated model
• Use an MBSE tool to build simple system model elements given existing system descriptions and artifacts.
• Given a fully-populated system model, produce typical project documents and artifact
• Demonstrate how multiple models can be managed as part of lifecycle technical data requirements
• Employ an existing model for re-use on a new system or application
• Demonstrate an understanding of basic SysML syntax
• Given an MBSE model and/or artifacts from model, infer details about the system's behavior as well as potential issues (i.e. gaps, overlaps, missing traceability, etc.)
• Point out omissions and other issues with a project by examining a full-populated system model and/or model-generated artifacts
• Examine the effects on system design and behavior by tracing changes (causes) through a given system model and/or model-generated artifacts
• Interpret typical systems engineering artifacts (i.e. requirements documents, functional flow diagrams) to determine system architecture and other information
• Combine multiple, diverse models into a single integrated model
• Modify a fully-populated system model to fix known problems or omissions
• Develop key systems engineering diagrams and other artifacts to communicate requirements validation, system context, functional behavior, physical architecture, interfaces, risks and other information
• For a given simple system that is already defined (requirements, functional architecture, physical architecture), develop a complete system model to include all basic SYSML diagrams as well as other typical artifacts (i.e. documents)
• Simulated model-based Design Review: Given a fully-populated system model, and/or model-generated artifacts representing baseline entrance criteria (i.e. MCR), assess the state of the project against baseline success criteria and recommend acceptance or changes