Business rules are also traceable into lifecycle artifacts. Business rules are, by their nature, constraints. As they move into software design, business rules become constraints on the class diagram. Here are the mappings for each type of business rule. 8.3.1 Structural FactsStructural facts often become attributes of classes on the class diagram. They also become entries in a data dictionary or glossary as the project proceeds. Structural facts generally cannot be tested in test cases. 8.3.2 Action-Restricting and Action-Triggering RulesAction-restricting rules usually become constraints on the class diagram. Constraints are restrictions on the associations between classes. Action-triggering rules are also indicated on the associations as association names and roles. Action-restricting and action-triggering rules are tested in test cases. 8.3.3 Calculations and InferencesCalculations and inferences become details of the operations of the classes. They may be translated into detailed design activity diagrams or directly into program code. Calculations and inferences are tested using test cases. |