Group Requirements Inspection

1. Group Requirements Inspection Carefully Read Wiegers Ch. 14

2. Perform a Team Inspection • See p 238 Wiegers • all team members participate in the inspection • follow the process (p 240) • assign roles • prepare the materials • plan the meetings • use entry/exit criteria

3. The Technical Review Process • Pre-Review Activities • Review Meeting Activities • Post-Review Activities

4. Pre-Review Activities (Production team) • Prepare and make available the artifact to be reviewed • The design document (milestone 3 deliverable) • Supporting material (milestone 1& 2 deliverables) • Call the meeting • Participants • Time and place • Identification of artifact to be reviewed • Agenda

5. Pre-Review Activities (Review team) • Inspect the artifact and note comments. Identify • Standards compliance • e.g., document structure (incl. cross-references, sign-offs etc.), possibility of validation,… • Presentation quality • e.g., readability, clarity of information, well-definedness, completeness… • Contents quality • Conformance – does it satisfy all the requirements specifications • Structure – is it technically satisfactory

6. Pre-Review Activities (Review team) • Prioritize the comments • High-impact • Low-impact • Identify action items • Write it up • Deliver it to the reviewed team • (to the instructor)

7. Defect report:For each defect • Date corrected • By whom • Effort (in staff hours) • Work product corrected • Resolution status • Notes • Defect ID • Description • Procedure to reproduce • Platform info • Date identified • By whom • Severity • Phase

8. Review Meeting Activities • Review the artifact, not the team • Set an agenda, and maintain it • Limit debate and rebuttal • Identify problems, defer problem resolution • Use a recorder

9. Review Meeting Activities

10. Processing the meeting

11. Post-Review Activities • Analyze the comments • Determine course of action (action items) • … and take it • File • the review report, • the minutes from the meeting(s), • the action items • their follow-up

12. Requirements validation: Define validation checklists: Are the requirements • Complete? • Consistent? • Comprehensible? • Precise? • Traceable? • Checkable? • According to standards?

13. Work Product • Written document this Friday (26 May) • main body • introduction to the inspection document • purpose, roles, dates • high level explanation of what happened • abstract the results and plans for remedies • include the defect reports • and notes that led to them in appendix (ref’d) • appendices with meeting announcements, plan, etc.

14. Preliminary Test Document • Due with final documents • Refer to Wiegers ch 14 • conceptual test cases for each functional requirement • think: • boundaries • zeroes • exceptions