| UML Representation: Constraint, stereotyped <<business rule>>.
Modeling of business rules is optional-they are often captured in document form in addition to or instead of a model.
Business rules can be captured in both model and document form. Business rules defining structural and behavioral
constraints are most easily captured directly in models, attached to the model elements to which they apply. Other
business rules, especially those describing computations or policy, or those that apply to many different model
elements, are best captured in document form.
Business Rules can also be included in other business or requirements specification documents.
|
