<?xml version="1.0" encoding='UTF-8'?>

<!--
Copyright 2006 Niels Heirbaut. All rights reserved.

Redistribution and use in source (XML DocBook) and 'compiled' forms (SGML,
XML, HTML, PDF, PostScript, RTF and so forth) with or without modification, are
permitted provided that the following conditions are met:

   1.  Redistributions of source code (XML DocBook) must retain the above
       copyright notice, this list of conditions and the following disclaimer
       as the first lines of this file unmodified.

THIS DOCUMENTATION IS PROVIDED BY THE AUTHOR "AS IS" AND ANY EXPRESS OR IMPLIED
WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO
EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,
EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT
OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
IN ANY WAY OUT OF THE USE OF THIS DOCUMENTATION, EVEN IF ADVISED OF THE
POSSIBILITY OF SUCH DAMAGE.
-->

<!--
This template can be used to create a Business Rules Document as described in
the Rational Unified Process. Where applicable, comments will provide guidance
to the author. At the authors discretion these comments can be deleted.
-->

<!--{{{-->
<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
 "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd"
[

<!--
Text entities. They are used to define document wide definitions. Replace the
'@@@ xxx @@@' definitions with the correct ones. If necessary custom text
entities should be added here.
-->
<!--{{{-->
<!ENTITY projectname    "@@@ Your Project @@@">
<!ENTITY projectacronym "@@@ Your Project Acronym @@@">
<!ENTITY firstname      "@@@ First Name @@@">
<!ENTITY surname        "@@@ Last Name @@@">
<!ENTITY copyrightyear  "@@@ Year @@@">
<!--}}}-->

]>
<!--}}}-->

<book lang="en"><!-- Business Rules {{{-->

  <!--
  This is the front matter definition of the Business Rules. Most data is set
  through the text entities above. Only the history per revision has to be set
  by hand. See <revhistory> below.
  -->
  <bookinfo><!-- Front Matter {{{-->

    <title>&projectname;</title>
    <subtitle>Business Rules</subtitle>

    <author>
      <firstname>&firstname;</firstname>
      <surname>&surname;</surname>
    </author>

    <copyright>
      <year>&copyrightyear;</year>
      <holder>&firstname; &surname;</holder>
    </copyright>

    <revhistory>

      <!--
      For each revision a <revision> section has to be added.
      -->
      <revision>
        <revnumber></revnumber>
        <date></date>
        <authorinitials></authorinitials>
        <revremark></revremark>
      </revision>

    </revhistory>

  </bookinfo><!--}}}-->

  <!--
  The introduction of the Business Rules provides an overview of the entire
  document. Present any information the reader might need to understand the
  document in this section. Save this document in a file called Business Rules.
  -->
  <chapter><!-- Introduction {{{-->
    <title>Introduction</title>

    <!--
    Specify the purpose of this document.
    -->
    <section><!-- Purpose {{{-->
      <title>Purpose</title>
      <para>
      </para>
    </section><!--}}}-->

    <!--
    A brief description of the scope of the Business Rules document; what
    Project(s) it is associated with and anything else that is affected or
    influenced by this document.
    -->
    <section><!-- Scope {{{-->
      <title>Scope</title>
      <para>
      </para>
    </section><!--}}}-->

    <!--
    This section provides a complete list of all documents referenced elsewhere
    in the Business Rules document. Identify each document 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.
    -->
    <section><!-- References {{{-->
      <title>References</title>
      <para>
      </para>
    </section><!--}}}-->

    <!--
    This section describes what the rest of the Business Rules document
    contains and explains how the document is organized.
    -->
    <section><!-- Overview {{{-->
      <title>Overview</title>
      <para>
      </para>
    </section><!--}}}-->

  </chapter><!--}}}-->

  <!--
  The terms defined here form the essential substance of the document. They can
  be defined in any order desired, but generally alphabetical order provides
  the greatest accessibility.
  -->
  <chapter><!-- Definitions {{{-->
    <title>Definitions</title>

    <para>
    </para>

    <!--
    The definition for a Business Rule is presented here, with as much
    information as the reader needs to understand the concept.

    Replace the '@@@'s and the text in between with the business rule.

    Add sections for each business rule.
    -->
    <section>
      <title>@@@ Business Rule @@@</title>
      <para>
      </para>
    </section>

    <!--
    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 Group Of Business Rules represents.
    Business Rules presented within the group are organized alphabetically for
    easy access.

    Replace the '@@@'s and the text in between with the name of the group.

    Add sections for each group.
    -->
    <section>
      <title>@@@ Group of Business Rules</title>

      <!--
      The definition for a Group Business Rule is presented here, with as much
      information as the reader needs to understand the concept.

      Replace the '@@@'s and the text in between with the business
      rule.

      Add sections for each business rule.
      -->
      <section>
        <title>@@@ A Group Business Rule @@@</title>
        <para>
        </para>
      </section>

    </section>

  </chapter><!--}}}-->

</book><!--}}}-->

<!-- vim: set ts=2 sw=2 fo+=t et ff=unix filetype=docbkxml fdm=marker: -->

