Before booking model-based systems engineering training, establish whether you need an engineering method, a modeling language, software skills or a combination. These capabilities work together, but a course that teaches one does not necessarily teach the others.
Consider a team preparing to model a subsystem change. One person needs to decide which dependencies matter, another needs to represent them correctly, and a reviewer needs to judge whether the resulting information supports a decision. A shared training budget does not make those learning needs identical.
What is the difference between method, language and tool?
The method organizes the engineering work: the questions to ask, information to develop and decisions to support. The language provides concepts and rules for expressing that information. The tool is the software used to create, maintain and work with the model. When comparing proposals, ask providers to identify each layer explicitly.
A language course may teach relationships and notation without a complete architecture workflow. A software course may teach editing and collaboration to people who already understand the engineering. Both can be appropriate purchases when their scope matches the job.
What does this look like with Arcadia and Capella?
Arcadia is a systems and architecture engineering method supported by the Capella modeling tool. Capella provides a domain-specific modeling environment; it should not be treated as another name for the Systems Modeling Language (SysML). The Eclipse Foundation’s explanation of Capella and the Systems Modeling Language describes both the relationship and the distinction.
For a Capella course, ask whether participants will learn the Arcadia engineering progression, the meaning of the model elements and the software operations needed to implement their work. A course covering all three should show how they connect in an exercise.
Which language version will the course teach?
The Object Management Group announced final adoption approval for Systems Modeling Language version 2.0 in July 2025. Its official specification page distinguishes the version 1 and version 2 specifications. A proposal that simply says “language training” leaves an important question unanswered.
Confirm the version, software implementation, available features and any migration content against your project’s environment. A version 2 course can be a good strategic choice, while a team maintaining an existing version 1 model may need a different immediate learning path.
How much depth does each role need?
Use these questions to discuss course scope with a provider. Henderson, McDermott and Salado (2024) describe role-specific training within organizational adoption.
| Role | Capability to test in the proposal |
|---|---|
| Model author | Create meaningful model information and maintain it in the intended software. |
| Architect | Connect stakeholder needs, architecture choices and supporting evidence. |
| Reviewer | Interpret relationships, challenge assumptions and trace the evidence behind a claim. |
| Manager | Understand the decisions the model supports and the limits of its evidence. |
Some reviewers will need substantial software skills to investigate a model independently. Some managers will author models themselves. Let actual responsibilities determine depth. Akundi and Ankobiah (2024) examine alignment between workforce needs and curricula; applying that research here means checking course content against the work your people perform.
How can a change-impact exercise help you compare courses?
Here is a hypothetical purchasing test. A subsystem’s power demand increases. Ask whether the exercise lets learners identify affected interfaces, explain relevant assumptions and trace the consequences to requirements and verification activities. Request a sample output or an instructor demonstration of the workflow.
A diagram alone is insufficient evidence of that capability. Descriptive relationships and quantitative analysis answer different questions; if the provider promises analytical conclusions, ask which calculations and assumptions produce them. Wach et al. (2025) review mathematical foundations, while Henderson and Salado (2021) and Campo et al. (2023) examine evidence for broader model-based benefits. None establishes a guaranteed return from a particular course.
Recent case: modeling across lunar engineering tasks
Jaden Cavender of Tietronix presented to the Gateway Digital Architecture Working Group on 27 February 2025. His presentation, Turbocharging Systems Engineering: Speeding Up ConOps, Requirements and Simulation Through Systems Modeling, is recorded in the NASA Technical Reports Server as document 20250002036. It connects concepts of operations, requirements and simulation in lunar interoperability work. That is a useful example of the connected tasks a course can teach; it is not an evaluation of training effectiveness. Read the NASA presentation record and source material.
Give every shortlisted provider the same brief
Write your capability gap in one sentence, then compare model-based systems engineering courses. Send shortlisted providers the same role, software version and engineering task. Their answers will make the proposals more comparable than their course titles.
Academic references
- Akundi, A. and Ankobiah, W. (2024) ‘Mapping industry workforce needs to academic curricula – A workforce development effort in model-based systems engineering’, Systems Engineering, 27(4), pp. 685–698. https://doi.org/10.1002/sys.21745.
- Campo, K.X., Teper, T., Eaton, C.E., Shipman, A.M., Bhatia, G. and Mesmer, B. (2023) ‘Model-based systems engineering: Evaluating perceived value, metrics, and evidence through literature’, Systems Engineering, 26(1), pp. 104–129. https://doi.org/10.1002/sys.21644.
- Henderson, K., McDermott, T. and Salado, A. (2024) ‘MBSE adoption experiences in organizations: Lessons learned’, Systems Engineering, 27(1), pp. 214–239. https://doi.org/10.1002/sys.21717.
- Henderson, K. and Salado, A. (2021) ‘Value and benefits of model-based systems engineering (MBSE): Evidence from the literature’, Systems Engineering, 24(1), pp. 51–66. https://doi.org/10.1002/sys.21566.
- Wach, P., Topcu, T.G., Jung, S., Sandman, B., Kulkarni, A.U. and Salado, A. (2025) ‘A systematic literature review on the mathematical underpinning of model-based systems engineering’, Systems Engineering, 28(1), pp. 134–153. https://doi.org/10.1002/sys.21781.