<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2// EN">
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>System Requirements Specification</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'>System Requirements Specification</p>

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

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

<p class=MsoNormal>&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 align=right style='text-align:right'>&nbsp;</p>

  <p class=InfoBlue><i>[<b>Note:</b> 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 must be deleted before publishing the document. A paragraph entered following 
    this style is automatically set to normal (style=Body Text).]</i></p>

</div>

<p>

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

</p>

<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;</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;</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;</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;</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;</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;</p>

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

<p class=MsoToc2><a href="#2.1               Use-Case Model Survey">2.1 Use-Case Model Survey</a>&nbsp;</p>

<p class=MsoToc2><a href="#2.2               Assumptions and Dependencies">2.2 Assumptions and Dependencies</a></p>

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

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

<p class=MsoToc3><a href="#3.1.1           Use-Case Reports">3.1.1 Use-Case Reports&nbsp;</a></p>

<p class=MsoToc3><a href="#3.1.2           Additional Functionality">3.1.2 Additional Functionality</a></p>

</div>

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

<div class=Section2> 
  <p class=MsoToc3><a href="#3.2.1          Usability">3.2.1 Usability&nbsp;</a></p>
  <p class=MsoToc3><a href="#3.2.2&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Reliability">3.2.2 
    Reliability&nbsp;</a></p>
  <p class=MsoToc3><a href="#3.2.3&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Performance">3.2.3 
    Performance&nbsp;</a></p>
  <p class=MsoToc3><a href="#3.2.4&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Supportability">3.2.4 
    Supportability&nbsp;</a></p>
  <p class=MsoToc3><a href="#3.2.5&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Design Constraints">3.2.5 
    Design Constraints&nbsp;</a></p>
  <p class=MsoToc3><a href="#3.2.6&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Additional Systems Engineering Considerations">3.2.6 
    Additional Systems Engineering Considerations&nbsp;</a></p>
  <p class=MsoToc7><a href="#3.2.6.1&nbsp;&nbsp;Physical Requirements">3.2.6.1 
    Physical Requirements&nbsp;</a></p>
  <p class=MsoToc7><a href="#3.2.6.2&nbsp;&nbsp;Environmental Requirements">3.2.6.2 
    Environmental Requirements&nbsp;</a></p>
  <p class=MsoToc7><a href="#3.2.6.3&nbsp;&nbsp;Other Product Assurance Requirements">3.2.6.3 
    Other Product Assurance Requirements&nbsp;</a></p>
  <p class=MsoToc7><a href="#3.2.6.4   Human-related Requirements">3.2.6.4 Human-Related 
    Requirements&nbsp;</a></p>
  <p class=MsoToc7><a href="#3.2.6.5   Logistics Requirements">3.2.6.5 Logistics 
    Requirements&nbsp;</a></p>
  <p class=MsoToc3><a href="#3.2.7&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Online User Documentation and Help System Requirements">3.2.7 
    Online User Documentation and Help System Requirements&nbsp;</a></p>
  <p class=MsoToc3><a href="#3.2.8          Purchased Components">3.2.8 Purchased 
    Components&nbsp;</a></p>
  <p class=MsoToc3><a href="#3.2.9&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Interfaces">3.2.9 
    Interfaces&nbsp;</a></p>
  <p class=MsoToc7><a href="#3.2.9.1&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;User Interfaces">3.2.9.1 
    User Interfaces&nbsp;</a></p>
  <p class=MsoToc7><a href="#3.2.9.2&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Hardware Interfaces">3.2.9.2 
    Hardware Interfaces&nbsp;</a></p>
  <p class=MsoToc7><a href="#3.2.9.3&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Software Interfaces">3.2.9.3 
    Software Interfaces&nbsp;</a></p>
  <p class=MsoToc7><a href="#3.2.9.4&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Communications Interfaces">3.2.9.4 
    Communications Interfaces&nbsp;</a></p>
  <p class=MsoToc3><a href="#3.2.10        Licensing Requirements">3.2.10 Licensing 
    Requirements&nbsp;</a></p>
  <p class=MsoToc3><a href="#3.2.11&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Legal, Copyright and Other Notices">3.2.11 
    Legal, Copyright,and Other Notices&nbsp;</a></p>
  <p class=MsoToc3><a href="#3.2.12        Applicable Standards">3.2.12 Applicable 
    Standards</a></p>
  <p class=MsoToc1><a href="#4.                  Supporting Information">4.<span style='font-size:12.0pt'>       
    </span>Supporting Information</a>&nbsp;&nbsp;&nbsp;&nbsp;</p>
  <p class=MsoTitle><br
