信息管理方向的CRM系统的相关文档

  <font size="2"><font face="Arial" size="2"><b>
  <p>User Interface Testing</p>
  </b></font>
  <blockquote>
    <p>Verify ease of navigation through a sample set of screens.</p>
    <p>Verify sample screens conform to GUI standards.</p>
    <p>Vision Document Section 10: &quot;The System shall be easy-to-use and
    shall be appropriate for the target market of computer-literate students and
    professors.&quot;</p>
    <p>Vision Document, Section 12.1: &quot;The desktop user-interface shall be
    Windows 95/98 compliant.&quot;</p>
    <p>Supplementary Specification, Section 5.1: &quot;The desktop
    user-interface shall be Windows 95/98 compliant.&quot;</p>
    <p>Supplementary Specification, Section 5.2: &quot;The user interface of the
    C-Registration System shall be designed for ease-of-use and shall be
    appropriate for a computer-literate user community with no additional
    training on the System.&quot;</p>
    <p>Supplementary Specification, Section 5.3: &quot;Each feature of the
    C-Registration System shall have built-in online help for the user. Online
    Help shall include step by step instructions on using the System. Online
    Help shall include definitions for terms and acronyms.&quot;</p>
  </blockquote>
  <font face="Arial" size="2"><b>
  <p>Performance Testing</p>
  </b></font>
  <blockquote>
    <p>Verify response time to access external Finance system.</p>
    <p>Verify response time to access external Course Catalog subsystem.</p>
    <p>Verify response time for remote login.</p>
    <p>Verify response time for remote submittal of course registration.</p>
    <p>Vision Document, Section 12.3: &quot;The system shall provide access to
    the legacy Course Catalog Database with no more than a 10 second
    latency.&quot;</p>
    <p>Supplementary Specification, Section 7.2: &quot;The system shall provide
    access to the legacy Course Catalog Database with no more than a 10 second
    latency.&quot;</p>
  </blockquote>
  <font face="Arial" size="2"><b>
  <p>Load Testing</p>
  </b></font>
  <blockquote>
    <p>Verify system response when loaded with 200 logged on students.</p>
    <p>Verify system response when 50 simultaneous student accesses to the
    Course Catalog.</p>
    <p>Supplementary Specification, Section 7.1: &quot;The system shall support
    2000 simultaneous users against the central database at any given time, and
    up to 500 simultaneous users against the local servers at any one
    time.&quot;</p>
  </blockquote>
  <font face="Arial" size="2"><b>
  <p>Stress Testing</p>
  </b></font>
  <blockquote>
    <p>Verify system response during prime time use of the UNIX Server.</p>
    <p>Verify system response during maximum student logins.</p>
  </blockquote>
  <font face="Arial" size="2"><b>
  <p>Volume Testing</p>
  </b></font>
  <blockquote>
    <p>Verify system response when Course Catalog Database at 90% capacity.</p>
  </blockquote>
  <font face="Arial" size="2"><b>
  <p>Security and Access Control Testing</p>
  </b></font>
  <blockquote>
    <p>Verify Logon from a local PC.</p>
    <p>Verify Logon from a remote PC.</p>
    <p>Verify Logon security through user name and password mechanisms.</p>
    <p>Supplementary Specification, Section 4.2: &quot;All functionality shall
    be available remotely through an internet connection.&quot;</p>
  </blockquote>
  <font face="Arial" size="2"><b>
  <p>Failover / Recovery Testing</p>
  </b></font>
  <blockquote>
    <p>Supplementary Specification, Section 6.1: &quot;The C-Registration System
    shall be available 24 hours a day, 7 days a week. There shall be no more
    than 4% down time.&quot;</p>
    <p>Supplementary Specification, Section 6.2: &quot;Mean Time Between
    Failures shall exceed 300 hours.&quot;</p>
  </blockquote>
  <font face="Arial" size="2"><b>
  <p>Configuration Testing</p>
  </b></font>
  <blockquote>
    <p>Vision Document, Section 12.2: &quot;The client component of the system
    shall run on Windows 95, Windows 98, and Microsoft Windows NT.&quot;</p>
    <p>Supplementary Specification, Section 9.4: &quot;The web-based interface
    for the C-Registration System shall run in Netscape 4.04 and Internet
    Explorer 4.0 browsers.</p>
    <p>Supplementary Specification, Section 9.5: &quot;The web-based interface
    shall be compatible with the Java 1.1 VM runtime environment.</p>
  </blockquote>
  <font face="Arial" size="2"><b>
  <p>Installation Testing</p>
  </b></font>
  <blockquote>
    <p>Supplementary Specification, Section 8.1: &quot;Upgrades to the PC client
    portion of the C-Registration shall be downloadable from the UNIX Server
    over the internet.&quot;</p>
    <p>Verify installation of server portion.</p>
    <p>Verify installation of client portion.</p>
  </blockquote>
  </font>
