Empulsys BV.
<Project Name>
Business Rules Document
Version <1.0>
[Note: The following template is provided for use with the Rational Unified Process. Text enclosed in square brackets and displayed in blue italics (style=InfoBlue) is included to provide guidance to the author and should be deleted before publishing the document. A paragraph entered following this style will automatically be set to normal (style=Body Text).]
Revision History
|
Date |
Version |
Description |
Author |
|
<dd/mmm/yy> |
<x.x> |
<details> |
<name> |
Table of Contents
Business Rules
[The introduction of the Business Rules Document should provide an overview of the entire document. Present any information the reader might need to understand the document in this section. This document is used to define terminology specific to the problem domain, explaining terms which may be unfamiliar to the reader of the use-case descriptions or other project documents. Often, this document can be used as an informal data dictionary, capturing data definitions so that use-case descriptions and other project documents can focus on what the system must do with the information. This document should be saved in a file called Business Rules Document .]
[Specify the purpose of this document.]
[A brief description of the scope of this Business Rules Document ; what Project(s) it is associated with, and anything else that is affected or influenced by this document.]
[This subsection should provide a complete list of all documents referenced elsewhere in the Business Rules Document . Each document should be identified by title, report number (if applicable), date, and publishing organization. Specify the sources from which the references can be obtained. This information may be provided by reference to an appendix or to another document.]
[This subsection should describe what the rest of the Business Rules Document contains and explain how the document is organized.]
[The terms defined here form the essential substance of the document. They can be defined in any order desired, but generally alphabetic order provides the greatest accessibility.]
[The definition for <aBusinessRule> is presented here, with as much information as the reader needs to understand the concept.]
[The definition for <anotherBusinessRule> is presented here, with as much information as the reader needs to understand the concept.]
[Sometimes it is useful to organize Business Rules into groups to improve readability. For example, if the problem domain contains Business Rules related to both accounting and building construction (as would be the case if we were developing a system to manage construction projects), presenting the Business Rules from the two different sub-domains might prove confusing to the reader. To solve this problem, we use groupings of Business Rules. In presenting the grouping of Business Rules, provide a short description that helps the reader understand what <aGroupOfBusinessRules> represents. When using the groups, or categories, be sure that it will be very clear which group/category a business rule belongs to. Business Rules presented within the group should be organized alphabetically for easy access.]
2.3.1 <aGroupBusinessRule>[The definition for <aGroupBusinessRule> is presented here, with as much information as the reader needs to understand the concept.]
2.3.2 <anotherGroupBusinessRule>[The definition for <anotherGroupBusinessRule> is presented here, with as much information as the reader needs to understand the concept.]
[The definition for the term is presented here, with as much information as the reader needs to understand the concept.]
2.4.2 <andAnotherGroupBusinessRule>[The definition for the term is presented here, with as much information as the reader needs to understand the concept.]
|
|
This content developed or partially developed by Empulsys BV.
|