Using SysML in UPDM Projects

For those unaware, the Unified Profile for DoDAF and MODAF (UPDM) has two compliance levels, but only one – Level 1 (L1) – utilizes SysML. NAVAIR’s MBSE path forward relies heavily on SysML, so it would make the most sense to create your UPDM/DoDAF models using the L1 compliance level. This will allow you and your team to leverage the SysML language and align with NAVAIR’s MBSE methodology.

The following are the two compliance levels specified by UPDM:

• Level 0 (L0): Based on UML 2 and Partial SoaML Import: This is an implementation of UPDM using primarily UML2 with some SoaML Stereotypes (mostly for service modeling).

• Level 1 (L1): Based on UML2 with Full SysML Support: This implementation includes everything in Level 0 along with the SysML profile and subprofiles and allows for seamless progression into pure SysML modeling.

The diagram below, from the OMG website, illustrates the scope of the two levels and their use of SoaML, UML2 and SysML:

On the surface, there’s very little difference when creating basic DoDAF models with either compliance level. However, once you start looking under the hood (especially in element and diagram properties), you’ll notice that most of the objects you create when using the L1 compliance mode are built upon SysML stereotypes.

For example, when you create a Capability in a L0 project, the element is nothing more than a UML Class with a UPDM Capability stereotype applied. In a L1 project, that Capability will still be a UML Class but will also have the SysML Block stereotype (a SysML Block is built on a UML Class). This allows the L1 Capabilities to be treated just like any other block in a SysML model in that it can have the standard elements, such as part properties, value properties and constraints.

This applies to diagrams as well. An L0 CV-2 diagram is treated as a UML Class Diagram, so the diagram toolbar has Class Diagram palettes along with the UPDM palettes. A L1 CV-2 diagram is a SysML Block Definition Diagram (BDD) and, therefore, will have the same palettes found on a normal BDD (assuming you have that option selected, which we will discuss in a moment).

Now, you must select two options when first creating a UPDM project that will allow you to use L1 compliance to its fullest. These options, which must be set to true, can be seen in the New Project dialog box below:

• SysML compliance model (UPDM L1 compliance level): This option is self-explanatory and will make your new project use UPDM L1 by loading all the L0 profiles along with the L1 profile and the SysML profiles.

• System Engineer User Interface Model: This option, which you can see in the help text is recommended when using the first option, brings all the normal SysML palettes to the diagram toolbars. This is particularly useful when combining UPDM with more traditional SysML features.

That’s it! Once you select those two options and click OK, your new UPDM project will be using the L1 compliance mode along with the additional SysML palettes.

If you have any questions, comments, or ideas for additional blog posts, please reply below!

Tools Used: Cameo Enterprise Architect v18.5 or Cameo System Modeler v18.5 (w/ UPDM2 Plugin)

Level: Beginner