June 2000 How to record the transactional logic behind UML object models. Scott Ambler A business rule is an operating principle or policy that your software must satisfy. Every organization has its own set of business rules Crules that must be reflected in the software it develops. My experience is that regardless of the development paradigm, business rules are a major aspect of requirements, modeling, programming and testing.
Rules often focus on access-control issues.
For example, university professors are allowed to input and modify the marks of the students taking their seminars but not the marks of students in other seminars. Figure 1 presents a fully documented version. Notice how the name offers a good idea about the topic of the business rule and how the description exactly defines the rule. A list of related business rules, if any, is provided to support traceability among rules. A revision history of the business rule indicates the date that a change was made, the person who made the change and a description of the change.