<?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 Supplementary Business Specification 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"><!-- Supplementary Business Specification {{{-->

  <!--
  This is the front matter definition of the Supplementary Business
  Specification. 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>Supplementary Business Specification</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 Supplementary Business Specification provides an
  overview of the entire document. It should include the purpose, scope,
  definitions, acronyms, abbreviations, references, and overview of this
  Supplementary Business Specification.
  -->
  <chapter><!-- Introduction {{{-->
    <title>Introduction</title>

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

    <!--
    A brief description of the scope of this Supplementary Business
    Specification; what Use Case model(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 the definitions of all terms, acronyms, and
    abbreviations required to properly interpret the Supplementary Business
    Specification. This information may be provided by reference to the
    project's Glossary.
    -->
    <section><!-- Definitions, acronyms and abbreviations {{{-->
      <title>Definitions, acronyms and abbreviations</title>
      <para>
      </para>
    </section><!--}}}-->

    <!--
    This section provides a complete list of all documents referenced elsewhere
    in the Supplementary Business Specification. 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 Supplementary Business
    Specification contains and explains how the document is organized.
    -->
    <section><!-- Overview {{{-->
      <title>Overview</title>
      <para>
      </para>
    </section><!--}}}-->

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

  <!--
  This chapter expresses general objectives for the behavior of the
  organization that are not specific to a particular business use case.
  -->
  <chapter><!-- Behavior {{{-->
    <title>Behavior</title>

    <para>
    </para>

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

  <!--
  This chapter includes all of those requirements that affect usability from
  the perspective of a business actor. Examples follow:
    * Specify the required training time for a normal users and power users of
      the organization to become productive at particular operations.
    * Specify measurable task times for typical task.
  -->
  <chapter><!-- Usability {{{-->
    <title>Usability</title>

    <para>
    </para>

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

  <!--
  Requirements for reliability (from a business actor perspective) of the
  organization should be specified here. Suggestions are as follows:
    * Availability: ”specify percentage of time available ( xx.xx%), anticipated
      hours of use, and so on.
    * Accuracy: ”specify precision (resolution) and accuracy (by some known
      standard) that is required in the output.
  -->
  <chapter><!--  Reliability{{{-->
    <title>Reliability</title>

    <para>
    </para>

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

  <!--
  The performance characteristics should be outlined in this section. Include specific response times. Where applicable, reference related business use cases by name.
    * Response time for a transaction (average, maximum).
    * Throughput; for example, transactions per second.
    * Capacity; for example, the number of customers or transactions the
      business can accommodate.
    * Resource use; for example, number of employees, memory capacity of
      systems, and so on.
  -->
  <chapter><!-- Performance {{{-->
    <title>Performance</title>

    <para>
    </para>

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

  <!--
  List and briefly describe any information about how you expect the
  organization to change size in the future and what limitations or precautions
  need to be considered to meet that change.
  -->
  <chapter><!-- Scaling Issues {{{-->
    <title>Scaling Issues</title>

    <para>
    </para>

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

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

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