clear=all style='page-break-before:always'>
    System Requirements Specification </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 introduction of the <b>System Requirements Specification 
    (SysRS) </b> provides an overview of the entire <b>SysRS</b>. It includes 
    the purpose, scope, definitions, acronyms, abbreviations, references, and 
    overview of the <b>SysRS</b>.]</p>
  <p class=InfoBlue>[<b>Note:</b> The <b>SysRS</b> captures the complete system 
    requirements for the system, or a portion of the system. Following is a typical 
    <b>SysRS</b> outline for a project using only traditional natural-language 
    style requirements - with <b>no use-case modeling. </b>It captures all requirements 
    in a single document, with the Supplementary Specifications combined, or equivalent 
    material inserted.]</p>
  <h2 style='margin-left:0in;text-indent:0in'><a name="1.1     Purpose">1.1<span
style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp; </span>Purpose</a></h2>
  <p class=InfoBlue>[Specify the purpose of this <b>SysRS</b>. The <b>SysRS</b> 
    fully describes the functional and behavioral capabilities of the identified 
    system. It also describes nonfunctional requirements, design constraints, 
    and other factors necessary to provide a complete and comprehensive description 
    of the requirements for the system.]</p>
  <h2 style='margin-left:0in;text-indent:0in'><a name="1.2     Scope">1.2<span
style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp; </span>Scope</a></h2>
  <p class=InfoBlue>[A brief description of the system that the <b>SysRS</b> applies 
    to, and anything else that is affected or influenced by this document.]</p>
  <h2 style='margin-left:0in;text-indent:0in'><a name="1.3     Definitions, Acronyms and Abbreviations">1.3<span
style='font:7.0pt "Times New Roman"'>&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>SysRS</b>.&nbsp;This 
    information can be provided by reference to the project Glossary.]</p>
  <h2 style='margin-left:0in;text-indent:0in'><a name="1.4     References">1.4<span
style='font:7.0pt "Times New Roman"'>&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>SysRS</b>. 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 can 
    be provided by reference to an appendix or to another document.]</p>
  <h2 style='margin-left:0in;text-indent:0in'><a name="1.5     Overview">1.5<span
