Stage Releases

CS 4500, Spring 2009

1. An implementation overview
   1. Open with a statement of the purpose of the report.
      
   2. Next, provide a nicely organized description current status action items.  This is usually best presented in a table, although a list can sometimes work. Include the following information for each action item:
      1. The unique number of the action item
      2. The severity of the action item
      3. Who is/was responsible for the action item
      4. The current status of the action item (is it complete? is someone working on it? when will it be completed?)
      5. A brief description of exactly what was done / will be done with the item
2. A README file should be a file rather than a link, and should describe the semantics of each file in the release.
3. The implementation itself:
   • Give location of the files and directories of your implementation. The current version of the implementation should be directly accessible from the top-level directory.
   • The source code should follow the team's code development and documentation standard (state which coding standard was used).
     
   • If the product can be run over the web, give the path which will launch the runnable product. If the product is not directly runnable over the web,  give information about the project and how the product can be obtained and run.

Preconditions to turning in the final implementation:

• State where an executable can be found, as well as a User Manual; otherwise, schedule a demo.
  
• The team should have reviewed the product carefully to ensure that all parts of the implementation follow  the documentation standards.
• Testing should be complete and documented as defined in the VVPv2 and reported in the VVRv2. (NOTE: Ensure that the VVR is updated to reflect the work carried out since the last version of the VVR!!! This is a key error made by many teams.)