Limit Model Complexity per Creator Project

After selecting a way to measure model complexity users should define limits to what they consider reasonable limits. Consider using different limits for junior vs senior modelers.

Recommendation: Limit main complexity measures per Creator project as follows:

Do not exceed and try to cover more than a maximum of 100 testable requirement references
Do not exceed a maximum of 100 tests to cover model logic, i.e., not counting tests whose only difference or value is to cover combinatorial or spreadsheet data
Do not exceed 20 activity diagrams project and do not nest them deeper than 5 levels.
Less than 20% of all activity diagrams should be of high diagram complexity.
Keep diagram complexity in line with your knowledge level

Note that the limits of 100 requirements and 100 tests are not coincidental – we should target to have at least one test per requirement. In other words we can use the number of tests as a basis to reason about requirements even if they are not explicitly referenced in a model. If you want to increase the number of tests per requirement, then rather reduce the maximum number of requirements than increasing the maximum number of tests.

Conformiq - Support

Limit Model Complexity per Creator Project

Analytics

Related content