style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp; </span>Overview</a></h2>
  <p class=InfoBlue>[This subsection describes what the rest of the <b>SysRS</b> 
    contains and explains how the document is organized.]</p>
  <h1><a name="2.                  Overall Description">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>Overall Description</a></h1>
  <p class="InfoBlue">[This section of the <b>SysRS</b> describes the general 
    factors that affect the system and its requirements.&nbsp;This section does 
    not state specific requirements.&nbsp;Instead, it provides a background for 
    those requirements, which are defined in detail in <b>Section 3</b>, and makes 
    them easier to understand. Include such items as:</p>
</div>
<ul>
  <li> 
    <div class=Section2>the context for the system</div>
  </li>
  <li> 
    <div class=Section2>system functions</div>
  </li>
  <li> 
    <div class=Section2>user characteristics</div>
  </li>
  <li> 
    <div class=Section2>constraints</div>
  </li>
  <li> 
    <div class=Section2>assumptions and dependencies</div>
  </li>
  <li> 
    <div class=Section2>requirements subsets.</div>
  </li>
</ul>
<div class=Section2> 
  <p class="InfoBlue">Reference can be made from this section to the Vision artifact, 
    rather than replicating material from that document.]</p>
  <h2><a name="2.1               Use-Case Model Survey">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>Use-Case Model Survey</a></h2>
  <p class=InfoBlue> [If you are using use-case modeling, this section contains 
    an overview of the use-case model. This includes a list of names and brief 
    descriptions of all use cases and actors, along with applicable diagrams and 
    relationships.&nbsp;Refer to the <b>Use-Case Model Survey Report</b>, which 
    can be used as an enclosure at this point.]</p>
  <h2><a name="2.2               Assumptions and Dependencies">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>Assumptions and Dependencies</a></h2>
  <p class=InfoBlue>[This section describes any key technical feasibility, subsystem 
    or component availability, or other project related assumptions on which the 
    viability of the system described by this <b>SysRS</b> might be based.]</p>
  <h1><a name="3.                  Specific Requirements">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>Specific Requirements</a> </h1>
  <p class=InfoBlue>[This section of the <b>SysRS</b> contains all the system 
    requirements to a level of detail sufficient to enable designers to design 
    a system to satisfy those requirements, and testers to test that the system 
    satisfies those requirements.</p>
  <p class=InfoBlue>When using use-case modeling, these requirements are captured 
    in the use cases and the applicable supplementary specifications (either as 
    an artifact itself, or according to the sections under &quot;3.2 Non-Functional 
    Requirements,&quot; in this document).]</p>
  <h2 style='margin-left:0in;text-indent:0in'><a name="3.1             &nbsp;&nbsp;System Capabilities">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>System Capabilities</a></h2>
  <p class=InfoBlue>[This section describes the required capabilities of the system, 
    expressed as use cases. For many systems, this might constitute the bulk of 
    the <b>SysRS</b> package, and thought must be given to the organization of 
    this section. This section is typically organized by feature, function, or 
    functional group (which broadly characterize a &quot;capability&quot; - tracing 
    from the Vision artifact), but alternative organization methods might also 
    be appropriate, for example, organization by user or role.]</p>
  <h3><a name="3.1.1           Use-Case Reports">3.1.1<span style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    </span>Use-Case Reports</a></h3>
  <p class=InfoBlue>[In use-case modeling, the use cases define the majority of 
    the functional requirements of the system, along with some non-functional 
    (performance-related) requirements. For each use case in the above use-case 
    model, refer to, or enclose, the use-case report in this section. Make sure 
    that each requirement is clearly labeled. Where appropriate, group the use 
    cases by capability - functionally refined if necessary - so that the 
    right level of functional and behavioral description is achieved.]</p>
  <h3><a name="3.1.2           Additional Functionality">3.1.2<span style="font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    </span>Additional Functionality</a></h3>
  <p class="InfoBlue">[This section describes any additional functional requirements 
    of the system (not captured as use cases), expressed in natural-language form.]</p>
  <h4><a name="3.1.2.1     &lt;Functional Requirement One&gt;">3.1.2.1<span style="font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp; 
    </span>&lt;Functional Requirement One&gt;</a></h4>
  <p class="InfoBlue">[The requirement description.]</p>
  <div class="Section2"> 
    <h2><a name="3.2&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Non-Functional Requirements">3.2<span style="font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span>Non-Functional 
      Requirements</a></h2>
    <p class="InfoBlue">[<b>Note:</b> If the Supplementary Specifications artifact 
      has been produced, it can simply be included here. It covers the same topics.]</p>
    <h3><a name="3.2.1          Usability">3.2.1<span
style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
      &nbsp; </span>Usability</a></h3>
    <p class="InfoBlue">[This section includes all of those requirements that 
      affect usability. For example:</p>
    </div>
</div>
<ul>
  <li> 
    <div class=Section2> 
      <div class="Section2">specify the required training time for normal users 
        and power users to become productive at particular operations</div>
    </div>
  </li>
  <li> 
    <div class=Section2> 
      <div class="Section2"><span style="font-family:Symbol;
font-style:normal"><span style="font:7.0pt &quot;Times New Roman&quot;"> </span></span>specify 
        measurable task times for typical tasks</div>
    </div>
  </li>
  <li>specify requirements to conform to common usability standards, for example, 
    IBM?s CUA standards or Microsoft?s GUI standards]</li>
</ul>
<div class=Section2>
  <div class="Section2"></div>
  <div class=Section2> 
    <div class="Section2"> </div>
  </div>
