<?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 Case 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 Case {{{-->

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

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

    <!--
    A brief description of the scope of this Business Case; 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 the definitions of all terms, acronyms, and
    abbreviations required to properly interpret the Business Case. 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 Business Case. 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 Case contains and
    explains how the document is organized.
    -->
    <section><!-- Overview {{{-->
      <title>Overview</title>
      <para>
      </para>
    </section><!--}}}-->

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

  <!--
  To give the reader a context, briefly describe the product being developed.
  Include the name of the system and possibly an acronym, if one is used.
  Explain what problem it solves and why the development will be worth the
  effort. Refer to the Vision document.
  -->
  <chapter><!-- Product Description {{{-->
    <title>Product Description</title>

    <para>
    </para>

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

  <!--
  Define the business context for the product. In which domain is it going to
  function (for example, telecom or bank) and what market-who are the users?
  State whether the product is being developed to fulfill a contract or if it
  is a commercial product. If it is a continuation of an existing project, this
  should also be mentioned.
  -->
  <chapter><!-- Business Context {{{-->
    <title>Business Context</title>

    <para>
    </para>

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

  <!--
  State the objectives for developing the product-the reasons why this is
  worthwhile. This includes a tentative schedule, and some assessment of
  schedule risks. Clearly defined and expressed objectives provide good grounds
  for formulating milestones and managing risks; that is, keeping the project
  on track and ensuring its success.
  -->
  <chapter><!-- Product Objectives {{{-->
    <title>Product Objectives</title>

    <para>
    </para>

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

  <!--
  For a commercial software product, the Business Case should include a set of
  assumptions about the project and the order of magnitude return on investment
  (ROI) if those assumptions are true. For example, the ROI will be a magnitude
  of five if completed in one year, two if completed in two years, and a
  negative number after that. These assumptions are checked again at the end of
  the elaboration phase when the scope and plan are known with more accuracy.
  The return is based on the cost estimate and the potential revenue estimates.

  The resource estimate encompasses the entire project, through to delivery.
  This estimate is updated at each phase and each iteration, and becomes more
  accurate as each iteration is completed. 

  An explanation of the basis of estimates should be included.
  -->
  <chapter><!-- Financial Forecast {{{-->
    <title>Financial Forecast</title>

    <para>
    </para>

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

  <!--
  Express the constraints under which the project is undertaken. These
  constraints impact risk and cost. They could be things like external
  interfaces that the system must adhere to, standards, certifications or a
  technical approach employed for strategic reasons, such as using a certain
  database technology or distribution mechanism.
  -->
  <chapter><!-- Constraints {{{-->
    <title>Constraints</title>

    <para>
    </para>

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

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

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

