<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2// EN">
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Vision</title>
<link type="text/css" href="../../../../css/default.css" rel="StyleSheet">
<script src="../../../../scripts/contentpage.js" type="text/javascript" language="JavaScript"></script><script type="text/javascript" language="JavaScript">
					backPath = './../../';
				</script>
</head>

<body >

<div class=Section1>

<p class=MsoTitle align=right style='text-align:right'>&lt;Project Name&gt;</p>

<p class=MsoTitle align=right style='text-align:right'>Vision</p>

<p class=MsoTitle align=right style='text-align:right'>&nbsp;</p>

<p class=MsoTitle align=right style='text-align:right'><span style='font-size:
14.0pt;'>Version &lt;1.0&gt;</span></p>

<p class=MsoTitle><span style='font-size:14.0pt;'>&nbsp;</span></p>

<p class=MsoNormal>&nbsp;</p>

<p class=InfoBlue>[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).]</p>

<p class=InfoBlue>&nbsp; </p>

</div>

<span style='font-size:10.0pt;font-family:"Times New Roman";'><br clear=all
style='page-break-before:always;'>
</span>

<div class=Section2>

<p class=MsoTitle>Revision History</p>

<table border=1 cellspacing=0 cellpadding=0 style='border-collapse:collapse;
 border:none;'>
 <tr>
  <td width=154 valign=top style='width:1.6in;border:solid windowtext .75pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=Tabletext align=center style='text-align:center'><b>Date</b></p>
  </td>
  <td width=77 valign=top style='width:.8in;border:solid windowtext .75pt;
  border-left:none;padding:0in 5.4pt 0in 5.4pt'>
  <p class=Tabletext align=center style='text-align:center'><b>Version</b></p>
  </td>
  <td width=250 valign=top style='width:2.6in;border:solid windowtext .75pt;
  border-left:none;padding:0in 5.4pt 0in 5.4pt'>
  <p class=Tabletext align=center style='text-align:center'><b>Description</b></p>
  </td>
  <td width=154 valign=top style='width:1.6in;border:solid windowtext .75pt;
  border-left:none;padding:0in 5.4pt 0in 5.4pt'>
  <p class=Tabletext align=center style='text-align:center'><b>Author</b></p>
  </td>
 </tr>
 <tr>
  <td width=154 valign=top style='width:1.6in;border:solid windowtext .75pt;
  border-top:none;padding:0in 5.4pt 0in 5.4pt'>
  <p class=Tabletext>&lt;dd/mmm/yy&gt;</p>
  </td>
  <td width=77 valign=top style='width:.8in;border-top:none;border-left:none;
  border-bottom:solid windowtext .75pt;border-right:solid windowtext .75pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=Tabletext>&lt;x.x&gt;</p>
  </td>
  <td width=250 valign=top style='width:2.6in;border-top:none;border-left:none;
  border-bottom:solid windowtext .75pt;border-right:solid windowtext .75pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=Tabletext>&lt;details&gt;</p>
  </td>
  <td width=154 valign=top style='width:1.6in;border-top:none;border-left:none;
  border-bottom:solid windowtext .75pt;border-right:solid windowtext .75pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=Tabletext>&lt;name&gt;</p>
  </td>
 </tr>
 <tr>
  <td width=154 valign=top style='width:1.6in;border:solid windowtext .75pt;
  border-top:none;padding:0in 5.4pt 0in 5.4pt'>
  <p class=Tabletext>&nbsp;</p>
  </td>
  <td width=77 valign=top style='width:.8in;border-top:none;border-left:none;
  border-bottom:solid windowtext .75pt;border-right:solid windowtext .75pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=Tabletext>&nbsp;</p>
  </td>
  <td width=250 valign=top style='width:2.6in;border-top:none;border-left:none;
  border-bottom:solid windowtext .75pt;border-right:solid windowtext .75pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=Tabletext>&nbsp;</p>
  </td>
  <td width=154 valign=top style='width:1.6in;border-top:none;border-left:none;
  border-bottom:solid windowtext .75pt;border-right:solid windowtext .75pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=Tabletext>&nbsp;</p>
  </td>
 </tr>
 <tr>
  <td width=154 valign=top style='width:1.6in;border:solid windowtext .75pt;
  border-top:none;padding:0in 5.4pt 0in 5.4pt'>
  <p class=Tabletext>&nbsp;</p>
  </td>
  <td width=77 valign=top style='width:.8in;border-top:none;border-left:none;
  border-bottom:solid windowtext .75pt;border-right:solid windowtext .75pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=Tabletext>&nbsp;</p>
  </td>
  <td width=250 valign=top style='width:2.6in;border-top:none;border-left:none;
  border-bottom:solid windowtext .75pt;border-right:solid windowtext .75pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=Tabletext>&nbsp;</p>
  </td>
  <td width=154 valign=top style='width:1.6in;border-top:none;border-left:none;
  border-bottom:solid windowtext .75pt;border-right:solid windowtext .75pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=Tabletext>&nbsp;</p>
  </td>
 </tr>
 <tr>
  <td width=154 valign=top style='width:1.6in;border:solid windowtext .75pt;
  border-top:none;padding:0in 5.4pt 0in 5.4pt'>
  <p class=Tabletext>&nbsp;</p>
  </td>
  <td width=77 valign=top style='width:.8in;border-top:none;border-left:none;
  border-bottom:solid windowtext .75pt;border-right:solid windowtext .75pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=Tabletext>&nbsp;</p>
  </td>
  <td width=250 valign=top style='width:2.6in;border-top:none;border-left:none;
  border-bottom:solid windowtext .75pt;border-right:solid windowtext .75pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=Tabletext>&nbsp;</p>
  </td>
  <td width=154 valign=top style='width:1.6in;border-top:none;border-left:none;
  border-bottom:solid windowtext .75pt;border-right:solid windowtext .75pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=Tabletext>&nbsp;</p>
  </td>
 </tr>
</table>

<p class=MsoNormal>&nbsp;</p>

<b><span style='font-size:18.0pt;font-family:Arial;'><br clear=all style='page-break-before:always'>
</span></b>

<p class=MsoTitle>Table of Contents</p>

<p class=MsoToc1><a href="#1.                  Introduction">1.<span style='font-size:12.0pt'>       </span>Introduction</a>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</p>

<p class=MsoToc2><a href="#1.1               Purpose">1.1<span
style='font-size:12.0pt'>     </span>Purpose</a>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</p>

<p class=MsoToc2><a href="#1.2               Scope">1.2<span
style='font-size:12.0pt'>     </span>Scope</a>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</p>

<p class=MsoToc2><a href="#1.3               Definitions, Acronyms and Abbreviations">1.3<span
style='font-size:12.0pt'>     </span>Definitions,
Acronyms, and Abbreviations</a>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</p>

<p class=MsoToc2><a href="#1.4               References">1.4<span
style='font-size:12.0pt'>     </span>References</a>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</p>

<p class=MsoToc2><a href="#1.5               Overview">1.5<span
style='font-size:12.0pt'>     </span>Overview</a>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</p>

<p class=MsoToc1><a href="#2.                  Positioning">2.<span style='font-size:12.0pt'>       </span>Positioning&nbsp;</a>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</p>

<p class=MsoToc2><a href="#2.1               Business Opportunity">2.1<span
style='font-size:12.0pt'>     </span>Business Opportunity</a>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</p>

<p class=MsoToc3><a href="#2.1.1     Current Position">2.1.1&nbsp;&nbsp;&nbsp;&nbsp;
Current Position&nbsp;</a></p>

<p class=MsoToc3><a href="#2.1.2     Justification for Change">2.1.2&nbsp;&nbsp;&nbsp;&nbsp;
Justification for Change</a></p>

<p class=MsoToc2><a href="#2.2               Problem Statement">2.2<span
style='font-size:12.0pt'>     </span>Problem Statement</a>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</p>

<p class=MsoToc2><a href="#2.3               Product Position Statement">2.3<span
style='font-size:12.0pt'>     </span>Product
Position Statement</a>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</p>

<p class=MsoToc1><a href="#3.                  Stakeholder and User Descriptions">3.<span style='font-size:12.0pt'>       </span>Stakeholder and
User Descriptions</a>&nbsp;&nbsp;</p>

<p class=MsoToc2><a href="#3.1               Market Demographics">3.1<span
style='font-size:12.0pt'>     </span>Market Demographics</a>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</p>

<p class=MsoToc2><a href="#3.2               Stakeholder Summary">3.2<span
style='font-size:12.0pt'>     </span>Stakeholder Summary</a>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</p>

<p class=MsoToc2><a href="#3.3               User Summary">3.3<span
style='font-size:12.0pt'>     </span>User Summary</a>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</p>

<p class=MsoToc2><a href="#3.4               User Environment">3.4<span
style='font-size:12.0pt'>     </span>User environment</a>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</p>

<p class=MsoToc2><a href="#3.5               Stakeholder Profiles">3.5<span
style='font-size:12.0pt'>     </span>Stakeholder Profiles</a>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</p>

<p class=MsoToc3><a href="#3.5.1          &lt;Stakeholder Name&gt;">3.5.1<span
style='font-size:12.0pt'>&nbsp;&nbsp;&nbsp;&nbsp; </span>&lt;Stakeholder
Name&gt;</a>           </p>

<p class=MsoToc2><a href="#3.6               User Profiles">3.6<span
style='font-size:12.0pt'>     </span>User Profiles</a>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</p>

<p class=MsoToc3><a href="#3.6.1          &lt;User Name&gt;">3.6.1<span
style='font-size:12.0pt'>&nbsp;&nbsp;&nbsp;&nbsp; </span>&lt;User
Name&gt;</a>           </p>

