Author Topic: Static Business Rule Documentation and Reporting  (Read 3003 times)

salayande

  • EA User
  • **
  • Posts: 224
  • Karma: +0/-0
  • I love YaBB 1 Gold!
    • View Profile
Static Business Rule Documentation and Reporting
« on: April 10, 2007, 09:10:45 am »
The format of a  static business rule is <<statement subject>> relationship or verb << statement object>>.

When documented in a CASE tool, there are two rules, the forward rule and the reverse.

The forward rule is <<Class 1>> relationship X<<Class 2>>
The reverse is <<Class 2>> relationship Y<<Class 1>>

Sometimes where the forward rule is true, the reverse may not be true. hence the need to articulate the two rules explicitly.


The subject and objects are Nouns modelled as classes in Class diagrams.

To verify the quality of a data model, we often have to generate these business rules from the data model documentation which are presented to the business domain experts for verification. These models validate the conceptual correctness of the data model and is often used as a user acceptance criteria on projects.

Old data modeling tools like Erwin enable this representation and the IE notation in EA should support this feature.

I need to create these statements from using EA document generator. Is there any RTF Document generator expert out there who can help.

Please, help me.

Jan ´Bary´ Glas

  • EA User
  • **
  • Posts: 408
  • Karma: +0/-0
  • Bary
    • View Profile
Re: Static Business Rule Documentation and Reporti
« Reply #1 on: April 11, 2007, 03:08:47 am »
Hi salayande,

interesting way how to depict business rules on domain diagram. If I understand your approach, you have a diagram (or model) like this example:

And you may start with such a report:

Here is the RTF template:


HTH,
  Bary
Jan 'Bary' Glas

salayande

  • EA User
  • **
  • Posts: 224
  • Karma: +0/-0
  • I love YaBB 1 Gold!
    • View Profile
Re: Static Business Rule Documentation and Reporti
« Reply #2 on: April 11, 2007, 08:01:13 am »
Thank you, Barry.

You are right.

It is the conbination of two classes and one relationship type which form a sentence that comprises a business rule.

Consider an airport check-in scenario where Class 1 is a Passenger, Class 2 is Bag (Luggage)and Class 3 is an Airline Agent. For the check-in scenario, A Passenger may submit zero, one or more Bags. The reverse statement, A Bag must belong to at least one or more Passengers is a critical business rule to airport security otherwise, the Bag will not be loaded to the Aircraft.

Likewise, An Airline Agent may weigh one or more Bags is a statement that expresses a familiar business rule. The reverse statement, A Bag is checked-in by one and only one Airline Agent is another rule that may /may not be true in that domain.

Thank you for your the RTF template. I will inform you of progress.

kind regards

salayande