Skip to main content

Eclipse Capella

Eclipse Capella is an open-source model-based systems engineering (MBSE) workbench (systems engineering / modeling) that supports the entire systems, software and hardware architecture design lifecycle through graphical, model-driven methods.

  • MBSE workbench for systems, software, and hardware architecture modeling (systems engineering / modeling).
  • Implements the Arcadia systems engineering method with dedicated viewpoints and diagrams (engineering methodology support).
  • Provides a graphical modeling environment on top of the Eclipse platform (developer tooling / Immutable Deployment Environment (IDE) extension).
  • Supports model refinement from operational analysis through logical and physical architecture (architecture design and analysis).
  • Extensible through add-ons and integrations for domain-specific needs and collaboration (toolchain integration / extensibility).

More About Eclipse Capella

Eclipse Capella is an open-source model-based systems engineering (MBSE) workbench (systems engineering / modeling) hosted by the Eclipse Foundation and built on the Eclipse platform. It targets the engineering of complex systems that combine software, hardware, and operational procedures, using models as the primary artifact across the lifecycle. Capella is designed to support teams that need a structured method to capture stakeholder needs, define system functions, and derive logical and physical architectures with consistency and traceability.

The workbench implements the Arcadia method (engineering methodology support), a model-based engineering approach for systems, software, and hardware architecture. Arcadia defines a sequence of engineering phases and viewpoints, and Capella provides tooling aligned with this structure. Users can work through operational analysis, system analysis, logical architecture, physical architecture, and, when applicable, software architecture, each supported by dedicated diagrams and modeling constructs. This method-tool pairing gives engineering teams a consistent workflow from initial need capture to detailed architecture design.

Capella provides a graphical modeling environment (modeling tooling) that runs on the Eclipse platform (developer tooling / IDE extension). It offers diagram editors for functions, components, interfaces, scenarios, and states, as well as data modeling capabilities. The tool manages semantic links between model elements so that changes in one view are propagated across related diagrams. This supports impact analysis, consistency checking, and documentation generation based on the model. Traceability between levels of abstraction is maintained, from operational needs down to system and component design.

In enterprise and institutional environments, Eclipse Capella is used as part of systems engineering toolchains (engineering lifecycle management). Typical uses include specifying system requirements in a structured model, defining system and subsystem architectures, analyzing interfaces and exchanges, and preparing input for downstream implementation or verification tools. Organizations employ Capella to document architecture decisions, coordinate work across engineering disciplines, and communicate system designs to stakeholders in a standardized, model-based format.

The project supports extensibility through add-ons and viewpoints (extensibility / ecosystem). The Capella ecosystem includes mechanisms to customize the metamodel, introduce domain-specific viewpoints, and integrate with other engineering tools for requirements management, configuration management, or simulation. Because it is based on the Eclipse platform, Capella can leverage existing Eclipse technologies for modeling, team collaboration, and version control integration.

From a categorization perspective, Eclipse Capella fits into MBSE and systems architecture design tools (systems engineering / architecture modeling). It is relevant for organizations that need a structured, method-based approach to designing complex systems, where consistency across operational, functional, logical, and physical views is required, and where model artifacts serve as central references throughout the engineering lifecycle.