Business Rules Analysis

The Business Rules Analysis pattern creates elements and a diagram to model Business Rules and Policies. The Policies and Business Rules are modeled as stereotyped Classes and a Qualify relationship has been used to indicate that the Business Rules qualify (or make concrete) the Policy.

Figure 1. Show a diagram used to model the relationship between Policies and Business Rules. The three Business Rules are said to qualify the Policy.
Discussion
The purpose of the pattern is to create a catalogue of the Business Rules and the Policies that they qualify and to visually represent these in a diagram. Having a catalogue of the Policies and Business Rules allows these elements that describe the way an organization functions to be related to other parts of an enterprise description such Activities in Business Processes, Steps in a Use Case, or Decisions in a Decision Model.

The pattern is typically used early on in an initiative or the description of an enterprise and certainly it would be judicious for an analyst to search exiting repositories for Policies and Business Rules that have been previously defined. (These could be inside an existing Enterprise Architect repository or documented in another system)

The following is a list of some things you may want to do when working with this pattern.
·	Rename the diagram.
Rename the Policy and the Business Rules to suit the initiative.
Add detailed notes that describe the business or system significance of the Policy and the Business Rules.
·	Update the properties of the Requirements to suit the initiative.

The following is a list of some of the next steps available when applying the pattern.
·	Define Trace relationships showing how the Requirements relate to up-process elements such as Strategies, Drivers, Goals and Requirements and down-process elements such as Activities in Business Process Diagrams, User Stories, Use Cases, Components, Artifacts and database tables.
Create high quality documentation generated automatically from the model.
·	Create Discussions and Reviews and engage in Chat to collaborate with team members, Requirement owners, Product Managers and other stakeholders.
Reference
The following help topics will assist you learn about how to work with this pattern.
Business Rules Analysis
Business Rules Model
Business Analysis Body of Knowledge (BABOK)
Traceability Tools
Documentation

The following are some of the tools that will be helpful when working with this pattern.
Stereotyping
A Business Rule is not defined as an element type in any of the built-in Toolbox palettes but can be created as a type using the Unified Modeling Language (UML) extension mechanism of Stereotypes. It is typically a model administrator or librarian that will set up the Stereotype but it can be applied by any modeler by setting the name in the 'Stereotype' field in the element's property sheet. For more details see the Stereotyping help topic.
Document Generator
The Document Generator is a powerful facility in Enterprise Architect that allows a Database Engineer or other stakeholder to create high quality corporate or technical documentation directly from the model, suitable for internal or external audiences. For more details see the Documentation help topic or the more general topic on Model Publishing.
Element Discussions
The Element Discussion facility is a fully featured collaboration tool allowing modelers and model viewers and reviewers to communicate with each other directly inside the repository. Modelers using the full client or occasional viewers using WebEA can both post and reply to discussions and communicate and engage in chat. For more details see the Element Discussions help topic.
Specification View
The Specification View can be used as a way of working with any element type in a spreadsheet or word process view. It is particularly useful when there are a large number of elements as is typically the case when describing a system of any appreciable size. For more details see the Specification View help topic.
Relationship Matrix
The Relationship Matrix provides a spreadsheet like view of two groups of elements and the relationships that exist between them. It can be a used as a powerful analysis mechanism to visually indicate how elements are related to each other and to discover which elements are missing relationships. For more details see the Relationship Matrix  help topic.
Traceability Window
The Traceability Window automatically displays the relationships that exist between Use Cases and other model elements including up-process and down-process elements. The traceability tree view can be conveniently expanded to see deeper relationships and elements displayed in the window can be located in all diagrams in which they appear. For more details see the Traceability Window  help topic.

© 2000 - 2018  Sparx Systems Pty Ltd.  All rights Reserved.