Book a Demo
Prev Next

Model Validation

Model validation banner

You use Model Validation to check UML models against known UML rules. The set of rules to validate against can be customized by enabling and disabling certain rules and rule categories. You can run Model Validation against a single UML element, a diagram or an entire Package. You can add to the system-provided validation rules by using an Add-In or an MDG Technology (such as BPMN) that contains its own rules. Model based add-ins are an effective tool for creating new and specific rules sets that implement custom rules specifically related to a single project, client or domain.



Design > Package > Manage > Validate > Validate Current Package

Validation Concepts



See also

Validating Objects

Validating a UML:

  • Element validates the element and its children, its features (attributes and operations) and its relationships (connectors)
  • Diagram validates the diagram itself (for correctness) as well as any elements and connectors within the diagram
  • Package validates the Package and all sub-Packages, elements, connectors and diagrams within it

Example - Model Violation

This UML diagram contains several basic violations of the UML rules:

An example UML diagram for demonstrating model validation functionality in Sparx Systems Enterprise Architect.

If you run Model Validation on this diagram, these violations are identified in the System Output window:

  • A UML ExpansionRegion (ExpansionRegion1) is missing its child input ExpansionNode
  • An invalid self-generalization exists on Class2 (UML elements cannot be self-generalized)
  • An OCL violation exists for the anonymous Association (between Class2 and Object1)
  • A UML ExceptionHandler (ExceptionHandler1) is missing its child input ObjectNode

Learn more