</ul>
<p><font size="3">5. <a name="_Toc314978533"></a><a name="_Toc324843639"></a><a name="_Toc324851946"></a><a name="_Toc324915529"></a><a name="_Toc433104442"></a></font><b><font face="Arial" size="3"><a name="_Toc447185690">Test
Strategy</a></font></b>
<ul>
  <font size="2">
  <p>The Test Strategy presents the recommended approach to the testing of the
  software applications. The previous section on Test Requirements described <i>what</i>
  will be tested; this describes <i>how</i> it will be tested.</p>
  <p>The main considerations for the test strategy are the techniques to be used
  and the criterion for knowing when the testing is completed.</p>
  <p>In addition to the considerations provided for each test below, testing
  should only be executed using known, controlled databases, in secured
  environments.</p>
  <p>The following test strategy is generic in nature and is meant to apply to
  the requirements listed in Section 4 of this document.
  <ol>
    <li><a name="_Toc314978534"></a><a name="_Toc324843640"></a><a name="_Toc324851947"></a><a name="_Toc324915530"></a><a name="_Toc433104443"></a><font face="Arial" size="2"><b><a name="_Toc447185691">Testing
      Types</a></b></font></li>
      
    </ol>
  </font>
</ul>
<blockquote>
  <blockquote>
    <b>
    <p><font face="Arial" size="2">1. <a name="_Toc314978535"></a><a name="_Toc324843641"></a><a name="_Toc324851948"></a><a name="_Toc324915531"></a><a name="_Toc433104444"></a></font><i><font face="Arial" size="2"><a name="_Toc447185692">Data
    and Database Integrity Testing</a></font></i></p>
    </b>
  </blockquote>
</blockquote>
<blockquote>
  <blockquote>
    <blockquote>
      <font size="2">
      <p>The databases and the database processes should be tested as separate
      systems. These systems should be tested without the applications (as the
      interface to the data). Additional research into the DBMS needs to be
      performed to identify the tools / techniques that may exist to support the
      testing identified below.</p></font>
    </blockquote>
  </blockquote>
</blockquote>
<div align="center"><center>

<table cellspacing="0" border="0" cellpadding="7" width="90%">
  <tr>
    <td width="34%" valign="TOP"><font size="2">Test Objective:</font></td>
    <td width="66%" valign="TOP"><font size="2">Ensure Database access methods
    and processes function properly and without data corruption.</font></td>
  </tr>
  <tr>
    <td width="34%" valign="TOP"><font size="2">Technique:</font></td>
    <td width="66%" valign="TOP">
    <ul>
      <font size="2">
      <li>Invoke each database access method and process, seeding each with
        valid and invalid data (or requests for data).</li>
      <li>Inspect the database to ensure the data has been populated as
        intended, all database events occurred properly, or review the returned
        data to ensure that the correct data was retrieved (for the correct
        reasons)</li></font>
    </ul>
    </td>
  </tr>
  <tr>
    <td width="34%" valign="TOP"><font size="2">Completion Criteria:</font></td>
    <td width="66%" valign="TOP"><font size="2">All database access methods and
    processes function as designed and without any data corruption.</font></td>
  </tr>
  <tr>
    <td width="34%" valign="TOP"><font size="2">Special Considerations:</font></td>
    <td width="66%" valign="TOP">
    <ul>
      <font size="2">
      <li>Testing may require a DBMS development environment or drivers to enter
        or modify data directly in the databases.</li>
      <li>Processes should be invoked manually.</li>
      <li>Small or minimally sized databases (limited number of records) should
        be used to increase the visibility of any non-acceptable events.</li></font>
    </ul>
    </td>
  </tr>
