Date due: Every iteration through the RUP according to your project plan, but before subsequent steps are completed and before the end of the phase.

Goals

• As part of the verification of your software artifacts, conduct a walkthrough review of the most important document or documents created during this RUP phase. The document you review will change as you proceed through the RUP phases.
• Create and execute a test plan to verify that your software artifacts are correct and document the test plan and results in a Test Plan Document.

Comments

The goal of this part of the RUP is to verify that your software artifacts are bug free..

• For information on how to conduct a walkthrough refer to pages 96 and 439 in the book. Since the book is rather light on how to conduct a walk through, I will give a brief description here.
  • A walkthrough is a presentation by the team that developed the document to a group of reviewers. The reviewers' job is to find as many bugs in the document as possible, but without attacking the team personally. This requires a great deal of tact.
  • Since we have three teams this semester, each team will need to act as reviewers for another team in a round-robin fashion. If you pair up and cross review, one of the teams will be left out.
  • First, find a team to review your document.
  • Second, provide them with a document and a review agenda. Use the agenda template I've provided.
  • Third, the reviewers need to read and critique the document before the meeting.
  • Fourth, conduct the walkthrough.
• You should adapt as appropriate to your project the discussions in class and the outlines for the Test Plan Document.
  • Some of the sections in the outlines may not apply to your project. Just say, "Does not apply."
  • Some sections are mainly UML diagrams. However, we should be able to see HOW you arrive at your design. That requires significant textual explanations, not just a pile of UML diagrams.
  • Some sections may be rather brief text discussions.

1. I expect your report to include the following:
   • A summary of the walkthrough, including all bugs that were identified.
   • Sections outlined in Test Plan Document.
2. Follow the guidelines/rules of thumb presented in class.