Digital Engineering Validation Tool

Release Notes

SAIC Digital Engineering Validation Tool Release Notes

Original Release Date: January 10, 2020

SAIC welcomes any and all comments about the rules, customizations or methods. Please contact us at DigitalEngineering@saic.com.

Version 2.6 includes:

  • 236 rules
  • Updated style guides and optional profiles
  • Updated Rhapsody rules
  • A new optional profile: SW4SysML, intended to support software development

Version 2.5 includes:

  • 224 rules
  • Native support for Cameo 2021x (and final release for 19.0)
  • Enhanced support for IBM’s Rhapsody modeling tool
  • An example UAF enterprise model based on the Ranger lunar probe
  • An example UAF-to-SysML federation mode (also based on Ranger)
  • Revised classification profile (incorporating feedback to be based upon inheritance and usage and not on composition).

Version 2.0 is a major release of SAIC’s Digital Engineering Validation Tool. It adds customizations and rules to support the federation of multiple system models into a system-of-systems model. This enables automated validation of interfaces and flows between the system models and includes a method for federating non-compliant models. V2.0 includes:

  • 221 rules
  • A federated model example (including 2 compliant and one non-compliant model)
  • A federation model template
  • Four videos related to the federation approach (over an hour of new content)
  • One video discussing how to plan model content

Version 1.9. v1.9 of SAIC's Digital Engineering Validation Tool adds model federation rules and a video tutorial for the included model template.

This release includes:

  • 201 Validation Rules (both language and style) for MagicDraw and Cameo Enterprise Architecture
  • A Rhapsody version of the Ranger example model
  • Video documentation for cloning the included model template, a demonstration of the Rhapsody Ranger model and using context patterns in Rhapsody

The SAIC validation rules were recently featured in a presentation at the 2022 American Institute of Aeronautics and Astronautics SciTech Forum. "A Mars Octet: Lessons Learned from Federating Eight Student Models in a SysML Class" illustrates how our validation rules support the creation of a coherent system-of-systems model by distributed teams. The paper, presentation and example models are available at the following links:

 

Version 1.85. v1.85 of SAIC's Digital Engineering Validation Tool revises markings and adds CUI.

This minor release includes:

  • 194 Validation Rules (both language and style) for MagicDraw and Cameo Enterprise Architecture
  • Revised ITAR markings (EAR99) for the MagicDraw and Rhapsody content
  • Controlled unclassified information (CUI) added to Classification Profile
  • Video documentation for updating the rules on a TeamWork Cloud server

 

Version 1.8. The v1.8 release of SAIC's Digital Engineering Validation Tool includes a modeling process 1-pager and beta UPDM rules.

The release contains:

  • 192 Validation Rules (both language and style) for MagicDraw and Cameo Enterprise Architecture
  • Updated Rhapsody rules
  • A 1-page modeling process activity diagram
  • Beta rules for UPDM models

The v1.8 release includes 21 new or modified rules; 183 of the rules are also available in Rhapsody. New to this release is a beta release of rules to support modeling in UPDM.

We have also include a 1-page modeling process activity diagram that provides an overview of the steps necessary to construct a model in compliance with our style guide and validation rules.

The Ranger sample model has been refreshed and complies with rules added since its initial release; the model also includes a set of “port helper tables” that simplify the process of resolving validation errors at system boundaries.

Finally, a model template is also included that contains a recommended folder structure and a set of useful tables and matrices.

 

Version 1.7. The v1.7 release of SAIC’s Digital Engineering Validation Tool adds methods to develop Failure Modes and Effects Analyses.

The release contains:

  • SAIC DE Profile (Validation Rules and Customizations)
    • 184 Validation Rules (both language and style) for Dassault Systemes/No Magic's MagicDraw and Cameo Enterprise Architecture, including 20 new/modified rules
    • 123 of the rules are also available for IBM Rational Rhapsody, including 38 new/modified rules
    • Customizations (including methods to connect deeply-nested ports, manage classification and data rights, and conduct failure analysis)
  • Model-Based Style Guide
  • Example Model (based upon the Ranger lunar probes)
  • Explanatory videos