</table>
</center></div>

<blockquote>
<blockquote>
  <p>
    <font size="2"><em><strong>2. <a name="_Toc433104445"></a><a name="_Toc447185693"></a></strong></em></font><strong><em><font face="Arial" size="2">System
    Testing</font></em></strong></p>
</blockquote>
</blockquote>
<blockquote>
  <blockquote>
    <blockquote>
      <font size="2">
      <p><a name="_Toc314978536"></a><a name="_Toc324843643"></a><a name="_Toc324851950"></a><a name="_Toc324915533">Testing
      of the application should focus on any target requirements that can be
      traced directly to use cases (or business functions), and business rules.
      The goals of these tests are to verify proper data acceptance, processing,
      and retrieval, and the appropriate implementation of the business rules.
      This type of testing is based upon black box techniques, that is,
      verifying the application (and its internal processes) by interacting with
      the application via the GUI and analyzing the output (results). Identified
      below is an outline of the testing recommended for each application:</a></p></font>
    </blockquote>
  </blockquote>
</blockquote>
<a name="_Toc324915533"></a>
<p align="center">&nbsp;</p>
<div align="center"><center>

<table cellspacing="0" border="0" cellpadding="7" width="90%">
  <tr>
    <td width="34%" valign="TOP"><font size="2">Test Objective:</font></td>
    <td width="66%" valign="TOP"><font size="2">Ensure proper application
    navigation, data entry, processing, and retrieval.</font></td>
  </tr>
  <tr>
    <td width="34%" valign="TOP"><font size="2">Technique:</font></td>
    <td width="66%" valign="TOP">
    <ul>
      <font size="2">
      <li>Execute each use case, use case flow, or function, using valid and
        invalid data, to verify the following:</li>
      <li>The expected results occur when valid data is used.</li>
      <li>The appropriate error / warning messages are displayed when invalid
        data is used.</li>
      <li>Each business rule is properly applied.</li></font>
    </ul>
    </td>
  </tr>
  <tr>
    <td width="34%" valign="TOP"><font size="2">Completion Criteria:</font></td>
    <td width="66%" valign="TOP">
    <ul>
      <font size="2">
      <li>All planned tests have been executed.</li>
      <li>All identified defects have been addressed.</li></font>
    </ul>
    </td>
  </tr>
  <tr>
    <td width="34%" valign="TOP"><font size="2">Special Considerations:</font></td>
    <td width="66%" valign="TOP">
    <ul>
      <font size="2">
      <li>Access to the Wylie College UNIX Server and the existing Course
        Catalog System and Billing System is required.</li></font>
    </ul>
  </td>
</tr>
</table>
</center></div>

<blockquote>
  <p>
  <font size="2"><strong>3. <a name="_Toc433104446"></a><a name="_Toc447185694"></a></strong></font><font face="Arial" size="2"><i><strong>Business
  Cycle Testing</strong></i></font></p>
  
</blockquote>
<blockquote>
  <blockquote>
    <font size="2">
    <p>Business Cycle Testing should emulate the activities performed on the
    system over time. A period should be identified, such as one year, and
    transactions and activities that would occur during a year's period should
    be executed. This includes all daily, weekly, monthly cycles and events that
    are date sensitive, such as ticklers.</p></font>
  </blockquote>
</blockquote>
<p align="center">&nbsp;</p>
<div align="center"><center>

<table cellspacing="0" border="0" cellpadding="7" width="90%">
  <tr>
    <td width="34%" valign="TOP"><font size="2">Test Objective</font></td>
    <td width="66%" valign="TOP"><font size="2">Ensure proper application and
    background processes function according to required business models and
    schedules.</font></td>
  </tr>
  <tr>
    <td width="34%" valign="TOP"><font size="2">Technique:</font></td>
    <td width="66%" valign="TOP">
    <ul>
      <font size="2">
      <li>Testing will simulate several business cycles by performing the
        following:</li>
      <li>The tests used for application function testing will be modified /