View the CRaG Systems Website | Overview | Process Concepts | Process Configurations | Process Glossary | Process Map | View the OMG's UML Website
Model-Driven Development Process
| Business Analysis | Requirements Gathering | System Analysis | System Architecture | Detailed Design |
| Project Management | Project Support | Coding | Testing | Rollout |
Return to Business Analysis Define Business Rules Task
Business rules will normally begin life as textual notes in the process model. This is because they will be gathered during a process development workshop and written straight into the process model. Once the process model is stable, then business rules should be formalised in this Business Rules Document and given a unique reference number within the hi-level process/project/system model from which they have been derived. Once formalised, the business rule reference in the form BR n[.m] should replace the textual note in the process model from which it has been derived.
Note that a single business rule may apply across multiple processes in the process model, also to data in the business data (conceptual) model and to statecharts for entities in the business data model. Where it is realised that the rule applies in more than one place, the reference to the rule, in the form BR n[.m], should also be made in the textual note property of each element. The elements could be entities, attributes, roles and relationships in the business data model, or states, events, transitions and conditions in the business state model.
Suggested Step Flow
Download Define Business Rules Task Guidelines in Word
Guidelines, Templates and Examples
Download Define Business Rules Task Guidelines in Word    Download Define Business Rules Document Template in Word
Business Process Analysis and Modelling using UML
Business Analysis and Systems Requirements Definition using UML and Use Cases
Business Analysis, Requirements Definition and Systems Analysis using UML