This is one of the possible Use Cases.
1. Abstract
Organizations, which manage their business policies and rules as part of governing and operating their organization and/or specifying their products and services, want to delegate the execution and enforcement of a significant part of their rules to information systems.
The interchange of rules in this use case, and the vocabulary (terms and facts) in terms of which the rules are formulated, takes place between two classes of rules systems:
Rules Systems Supporting Interchange of Human-oriented Business Rules Rules Systems Supporting Business Communication of Rules i.e. rule editing systems that support specification, analysis, verification & validation of rules in business terms using controlled natural language underpinned by formal logic
Rules systems for Designing and/or Operating Information Systems i.e. rule-enabled IT application development environments for, and/or rule system components of, the IT systems that support the organization’s business processes.
2. Status
Describe the status of the use case, e.g. proposed, revised, reviewed, approved etc (and by whom, using a WikiName if possible). Note that the wiki will automatically keep a revision history, so version numbers aren't necessary.
3. Benefits of Interchange
List below some benefits of interchange in this use case, i.e. why interchange matters.
Benefit 1
...
Benefit n
4. Requirements on the RIF
List requirements of this use case on the RIF.
Requirement 1
...
Requirement n
5. Breakdown
5.1. Actors and their Goals
List the different parties who interact in this use case, along with their goals. They should be named with abstract role names, like "Buyer", "Seller", "Buyer's Agent", and "Government Agency".
Actor 1 - wants ...
...
Actor n - wants ...
5.2. Main Sequence
Provide the typical course of events, ordered as below in a sequence of steps.
First step of sequence
...
Last step of sequence
5.3. Alternate Sequences
Describe possible variations of the main sequence in separate subsections, assigning a title to each.
5.3.1. (Title of Alternate Sequence)
Describe the alternate sequence, referring to the steps in the main sequence above if convenient (to avoid repetition).
6. Narratives
Describe possible scenarios illustrating the use case in separate subsections, assigning a title to each.
6.1. (Title of Narrative)
Describe an individual scenario. Samples rules and other test data may be optionally included.
7. Commentary
Comments, issues, etc. Again, note that the wiki automatically keeps a revision history.