mbse-tools

name	mbse-tools
description	Model-Based Systems Engineering (MBSE) tools — SysML language (blocks, activity, sequence, requirements diagrams), Cameo/MagicDraw, Rhapsody, Enterprise Architect, model verification, requirement traceability, INCOSE SE handbook, NASA MBSE initiatives, V-model integration, digital twin connection, DoDAF/MODAF architecture frameworks.
metadata	{"priority":7,"promptSignals":{"phrases":["MBSE","model based systems engineering","SysML","Cameo systems","systems engineering model","requirements traceability MBSE"],"minScore":3}}

Model-Based Systems Engineering (MBSE) — Complete Skill

MBSE Fundamentals

Definition and Value

MBSE (INCOSE definition): the formalized application of modeling to support system requirements, design, analysis, verification, and validation activities beginning in the conceptual design phase and continuing throughout development and later life cycle phases

Traditional document-centric SE problems: Requirements in Word documents → inconsistencies when documents diverge; no automatic traceability Design in PowerPoint/Excel → no formal connection to requirements Changes not propagated → design-requirement gaps MBSE solution: single model → automatic consistency; traceability across artifacts; change propagation

MBSE advantages: Automatic requirement-to-design traceability (no manual matrices) Simulation and analysis directly from model Reduced integration errors (30–50% error reduction in complex systems per NASA study) Reuse across product lines (model library) Digital thread foundation (connects to PLM, simulation, manufacturing)

SysML Language

SysML Overview

SysML (Systems Modeling Language): UML 2 profile for SE; standardized by OMG; ISO/IEC 19514:2017 Diagram types: 9 total; 4 structural, 4 behavioral, 1 requirement

Structural Diagrams

Block Definition Diagram (BDD): Defines blocks (system elements), their properties, and relationships (generalizations, associations, compositions) Block = system element (hardware, software, function, subsystem) Property = attribute (mass, temperature, voltage), part (subblock), reference, value

block Engine {
  values:
    mass: Real;
    maxPower: Real;
  parts:
    cylinder[4]: Cylinder;
    crankshaft[1]: Crankshaft;
}

Internal Block Diagram (IBD): Shows internal structure of a block; how parts connect via ports and connectors Flow ports: conveying items (material, energy, signals) Full ports: complex interactions; proxy ports = abstract interface Connectors: represent physical connections (pipe, wire, data link)

Package Diagram: organizes model elements into namespaces/packages

Parametric Diagram: constraint blocks with equations; analysis and simulation integration Links SysML blocks to analysis parameters → enables performance prediction

Behavioral Diagrams

Activity Diagram: Models behavior as flow of actions; tokens represent items flowing through process Action = computational step; Control flow = sequencing; Object flow = data/material flow Uses: process modeling, operational scenarios, function allocation

Sequence Diagram: Interaction between system elements over time; messages exchanged; lifelines = elements Uses: interface definition; protocol specification; verification of communication

State Machine Diagram: Finite state machines; states, transitions, events, guards, actions Critical for embedded software; control system modes; operational modes of complex systems

Use Case Diagram: System boundary, actors (external entities), use cases (system functions) Context definition; stakeholder needs capture

Requirement Diagram

SysML Requirement:

requirement "High Level Requirement 001" {
  id = "SYS-001"
  text = "The system shall achieve 95% availability"
}

Relationships: refine: requirement → design element that realizes it verify: verification case → requirement being verified satisfy: block → requirement being satisfied derive: lower-level from higher-level requirement (derivation trace)

MBSE Tools

Cameo Systems Modeler (formerly MagicDraw — Dassault)

Industry standard for defense/aerospace MBSE: Full SysML + UML support; plugin architecture (Cameo Safety Analyzer, Cameo Requirements+) DOORS/DOORS NG integration: bidirectional requirement synchronization Excel round-trip: import/export for non-modelers

Key features: Model validation: well-formedness rules; profile constraints Report generation: Docx/Excel/HTML from model template Simulation: Cameo Simulation Toolkit for state machine execution; animation

Pricing: ~$10,000–$20,000/seat (enterprise license); NASA, Lockheed, Boeing, Airbus primary users

IBM Rhapsody

Specialized for: real-time embedded systems + SysML Strong: automatic code generation (C, C++, Java) from state machines and activity diagrams Round-trip: model ↔ code synchronization Integrates: Rational DOORS requirements management

Enterprise Architect (Sparx Systems)

Lower cost: ~$1,000/seat (< Cameo); fully featured SysML Strong for: smaller organizations; agile teams Limitation: some advanced SysML features less mature than Cameo Plugin ecosystem: Simulation, code generation, document generation

Capella (Eclipse-based, open source)

