1. Requirements Verification & Validation Jerzy.Nawrocki@put.poznan.pl www.cs.put.poznan.pl/jnawrocki/require/ Requirements Engineering & Project Management Lecture 9

2. J.Nawrocki, Verification and Validation XPrince Roles and V&V Project Manager Analyst Architect Time + Auditor

3. J.Nawrocki, Verification and Validation Architecture Aim & Scope XPrince Artefacts and V&V Business Model and System Scope Most Important Use Cases Architect. Vision & Tools Requirements Spec. Mockup Accept. Tests Frame Initial Prototype (code + test cases) GUI Design A&S Plan Init. Project Plan Architect. Plan Updat. Proj. Plan Analyst Architect Project Manager

4. J.Nawrocki, Verification and Validation Bibliography X 

5. J.Nawrocki, Verification and Validation Agenda Requirements Analysis & Negotiation Requirements Validation Capture & Recapture Introduction XPrince Team Project Lifecycle The Analyst Role The Architect Role The Project Manager Role Scaling up Conclusions

6. J.Nawrocki, Verification and Validation Agenda Requirements Analysis & Negotiation Requirements Validation Capture & Recapture Introduction XPrince Team Project Lifecycle The Analyst Role The Architect Role The Project Manager Role Scaling up Conclusions

7. J.Nawrocki, Verification and Validation Requirements Analysis and Negotiation The requirements document Requirements elicitation Reqs analysis & negotiation Describing requirements System modelling Requirements validation Requirements management RE for critical systems BasicIntermAdv 8 6 5 4 3 4 4 2 36 - 6 2 1 3 3 3 3 21 - 1 1 - - 1 2 4 9

8. J.Nawrocki, Verification and Validation Basic guidelines Analysis and negotiation Define system boundaries System Person 1 Person 2 Institution Device Process requirements System requirements Software requirements

9. J.Nawrocki, Verification and Validation Basic guidelines Analysis and negotiation Define system boundaries Use checklists for requirements analysis

10. J.Nawrocki, Verification and Validation A Checklist Example Does a requirement imply the need for some decision- making based on incomplete or unreliable information? Will the implementation of a requirement need information which is outside the defined database for the system? Is a requirement concerned with the core functionality of the system? Is a requirement concerned with the functionality or performance of equipment which is external to the system? Analysing system’s boundaries

11. J.Nawrocki, Verification and Validation Another Checklist Example a) Correct; b) Unambiguous; c) Complete; d) Consistent; e) Ranked for importance and/or stability; f) Verifiable; g) Modifiable; h) Traceable. IEEE Std 830-1998

12. J.Nawrocki, Verification and Validation A Checklist for Use Cases Is there a shared clear vision? Are there visible boundaries? Is there clear cast of characters describing end-users? Are all user-level use-cases user-valued transactions? Does each use case have a complete single goal? Is its naming clear and depicting the goal? Are the alternatives an exhaustive set? Are use cases describing just behaviour? Are adornments properly used? Are the conditions detectable?

13. J.Nawrocki, Verification and Validation Basic guidelines Analysis and negotiation Define system boundaries Use checklists for requirements analysis Provide software to support negotiations Plan for conflicts and conflict resolution Prioritise requirements

14. J.Nawrocki, Verification and Validation Intermediate guidelines Analysis and negotiation Classify requirements using a multidimensional approach System, User interface, Database, Communications, Security

15. J.Nawrocki, Verification and Validation Intermediate guidelines Analysis and negotiation Classify requirements using a multidimensional approach Use interaction matrices to find conflicts and overlaps System, User interface, Database, Communications, Security

16. J.Nawrocki, Verification and Validation Advanced guidelines Analysis and negotiation Assess requirements risks

17. J.Nawrocki, Verification and Validation Agenda Requirements Analysis & Negotiation Requirements Validation Capture & Recapture Introduction XPrince Team Project Lifecycle The Analyst Role The Architect Role The Project Manager Role Scaling up Conclusions

18. J.Nawrocki, Verification and Validation Requirements Validation The requirements document Requirements elicitation Reqs analysis & negotiation Describing requirements System modelling Requirements validation Requirements management RE for critical systems BasicIntermAdv 8 6 5 4 3 4 4 2 36 - 6 2 1 3 3 3 3 21 - 1 1 - - 1 2 4 9

