There are many "quality reports" called for in the "Life Cycle Of A CS577 Document" process suggested in my presentation (web-cast) of Sept 26, 2001. An updated version is shown below.
The above diagram shows all possible steps for each of the “first class” documents (OCD, Prototype (report), SSRD, SSAD, LCP, and FRD), but does not reflect the possibility of skipping steps or repeating them (looping through multiple cycles). In reality, your team’s Rose model is also an Artifact that should go through a similar process, but one where there is NO direct presentation to the ARB.
For EACH of the document types in each phase, list the steps in order they are performed, and then provide as an attachment to the list the actual “quality assessment” recording documents, especially the “defect” logs and Table SPD-8[1].
1. If you had a “Developer Client Discussion”, generate a “User Feedback Summary”[2] covering all items raised during the discussion AND the changes actually made.
2. If a review or presentation of your “Prototype” was used for development of the document,
3. If, in the process of developing or updating a document (the “Produce” action), you had occasion to ask your client, teammates or for comment, then generate a “User Feedback Summary”2 covering all items raised during the discussion AND the changes actually made.
4. Every document must go through some team-based “Quality Assessment Review” before the ARB. Your team must decide whether it will be an inspection or some other form of review: If you do or did an inspection, fill in the “577 Inspection Forms”[3]. If you do an “Internal Review”, then you will fill in the “Review Forms”[4] using the “internal review” mode.
5. Each document will be looked at, at least cursorily, during the ARB. Please attach a copy of your teams feed back forms AND any marked up pages from the documents.
6. Before grading, you will have to react to comments from the ARB. If you hold discussions with your client, colleagues of other than a simple clarification nature, make sure you also provide a “User Feedback” form at or comment
7. Finally, just before grading, you will have to update the document based on comments from the ARB. Use the Formal Review version of the Review Form5 for the list of issue areas and changes (AKA defects).
All the forms are included in the zip file.