<?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 Problem Resolution Plan 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"><!-- Problem Resolution Plan {{{-->

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

    <!--
    Specify the purpose of this Problem Resolution Plan.
    -->
    <section><!-- Purpose {{{-->
      <title>Purpose</title>

      <para>
      </para>

    </section><!--}}}-->

    <!--
    A brief description of the scope of this Problem Resolution Plan; 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 Problem Resolution Plan.
    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 Problem Resolution Plan. 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 Problem Resolution Plan
    contains and explains how the document is organized.
    -->
    <section><!-- Overview {{{-->
      <title>Overview</title>

      <para>
      </para>

    </section><!--}}}-->

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

  <!--
  A brief description of the Problem Resolution tasks to be performed during
  the project. In this section you should describe the following:

    * The procedure the project team will follow for reporting problems
    * The procedure to be used for analyzing problems 
    * The procedure to be followed to implement appropriate corrective actions

  Where these procedures differ for different categories of problems (product,
  project, and process, see Activity: Develop Problem Resolution Plan),
  describe the procedure for each under a separate sub-section.
  -->
  <chapter><!-- Problem Resolution Tasks {{{-->
    <title>Problem Resolution Tasks</title>

    <para>
    </para>

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

  <!--
  List the specific groups or individuals to be involved in the analysis and
  resolution of each category of problem, and identify the tasks and
  responsibilities of each.
  -->
  <chapter><!-- Organization and Responsibilities {{{-->
    <title>Organization and Responsibilities</title>

    <para>
    </para>

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

  <!--
  List the tools and techniques that will be used to store problem information,
  analyze problems, and track the status of problems.
  -->
  <chapter><!-- Tools and Techniques {{{-->
    <title>Tools and Techniques</title>

    <para>
    </para>

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

  <!--
  Identify problem categories and where they are stored and tracked, for
  example:

    * Product and process problems (defects) may be stored and tracked in a
      Change Tracking System.
    * Project problems (issues) may be tracked in an issues list, which is a
      component of the Status Assessment.
    * Process problems (non-conformances) may be recorded in an audit report
      and then tracked in a Change Tracking System (as a kind of Change
      Request).
    * Review anomalies will be recorded in the Review Record and tracked from
      there; if the scope of the problem requires it, a Change Request may be
      raised.
  -->
  <chapter><!-- Problem Tracking {{{-->
    <title>Problem Tracking</title>

    <para>
    </para>

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

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

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

