|
See Also
To make it easier to trace a
business rule in a larger rule base, group Business Rules
together.
To group a business rule,
perform some or all of the following optional steps:
| 1.
|
Retrieve the rule's definition by choosing TeamWork,
Definition, Business Rules and Processes from the main menu, and
then querying the rule by ID or by its Definition text. |
TIP:
You can find all rules that
have "delivery" in their Definition text by entering "%delivery%"
in the Definition text as a search condition, and then browse
through the results to find the rule you want to add information
to.
| 2.
|
Choose a Motivation, Classification and Source for the
rule. |
| 3.
|
Choose what Business Area, Business Object and Rule Set the
rule belongs to. |
NOTE:
If you leave Business Area
open and the Business Object or Rule Set you choose belongs to a
Business Area, then USoft will automatically select that Business
Area for the rule as well. This does not happen if the Business
Object and the Rule Set belong to different Business Areas.
| 4.
|
To facilitate progress monitoring: |
|
·
|
In the Approved By field indicate the initials of who is to
approve the definition of the business rule. |
|
·
|
When the Approved field is checked this indicates that the rule
is described properly (and therefore can be built). |
|
·
|
The Built By field enables the application developer to
indicate who is responsible for building the rule. |
|
·
|
When the Built field is checked, this indicates that the rule
is built. |
|
·
|
If the rule has to be changed later on, clear the Approved and
Built fields to indicate that the process has to start all over
again. |
|
·
|
The Tested By field enables another developer to indicate who
is responsible for testing the rule. |
|
·
|
When the Test field is checked, this indicates that the rule
has been tested. |
|
·
|
The Created On field is where the date on which the design of
the business rule was created is indicated. |
|
·
|
The Created By field allows the project member(s) who created
the business rule to indicate this. |
|
·
|
The Changed On field is where the date on which the design of
the business rule was created is indicated. |
|
·
|
The Changed By field allows the project member(s) who made the
most recent change to the business rule to indicate this. |
| 5.
|
Use the lookup button to choose the motivation behind the
business rule expressing the business objective or
requirement. |
| 6.
|
Provide a classification to group together different types of
business rules. |
| 7.
|
Use the lookup button to choose the source of the business rule
to be inserted in the field. |
| 8.
|
Click the Add Rule button and the Business Rule wizard appears.
Enter the requested information in each of the wizard's dialogs to
add a constraint to a business rule. |
|
