BMA Rules

These are the rules we implemented and on which the model is analysed.

• BMA rule: Aggregate metadata includes non-aggregate entities
• BMA rule: Aggregate not self-contained, attributes out of scope
• BMA rule: Aggregates should not contain too many metadata elements
• BMA rule: AQ_RequestParameters service should be implemented in certain way
• BMA rule: Condition node should have a label
• BMA rule: Decision table gap and overlap analysis
• BMA rule: Decision table should not be used as an attribute default value
• BMA rule: Duplicate expressions should be eliminated
• BMA rule: Element names should comply with a naming convention
• BMA rule: Elements should not contain connection details
• BMA rule: Elements should not contain username and password
• BMA rule: Elements should not have too many specializations
• BMA rule: Exposed flows should have role(s) assigned
• BMA rule: Expression is too complex
• BMA rule: Expression may be simplified
• BMA rule: Flow contains incorrect condition node
• BMA rule: Flow contains rest service client with unconnected exits
• BMA rule: Flows should fit the default viewport
• BMA rule: Flows should not contain many complex elements
• BMA rule: Flows should not contain too many elements
• BMA rule: Incorrect usage of today
• BMA rule: Library elements should be used
• BMA rule: Module should not contain specialized elements
• BMA rule: Precondition should not evaluate to a constant value
• BMA rule: Projects should not contain diamond shaped module structure
• BMA rule: Reusable expressions should not be duplicated
• BMA rule: Unconnected default exit on repeat flow