Applied MBSE (APPEL-MBSE2)

PARTICIPANT TESTIMONIALS

  • Systems Engineering & Engineering
    Systems Engineering & Engineering

This 2-day course provides a broad overview of the processes, practices, tools and techniques that comprise the emerging discipline of model-based systems engineering (MBSE), with a greater focus on application for the user and practitioner. The course begins with a review of the systems engineering framework and protocols that establish the context for MBSE practice. We then examine the evolution of MBSE from paper to software and briefly review the concept and usages of modeling languages (UML, SYSML, LML, etc.) and tools. The course focuses on the key value propositions MBSE offers-Capturing, Connecting, Controlling, Communicating, Collaborating and Cycling-with specific examples, lessons learned from applications in NASA and commercial projects. Application of MBSE to develop and deliver artifacts in support of all 17 processes that comprise the NASA Systems Engineering "engine" across the program/project lifecycle are examined in detail. The course includes a series of hands-on exercises to explore MBSE tool use and application in a practical project context.

This course that begins with a broad overview and then takes practitioners' understanding farther by focusing on the application of MBSE. It can be delivered as a stand-alone course or as part of a modular, concurrently delivered three-day series featuring all three MBSE courses.

This course is intended for practicing systems engineers, payload principal investigators, subsystem engineers or project managers involved in any phase of the space mission life cycle who are curious about application of MBSE to their projects and are seeking both a basic foundation in the subject as well as an appreciation of for practical applications in their own programs/projects. Some basic understanding of systems engineering principles and processes is assumed.

Systems Engineering Competencies
  • SE 1.1 Stakeholder Expectation Definition & Management
  • SE 1.2 Technical Requirements Definition
  • SE 1.3 Logical Decomposition
  • SE 1.4 Design Solution Definition
  • SE 2.1 Product Implementation
  • SE 2.2 Product Integration
  • SE 2.3 Product Verification
  • SE 2.4 Product Validation
  • SE 3.1 Technical Planning
  • SE 3.2 Requirements Management
  • SE 3.3 Interface Management
  • SE 3.5 Configuration Management
  • SE 3.6 Technical Data Management

Click here to view full competency model.

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)
  • Generalize the organization (schema) used by MBSE tools
  • Discuss the value proposition for MBSE within the project context
  • Summarize specific examples, usage extent and lessons learned from MBSE application to NASA and other programs
  • 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.
  • 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
  • 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

Share With Your Colleagues