1.1 Business Rule Name

Identifier: BR##

Description: 
Detailed description of the rule.  Typically written in structured English or psuedocode.  
Consider using a flowchart or UML activity diagram to depict procedural logic.

Example:
Optional section.  Sometimes a business rule is easier to understand when one or more 
examples are provided.

Source(s):
Names of the person, department, document, ... from which this business rule originated

Related Rules:
Other business rules related to this one.  

Reference(s):
Applicable references, such as explanatory documents (printed or electronic), 
pertinent to this business rule.

Notes:
Any applicable notes, issues, ...

Assumptions:
1. Assumption... (indicate "None" if none)

Issues:
1. List an "to dos", concerns to be addressed, ... 

Decisions:
List any important decisions made during the development of this business rule.