Assignment#4

Due Date: Friday, April 21 (at start of class)

In this assignment you are (teams of 5) to write an X page long (I am not going to specify a number as it will depend on your test cases,...etc, of your system) Test Report Document (TRD) for the Client/Server Assignment Submission System. (15 - 20 non-trivial test cases should be ok).

Download the following template (Test Report Document). Use this template as a guideline for the tasks that need to be done for this assignment. The format (fonts, etc) of this template is not consistent, so make sure the format of your final document is consistent.

Start by meeting with your group members and distributing the work. Now that the object design has been finalized, you may want to have 2 members of your group finalizing the implementation (if it hasn't been finalized yet), 2 members writing and executing test cases, and one preparing for the presentation. Each person's work should be reviewed by at least one other person in the group, and be prepared to merge and check your work with other group members. At the end, the document must be consistent in terms of formatting and, more importantly, concepts used throughout the document. On April 21 (at start of class), hand in your document (printed version), ALONG WITH REVISED RAD, SDD, and ODD documents enclosed in a binder....everyone . Also, please include a disk containing all the source code and TEST CASES, PLUS instructions describing how to run the test cases.

Marking Scheme: you will be marked out of 50 according to the following scheme:

• 3 marks: spelling (use a spell checker)
• 3 marks: aimed at the correct audience and understandable by them
• 5 marks: precise description of testing strategies (for unit, integration, and system)
• 13 marks: clear description of 15 - 20 (NON-TRIVIAL) test cases [unit testing]
• 13 marks: test analysis (running tests and comparing results) [unit testing]
• 4 marks: description of integration and system testing. Once you finished performing unit or class testing, how did you go about performing the integration and system testing? What errors were found and how did you fix them?
• 3 marks: consistent terms throughout the document. Make sure all terms used by different team members are consistent.
• 2 marks: changes AND description of changes made to the Requirements Analysis Document in the appropriate place (e.g. revision history)
• 2 marks: changes AND description of changes made to the System Design Document in the appropriate place (e.g. revision history)
• 2 marks: changes AND description of changes made to the Object Design Document in the appropriate place (e.g. revision history)

If you have any questions, please see me or send me an email but please allow two working days for a reply.