19. J.Nawrocki, Verification and Validation Basic guidelines Requirements validation Check that the requirements document meets your standard Organise formal requirements inspections 

20. J.Nawrocki, Verification and Validation Artefact Reviews and Inspection Review = Analysis of an artefact (e.g. code, document) done by 1 or more people. Goals of review : Quality assurance Knowledge dissemination Review

21. J.Nawrocki, Verification and Validation FTR Procedure Casting Producer (author) Project Manager Facilitator Reviewer(s) Recorder FTR = Formal Technical Review (Formalny przegląd techniczny)

22. J.Nawrocki, Verification and Validation FTR Procedure 1. Producer advices the Project Manager + Facilitator that the artefact is ready and sends them a copy. 2. Facilitator contacts all the inspection participants and decides about the date and time of the meeting (the sooner the better). He also sends the artefact to the reviewers. 3. Facilitator writes the agenda for the meeting. 4. FTR meeting 5. Recorder prepares inspection report and sends it to the participants. A copy of it goes also to the Project Manager.

23. J.Nawrocki, Verification and Validation FTR Meeting Agenda’s template (I) Facilitator: Presents the agenda. The participants may propose changes. Recorder: Collects copies of the preparation forms. Producer: Presents the artefact. Reviewers may ask questions. Recorder takes notes (issues and defects).

24. J.Nawrocki, Verification and Validation FTR Meeting Agenda’s template (II) Recorder: Summerizes the issues and defects. All participants except the producer: Initial secret vote. Recorder: Collects the votes and presents the result. Producer: “Last word” All the participants except the producer: Final secret vote.

25. J.Nawrocki, Verification and Validation FTR Meeting Decision Acceptance. No modifications are necessary. Conditional acceptance. There are some defects but additional inspection is not necessary (the Project Manager will check the final version). Rejection. There are serious defects and an additional inspection is necessary.

26. J.Nawrocki, Verification and Validation Agenda Requirements Analysis & Negotiation Requirements Validation Capture & Recapture Introduction XPrince Team Project Lifecycle The Analyst Role The Architect Role The Project Manager Role Scaling up Conclusions

27. J.Nawrocki, Verification and Validation Capture-Recapture How many fish are there?

28. J.Nawrocki, Verification and Validation Capture-Recapture 1 Catch a sample

29. J.Nawrocki, Verification and Validation Capture-Recapture 1 Catch a sample 2 Tag them

30. J.Nawrocki, Verification and Validation Capture-Recapture 1 Catch a sample 2 Tag them 3 Release them

31. J.Nawrocki, Verification and Validation Capture-Recapture 1 Catch a sample 2 Tag them 3 Release them 4 Catch another group

32. J.Nawrocki, Verification and Validation Capture-Recapture 1 Catch a sample 2 Tag them 3 Release them 4 Catch another group 5 How many tagged?

33. J.Nawrocki, Verification and Validation Capture-Recapture 1 Catch a sample 2 Tag them 3 Release them 4 Catch another group 5 How many tagged?

34. J.Nawrocki, Verification and Validation Capture-Recapture 1 Catch a sample 2 Tag them 3 Release them 4 Catch another group 5 How many tagged? Total = 20 * 30 / 5 = 120

35. J.Nawrocki, Verification and Validation Capture-Recapture A B C Total defects = A * B / C If C = 0... Artefact

36. J.Nawrocki, Verification and Validation Capture-Recapture More than 2 reviewers A B unique Most unique defects found All others Total defects = A * B / C

37. J.Nawrocki, Verification and Validation Basic guidelines Requirements validation Check that the requirements document meets your standard Organise formal requirements inspections Use multidisciplinary teams to review requirements Define validation checklists 

38. J.Nawrocki, Verification and Validation Intermediate guidelines Requirements validation Use prototyping to animate requirements Write a draft user manual Propose requirements test cases 

39. J.Nawrocki, Verification and Validation Advanced guidelines Requirements validation Paraphrase system models 

40. J.Nawrocki, Verification and Validation Summary Requirements analysis: Checklists Requirements negotiation Requirements validation: Reviews & FTR Capture-Recapture Mockups

41. J.Nawrocki, Verification and Validation Questions?

42. J.Nawrocki, Verification and Validation Quality assessment 1. What is your general impression? (1 - 6) 2. Was it too slow or too fast? 3. What important did you learn during the lecture? 4. What to improve and how?