Open source: free; actively developed; Airbus subsidiary (Obeo) Own modeling language: Arcadia/Capella (not SysML but similar); layer-based system architecture Good for: operational analysis → system analysis → logical → physical layers Learning curve: moderate; supported by Polarsys

Requirement Management

DOORS Integration (IBM DOORS / DOORS Next)

Bidirectional synchronization: Requirement in DOORS → created as SysML requirement in Cameo (via integration adapter) SysML model changes → reflected in DOORS Traceability matrix: automatically generated from «satisfy», «refine», «verify» relationships

DOORS hierarchy: Stakeholder requirements (SHTD) → System requirements (SRD) → Software/Hardware requirements (SRS/HRS) Each level in DOORS links to SysML model elements at appropriate abstraction

Verification status tracking: Each requirement has: verification method (test/analysis/inspection/demonstration), verification status, responsible engineer MBSE model enables real-time coverage analysis → "how many requirements lack verification?"

Requirement Quality (INCOSE Guide for Writing Requirements)

SMART requirements: Specific: unambiguous; one interpretation only Measurable: quantifiable criteria; shall achieve X within Y under condition Z Achievable: technically feasible; stakeholder validated Relevant: traces to stakeholder need Testable: verification method defined; acceptance criteria clear

Common requirement defects: Ambiguity: "adequate" "sufficient" "appropriate" → not testable Multiple requirements in one (and/but): separate into two requirements Implementation specified (how vs. what): shall use specific algorithm → constrained to design; specify performance instead

V-Model Integration

V-Model and MBSE

Left side (decomposition): Stakeholder needs → System requirements → Subsystem requirements → Component specifications → Design Each level: MBSE model captures requirements, architecture, interfaces

Right side (integration and verification): Component test → Subsystem test → System test → System acceptance Each level: SysML verification cases link to left-side requirements

Traceability chain: Stakeholder Need #1 → System Requirement SYS-001 → Subsystem Requirement SUB-001 → Component spec COMP-001 → Component test T-COMP-001 → Subsystem test T-SUB-001 → System test T-SYS-001

MBSE enables: automatic coverage check (every requirement covered by at least one test); impact analysis (change propagation); completeness report

Architecture Frameworks

DoDAF (Department of Defense Architecture Framework)

Six viewpoints:

• AV: All-views (overview, dictionary)
• OV: Operational viewpoint (operational context, activities, information flows)
• SV: Systems viewpoint (system interfaces, system data flows)
• DIV: Data & Information viewpoint
• TV: Technical Standards viewpoint (standards constraints)
• CV: Capability viewpoint

SysML to DoDAF mapping: Use Case → OV-5a (Operational Activity Decomposition) Block Definition → SV-1 (System Interface Description) Activity → SV-4 (Systems Functionality Description)

MODAF/NAF (UK MOD / NATO Architecture Framework)

Similar to DoDAF; adapted for UK and NATO standards; increasing SysML integration

MBSE and Digital Twin

Digital twin connection: MBSE model → functional requirements and architecture Digital twin: simulation model + real-time data from physical asset Model parameters from MBSE (mass, power, thermal) → instantiated in simulation → updated by sensor data Tools: Ansys Systems of Systems, Dassault CATIA/DELMIA + Cameo integration; PTC ThingWorx

NASA MBSE Initiatives

NASA SE Handbook (SP-2016-6105): incorporates MBSE throughout SE process MBSE Infusion: Dragon capsule, SLS (Space Launch System), James Webb Space Telescope → all used MBSE for requirements and design Lessons learned: early investment in model framework → 15% schedule reduction (NASA MBSE pilot study) JPL Insight mission: full MBSE from inception; design-to-operations model continuity

Standards

Standard	Scope
ISO/IEC 19514:2017	SysML language specification
INCOSE SE Handbook v4	Systems engineering process guide
ISO/IEC/IEEE 15288	Systems life cycle processes
OMG SysML 1.6	Formal SysML specification
MIL-STD-499C (draft)	Systems engineering for defense
DoDAF 2.02	DoD architecture framework
NASA SP-2016-6105	NASA systems engineering handbook

Output

Provide: project type (aerospace/defense/automotive/industrial), MBSE scope (concept/preliminary/detailed design), tool selected (Cameo/Rhapsody/Enterprise Architect/Capella) with justification, SysML diagram types used (BDD/IBD/Activity/Sequence/State Machine/Requirement/Parametric), requirement management approach (DOORS integration, traceability relationships: satisfy/verify/refine), architecture framework (DoDAF/MODAF/NAF; viewpoints covered), number of system requirements and traceability coverage [%], V-model verification linkage (test coverage [%]), simulation integration (parametric diagram → analysis tool), digital twin connection (if applicable), model governance (version control: GIT/Subversion; configuration management), and applicable standard (ISO/IEC 19514, INCOSE SE Handbook, MIL-STD-499C).