</div>
<div class=Section2> 
  <div class="Section2"> 
    <h4><a name="3.2.1.1     &lt;Usability Requirement One&gt;">3.2.1.1<span style="font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp; 
      </span>&lt;Usability Requirement One&gt;</a></h4>
    <p class="InfoBlue">[The requirement description.]</p>
    <h3><a name="3.2.2&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Reliability">3.2.2<span style="font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span>Reliability</a></h3>
    <p class="InfoBlue">[Specify the requirements for reliability of the system 
      here. Suggestions are as follows:</p>
  </div>
</div>
<ul>
  <li> 
    <div class=Section2> 
      <div class="Section2">Availability - Specify percentage of time available 
        ( xx.xx%), hours of use, maintenance access, degraded mode operations,and 
        so forth.</div>
    </div>
  </li>
  <li> 
    <div class=Section2> 
      <div class="Section2"><span style="font-family:Symbol;
font-style:normal"><span style="font:7.0pt &quot;Times New Roman&quot;"> </span></span>Mean 
        Time Between Failures (MTBF) - This is usually specified in hours, but 
        it could also be specified in terms of days, months, or years.</div>
    </div>
  </li>
  <li> 
    <div class=Section2> 
      <div class="Section2"><span style="font-family:Symbol;
font-style:normal"><span style="font:7.0pt &quot;Times New Roman&quot;"> </span></span>Mean 
        Time To Repair (MTTR) - How long is the system allowed to be out of 
        operation after it has failed?</div>
    </div>
  </li>
  <li> 
    <div class=Section2> 
      <div class="Section2">Accuracy - Specify precision (resolution) and accuracy 
        (by some known standard) that is required in the systems output.</div>
    </div>
  </li>
  <li> 
    <div class=Section2> 
      <div class="Section2"><span style="font-family:Symbol;
font-style:normal"><span style="font:7.0pt &quot;Times New Roman&quot;"> </span></span>Maximum 
        bugs or defect rate - usually expressed in terms of bugs/KLOC (thousands 
        of lines of code), or bugs/function-point.</div>
    </div>
  </li>
  <li> 
    <div class=Section2> 
      <div class="Section2"><span style="font-family:Symbol;
font-style:normal"><span style="font:7.0pt &quot;Times New Roman&quot;"> </span></span>Bugs 
        or defect rate - categorized in terms of minor, significant, and critical 
        bugs: the requirement(s) must define what is meant by a ?critical? bug 
        (for example, complete loss of data or complete inability to use certain 
        parts of the functionality of the system).]</div>
    </div>
  </li>
