One might think of Model-Based Systems Engineering (MBSE) as the toast and Systems Modeling Language (SysML) as the butter. The two complimenting entities are receiving a lot of attention in the systems engineering world, and for good reason.
MBSE is an innovative approach to overcome traditional, error-prone, document-based product development. The advantages of using formal models to specify a complex technical system are many including fewer inconsistencies, less redundancies, clearer communications among all stakeholders and sustainable documentation.
SysML is an enabling technology for MBSE. It’s a very visual modeling language that relies on diagrams to render the MBSE approach meaningful. Overall there are nine types of diagrams:
- Block definition diagram
- Internal block diagram
- Package diagram
- Use case diagram
- Requirement Diagram
- Activity diagram
- Sequence diagram
- State machine diagram
- Parametric diagram
These graphical constructs represent text based requirements that relate to other model elements. For example, the requirements diagram captures requirements hierarchies and requirements derivation, and the satisfy and verify relationships allow a modeler to relate a requirement to a model element that satisfies or verifies the requirements. The requirement diagram provides a bridge between the typical requirements management tools and the system models.
The parametric diagram represents constraints on system property values such as performance, reliability and mass properties, and serves as a means to integrate the specification and design models with engineering analysis models.
The state machine diagram (also called statechart diagrams) represent the behavior of entities capable of dynamic behavior by specifying its response to the receipt of event instances. Typically, the state machine diagrams describe the behavior of classes, but the statecharts can also describe the behavior of other model entities such as use cases, actors, subsystems, operations or methods.
An internal block diagram captures the internal structure of a block in terms of properties and connections among properties. A block includes properties so that its values, parts, and references to other blocks can be specified. However, whereas an internal block diagram created for a block (as an inner element) will only display the inner elements of a classifier (parts, ports and connectors), an internal block diagram created for a package will display additional elements (shapes, notes and comments).
All properties and connectors that appear inside an internal block diagram belong to (are owned by) a block whose name is written in the diagram heading. That particular block is the context of the diagram. SysML allows any property (part) to be shown in an internal block diagram to display compartments within the property (or part) symbol.
Tonex offers a 3-day SysML Training course delivered in the form of interactive presentation. Course covers the concepts, requirements, tools, and techniques of Systems Modeling Language (SysML). SysML Training Crash Course teaches you how to effectively collect requirements to design the embedded software based on the system specifications using UML 2 and SysML.
This training course is of particular interest to students because the class is worth 24 college credits.
There are also many more SysML Training related courses designed for students, systems engineers, system modelers, system architects, software engineers, system integrators, analysts and designers, product developers, project leaders and project heads.
Since 1993 Tonex has made available reasonably priced classes taught by the best trainers is the reason all kinds of organizations from Fortune 500 companies to government’s most important agencies return for updates in courses and hands-on workshops.
Contact us for more information, questions, comments.