Analyzing UML models with static analysis tools

You can use static analysis tools to analyze UML models. For example, you can review UML models to detect errors so that you can correct them. You can collect information on UML models to determine whether your model follows best practices. You can also define new custom metrics and rules by using templates.

• Reviewing UML models
  You can run a UML Model Review analysis configuration on a UML model to detect 15 different types of problems in the model. For example, you can check your model for broken semantic relationships, missing specifications, or correct Java™ naming conventions. UML review rules are grouped into five categories: completeness, correctness, Java naming, style, and traceability.
• Collecting metrics on UML models
  You can run a UML Metrics analysis configuration on a UML model to collect 19 different types of information about the model. For example, you can discover the number of diagrams, the number of classes in a package, or the depth of a classifier in its inheritance hierarchy. UML metrics are grouped into four categories: coupling, diagrams, inheritance, and size. Metrics that express the number of occurrences for each namespace are summed and all other metrics are averaged. For each metric, you can optionally configure the severity, lower bound, and upper bound. Metrics that are out of the range of the lower and upper bounds are reported as problems and are displayed in red. To inspect metrics results, you expand the result tree starting at the root and read the results from the bottom up.
• Defining custom metrics and rules for UML models by using templates
  You can create custom UML metrics to collect on a UML model in addition to the 19 metrics that are available by default. You can also create custom UML review rules to supplement the 15 rules that are available by default. Two templates are available for creating custom UML metrics. Four templates are available for creating custom UML review rules. You can add custom rules and metrics to existing analysis configurations or to new analysis configurations.
• Static analysis metrics for analyzing UML model
  You can collect 19 different types of information about a UML model. For example, you can discover the number of diagrams, the number of classes in a package, or the depth of a classifier in its inheritance hierarchy. UML metrics are grouped into four categories: coupling, diagrams, inheritance, and size.
• Static analysis rules for reviewing UML models
  The rules for analyzing UML models can help you determine whether a UML model follows best practices. You can detect 15 different types of problems in a model. For example, you can examine a model for broken semantic relationships, missing specifications, or correct Java naming conventions. UML review rules are grouped into five categories: completeness, correctness, Java naming, style, and traceability.