Enterprise Architect Model Checker

Enterprise Architect allows patterns that are invalid in UML. The Enterprise Architect Model Checker lists known patterns that are not handled by the current solution and may need refactor on input model for proper publishing to MagicDraw.

The option ea2md.check.input in the publisher.properties controls the execution of the Enterprise Architect Model Checker.

Enabling/disabling Enterprise Architect Model Checker property

Set to following option in publisher.properties file:

# Enable Enterprise Architect ModelChecker before transformation. Available values: True, False - default: True ea2md.check.input=True

Model Checking report

The report is available in the log file head generated after publishing
2024-09-12 04:26:39.204 info - PUBLISHING - 2 ModelChecker(s) in error. 2024-09-12 04:26:39.205 info - PUBLISHING - > ModelChecker CHECK002 Detect invalid Diagrams containing associations between Instance Specifications 2024-09-12 04:26:39.205 info - PUBLISHING - 1 Element(s) in error 2024-09-12 04:26:39.205 info - PUBLISHING - 0001... CommunicationDiagram EA_Model::CommunicationPackage::Communication between Components 2024-09-12 04:26:39.206 info - PUBLISHING - > ModelChecker CHECK001 Detect invalid Diagrams containing ports connected with Associations instead of Connectors 2024-09-12 04:26:39.206 info - PUBLISHING - 2 Element(s) in error 2024-09-12 04:26:39.207 info - PUBLISHING - 0001... DeploymentDiagram EA_Model::Deployment::Component deployment in target platform 2024-09-12 04:26:39.207 info - PUBLISHING - 0002... CompositeStructureDiagram EA_Model::Structure::Component Structure Diagram
Model Checker codes

List of Model Checker codes

Checker code Description

CHECK001 Detect invalid Diagrams containing ports connected with Associations instead of Connectors
In UML, Associations are drawn between Classifiers for describing that there can be links between instances typed to those Classifiers.
In general links between Ports are Connectors for describing a connection between them, or InformationFlows for a more abstract data flow relationship.

CHECK002 Detect invalid Diagrams containing associations between Instance Specifications
In UML, Associations are drawn between Classifiers for describing that there can be links between instances typed to those Classifiers.
An Instance Specification is not a Classifier.

CHECK003 Detect invalid DeploymentDiagrams drawing Activities
In UML, Activity content as ActivityEdges or ActivityNodes is not allowed in a DeploymentDiagram.

CHECK004 Detect invalid Diagrams containing Associations between Activity Nodes
In UML, an Association is not allowed between Activity Nodes in an Activity Diagram

CHECK005 Detect invalid Diagrams containing Decision Node having more than 2 incoming edges
In UML, a Decision Node can only have a maximum of 2 incoming edges. If this happens, MagicDraw can remove extra edges.

CHECK006 Detect invalid DeploymentDiagrams drawing Graph Nodes with no semantics
In UML, Graph Nodes without semantic elements are not allowed in Deployment Diagram.

CHECK007 Detect invalid ActivityDiagrams drawing Packages
In UML, Packages are not allowed in a ActivityDiagram.

CHECK008 Detect Interaction Overview Diagrams not yet handled by the current solution
Due to missing data in XMI produced by Enterprise Architect, this kind of Diagram is not published.

Checker code	Description
CHECK001	Detect invalid Diagrams containing ports connected with Associations instead of Connectors In UML, Associations are drawn between Classifiers for describing that there can be links between instances typed to those Classifiers. In general links between Ports are Connectors for describing a connection between them, or InformationFlows for a more abstract data flow relationship.
CHECK002	Detect invalid Diagrams containing associations between Instance Specifications In UML, Associations are drawn between Classifiers for describing that there can be links between instances typed to those Classifiers. An Instance Specification is not a Classifier.
CHECK003	Detect invalid DeploymentDiagrams drawing Activities In UML, Activity content as ActivityEdges or ActivityNodes is not allowed in a DeploymentDiagram.
CHECK004	Detect invalid Diagrams containing Associations between Activity Nodes In UML, an Association is not allowed between Activity Nodes in an Activity Diagram
CHECK005	Detect invalid Diagrams containing Decision Node having more than 2 incoming edges In UML, a Decision Node can only have a maximum of 2 incoming edges. If this happens, MagicDraw can remove extra edges.
CHECK006	Detect invalid DeploymentDiagrams drawing Graph Nodes with no semantics In UML, Graph Nodes without semantic elements are not allowed in Deployment Diagram.
CHECK007	Detect invalid ActivityDiagrams drawing Packages In UML, Packages are not allowed in a ActivityDiagram.
CHECK008	Detect Interaction Overview Diagrams not yet handled by the current solution Due to missing data in XMI produced by Enterprise Architect, this kind of Diagram is not published.