</ul>
<div class=Section2> 
  <div class="Section2"> 
    <h4><a name="3.2.2.1&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;Reliability Requirement One&gt;">3.2.2.1<span style="font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span>&lt;Reliability 
      Requirement One&gt;</a></h4>
    <p class="InfoBlue">[The requirement description.]</p>
    <h3><a name="3.2.3&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Performance">3.2.3<span style="font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span>Performance</a></h3>
    <p class="InfoBlue">[Outline the performance characteristics of the system 
      in this section. Include specific response times. Where applicable, reference 
      related use cases by name. In general, associate all required capabilities, 
      whether described in use-case form or simply by text, with some performance 
      statement (describing how well the system should provide the capability 
      or function). It is better to keep those statements of performance in proximity 
      to the affected capability (in the &quot;special requirements&quot; part 
      of a use-case description, for example). Here, you can keep statements of 
      requirements that need to be tested, but which are not aligned with specific 
      capability. Performance characteristics include:</p>
  </div>
</div>
<ul>
  <li> 
    <div class=Section2> 
      <div class="Section2"><span style="font-family:Symbol;
font-style:normal"><span style="font:7.0pt &quot;Times New Roman&quot;"> </span></span>Response 
        time for a transaction (average, maximum).</div>
    </div>
  </li>
  <li>
    <div class=Section2>
      <div class="Section2">Throughput (for example, transactions per second. 
        <div class=Section2> 
          <div class="Section2"></div>
        </div>
      </div>
    </div>
  </li>
  <li> 
    <div class=Section2> 
      <div class="Section2">Capacity (for example, the number of customers or 
        transactions the system can accommodate).</div>
    </div>
  </li>
  <li> 
    <div class=Section2> 
      <div class="Section2"><span style="font-family:Symbol;
font-style:normal"><span style="font:7.0pt &quot;Times New Roman&quot;"> </span></span>Degradation 
        modes (what is the acceptable mode of operation when the system has been 
        degraded in some manner).</div>
    </div>
  </li>
  <li> 
    <div class=Section2> 
      <div class="Section2"><span style="font-family:Symbol;
font-style:normal"><span style="font:7.0pt &quot;Times New Roman&quot;"> </span></span>Resource 
        utilization: memory, disk, communications, and so forth.]</div>
    </div>
  </li>
</ul>
<div class=Section2>
  <div class="Section2">
    <h4><a name="3.2.3.1      &lt;Performance Requirement One&gt;">3.2.3.1<span style="font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
      </span>&lt;Performance Requirement One&gt;</a></h4>
    <p class="InfoBlue">[The requirement description.]</p>
    <h3><a name="3.2.4&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Supportability">3.2.4<span style="font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span>Supportability</a></h3>
    <p class="InfoBlue">[This section indicates any requirements that enhance 
      the supportability or maintainability of the system being built, including 
      coding standards, naming conventions, class libraries, maintenance access, 
      and maintenance utilities.]</p>
    <h4><a name="3.2.4.1&nbsp;&nbsp;&nbsp;&nbsp;&lt;Supportability Requirement One&gt;">3.2.4.1<span style="font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;</span>&lt;Supportability 
      Requirement One&gt;</a></h4>
    <p class="InfoBlue">[The requirement description.]</p>
    <h3><a name="3.2.5&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Design Constraints">3.2.5<span style="font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span>Design 
      Constraints</a></h3>
    <p class="InfoBlue">[This section indicates any design constraints on the 
      system being built. Design constraints represent design decisions that have 
      been mandated and must be adhered to.&nbsp;Examples include software languages, 
      software process requirements, prescribed use of developmental tools, architectural 
      and design constraints, purchased components, class libraries, and so on.]</p>
    <h4><a name="3.2.5.1&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;Design Constraint One&gt;">3.2.5.1<span style="font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span>&lt;Design 
      Constraint One&gt;</a></h4>
    <p class="InfoBlue">[The requirement description.]</p>
  </div>
  <div class="Section2"> 
    <h3><a name="3.2.6&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Additional Systems Engineering Considerations">3.2.6&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Additional 
      Systems Engineering Considerations</a></h3>
    <p class="InfoBlue">[Systems engineering potentially requires other types 
      of requirements to be addressed:]</p>
    <h4><a name="3.2.6.1&nbsp;&nbsp;Physical Requirements">3.2.6.1&nbsp;&nbsp;Physical 
      Requirements</a></h4>
    <p class="InfoBlue">[For example, weight, size, power, and so forth.]</p>
    <h4><a name="3.2.6.2&nbsp;&nbsp;Environmental Requirements">3.2.6.2&nbsp;&nbsp;Environmental 
      Requirements</a></h4>
    <p class="InfoBlue">[For example, moisture, contaminant, thermal, electrical, 
      mechanical, and so on.]</p>
    <h4><a name="3.2.6.3&nbsp;&nbsp;Other Product Assurance Requirements">3.2.6.3&nbsp;&nbsp;Other 
      Product Assurance Requirements</a></h4>
    <h4><a name="3.2.6.3.x     &lt;Category&gt;">3.2.6.3.x&nbsp;&nbsp;&nbsp;&nbsp; 
      &lt;Category&gt;</a></h4>
    <p class="InfoBlue">[For example, safety, security, other quality factors 
      (for example, survivability).]</p>
    <h4><a name="3.2.6.4   Human-related Requirements">3.2.6.4&nbsp;&nbsp; Human-Related 
      Requirements</a></h4>
    <p class="InfoBlue">[Describe the requirements imposed on the system in support 
      of the people who use and support the system. Examples include training 
      capabilities - equipment and materials to be included for training - maintenance 
      capabilities, and ergonomic considerations not covered by interface descriptions 
      and standards.]</p>
    <h4><a name="3.2.6.5   Logistics Requirements">3.2.6.5&nbsp;&nbsp; Logistics 
      Requirements</a></h4>
    <p class="InfoBlue">[Describe the requirements imposed on the system because 
      of logistics considerations including maintenance, support, transportation, 
      supply, and accommodation of existing systems.]</p>
    <h3><a name="3.2.7&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Online User Documentation and Help System Requirements">3.2.7<span style="font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span>Online 
      User Documentation and Help System Requirements</a></h3>
    <p class="InfoBlue">[Describes the requirements, if any, for online user documentation, 
      help systems, help about notices, and so on.]</p>
    <h3><a name="3.2.8          Purchased Components">3.2.8<span style="font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
      </span>Purchased Components</a></h3>
    <p class="InfoBlue">[This section describes any purchased components to be 
      used with the system, any applicable licensing or usage restrictions, and 
      any associated compatibility/interoperability or interface standards.]</p>
    <h3><a name="3.2.9&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Interfaces">3.2.9<span style="font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span>Interfaces</a></h3>
    <p class="InfoBlue">[This section defines the interfaces that must be supported 
      by the system. It must contain adequate specificity, protocols, ports and 
      logical addresses, and so forth, so that the system can be developed and 
      verified against the interface requirements. Any requirements to be imposed 
      on interfaces internal to the system must also be described. These arise, 
      for example, when the system design is constrained to use existing hardware 
      or software components internally.]</p>
    <h4><a name="3.2.9.1&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;User Interfaces">3.2.9.1<span style="font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span>User 
      Interfaces</a></h4>
    <p class="InfoBlue">[Describe the user interfaces that are to be implemented 
      by the system.]</p>
    <h4><a name="3.2.9.2&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Hardware Interfaces">3.2.9.2<span style="font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span>Hardware 
      Interfaces</a></h4>
    <p class="InfoBlue">[This section defines any hardware interfaces that are 
      to be supported by the system, including logical structure, physical addresses, 
      expected behavior, and so forth.]</p>
    <h4><a name="3.2.9.3&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Software Interfaces">3.2.9.3<span style="font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span>Software 
      Interfaces</a></h4>
    <p class="InfoBlue">[This section describes software interfaces to be supported 
      by the system, in terms of operations and signals supported (and for which 
      support is required), protocols, and data characteristics.]</p>
    <h4><a name="3.2.9.4&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Communications Interfaces">3.2.9.4<span style="font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span>Communications 
      Interfaces</a></h4>
    <p class="InfoBlue">[Describe any communications interfaces to other systems 
      or devices such as local area networks, and so on.]</p>
    <h3><a name="3.2.10        Licensing Requirements">3.2.10<span style="font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
      </span>Licensing Requirements</a></h3>
    <p class="InfoBlue">[Defines any licensing enforcement requirements or other 
      usage restriction requirements which are to be exhibited by the system.]</p>
    <h3><a name="3.2.11&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Legal, Copyright and Other Notices">3.2.11<span style="font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span>Legal, 
      Copyright, and Other Notices</a></h3>
    <p class="InfoBlue">[This section describes any necessary legal disclaimers, 
      warranties, copyright notices, patent notice, wordmark, trademark or logo 
      compliance issues for the system.]</p>
    <h3><a name="3.2.12        Applicable Standards">3.2.12<span style="font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
      </span>Applicable Standards</a></h3>
    <p class="InfoBlue">[This section describes by reference any applicable standards 
      and the specific sections of any such standards that apply to the system 
      being described. For example, this could include legal, quality and regulatory 
      standards, industry standards for usability, interoperability, internationalization, 
      operating system compliance, and so forth.]</p>
  </div>
  <h1><a name="4.                  Supporting Information">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>Supporting Information</a></h1>
  <p class=InfoBlue>[The supporting information makes the <b>SysRS</b> easier 
    to use. It includes:</p>
</div>
<ul>
  <li> 
    <div class=Section2>Index</div>
  </li>
  <li> 
    <div class=Section2>Appendices</div>
  </li>
</ul>
<div class=Section2>
  <p class=InfoBlue>These might include information about architectural and user-interface 
    prototypes. When appendices are included, the <b>SysRS</b> must explicitly 
    state whether or not the appendices are to be considered part of the requirements.]</p>
</div>

</body>

</html>