<p class=MsoToc2><a href="#3.7               Key Stakeholder / User Needs">3.7<span
style='font-size:12.0pt'>     </span>Key
Stakeholder or User Needs</a>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</p>

<p class=MsoToc2><a href="#3.8               Alternatives and Competition">3.8<span
style='font-size:12.0pt'>     </span>Alternatives
and Competition</a>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</p>

<p class=MsoToc3><a href="#3.8.1          &lt;aCompetitor&gt;">3.8.1<span
style='font-size:12.0pt'>&nbsp;&nbsp;&nbsp;&nbsp; </span>&lt;aCompetitor&gt;</a>           </p>

<p class=MsoToc3><a href="#3.8.2          &lt;anotherCompetitor&gt;">3.8.2<span
style='font-size:12.0pt'>&nbsp;&nbsp;&nbsp;&nbsp; </span>&lt;anotherCompetitor&gt;</a>           </p>

<p class=MsoToc2><a href="#3.9       Development Alternatives Considered">3.9&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Development Alternatives Considered</a></p>

<p class=MsoToc1><a href="#4.                  Product Overview">4.<span style='font-size:12.0pt'>       </span>Product
Overview</a>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</p>

<p class=MsoToc2><a href="#4.1               Product Perspective">4.1<span
style='font-size:12.0pt'>     </span>Product Perspective</a>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</p>

<p class=MsoToc2><a href="#4.2               Summary of Capabilities">4.2<span
style='font-size:12.0pt'>     </span>Summary
of Capabilities</a>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</p>

<p class=MsoToc2><a href="#4.3               Assumptions and Dependencies">4.3<span
style='font-size:12.0pt'>     </span>Assumptions
and Dependencies</a>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</p>

<p class=MsoToc2><a href="#4.4               Cost and Pricing">4.4<span
style='font-size:12.0pt'>     </span>Cost
and Pricing</a>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</p>

<p class=MsoToc2><a href="#4.5               Licensing and Installation">4.5<span
style='font-size:12.0pt'>     </span>Licensing
and Installation</a>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</p>

<p class=MsoToc1><a href="#5.                  Product Features">5.<span style='font-size:12.0pt'>       </span>Product
Features</a>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</p>

<p class=MsoToc2><a href="#5.1               Features">5.1<span
style='font-size:12.0pt'>     </span>Features&nbsp;</a>&nbsp;&nbsp;&nbsp;&nbsp;</p>

<p class=MsoToc3><a href="#5.1.1     &lt;aFeature&gt;">5.1.1&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&lt;aFeature&gt;</a></p>

<p class=MsoToc3><a href="#5.1.2     &lt;anotherFeature&gt;">5.1.2&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&lt;anotherFeature&gt;</a></p>

<p class=MsoToc2><a href="#5.2               Operational Scenarios">5.2<span
style='font-size:12.0pt'>     </span>Operational Scenarios</a></p>

<p class=MsoToc2><a href="#5.3               Support Provision">5.3&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Support Provision&nbsp;</a>&nbsp;&nbsp;&nbsp;</p>

<p class=MsoToc1><a href="#6.                  Constraints">6.<span style='font-size:12.0pt'>       </span>Constraints</a>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</p>

<p class=MsoToc1><a href="#7.                  Quality Ranges">7.<span style='font-size:12.0pt'>       </span>Quality
Ranges</a></p>

<p class=MsoToc1><a href="#8.                  Precedence and Priority">8.<span style='font-size:12.0pt'>       </span>Precedence and
Priority</a></p>

<p class=MsoToc1><a href="#9.                  Other Product Requirements">9.<span style='font-size:12.0pt'>       </span>Other Product
Requirements</a></p>

<p class=MsoToc2><a href="#9.1               Applicable Standards">9.1<span
style='font-size:12.0pt'>     </span>Applicable Standards</a>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</p>

<p class=MsoToc2><a href="#9.2               System Requirements">9.2<span
style='font-size:12.0pt'>     </span>System Requirements</a>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</p>

<p class=MsoToc2><a href="#9.3               Performance Requirements">9.3<span
style='font-size:12.0pt'>     </span>Performance Requirements</a>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</p>

<p class=MsoToc2><a href="#9.4               Environmental Requirements">9.4<span
style='font-size:12.0pt'>     </span>Environmental Requirements</a>&nbsp;&nbsp;&nbsp;</p>

<p class=MsoToc2><a href="#9.5       Physical Requirements">9.5&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Physical Requirements&nbsp;&nbsp;</a></p>

<p class=MsoToc1><a href="#10.             Documentation Requirements">10.<span style='font-size:12.0pt'>            </span>Documentation
Requirements</a>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</p>

<p class=MsoToc2><a href="#10.1            User Manual">10.1<span
style='font-size:12.0pt'>     </span>User Manual</a>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</p>

<p class=MsoToc2><a href="#10.2            On-line Help">10.2<span
style='font-size:12.0pt'>     </span>Online Help</a>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</p>

<p class=MsoToc2><a href="#10.3            Installation Guides, Configuration, Read Me File">10.3<span
style='font-size:12.0pt'>     </span>Installation
Guides, Configuration, and Read Me File</a>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</p>

<p class=MsoToc2><a href="#10.4            Labeling and Packaging">10.4<span
style='font-size:12.0pt'>     </span>Labeling
and Packaging</a>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</p>

<p class=MsoToc1><a href="#A.             Feature Attributes">A.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Feature Attributes</a>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</p>

<p class=MsoToc2>&nbsp;&nbsp;&nbsp;</p>

<p class=MsoTitle><br
clear=all style='page-break-before:always'>Vision</p>

<h1><a name="1.                  Introduction">1.<span
style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span>Introduction</a></h1>

<p class=InfoBlue>[The purpose of this document is to collect,
analyze, and define high-level needs and features of the <span
style='font-style:normal'>&lt;&lt;System Name&gt;&gt;</span>. It focuses on the capabilities needed by the
stakeholders, and the target users, and <b>why</b> these needs exist. The details of how the <span
style='font-style:normal'>&lt;&lt;System Name&gt;&gt;</span> fulfills these
needs are detailed in the use-case and supplementary specifications. <b>Note:
this Vision template attempts to cover all kinds of developments, from
shrink-wrapped products, developed speculatively for a perceived market need, to
one-off systems, developed under contract, to a specific customer's requirements.
Consequently, the word 'product' and 'system' may be used without careful
differentiation, standing for 'thing to be developed'. We would expect that the
document tailoring would tighten this up for a specific application.</b>]</p>

<p class=InfoBlue> [The
introduction of the <b>Vision </b>document provides an overview of the
entire document. It should include the purpose, scope, definitions, acronyms,
abbreviations, references, and overview of this <b>Vision </b>document.]</p>

<h2><a name="1.1               Purpose">1.1<span
style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span>Purpose</a></h2>

<p class=InfoBlue>[Specify the purpose of this <b>Vision </b>document<b>.</b>]</p>

<h2><a name="1.2               Scope">1.2<span
style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span>Scope</a></h2>

<p class=InfoBlue>[A brief description of the scope of this <b>Vision
</b>document; what Project(s) it is associated with and anything else that is
affected or influenced by this document.]</p>

<h2><a name="1.3               Definitions, Acronyms and Abbreviations">1.3<span
style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span>Definitions, Acronyms, and Abbreviations</a></h2>

