| Scope... |
|---|
| Business Model... |
|---|
| System Model... |
|---|
| Technology Model... |
|---|
|
Motivation| Detailed Representations... |
|---|
Technology Model-Motivation
Zachman Definition
"Rule Design"
This is a physical specification of the Business Rules. The rules are not presently
factored out from their implementations and therefore are found as
cardinality and optionality in the data models (Column 1), as procedural
code (Column 2) or as policy specification (Column 4). However, historically, there have been
"inference engine"-style technologies that allow expression of rules quite
independent from data and logic, and the tools in which these ideas
persist may influence the general marketplace with their formalisms.
Select Perspective
As explained in the Scope-Motivation cell, the Select Perspective is driven from Organization Vision Statement. This was extended in the Business-Motivation and System-Motivation cells to include the business objectives and similarly, the Select Perspective output of this cell decomposes the objectives into the Business Rules and adds any additional detail.
It is expected that if the business rules have been gathered from projects, then the model in the System-Motivation cell will be the same as that for this cell.
Select Solution Factory
Use the Requirements section of the dictionary tab and the Relationships tab in Select Architect to document the Business Rules as Requirements, sub-Requirements and Dependant Requirements of the Business Objectives and Strategies in the Enterprise model and add any additional data into the properties of the rules:
