Acceptance Testing

Acceptance Testing

Please use the following checklist in preparation for your final presentation and demo.

SOFTWARE (The following is 0.5 point each):
(   ) Software configuration is complete.  Document includes requirements,
      design, test plan, test results, source codes, user manual,
      installation procedure (which may be included in user manual),
      software maintenance procedure (may also be included in user manual).
(   ) Software supports a "DB load mode" to read from a script
      to set up a database DB ready to be
      used.  Likewise, software can generate such a script from DB.
(   ) Software can be run on PC under Windows without any additional
      plug-ins.  In other words, software can be installed from a
      CD, memory stick, or website by loading a file install.exe and
      executing it.  In case the software is for a Unix workstation,
      software can be installed by ftp the executable in a project
      directory.

DOCUMENT (The following is 0.5 point each):
(   ) a plastic jacket containing the CD for the source.
(   ) sections in the document are separated by labelled dividers.
(   ) changes you made after the reviews, are clearly indicated, for example,
      with yellow tabs.  In other words, this document should include the
      revision history so that the reader can understand what
      changes have been made and the current status of things.
(   ) cross references throughout the document.  If your document is
      on the web, one can click on an URL to go to another section
      of the document.  If your document is a hard copy, cross
      references are made to specific sections, pages, etc.

PRESENTATION (The following is 0.5 point each):
(   ) There is a PPT presentation explaining the highlights of the software.
(   ) All project team members are present and their contributions clearly explained.

DEMO (The following is 0.5 point each):
(   ) Install TGS (Testing and Grading System) software.
(   ) Start the TGS system.
(   ) Verify a student login.
(   ) A student can select a course and a test.
(   ) Let the student take the test and compute grade.
(   ) Display the correct answers to the students after a test.
(   ) Store the grades in the database, and display saved grades to the student later.
(   ) Verify an instructor login to open a new or an existing database DB.
(   ) Display all students' grades to the instructor.
(   ) Display a specific student's grades to the instructor.
(   ) Show how you can maintain the software: find source code, make a simple
      modification and recompile.  Time may not permit you to go through the
      entire sequence, so you should include this also in the user manual
      as a separate section on software maintenance.

EXTRA CREDIT (filled in by instructor):
(   ) (0.5 point) Instructor can create a new test entry.
(   ) (0.5 point) Instructor can modify, delete, save and search for a test in a DB.
(   ) (1 point) TGS is integrated with VC, so that a student can take a test through VC.
       The integration should be accomplished through message passing.  
       The mere invocation of TGS from VC does not count as true integration.
(   ) (1 point) TGS is integrated with VC, so that an instructor can 
       create new test entries through VC.

(   )

(   )

TOTAL: (         )

REMEMBER, ENTIRE SHOW AND TELL SHOULD BE NO LONGER THAN 10 MINUTES!