<p class=InfoBlue>[This subsection provides the
definitions of all terms, acronyms, and abbreviations required to properly
interpret the <b>Vision </b>document. This information may be provided by
reference to the project's Glossary.]</p>

<h2><a name="1.4               References">1.4<span
style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span>References</a></h2>

<p class=InfoBlue>[This subsection provides a complete
list of all documents referenced elsewhere in the <b>Vision </b>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.]</p>

<h2><a name="1.5               Overview">1.5<span
style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span>Overview</a></h2>

<p class=InfoBlue>[This subsection describes what the
rest of the <b>Vision </b>document contains and explains how the document is
organized.]</p>

<h1><a name="2.                  Positioning">2.<span style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span>Positioning</a></h1>

<h2><a name="2.1               Business Opportunity">2.1<span
style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span>Business Opportunity</a></h2>

<p class=InfoBlue>[Briefly describe the business opportunity being met by this
project.]</p>

<h3><a name="2.1.1     Current Position">2.1.1&nbsp;&nbsp;&nbsp;&nbsp; Current Position</a></h3>

<p class="InfoBlue">[In this subsection, describe the background, purpose and
scope of the existing system or business circumstance, including, as applicable,
the policies that apply, the capabilities of the current system, the
stakeholders involved, and the support issues.]</p>

<h3><a name="2.1.2     Justification for Change">2.1.2&nbsp;&nbsp;&nbsp;&nbsp; Justification for Change</a></h3>

<p class="InfoBlue">[In this subsection, describe the new circumstances or needs
that have arisen, in a business or operational sense, which warrant a change.
Identify briefly changes proposed and rejected and the associated rationale. If
any trade studies (on change needs) have been done, they may be referenced.]</p>

<h2><a name="2.2               Problem Statement">2.2<span
style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span>Problem Statement</a></h2>

<p class=InfoBlue>[Provide a statement summarizing the problem being solved by
this project. The following format may be used:]</p>

<table border=0 cellspacing=0 cellpadding=0 style='margin-left:41.4pt;
 border-collapse:collapse;'>
 <tr>
  <td width=198 valign=top style='width:148.5pt;border:solid windowtext 1.5pt;
  border-bottom:solid windowtext .75pt;background:#BFBFBF;padding:0in 5.4pt 0in 5.4pt'>
  <p class=MsoBodyText style='margin-left:.05in;page-break-after:avoid'>The
  problem of</p>
  </td>
  <td width=348 valign=top style='width:261.0pt;border-top:solid windowtext 1.5pt;
  border-left:none;border-bottom:solid windowtext .75pt;border-right:solid windowtext 1.5pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=InfoBlue>[describe the problem]</p>
  </td>
 </tr>
 <tr>
  <td width=198 valign=top style='width:148.5pt;border-top:none;border-left:
  solid windowtext 1.5pt;border-bottom:solid windowtext .75pt;border-right:
  solid windowtext 1.5pt;background:
  #BFBFBF;padding:0in 5.4pt 0in 5.4pt'>
  <p class=MsoBodyText style='margin-left:.05in;page-break-after:avoid'>affects</p>
  </td>
  <td width=348 valign=top style='width:261.0pt;border-top:none;border-left:
  none;border-bottom:solid windowtext .75pt;border-right:solid windowtext 1.5pt;padding:0in 5.4pt 0in 5.4pt'>
  <p class=InfoBlue>[the stakeholders affected by the problem]</p>
  </td>
 </tr>
 <tr>
  <td width=198 valign=top style='width:148.5pt;border-top:none;border-left:
  solid windowtext 1.5pt;border-bottom:solid windowtext .75pt;border-right:
  solid windowtext 1.5pt;background:
  #BFBFBF;padding:0in 5.4pt 0in 5.4pt'>
  <p class=MsoBodyText style='margin-left:.05in;page-break-after:avoid'>the
  impact of which is</p>
  </td>
  <td width=348 valign=top style='width:261.0pt;border-top:none;border-left:
  none;border-bottom:solid windowtext .75pt;border-right:solid windowtext 1.5pt;padding:0in 5.4pt 0in 5.4pt'>
  <p class=InfoBlue>[what is the impact of the problem?]</p>
  </td>
 </tr>
 <tr>
  <td width=198 valign=top style='width:148.5pt;border-top:none;border-left:
  solid windowtext 1.5pt;border-bottom:solid windowtext .75pt;border-right:
  solid windowtext 1.5pt;background:
  #BFBFBF;padding:0in 5.4pt 0in 5.4pt'>
  <p class=MsoBodyText style='margin-left:.05in'>a successful solution would be</p>
  </td>
  <td width=348 valign=top style='width:261.0pt;border-top:none;border-left:
  none;border-bottom:solid windowtext .75pt;border-right:solid windowtext 1.5pt;padding:0in 5.4pt 0in 5.4pt'>
  <p class=InfoBlue>[list some key benefits of a successful solution]</p>
  </td>
 </tr>
</table>

<h2><a name="2.3               Product Position Statement">2.3<span
style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span>Product Position Statement</a></h2>

<p class=InfoBlue>[Provide an overall statement summarizing, at the highest
level, the unique position the product intends to fill in the marketplace. The
following format may be used:]</p>

<table border=0 cellspacing=0 cellpadding=0 style='margin-left:41.4pt;
 border-collapse:collapse;'>
 <tr>
  <td width=186 valign=top style='width:139.5pt;border:solid windowtext 1.5pt;
  border-bottom:solid windowtext .75pt;background:#BFBFBF;padding:0in 5.4pt 0in 5.4pt'>
  <p class=MsoBodyText style='margin-left:.05in;page-break-after:avoid'>For</p>
  </td>
  <td width=360 valign=top style='width:3.75in;border-top:solid windowtext 1.5pt;
  border-left:none;border-bottom:solid windowtext .75pt;border-right:solid windowtext 1.5pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=InfoBlue>[target customer]</p>
  </td>
 </tr>
 <tr>
  <td width=186 valign=top style='width:139.5pt;border-top:none;border-left:
  solid windowtext 1.5pt;border-bottom:solid windowtext .75pt;border-right:
  solid windowtext 1.5pt;background:
  #BFBFBF;padding:0in 5.4pt 0in 5.4pt'>
  <p class=MsoBodyText style='margin-left:.05in;page-break-after:avoid'>Who</p>
  </td>
  <td width=360 valign=top style='width:3.75in;border-top:none;border-left:
  none;border-bottom:solid windowtext .75pt;border-right:solid windowtext 1.5pt;padding:0in 5.4pt 0in 5.4pt'>
  <p class=InfoBlue>[statement of the need or opportunity]</p>
  </td>
 </tr>
 <tr>
  <td width=186 valign=top style='width:139.5pt;border-top:none;border-left:
  solid windowtext 1.5pt;border-bottom:solid windowtext .75pt;border-right:
  solid windowtext 1.5pt;background:
  #BFBFBF;padding:0in 5.4pt 0in 5.4pt'>
  <p class=MsoBodyText style='margin-left:.05in;page-break-after:avoid'>The
  (product name)</p>
  </td>
  <td width=360 valign=top style='width:3.75in;border-top:none;border-left:
  none;border-bottom:solid windowtext .75pt;border-right:solid windowtext 1.5pt;padding:0in 5.4pt 0in 5.4pt'>
  <p class=InfoBlue> is a [product
  category]</p>
  </td>
 </tr>
 <tr>
  <td width=186 valign=top style='width:139.5pt;border-top:none;border-left:
  solid windowtext 1.5pt;border-bottom:solid windowtext .75pt;border-right:
  solid windowtext 1.5pt;background:
  #BFBFBF;padding:0in 5.4pt 0in 5.4pt'>
  <p class=MsoBodyText style='margin-left:.05in;page-break-after:avoid'>That</p>
  </td>
  <td width=360 valign=top style='width:3.75in;border-top:none;border-left:
  none;border-bottom:solid windowtext .75pt;border-right:solid windowtext 1.5pt;padding:0in 5.4pt 0in 5.4pt'>
  <p class=InfoBlue>[statement of key benefit; that is, the compelling reason to
  buy]</p>
  </td>
 </tr>
 <tr>
  <td width=186 valign=top style='width:139.5pt;border-top:none;border-left:
  solid windowtext 1.5pt;border-bottom:solid windowtext .75pt;border-right:
  solid windowtext 1.5pt;background:
  #BFBFBF;padding:0in 5.4pt 0in 5.4pt'>
  <p class=MsoBodyText style='margin-left:.05in;page-break-after:avoid'>Unlike</p>
  </td>
  <td width=360 valign=top style='width:3.75in;border-top:none;border-left:
  none;border-bottom:solid windowtext .75pt;border-right:solid windowtext 1.5pt;padding:0in 5.4pt 0in 5.4pt'>
  <p class=InfoBlue>[primary competitive alternative]</p>
  </td>
 </tr>
 <tr>
  <td width=186 valign=top style='width:139.5pt;border:solid windowtext 1.5pt;
  border-top:none;background:#BFBFBF;padding:0in 5.4pt 0in 5.4pt'>
  <p class=MsoBodyText style='margin-left:.05in'>Our product</p>
  </td>
  <td width=360 valign=top style='width:3.75in;border-top:none;border-left:
  none;border-bottom:solid windowtext 1.5pt;border-right:solid windowtext 1.5pt;padding:0in 5.4pt 0in 5.4pt'>
  <p class=InfoBlue>[statement of primary differentiation]</p>
  </td>
 </tr>
</table>

<p class=InfoBlue>[A product or system position statement communicates the intent of the
system and the importance of the project to all concerned personnel.]</p>

<h1><a name="3.                  Stakeholder and User Descriptions">3.<span style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span>Stakeholder and User Descriptions</a></h1>

<p class=InfoBlue>[To effectively
provide products and services that meet your stakeholders and users' real
needs, it is necessary to involve all of the stakeholders as part
of the Requirements Modeling process. You must also identify the users of the system and ensure that the
stakeholder community adequately represents them. This section provides a profile of the stakeholders and users
involved in the project, and the key problems that they perceive to be addressed
by the proposed solution. It does not
describe their specific requests or requirements as these are captured in a
separate stakeholder requests artifact. Instead, it provides the background and justification for why the
requirements are needed.]</p>

<h2><a name="3.1               Market Demographics">3.1<span
style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span>Market Demographics</a></h2>

<p class=InfoBlue>[Summarize the key
market demographics that motivate your product decisions. Describe and position
target market segments. Estimate the market?s size and growth by using the
number of potential users, or the amount of money your customers spend trying
to meet needs that your product or enhancement would fulfill. Review major industry
trends and technologies. Answer these strategic questions:</p>

<p class=InfoBlue>?          What is your organization?s reputation
in these markets? </p>

<p class=InfoBlue>?           What would you like it to be? </p>

<p class=InfoBlue>?          How does this product or service
support your goals?]</p>

<h2><a name="3.2               Stakeholder Summary">3.2<span
style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span>Stakeholder Summary</a></h2>

<p class=InfoBlue>[There are a number of stakeholders with an interest in the
development and not all of them are users. Present a summary
list of these non-user stakeholders. (The users are summarized in section 3.3.)]</p>

<table border=1 cellspacing=0 cellpadding=0 style='margin-left:41.4pt;
 border-collapse:collapse;border:none;'>
 <tr>
  <td width=168 valign=top style='width:1.75in;border:solid black .75pt;
  background:#BFBFBF;padding:0in 5.4pt 0in 5.4pt'>
  <p class=MsoBodyText style='margin-left:0in'><b>Name</b></p>
  </td>
  <td width=192 valign=top style='width:2.0in;border:solid black .75pt;
  border-left:none;background:#BFBFBF;padding:0in 5.4pt 0in 5.4pt'>
  <p class=MsoBodyText style='margin-left:0in'><b>Description</b></p>
  </td>
  <td width=204 valign=top style='width:153.0pt;border:solid black .75pt;
  border-left:none;background:#BFBFBF;padding:0in 5.4pt 0in 5.4pt'>
  <p class=MsoBodyText style='margin-left:0in'><b>Responsibilities</b></p>
  </td>
 </tr>
 <tr>
  <td width=168 valign=top style='width:1.75in;border:solid black .75pt;
  border-top:none;padding:0in 5.4pt 0in 5.4pt'>
  <p class=InfoBlue style='margin-left:0in'>[Name
  the stakeholder type.]</p>
  </td>
  <td width=192 valign=top style='width:2.0in;border-top:none;border-left:none;
  border-bottom:solid black .75pt;border-right:solid black .75pt;padding:0in 5.4pt 0in 5.4pt'>
  <p class=InfoBlue>[Briefly describe the stakeholder.]</p>
  </td>
  <td width=204 valign=top style='width:153.0pt;border-top:none;border-left:
  none;border-bottom:solid black .75pt;border-right:solid black .75pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=InfoBlue>[Summarize the stakeholder's key responsibilities with
  regard to the system being developed; that is, their interest as a
  stakeholder. For example, this stakeholder:</p>
  <p class=InfoBlue>- ensures that the system will be maintainable</p>
  <p class=InfoBlue>- ensures that there will be a market demand for the
  product's features</p>
  <p class=InfoBlue>- monitors the project's progress</p>
  <p class=InfoBlue>- approves funding]</p>

  </td>
 </tr>
</table>

<h2><a name="3.3               User Summary">3.3<span
style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span>User Summary</a></h2>

<p class=InfoBlue>[Present a summary
list of all identified users.]</p>

<table border=1 cellspacing=0 cellpadding=0 style='border-collapse: collapse; border-style: none; border-width: medium; margin-left: 41.4pt' width="604">
 <tr style='height:20.9pt'>
  <td width=105 valign=top style='background-color: #BFBFBF; background-repeat: repeat; background-attachment: scroll; height: 20.9pt; border: .75pt solid black; padding-left: 5.4pt; padding-right: 5.4pt; padding-top: 0in; padding-bottom: 0in; background-position: 0%'>
  <p class=MsoBodyText style='margin-left:0in'><b>Name</b></p>
  </td>
  <td width=104 valign=top style='background-color: #BFBFBF; background-repeat: repeat; background-attachment: scroll; height: 20.9pt; border-left-style: none; border-left-width: medium; border-right: .75pt solid black; border-top: .75pt solid black; border-bottom: .75pt solid black; padding-left: 5.4pt; padding-right: 5.4pt; padding-top: 0in; padding-bottom: 0in; background-position: 0%'>
  <p class=MsoBodyText style='margin-left:0in'><b>Description</b></p>
  </td>
  <td width=321 valign=top style='background-color: #BFBFBF; background-repeat: repeat; background-attachment: scroll; height: 20.9pt; border-left-style: none; border-left-width: medium; border-right: .75pt solid black; border-top: .75pt solid black; border-bottom: .75pt solid black; padding-left: 5.4pt; padding-right: 5.4pt; padding-top: 0in; padding-bottom: 0in; background-position: 0%'>
  <b><font size="2">Responsibilities</font></b>
  </td>
  <td width=297 valign=top style='background-color: #BFBFBF; background-repeat: repeat; background-attachment: scroll; height: 20.9pt; border-left-style: none; border-left-width: medium; border-right: .75pt solid black; border-top: .75pt solid black; border-bottom: .75pt solid black; padding-left: 5.4pt; padding-right: 5.4pt; padding-top: 0in; padding-bottom: 0in; background-position: 0%'>
  <p class=MsoBodyText style='margin-left:0in'><b>Stakeholder</b></p>
  </td>
 </tr>
 <tr style='height:48.8pt'>
  <td width=105 valign=top style='height: 48.8pt; border-left: .75pt solid black; border-right: .75pt solid black; border-top-style: none; border-top-width: medium; border-bottom: .75pt solid black; padding-left: 5.4pt; padding-right: 5.4pt; padding-top: 0in; padding-bottom: 0in'>
  <p class=InfoBlue style='margin-left:0in'>[Name
  the user type.]</p>
  </td>
  <td width=104 valign=top style='height: 48.8pt; border-left-style: none; border-left-width: medium; border-right: .75pt solid black; border-top-style: none; border-top-width: medium; border-bottom: .75pt solid black; padding-left: 5.4pt; padding-right: 5.4pt; padding-top: 0in; padding-bottom: 0in'>
  <p class=InfoBlue>[Briefly describe
  what they represent with respect to the system.]</p>
  </td>
  <td width=321 valign=top style='height: 48.8pt; border-left-style: none; border-left-width: medium; border-right: .75pt solid black; border-top-style: none; border-top-width: medium; border-bottom: .75pt solid black; padding-left: 5.4pt; padding-right: 5.4pt; padding-top: 0in; padding-bottom: 0in'>
  <p class=InfoBlue>[List the user's key responsibilities with regard to the
  system being developed; for example:</p>
  <p class=InfoBlue>- captures details</p>
  <p class=InfoBlue>- produces reports</p>
  <p class=InfoBlue>- coordinates work]</p>
  </td>
  <td width=297 valign=top style='height: 48.8pt; border-left-style: none; border-left-width: medium; border-right: .75pt solid black; border-top-style: none; border-top-width: medium; border-bottom: .75pt solid black; padding-left: 5.4pt; padding-right: 5.4pt; padding-top: 0in; padding-bottom: 0in'>
  <p class=InfoBlue>[If the user is not directly represented, identify which
  stakeholder is responsible for representing the user's interests.]</p>
  </td>
 </tr>
</table>

<p class=MsoBodyText>&nbsp;</p>

<h2><a name="3.4               User Environment">3.4<span
style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span>User Environment</a></h2>

<p class=InfoBlue>[Detail the working
environment of the target user. Here are some suggestions:</p>

<ul>
  <li>
    <p class="InfoBlue">Number of people
involved in completing the task? Is this changing?</li>
  <li>
    <p class="InfoBlue">How long is a task
cycle? Amount of time spent in each activity? Is this changing?</li>
  <li>
    <p class="InfoBlue">Any unique
environmental constraints: mobile, outdoors, in-flight, and so on.?</li>
  <li>
    <p class="InfoBlue">Which systems
platforms are in use today? Future platforms?</li>
  <li>
    <p class="InfoBlue">What other systems/applications are in use? Does your
    system need to integrate with them?</li>
</ul>

<p class=InfoBlue>This is where
extracts from the Business Model could be included to outline the task and
business workers involved, and so on.]</p>

<h2><a name="3.5               Stakeholder Profiles">3.5<span style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span>Stakeholder Profiles</a>&nbsp; </h2>

<p class=InfoBlue>[Describe each
stakeholder in the system here by filling in the following table for each
stakeholder. Remember that stakeholder types
can be as divergent as users, departments, and technical developers. A thorough profile
would cover the following topics for each type of stakeholder.]</p>

<h3><a name="3.5.1          &lt;Stakeholder Name&gt;">3.5.1<span
style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span>&lt;Stakeholder Name&gt;</a></h3>

<table border=1 cellspacing=0 cellpadding=0 style='margin-left:36.9pt;
 border-collapse:collapse;border:none;'>
 <tr>
  <td width=126 valign=top style='width:94.5pt;border:solid windowtext .5pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=MsoNormal><b>Representative</b></p>
  </td>
  <td width=463 valign=top style='width:347.4pt;border:solid windowtext .5pt;
  border-left:none;padding:0in 5.4pt 0in 5.4pt'>
  <p class=InfoBlue>[Who is the
  stakeholder representative to the project?  (Optional if documented elsewhere.) 
  What we want here is names.]</p>
  </td>
 </tr>
 <tr>
  <td width=126 valign=top style='width:94.5pt;border:solid windowtext .5pt;
  border-top:none;padding:0in 5.4pt 0in 5.4pt'>
  <p class=MsoNormal><b>Description</b></p>
  </td>
  <td width=463 valign=top style='width:347.4pt;border-top:none;border-left:
  none;border-bottom:solid windowtext .5pt;border-right:solid windowtext .5pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=InfoBlue>[Brief description
  of the stakeholder type.]</p>
  </td>
 </tr>
 <tr>
  <td width=126 valign=top style='width:94.5pt;border:solid windowtext .5pt;
  border-top:none;padding:0in 5.4pt 0in 5.4pt'>
  <p class=MsoNormal><b>Type</b></p>
  </td>
  <td width=463 valign=top style='width:347.4pt;border-top:none;border-left:
  none;border-bottom:solid windowtext .5pt;border-right:solid windowtext .5pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=InfoBlue>[Qualify the
  stakeholder?s expertise, technical background, and degree of
  sophistication?that is, guru, business, expert, casual user, and so on.]</p>
  </td>
 </tr>
 <tr>
  <td width=126 valign=top style='width:94.5pt;border:solid windowtext .5pt;
  border-top:none;padding:0in 5.4pt 0in 5.4pt'>
  <p class=MsoNormal><b>Responsibilities</b></p>
  </td>
  <td width=463 valign=top style='width:347.4pt;border-top:none;border-left:
  none;border-bottom:solid windowtext .5pt;border-right:solid windowtext .5pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=InfoBlue>[List the stakeholder?s key responsibilities with regards
  to the system being developed?that is, their interest as a stakeholder.]</p>
  </td>
 </tr>
 <tr>
  <td width=126 valign=top style='width:94.5pt;border:solid windowtext .5pt;
  border-top:none;padding:0in 5.4pt 0in 5.4pt'>
  <p class=MsoNormal><b>Success Criteria</b></p>
  </td>
  <td width=463 valign=top style='width:347.4pt;border-top:none;border-left:
  none;border-bottom:solid windowtext .5pt;border-right:solid windowtext .5pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=InfoBlue>[How does the
  stakeholder define success? </p>
  <p class=InfoBlue>How is the
  stakeholder rewarded?]</p>
  </td>
 </tr>
 <tr>
  <td width=126 valign=top style='width:94.5pt;border:solid windowtext .5pt;
  border-top:none;padding:0in 5.4pt 0in 5.4pt'>
  <p class=MsoNormal><b>Involvement</b></p>
  </td>
  <td width=463 valign=top style='width:347.4pt;border-top:none;border-left:
  none;border-bottom:solid windowtext .5pt;border-right:solid windowtext .5pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=InfoBlue>[How is the
  stakeholder involved in the project? Relate where possible to Rational Unified Process
  roles?that is, Requirements Reviewer,
  and so on.]</p>
  </td>
 </tr>
 <tr>
  <td width=126 valign=top style='width:94.5pt;border:solid windowtext .5pt;
  border-top:none;padding:0in 5.4pt 0in 5.4pt'>
  <p class=MsoNormal><b>Deliverables</b></p>
  </td>
  <td width=463 valign=top style='width:347.4pt;border-top:none;border-left:
  none;border-bottom:solid windowtext .5pt;border-right:solid windowtext .5pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=InfoBlue>[Are there any
  additional deliverables required by the stakeholder?  These could be project deliverables or
  outputs from the system under development.]</p>
  </td>
 </tr>
 <tr>
  <td width=126 valign=top style='width:94.5pt;border:solid windowtext .5pt;
  border-top:none;padding:0in 5.4pt 0in 5.4pt'>
  <p class=MsoNormal><b>Comments / Issues</b></p>
  </td>
  <td width=463 valign=top style='width:347.4pt;border-top:none;border-left:
  none;border-bottom:solid windowtext .5pt;border-right:solid windowtext .5pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=InfoBlue>[Problems that
  interfere with success and any other relevant information go here.]</p>
  </td>
 </tr>
</table>

<p class=MsoBodyText>&nbsp;</p>

<h2><a name="3.6               User Profiles">3.6<span
style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span>User Profiles</a>&nbsp; </h2>

<p class=InfoBlue>[Describe each
unique user of the system here by filling in the following table for each user
type. Remember user types can be as
divergent as gurus and novices. For example, a guru might need a sophisticated,
flexible tool with cross-platform support, while a novice might need a tool
that is easy to use and user-friendly. A thorough profile covers the
following topics for each type of user.]</p>

<h3><a name="3.6.1          &lt;User Name&gt;">3.6.1<span
style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span>&lt;User Name&gt;<br>
</a></h3>

<table border=1 cellspacing=0 cellpadding=0 style='margin-left:36.9pt;
 border-collapse:collapse;border:none;'>
 <tr>
  <td width=126 valign=top style='width:94.5pt;border:solid windowtext .5pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=MsoNormal><b>Representative</b></p>
  </td>
  <td width=463 valign=top style='width:347.4pt;border:solid windowtext .5pt;
  border-left:none;padding:0in 5.4pt 0in 5.4pt'>
  <p class=InfoBlue>[Who is the user
  representative to the project?  (Optional&nbsp; if documented
  elsewhere.)  This often refers to the
  Stakeholder that represents the set of users, for example, Stakeholder: Stakeholder1.]</p>
  </td>
 </tr>
 <tr>
  <td width=126 valign=top style='width:94.5pt;border:solid windowtext .5pt;
  border-top:none;padding:0in 5.4pt 0in 5.4pt'>
  <p class=MsoNormal><b>Description</b></p>
  </td>
  <td width=463 valign=top style='width:347.4pt;border-top:none;border-left:
  none;border-bottom:solid windowtext .5pt;border-right:solid windowtext .5pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=InfoBlue>[A brief
  description of the user type.]</p>
  </td>
 </tr>
 <tr>
  <td width=126 valign=top style='width:94.5pt;border:solid windowtext .5pt;
  border-top:none;padding:0in 5.4pt 0in 5.4pt'>
  <p class=MsoNormal><b>Type</b></p>
  </td>
  <td width=463 valign=top style='width:347.4pt;border-top:none;border-left:
  none;border-bottom:solid windowtext .5pt;border-right:solid windowtext .5pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=InfoBlue>[Qualify the
  user?s expertise, technical background, and degree of sophistication?that is,
  guru, casual user, and so on.] </p>
  </td>
 </tr>
 <tr>
  <td width=126 valign=top style='width:94.5pt;border:solid windowtext .5pt;
  border-top:none;padding:0in 5.4pt 0in 5.4pt'>
  <p class=MsoNormal><b>Responsibilities</b></p>
  </td>
  <td width=463 valign=top style='width:347.4pt;border-top:none;border-left:
  none;border-bottom:solid windowtext .5pt;border-right:solid windowtext .5pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=InfoBlue>[List the user?s
  key responsibilities with regard to the system being developed? that is,
  captures details, produces reports, coordinates work, and so on.]</p>
  </td>
 </tr>
 <tr>
  <td width=126 valign=top style='width:94.5pt;border:solid windowtext .5pt;
  border-top:none;padding:0in 5.4pt 0in 5.4pt'>
  <p class=MsoNormal><b>Success Criteria</b></p>
  </td>
  <td width=463 valign=top style='width:347.4pt;border-top:none;border-left:
  none;border-bottom:solid windowtext .5pt;border-right:solid windowtext .5pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=InfoBlue>[How does the user
  define success?</p>
  <p class=InfoBlue> How is the user rewarded?]</p>
  </td>
 </tr>
 <tr>
  <td width=126 valign=top style='width:94.5pt;border:solid windowtext .5pt;
  border-top:none;padding:0in 5.4pt 0in 5.4pt'>
  <p class=MsoNormal><b>Involvement</b></p>
  </td>
  <td width=463 valign=top style='width:347.4pt;border-top:none;border-left:
  none;border-bottom:solid windowtext .5pt;border-right:solid windowtext .5pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=InfoBlue>[How the user is
  involved in the project? Relate where possible to Rational Unified Process roles?that is,
  Requirements Reviewer, and the like.]</p>
  </td>
 </tr>
 <tr>
  <td width=126 valign=top style='width:94.5pt;border:solid windowtext .5pt;
  border-top:none;padding:0in 5.4pt 0in 5.4pt'>
  <p class=MsoNormal><b>Deliverables</b></p>
  </td>
  <td width=463 valign=top style='width:347.4pt;border-top:none;border-left:
  none;border-bottom:solid windowtext .5pt;border-right:solid windowtext .5pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=InfoBlue>[Are there any
  deliverables the user produces and, if so, for whom?]</p>
  </td>
 </tr>
 <tr>
  <td width=126 valign=top style='width:94.5pt;border:solid windowtext .5pt;
  border-top:none;padding:0in 5.4pt 0in 5.4pt'>
  <p class=MsoNormal><b>Comments / Issues</b></p>
  </td>
  <td width=463 valign=top style='width:347.4pt;border-top:none;border-left:
  none;border-bottom:solid windowtext .5pt;border-right:solid windowtext .5pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=InfoBlue>[Problems that
  interfere with success and any other relevant information go here. These would include
  trends that make the user?s job easier or harder.]</p>
  </td>
 </tr>
</table>

<p class=MsoBodyText>&nbsp;</p>

<h2><a name="3.7               Key Stakeholder / User Needs">3.7<span
style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span>Key Stakeholder or User Needs</a></h2>

<p class=InfoBlue>[List the key
problems with existing solutions as perceived by the stakeholder. Clarify the
following issues for each problem:</p>

<p class=InfoBlue>?          What are the reasons for this problem?
</p>

<p class=InfoBlue>?          How is it solved now?</p>

<p class=InfoBlue>?          What solutions does the stakeholder or
user want?]</p>

<p class=InfoBlue>[It is important to
understand the <b>relative</b> importance the stakeholder or user places on
solving each problem. Ranking and cumulative voting techniques indicate
problems that <b>must</b> be
solved versus issues they would like addressed.</p>

<p class=InfoBlue>Fill in the
following table.  When using Rational RequisitePro to capture the Needs, this could be an
extract or report from that tool.]</p>

<table border=1 cellspacing=0 cellpadding=0 style='border-collapse: collapse; border-style: none; border-width: medium' width="703">
 <tr>
  <td width=186 valign=top style='background-color: #BFBFBF; background-repeat: repeat; background-attachment: scroll; border: .75pt solid black; padding-left: 5.4pt; padding-right: 5.4pt; padding-top: 0in; padding-bottom: 0in; background-position: 0%'>
  <p class=MsoBodyText style='margin-left:0in'><b>Need</b></p>
  </td>
  <td width=60 valign=top style='background-color: #BFBFBF; background-repeat: repeat; background-attachment: scroll; border-left-style: none; border-left-width: medium; border-right: .75pt solid black; border-top: .75pt solid black; border-bottom: .75pt solid black; padding-left: 5.4pt; padding-right: 5.4pt; padding-top: 0in; padding-bottom: 0in; background-position: 0%'>
  <p class=MsoBodyText style='margin-left:0in'><b>Priority</b></p>
  </td>
  <td width=90 valign=top style='background-color: #BFBFBF; background-repeat: repeat; background-attachment: scroll; border-left-style: none; border-left-width: medium; border-right: .75pt solid black; border-top: .75pt solid black; border-bottom: .75pt solid black; padding-left: 5.4pt; padding-right: 5.4pt; padding-top: 0in; padding-bottom: 0in; background-position: 0%'>
  <p class=MsoBodyText style='margin-left:0in'><b>Concerns</b></p>
  </td>
  <td width=136 valign=top style='background-color: #BFBFBF; background-repeat: repeat; background-attachment: scroll; border-left-style: none; border-left-width: medium; border-right: .75pt solid black; border-top: .75pt solid black; border-bottom: .75pt solid black; padding-left: 5.4pt; padding-right: 5.4pt; padding-top: 0in; padding-bottom: 0in; background-position: 0%'>
  <p class=MsoBodyText style='margin-left:0in'><b>Current Solution</b></p>
  </td>
  <td width=155 colspan=2 valign=top style='background-color: #BFBFBF; background-repeat: repeat; background-attachment: scroll; border-left-style: none; border-left-width: medium; border-right: .75pt solid black; border-top: .75pt solid black; border-bottom: .75pt solid black; padding-left: 5.4pt; padding-right: 5.4pt; padding-top: 0in; padding-bottom: 0in; background-position: 0%'>
  <p class=MsoBodyText style='margin-left:0in'><b>Proposed Solutions</b></p>
  </td>
 </tr>
 <tr>
  <td width=186 valign=top style='border-left: .75pt solid black; border-right: .75pt solid black; border-top-style: none; border-top-width: medium; border-bottom: .75pt solid black; padding-left: 5.4pt; padding-right: 5.4pt; padding-top: 0in; padding-bottom: 0in'>
  <p class=MsoBodyText style='margin-left:0in'>Broadcast
  messages</p>
  </td>
  <td width=60 valign=top style='border-left-style: none; border-left-width: medium; border-right: .75pt solid black; border-top-style: none; border-top-width: medium; border-bottom: .75pt solid black; padding-left: 5.4pt; padding-right: 5.4pt; padding-top: 0in; padding-bottom: 0in'>
  <p class=MsoBodyText style='margin-left:0in'>&nbsp;</p>
  </td>
  <td width=90 valign=top style='border-left-style: none; border-left-width: medium; border-right: .75pt solid black; border-top-style: none; border-top-width: medium; border-bottom: .75pt solid black; padding-left: 5.4pt; padding-right: 5.4pt; padding-top: 0in; padding-bottom: 0in'>
  <p class=MsoBodyText style='margin-left:0in'>&nbsp;</p>
  </td>
  <td width=127 colspan=2 valign=top style='border-left-style: none; border-left-width: medium; border-right: .75pt solid black; border-top-style: none; border-top-width: medium; border-bottom: .75pt solid black; padding-left: 5.4pt; padding-right: 5.4pt; padding-top: 0in; padding-bottom: 0in'>
  <p class=MsoBodyText style='margin-left:0in'>&nbsp;</p>
  </td>
  <td width=164 valign=top style='border-left-style: none; border-left-width: medium; border-right: .75pt solid black; border-top-style: none; border-top-width: medium; border-bottom: .75pt solid black; padding-left: 5.4pt; padding-right: 5.4pt; padding-top: 0in; padding-bottom: 0in'>
  <p class=MsoBodyText style='margin-left:0in'>&nbsp;</p>
  </td>
 </tr>
 <tr height=0>
  <td width=202 style='border-style: none; border-width: medium'></td>
  <td width=75 style='border-style: none; border-width: medium'></td>
  <td width=105 style='border-style: none; border-width: medium'></td>
  <td width=151 style='border-style: none; border-width: medium'></td>
  <td width=1 style='border-style: none; border-width: medium'></td>
  <td width=179 style='border-style: none; border-width: medium'></td>
 </tr>
</table>

<p class=MsoBodyText>&nbsp;</p>

<h2><a name="3.8               Alternatives and Competition">3.8<span
style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span>Alternatives and Competition</a></h2>

<p class=InfoBlue>[Identify
alternatives the stakeholder perceives as available. These can include buying a
competitor?s product, building a homegrown solution or simply maintaining the
status quo. List any known competitive choices that exist or may become
available. Include the major strengths and weaknesses of each competitor as
perceived by the stakeholder or user.]</p>

<h3><a name="3.8.1          &lt;aCompetitor&gt;">3.8.1<span
style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span>&lt;aCompetitor&gt;</a></h3>

<h3><a name="3.8.2          &lt;anotherCompetitor&gt;">3.8.2<span
style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span>&lt;anotherCompetitor&gt;</a></h3>

<h2><a name="3.9       Development Alternatives Considered">3.9&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Development Alternatives Considered</a></h2>

<p class="InfoBlue">[In this subsection, describe any alternatives to the
proposed product that were considered, and any associated trade studies.]</p>

<h1><a name="4.                  Product Overview">4.<span
style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span>Product Overview</a></h1>

<p class=InfoBlue>[This section provides a high level view of the product
capabilities, interfaces to other systems, and systems configurations.]&nbsp; </p>

<h2><a name="4.1               Product Perspective">4.1<span
style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span>Product Perspective</a></h2>

<p class=InfoBlue>[This subsection of the <b>Vision</b> document puts the
product in perspective to other related products and the user?s environment. If
the product is independent and totally self-contained, state it here. If the
product is a component of a larger system, then this subsection relates
how these systems interact and identifies the relevant interfaces between
the systems. One easy way to display the major components of the larger system,
interconnections, and external interfaces is with a block diagram.&nbsp;</p>

<p class=InfoBlue>Identify the operational, organizational and developmental
impacts on the stakeholders and other systems.]</p>

<h2><a name="4.2               Summary of Capabilities">4.2<span
style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span>Summary of Capabilities</a></h2>

<p class=InfoBlue>[Summarize the major benefits and features the product will
provide. For example, a <b>Vision</b> document for a customer support system
may use this part to address problem documentation, routing, and status
reporting without mentioning the amount of detail each of these functions requires.</p>

<p class=InfoBlue>Organize the functions so the list is understandable to the
customer or to anyone else reading the document for the first time. A simple
table listing the key benefits and their supporting features might suffice. For
example:]</p>

<p class=MsoNormal style='margin-top:0in;margin-right:.05in;margin-bottom:0in;
margin-left:2.0in;margin-bottom:.0001pt;text-indent:.5in;page-break-after:avoid'><b>Table
4-1&nbsp;&nbsp; Customer Support System</b></p>

<table border=1 cellspacing=0 cellpadding=0 style='border-collapse: collapse; border-style: none; border-width: medium; margin-left: 59.4pt' width="535">
 <tr>
  <td width=216 valign=top style='border-left: 1.5pt solid navy; border-right: .75pt solid navy; border-top: 1.5pt solid navy; border-bottom: .75pt solid navy; padding-left: 5.4pt; padding-right: 5.4pt; padding-top: 0in; padding-bottom: 0in'>
  <p class=MsoNormal style='margin-right:.05in;page-break-after:avoid'><b><span style='color:black'>Customer
  Benefit</span></b></p>
  </td>
  <td width=286 valign=top style='border-left-style: none; border-left-width: medium; border-right: 1.5pt solid navy; border-top: 1.5pt solid navy; border-bottom: .75pt solid navy; padding-left: 5.4pt; padding-right: 5.4pt; padding-top: 0in; padding-bottom: 0in'>
  <p class=MsoNormal style='margin-right:.1in'><b><span style='color:black'>Supporting Features</span></b></p>
  </td>
 </tr>
 <tr>
  <td width=216 valign=top style='border-left: 1.5pt solid navy; border-right: .75pt solid navy; border-top-style: none; border-top-width: medium; border-bottom: .75pt solid navy; padding-left: 5.4pt; padding-right: 5.4pt; padding-top: 0in; padding-bottom: 0in'>
  <p class=MsoNormal style='margin-right:-.7pt;page-break-after:avoid'><span
  style='color:black'>New support staff can quickly get up to speed.</span></p>
  </td>
  <td width=286 valign=top style='border-left-style: none; border-left-width: medium; border-right: 1.5pt solid navy; border-top-style: none; border-top-width: medium; border-bottom: .75pt solid navy; padding-left: 5.4pt; padding-right: 5.4pt; padding-top: 0in; padding-bottom: 0in'>
  <p class=MsoNormal style='margin-right:.1in'><span style='color:black'>Knowledge
  base assists support personnel in quickly identifying known fixes and
  workarounds.</span></p>
  </td>
 </tr>
 <tr>
  <td width=216 valign=top style='border-left: 1.5pt solid navy; border-right: .75pt solid navy; border-top-style: none; border-top-width: medium; border-bottom: .75pt solid navy; padding-left: 5.4pt; padding-right: 5.4pt; padding-top: 0in; padding-bottom: 0in'>
  <p class=MsoNormal style='margin-right:-.7pt;page-break-after:avoid'><span
  style='color:black'>Customer satisfaction is improved because nothing falls
  through the cracks.</span></p>
  </td>
  <td width=286 valign=top style='border-left-style: none; border-left-width: medium; border-right: 1.5pt solid navy; border-top-style: none; border-top-width: medium; border-bottom: .75pt solid navy; padding-left: 5.4pt; padding-right: 5.4pt; padding-top: 0in; padding-bottom: 0in'>
  <p class=MsoNormal style='margin-right:.1in'><span style='color:black'>Problems
  are uniquely itemized, classified and tracked throughout the resolution
  process. Automatic notification occurs for any aging issues.</span></p>
  </td>
 </tr>
 <tr>
  <td width=216 valign=top style='border-left: 1.5pt solid navy; border-right: .75pt solid navy; border-top-style: none; border-top-width: medium; border-bottom: .75pt solid navy; padding-left: 5.4pt; padding-right: 5.4pt; padding-top: 0in; padding-bottom: 0in'>
  <p class=MsoNormal style='margin-right:-.7pt;page-break-after:avoid'><span
  style='color:black'>Management can identify problem areas and gauge staff
  workload.</span></p>
  </td>
  <td width=286 valign=top style='border-left-style: none; border-left-width: medium; border-right: 1.5pt solid navy; border-top-style: none; border-top-width: medium; border-bottom: .75pt solid navy; padding-left: 5.4pt; padding-right: 5.4pt; padding-top: 0in; padding-bottom: 0in'>
  <p class=MsoNormal style='margin-right:.1in'><span style='color:black'>Trend
  and distribution reports allow high level review of problem status.</span></p>
  </td>
 </tr>
 <tr>
  <td width=216 valign=top style='border-left: 1.5pt solid navy; border-right: .75pt solid navy; border-top-style: none; border-top-width: medium; border-bottom: .75pt solid navy; padding-left: 5.4pt; padding-right: 5.4pt; padding-top: 0in; padding-bottom: 0in'>
  <p class=MsoNormal style='margin-right:-.7pt;page-break-after:avoid'><span
  style='color:black'>Distributed support teams can work together to solve
  problems.</span></p>
  </td>
  <td width=286 valign=top style='border-left-style: none; border-left-width: medium; border-right: 1.5pt solid navy; border-top-style: none; border-top-width: medium; border-bottom: .75pt solid navy; padding-left: 5.4pt; padding-right: 5.4pt; padding-top: 0in; padding-bottom: 0in'>
  <p class=MsoNormal style='margin-right:.1in'><span style='color:black'>Replication
  server allows current database information to be shared across the enterprise.</span></p>
  </td>
 </tr>
 <tr>
  <td width=216 valign=top style='border-left: 1.5pt solid navy; border-right: .75pt solid navy; border-top-style: none; border-top-width: medium; border-bottom: 1.5pt solid navy; padding-left: 5.4pt; padding-right: 5.4pt; padding-top: 0in; padding-bottom: 0in'>
  <p class=MsoNormal style='margin-right:-.7pt;page-break-after:avoid'><span
  style='color:black'>Customers can help themselves, lowering support costs and
  improving response time.</span></p>
  </td>
  <td width=286 valign=top style='border-left-style: none; border-left-width: medium; border-right: 1.5pt solid navy; border-top-style: none; border-top-width: medium; border-bottom: 1.5pt solid navy; padding-left: 5.4pt; padding-right: 5.4pt; padding-top: 0in; padding-bottom: 0in'>
  <p class=MsoNormal style='margin-right:.1in'><span style='color:black'>Knowledge
  base can be made available over the Internet. Includes hypertext search
  capabilities and graphical query engine.</span></p>
  </td>
 </tr>
</table>

<h2><a name="4.3               Assumptions and Dependencies">4.3<span
style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span>Assumptions and Dependencies</a></h2>

<p class=InfoBlue>[List each of the factors that affects the features stated in
the <b>Vision</b> document. List assumptions that, if changed, will alter the <b>Vision
</b>document. For example, the <b>Vision</b> is constructed in the context of
some larger enterprise, and if anything changes in that context, the <b>Vision</b>
may need to change. This may include, for example, economic, political, legal or
environmental factors. The <b>Vision</b> may also have dependencies on the
availability of equipment, software or other system components, or the
availability of particular expertise or skills.]</p>

<h2><a name="4.4               Cost and Pricing">4.4<span
style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span>Cost and Pricing</a></h2>

<p class=InfoBlue>[For products sold to external customers and for many in-house
systems, cost and pricing issues can directly impact the system's definition and implementation. In this section, record any cost
and pricing constraints that are relevant. For example, distribution costs (#
of diskettes, # of CD-ROMs, CD mastering) or other cost of goods sold constraints
(manuals, packaging) may be material to the projects success, or irrelevant,
depending on the nature of the system.]</p>

<h2><a name="4.5               Licensing and Installation">4.5<span
style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span>Licensing and Installation</a></h2>

<p class=InfoBlue>[Licensing and installation issues can also directly impact
the development effort. For example, the need to support access controls, serializing, password
security or network licensing will create additional requirements of the system
that must be considered in the development effort.</p>

<p class=InfoBlue>Installation requirements may also affect software
construction, or create
the need for separate installation software. Physical systems may also impose
special installation requirements, if they are subject to particular security or
survivability constraints, for example.]</p>

<h1><a name="5.                  Product Features">5.<span
style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span>Product Features</a></h1>

<p class=InfoBlue>[List and briefly describe the product features. Features are
the high-level capabilities of the system that are necessary to deliver
benefits to the users. Also, describe with each feature any associated
performance characteristics - say 'how well' something is to be done, along some
dimension: for example, along the time dimension, response time, transaction
rate. The word 'feature' is not chosen to have any special
significance, you may prefer 'capability' or 'function', all describing
something the system or product has to do. Each feature is an externally desired service that
typically requires a series of inputs to achieve the desired result. For
example, a feature of a problem tracking system might be the ability to provide
trending reports. As the use-case model takes shape, update the description to
refer to the use cases.</p>

<p class=InfoBlue>Because the <b>Vision</b> document is reviewed by a wide
variety of involved personnel, the level of detail needs to be general enough for
everyone to understand. However, enough detail must be available to provide
the team with the information they need to create a use-case model.</p>

<p class=InfoBlue>To effectively manage complexity, we recommend
for any new system, or an increment to an existing system, capabilities are
abstracted to a high enough level so 25-99 features result. These features
provide the fundamental basis for product definition, scope management, and
project management. Each feature will be expanded in greater detail in the use-case
model, or in natural-language, say, if the project elects not to produce use
cases.</p>

<p class=InfoBlue>Throughout this section, each feature will be externally
perceivable by users, operators or other external systems. These features
should include a description of functionality and any relevant usability issues
that must be addressed. The following guidelines apply:</p>

<p class=InfoBlue style='margin-left:27.0pt;text-indent:-27.0pt'>?          Avoid design. Keep feature
descriptions at a general level. Focus on capabilities needed and why (not
how)   they should be implemented.</p>

<p class=InfoBlue style='margin-left:27.0pt;text-indent:-27.0pt'>?          If you are using the
Rational RequisitePro
toolkit, all need to be selected as requirements of type for easy reference and
tracking.]</p>

<h2><a name="5.1               Features">5.1<span
style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span>Features</a></h2>

<h3><a name="5.1.1     &lt;aFeature&gt;">5.1.1&nbsp;&nbsp;&nbsp;&nbsp;
&lt;aFeature&gt;</a></h3>

<h3><a name="5.1.2     &lt;anotherFeature&gt;">5.1.2&nbsp;&nbsp;&nbsp;&nbsp;
&lt;anotherFeature&gt;</a></h3>

<h2><a name="5.2               Operational Scenarios">5.2<span
style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span>Operational Scenarios</a></h2>

<p class="InfoBlue">[Describe a few usages of the product or system that
illustrate some interesting or important interactions between the system and its
users, its environment, and/or other systems.]</p>

<h2><a name="5.3               Support Provision">5.3<span
style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span>Support Provision</a></h2>

<p class="InfoBlue">[In this subsection, describe how, in concept, support is to
be provided, including descriptions of the support organization, equipment,
maintenance cycles and supply arrangements.]</p>

<h1><a name="6.                  Constraints">6.<span
style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span>Constraints</a> </h1>

<p class=InfoBlue>[Note any design constraints, external constraints or other
dependencies.]</p>

<h1><a name="7.                  Quality Ranges">7.<span
style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span>Quality Ranges</a> </h1>

<p class=InfoBlue>[Define the quality ranges for performance, robustness, fault
tolerance, usability, and similar characteristics that are not captured in the
Feature Set.]</p>

<h1><a name="8.                  Precedence and Priority">8.<span
style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span>Precedence and Priority</a></h1>

<p class=InfoBlue>[Define the priority of the different system features.]</p>

<h1><a name="9.                  Other Product Requirements">9.<span
style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span>Other Product Requirements</a></h1>

<p class=InfoBlue>[At a high-level, list applicable standards, hardware or
platform requirements, performance requirements, and environmental
requirements.]</p>

<h2><a name="9.1               Applicable Standards">9.1<span
style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span>Applicable Standards</a></h2>

<p class=InfoBlue>[List all standards with which the product must comply. These
can include legal and regulatory (FDA, UCC) communications standards (TCP/IP,
ISDN), platform compliance standards (Windows, UNIX, and so on), and quality and
safety standards (UL, ISO, CMM).]</p>

<h2><a name="9.2               System Requirements">9.2<span
style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span>System Requirements</a></h2>

<p class=InfoBlue>[For software system development, define any system requirements necessary to support the
application. These can include the supported host operating systems and network
platforms, configurations, memory, peripherals, and companion software.]</p>

<h2><a name="9.3               Performance Requirements">9.3<span
style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span>Performance Requirements</a></h2>

<p class=InfoBlue>[Use this section to detail performance requirements.
Performance issues can include such items as user load factors, bandwidth or
communication capacity, throughput, accuracy, and reliability or response times
under a variety of loading conditions.]</p>

<h2><a name="9.4               Environmental Requirements">9.4<span
style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span>Environmental Requirements</a></h2>

<p class=InfoBlue>[Detail environmental requirements as needed. For physical systems, environmental issues can include temperature, shock, humidity,
radiation, and so forth. For software systems, environmental factors can include
usage conditions, user environment, resource availability, maintenance issues,
and error handling and recovery.]</p>

<h2><a name="9.5       Physical Requirements">9.5&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Physical Requirements</a></h2>

<p class=InfoBlue>[If there are any physical requirements, such as weight or
mass limits or size limits, describe them in this subsection.]</p>

<h1><a name="10.             Documentation Requirements">10.<span
style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span>Documentation Requirements</a></h1>

<p class=InfoBlue>[This section describes the documentation that must be
developed to support successful system deployment.]</p>

<h2><a name="10.1            User Manual">10.1<span
style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span>User Manual</a></h2>

<p class=InfoBlue>[Describe the purpose and contents of the User Manual.
Discuss desired length, level of detail, need for index, glossary of terms,
tutorial versus reference manual strategy, and so on. Formatting and printing constraints
must be identified also.]</p>

<h2><a name="10.2            On-line Help">10.2<span
style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span>Online Help</a></h2>

<p class=InfoBlue>[Many systems provide online help to assist
the user. The nature of these systems is unusual, as
they combine aspects of programming (hyperlinks, and so on) with aspects of technical
writing such as organization and presentation. Many have found the development of
online help system is a project within a project that benefits from up-front
scope management and planning activity.]</p>

<h2><a name="10.3            Installation Guides, Configuration, Read Me File">10.3<span
style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span>Installation Guides, Configuration, and Read Me File</a></h2>

<p class=InfoBlue>[A document that includes installation instructions and
configuration guidelines is important to a full solution offering. Also, a Read
Me file is typically included as a standard component. The Read Me file can include
a &quot;What's New With This Release? section, and a discussion of
compatibility issues with earlier releases. Most users also appreciate
documentation defining any known bugs and workarounds in the Read Me file.]</p>

<h2><a name="10.4            Labeling and Packaging">10.4<span
style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span>Labeling and Packaging</a></h2>

<p class=InfoBlue>[Modern systems strive to provide a consistent
look and feel that begins with product packaging and manifests through
installation menus, splash screens, help systems, GUI dialogs, and so on. This
section defines the needs and types of labeling to be incorporated into the
system. Examples include copyright and patent notices, corporate logos,
standardized icons and other graphic elements, and so forth.]</p>

  <h1><a name="A.             Feature Attributes">A.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    Feature Attributes</a></h1>

<p class=InfoBlue>[Features are given attributes that can be used to
evaluate, track, prioritize, and manage the product items proposed for
implementation. All requirement types and attributes are outlined in the
Requirements Management Plan, however you may wish to list and briefly describe the attributes for features that have been chosen.
The following
subsections represent a set of suggested feature attributes.]</p>

<h2><a name="A.1            Status">A.1<span
style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span>Status</a></h2>

<p class=InfoBlue>[Set after negotiation and review by the project management
team. Tracks progress during definition of the project baseline.]</p>

<table border=1 cellspacing=0 cellpadding=0 style='margin-left:75pt;
 border-collapse:collapse;border:none;'>
 <tr>
  <td width=94 valign=top style='width:70.5pt;border:solid black 1.5pt;
  border-right:solid black .75pt;padding:0in 5.4pt 0in 5.4pt'>
  <p class=MsoBodyText style='margin-left:.05in'>Proposed</p>
  </td>
  <td width=387 valign=top style='width:290.4pt;border:solid black 1.5pt;
  border-left:none;padding:0in 5.4pt 0in 5.4pt'>
  <p class=InfoBlue>[Used to describe features that are under discussion but
  have not yet been reviewed and accepted by the &quot;official channel,&quot;
  such as a working group consisting of representatives from the project team,
  product management, and user or customer community.]</p>
  </td>
 </tr>
 <tr>
  <td width=94 valign=top style='width:70.5pt;border-top:none;border-left:solid black 1.5pt;
  border-bottom:solid black .75pt;border-right:solid black .75pt;padding:0in 5.4pt 0in 5.4pt'>
  <p class=MsoBodyText style='margin-left:.05in'>Approved</p>
  </td>
  <td width=387 valign=top style='width:290.4pt;border-top:none;border-left:
  none;border-bottom:solid black .75pt;border-right:solid black 1.5pt;padding:0in 5.4pt 0in 5.4pt'>
  <p class=InfoBlue>[Capabilities that are deemed useful and feasible, and have
  been approved for implementation by the official channel. ]</p>
  </td>
 </tr>
 <tr>
  <td width=94 valign=top style='width:70.5pt;border-top:none;border-left:solid black 1.5pt;
  border-bottom:solid black 1.5pt;border-right:solid black .75pt;padding:0in 5.4pt 0in 5.4pt'>
  <p class=MsoBodyText style='margin-left:.05in'>Incorporated</p>
  </td>
  <td width=387 valign=top style='width:290.4pt;border-top:none;border-left:
  none;border-bottom:solid black 1.5pt;border-right:solid black 1.5pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=InfoBlue>[Features incorporated into the product baseline at a
  specific point in time.]</p>
  </td>
 </tr>
</table>

<h2><a name="A.2            Benefit">A.2<span
style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span>Benefit</a></h2>

<p class=InfoBlue>[Set by Marketing, the product manager or the business
analyst. All requirements are not created equal. Ranking requirements by their
relative benefit to the user opens a dialogue with customers, analysts, and
members of the development team. Used in managing scope and determining
development priority.]<span style='color:black'></span></p>

<table border=1 cellspacing=0 cellpadding=0 style='margin-left:75pt;
 border-collapse:collapse;border:none;'>
 <tr>
  <td width=78 valign=top style='width:58.85pt;border:solid black 1.5pt;
  border-right:solid black .75pt;padding:0in 5.4pt 0in 5.4pt'>
  <p class=MsoBodyText style='margin-left:.05in;page-break-after:avoid'>Critical</p>
  </td>
  <td width=403 valign=top style='width:302.05pt;border:solid black 1.5pt;
  border-left:none;padding:0in 5.4pt 0in 5.4pt'>
  <p class=InfoBlue>[Essential features. Failure to implement means the system
  will not meet customer needs. All critical features must be implemented in
  the release or the schedule will slip.]</p>
  </td>
 </tr>
 <tr>
  <td width=78 valign=top style='width:58.85pt;border-top:none;border-left:
  solid black 1.5pt;border-bottom:solid black .75pt;border-right:solid black .75pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=MsoBodyText style='margin-left:.05in;page-break-after:avoid'>Important</p>
  </td>
  <td width=403 valign=top style='width:302.05pt;border-top:none;border-left:
  none;border-bottom:solid black .75pt;border-right:solid black 1.5pt;padding:0in 5.4pt 0in 5.4pt'>
  <p class=InfoBlue>[Features important to the effectiveness and efficiency of
  the system for most uses. The functionality cannot be easily provided
  in some other way. Lack of inclusion of an important feature may affect
  customer or user satisfaction, or even revenue, but release will not be
  delayed due to lack of any important feature.]</p>
  </td>
 </tr>
 <tr>
  <td width=78 valign=top style='width:58.85pt;border-top:none;border-left:
  solid black 1.5pt;border-bottom:solid black 1.5pt;border-right:solid black .75pt;padding:0in 5.4pt 0in 5.4pt'>
  <p class=MsoBodyText style='margin-left:.05in'>Useful</p>
  </td>
  <td width=403 valign=top style='width:302.05pt;border-top:none;border-left:
  none;border-bottom:solid black 1.5pt;border-right:solid black 1.5pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=InfoBlue>[Features that support less typical usage, and in
  consequence will be used less frequently, or for which reasonably efficient workarounds can be
  achieved. No significant revenue or customer satisfaction impact can be
  expected if such an item is not included in a release.]</p>
  </td>
 </tr>
</table>

<p class=Paragraph4>&nbsp;</p>

<h2><a name="A.3            Effort">A.3<span
style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span>Effort</a></h2>

<p class=InfoBlue>[Set by the development team. Because some features require
more time and resources than others, estimating the number of team or
person-weeks, or some measure of size that correlates with effort (such as lines of code required or function
points for software), is the
best way to gauge complexity and set expectations of what can and cannot be
accomplished in a given time frame. Used in managing scope and determining
development priority.]</p>

<h2><a name="A.4            Risk">A.4<span
style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span>Risk</a></h2>

<p class=InfoBlue>[Set by development team based on the probability the project
will experience undesirable events, such as cost overruns, schedule delays or
even cancellation. Most project managers find categorizing risks as high,
medium, and low is sufficient, although finer gradations are possible. Risk can
often be indirectly assessed by measuring the uncertainty (range) of the
projects team's schedule estimate.]</p>

<h2><a name="A.5            Stability">A.5<span
style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span>Stability</a></h2>

<p class=InfoBlue>[Set by analyst and development team based on the probability
the feature will change or the team?s understanding of the feature will change.
Used to help establish development priorities and determine those items for
which additional elicitation is the appropriate next action.]</p>

<h2><a name="A.6            Target Release">A.6<span
style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span>Target Release</a></h2>

<p class=InfoBlue>[Records the intended product version in which the feature
will first appear. This field can be used to allocate features from a <b>Vision
</b>document into a particular baseline release. When combined with the status
field, your team can propose, record, and discuss various features of the
release without committing them to development. Only features whose Status is
set to Incorporated and whose Target Release is defined will be implemented.
When scope management occurs, the Target Release Version Number can be
increased so the item will remain in the <b>Vision</b> document but will be
scheduled for a later release.]</p>

<h2><a name="A.7            Assigned To">A.7<span
style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span>Assigned To</a></h2>

<p class=InfoBlue>[In many projects, features will be assigned to &quot;feature
teams&quot; responsible for further elicitation, capturing and refining the requirements, and implementation. This simple pull-down list will help everyone
on the project team to understand responsibilities better.]</p>

<h2><a name="A.8            Reason">A.8<span
style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span>Reason</a></h2>

<p class=InfoBlue>[This text field is used to track the source of the requested
feature. Requirements exist for specific reasons. This field records an
explanation or a reference to an explanation. For example, the reference might
be to a page and line number of a product requirement specification or to a
minute marker on a video of an important customer review.]</p>

<h1 style='margin-left:0in;text-indent:0in;'>&nbsp;</h1>

</div>

</body>

</html>
