 |
| Prototyping rules is an important step of the rule analysis, as it is when we are really coding that issues arrived. Paper work is fine, but working rules is far better. |
| Disciplines: Rule Design |
|
Relationships
| Roles | Primary Performer:
| Additional Performers:
|
Main Description
|
The goal of the Rule Analysis activity is to prepare the rules for the
implementation. The rule analyst and the rule writer will analyze the rules discovered in a disjointed way into a
complete and coherent set. From the rule description, the glossary of business terms and may be from a first version of
the logical data model (LDM), the discovery team needs to transform the rules using the terms of the business to
elements that will be implemented by the rule writers. The rule analyst executes a set of iterative tasks to reach rule
implementation.
|
Steps
|
Create a simple rule flow
Prepare a simple unit test code
The unit test should prepare the input parameter(s) and other related data to trigger the rule execution under
development. Rule writer should work with the business user to define test data and scenario. Using the IDE to author
and test rules the rule testing framework can be created, executed, tuned in the same environment to quickly write and
test rules. As Agile method we recommend to use a Test Driven Development approach.
|
Code the rule under test
Validate the execution
Report any issue, questions, concerns for the next discovery meeting
|
More Information
|
