Professional Computing CITS3200

Definition of Deliverable C

This Deliverable has eight parts. All are to be submitted in electronic form, but ONLY parts 4-7 are also to be submitted in hard copy. Use a single (Zip or tar/gzip) containing the parts 1-7 and ensure your Group ID is cleary in the filenames.

Part 8 is different from the other parts, because every student is expected to submit their own copy of the spreadsheet. As a result, there is a separate cssubmit line for this component.

1. The source code of the completed system and any user documentation (see below).
2. Source code version repository (i.e. RCS/CVS/Subversion version tree).
3. Instructions on how to run your system in a CSSE environment to be agreed between the team and Client.
4. Documentation of your testing process, planning and results. LIMIT 30 PAGES.
5. A check list of Acceptance Tests, from Del B, and results of tests conducted with the Client.
6. Time analysis and discussion
7. Ethics checklist and discussion
8. Group Relative Effort Computation.

Looking more closely at these:

• Testing
  • Documentation of the attempts you made during the Deliverable C milestone to perform high quality verification and validation.
  • System testing specification consisting of a series of test cases and expected results, and evidence of actual test results (several pages). Include details of any automatic testing process you used. You may wish to follow the format suggested in Bruegge & Dutoit Section 9.5.2 as appropriate, but ensure that you use mainly tables and lists of tests actually planned, performed and repeated. Credit will only be given for credible work! (Give brief evidence that you actually did run these tests). Do not repeat material from Part B, although you may show test results.
• Time Analyis. Summarise your time data, showing differences between planned with actual values. Show where those hours of toil went. Give the total hours spent on the project as a whole. This is really a distillation and analysis of the information that was included in your timesheets. Provide brief explanation of any major variations between estimated and actual times. Perhaps indicate briefly how your estimates were constructed.
• Ethics Checklist. Complete the form listing the ACS guidelines ( Spreadsheet here CSV file if you do not have Excel). For each item indicate the degree to which it was observed, on a scale Observed, Partially observed, Violated, Not applicable. Give no more than a 150 word explanation of your scores, picking out just the key features. Give it some real thought, but don't invent something just to tick the box.
• The Group Relative Effort Computation is an Excel which is found here. The aim of the spreadsheet is to get your view of the relative effort contributed to the project by each member. It is not expected that all members of a group will make exactly the same contribution to the project; you have different roles in the group and come with a range of skills - it is a team effort! This is a management tool to get the big picture and see if there are any significant discrepancies. As such, it may influence the apportionment of marks for the project, though the default remains that every member will get the same mark.

The source code should contain:

• A very brief document called README.txt which details a little bit about the project, the people involved and how the source directory is organized and how a user would go about running the application.
• A document called INSTALL.txt which details how to build, install and run the software including running the acceptance tests. Other information such as login names and passwords, plus other essential requirements, e.g. some movies in your database for an initial search test. These instructions are to be very brief indeed, in point form, taking no more than HALF A PAGE maximum; they are not full documentation.
• Any user documentation as specified by the Client. This will be assumed to be part of the deliverables to be marked by the Client under the Acceptance Testing process. (You are recommended to get a clear specification from the Client as to what, if anything, is required here. Perhaps even add the docoumentation as a separate Acceptance Test section.)

If the platform is projects.csse.uwa.edu.au, leave a working version on that machine in addition to the version in CVS. Ensure that file permissions are appropriate for the unit coordinator.