New to the Version 1.7 release is an initial version of a profile that enables model-based failure analysis. This profile, initially presented at the 2020 National Defense Industrial Association’s Systems and Mission Engineering Conference (see Using SysML State Machines to Automatically Conduct Failure Modes and Effects Analysis), leverages the full behavioral and structural integration made possible by the SAIC modeling style and validation rules to maximize the rigor and minimize the effort required for failure analysis.

The SAIC Digital Engineering Validation Tools will be featured in the MBSE Lightning Round at the 2021 INCOSE International Workshop (see Treadstone + 1: The First Anniversary of the SAIC Digital Engineering Validation Tool). This presentation will discuss the use of the profile, its growth over the past year, and its use in training modelers.

 

Version 1.6. The v1.6 release of SAIC’s Digital Engineering Validation Tool adds methods to manage Data Rights and Classification.

The release contains:

  • SAIC DE Profile (Validation Rules and Customizations)
    • 168 Validation Rules (both language and style) for Dassault Systemes/No Magic's MagicDraw and Cameo Enterprise Architecture, including 19 new/modified rules
    • 112 of the rules are also available for IBM Rational Rhapsody, including 52 new/modified rules
    • Customizations (including methods to connect deeply-nested ports)
  • Model-Based Style Guide (with detailed examples and rationale)
  • Example Model (based upon the Ranger lunar probes)
  • Explanatory videos

 

Version 1.5. The v1.5 release of SAIC’s Digital Engineering Validation Tool includes:

  • SAIC DE Profile (Validation Rules and Customizations) (MagicDraw/Cameo format and initial release of Rhapsody version)
  • Style Guide (with detailed examples and rationale)
  • Example Model (based upon the Ranger lunar probes)
  • Explanatory videos

 

Version 1.0. The SAIC Solutions and Technology Group is providing this SysML profile (in MagicDraw format) as a courtesy to the worldwide systems modeling and engineering community. It is our hope that it will improve model quality, demonstrate state-of-the-art validation techniques, and stimulate discussion about best practices.

Please see the model itself for licensing terms. Note that example models, explanatory videos, and other relevant content will be provided as this effort continues.

Digital Engineering: https://www.saic.com/digital-engineering

Contact Us: DigitalEngineering@saic.com

Assumptions:

  • General Disclaimer: We do NOT claim that someone not fully conformant to our rules is “doing SysML wrong.” They represent an attempt to guide model development where multiple choices are available to ensure that a team of modelers always makes the SAME choice. This creates model consistency that is essential for leveraging the power and efficiency of tools used to analyze the technical content in the model and validate its internal integrity.
  • Cameo Enterprise Architecture (MagicDraw) and SysML are the focus of this initial effort. Do NOT use UPDM/UAF profiles with this model
  • No validation rules are based on the model package’s structure (although we do recommend a structure in an example model that will be released in 2020)

Goals:

  • Maximize the effectiveness of the modeling effort by enabling large teams to build models with consistent style and internal integrity
  • Maximize the efficiency of the modeling effort by minimizing the number of elements and relationships needed to rigorously describe the system (get the most value out of the fewest “clicks”)
  • Rely on data rather than diagrams (although building many diagrams may be part of creating the data)
  • Allow redefinition and traceability between architectures (behavioral, logical, physical)
  • Accommodate the use of non-textual requirements (i.e. making model elements contractual)
  • Accommodate reasonable program variation
  • Leverage automation whenever possible to ensure style guide compliance and increase model integrity

Other:

  • This profile and associated validation rules have been tested against a number of models (both public and proprietary) to ensure that they function as intended. If you detect false positives or false negatives in your use of the model, please relay that information to us so that we may correct the validation logic.
  • Any and all comments (including feedback on their usefulness or suggestions for additional rules) are welcome.