1. Introduction to Requirements Eng. Copyright, 2001 © Jerzy R. Nawrocki Jerzy.Nawrocki@put.poznan.pl www.cs.put.poznan.pl/jnawrocki/mse/require/ Requirements Engineering Lecture 1 Requirements Engineering Lecture 1

2. J. Nawrocki, Requirements Eng. (1) 2 Plan of the lecture Organisational issues Structured meetings FAST Delphi method Fagan inspections

3. J. Nawrocki, Requirements Eng. (1) 3 Success stories Scholarships of the Ministry of National Education: Leszek GawronLeszek Gawron Wojtek GryncewiczWojtek Gryncewicz Grzegorz JachimkoGrzegorz Jachimko Tomek JaniszewskiTomek Janiszewski Michał JasinskiMichał JasinskiKKIO’2001: Grzegorz WieczerzakGrzegorz Wieczerzak

4. J. Nawrocki, Requirements Eng. (1) 4 SDS 2001/02 Laboratory 214 (6 workstations + server) Rational Suite CMMI Level 2 + XP (Customer) + RUP Standard activities: FAST, Delphi, Fagan inspectionsFAST, Delphi, Fagan inspections Roles for 5th-year students: Facilitator, Tester (acceptance tests), ReviewerFacilitator, Tester (acceptance tests), Reviewer Roles for 4 th -year students: Analyst, Project Manager, Configuration Manager, TrackerAnalyst, Project Manager, Configuration Manager, Tracker

5. J. Nawrocki, Requirements Eng. (1) 5 LecturesLectures 3.10: Introduction 3.10: Introduction 10.10: RequisitePro (1) 15.10: RequisitePro (2), 15:15, Prof. Club 24.10: RequisitePro (3) 31.10: ClearCase LT (1) 7.11: ClearCase LT (2) 7.11: ClearCase LT (2) 14.11: ClearQuest 21.11: SoDA (1) 28.11: SoDA (2)

6. J. Nawrocki, Requirements Eng. (1) 6 LecturesLectures 5.12: Rose (1) 5.12: Rose (1) 12.12: Rose (2) 19.12: CMMI Level 2 9.01: Personality issues 9.01: Personality issues 16.01: Pre-exam

7. J. Nawrocki, Requirements Eng. (1) 7 LaboratoriesLaboratories 10.10: Organisational issues, team game 24.10: RequisitePro 31.10: RequisitePro 7.11: ClearCase LT 7.11: ClearCase LT 14.11: ClearCase LT 21.11: ClearQuest 28.11: SoDA 5.12: SoDA 5.12: SoDA 12.12: Rose...... 16.01: Pre-exam 23.01: Grades

8. J. Nawrocki, Requirements Eng. (1) 8 GradingGrading Pre-exam: 14.01, 2 groups: 13:45 group A + B (rooms 722 + 214)13:45 group A + B (rooms 722 + 214) 15:00 group C + D (rooms 16 + 17)15:00 group C + D (rooms 16 + 17) 21.01: grades announcement Exam grades: 0.6 x Paper + 0.3 x Tutorials + 0.1 x Presence

9. J. Nawrocki, Requirements Eng. (1) 9 Plan of the lecture Organisational issues Structured meetings FAST Delphi method Fagan inspections

10. J. Nawrocki, Requirements Eng. (1) 10 Sommerville’s Model Requirements elicitation Requirements analysis Requirements negotiation RequirementsdefinitionRequirementsdefinition

11. J. Nawrocki, Requirements Eng. (1) 11 Developers Customers FASTFAST FAST = Facilitated Application Specification Technique JAD Joint Application Development - another approach to FAST Facilitator Recorder

12. J. Nawrocki, Requirements Eng. (1) 12 FASTFAST Facilitator - runs the meeting(s) Recorder - takes notes, serves tape recorder or video recorder Developers & customer representatives - work on requirements Senior manager - knows about the meeting date & time Persons involved

13. J. Nawrocki, Requirements Eng. (1) 13 FASTFAST The list of stakeholders and views should be ready before the project leaders start to organise the first FAST meeting. Get from the customer the initial list of requirements sources (manuals, organisation charts, technical data,..) and read it before the meeting. Conducting a FAST meeting via phone or e-mail should be avoided. Before the first meeting

14. J. Nawrocki, Requirements Eng. (1) 14 FASTFAST Product request (  Project Proposal) Aim & goals of the meeting Agenda for the meeting Information about place and time Input documents

15. J. Nawrocki, Requirements Eng. (1) 15 FASTFAST A worksheet to fill in Missing stakeholders Missing requirements sources Objects (devices, documents, etc.): external to the system produced by the system internal - used by the system Services that manipulate the objects Constraints (cost, size, time,...) Input documents

16. J. Nawrocki, Requirements Eng. (1) 16 FASTFAST Product justification (consensus) Presentation of the worksheets (one by one, no critique) Deciding (discussion) about: Stakeholders System architecture (objects) Services Constraints Validation criteria An agenda example

17. J. Nawrocki, Requirements Eng. (1) 17 FASTFAST Direct: Meeting minutes Indirect: Software Requirements Specification (validation criteria!) Meeting outcomes

18. J. Nawrocki, Requirements Eng. (1) 18 Plan of the lecture Organisational issues Structured meetings FAST Delphi method Fagan inspections

19. J. Nawrocki, Requirements Eng. (1) 19 Delphi method Rand Corporation, Boehm’81 A few experts individually produce effort estimates.A few experts individually produce effort estimates. A Delphi process is used to reach a consensus.A Delphi process is used to reach a consensus. Pythia

20. J. Nawrocki, Requirements Eng. (1) 20 Delphi method 1. Experts get the specification and an estimation form 2. They meet for discussion (project goals, assumptions, estimation issues) 3. Each expert anonymously lists the tasks and estimates the size 4. The estimates go to the estimate moderator. He tabulates the results and returns them to the experts. The Delphi procedure The estimate moderator

21. J. Nawrocki, Requirements Eng. (1) 21 Delphi method Estimator: Jerzy Nawrocki Date: 22.06.1999 Project: Sorting routine The estimates from the 1st round: e E M e e e E M e e 0 20 40 60 80 100 0 20 40 60 80 100 e - estimates, E - your estimate, M - median estimate Your estimate for the next round:......... Hours. A rationale for your estimate:........................................................................................................................................

22. J. Nawrocki, Requirements Eng. (1) 22 Delphi method 5. The experts meet to discuss the results. They review the tasks they have defined but not their size estimates. 6. The procedure is repeated from step 3 until the estimates are acceptably near The Delphi procedure The estimate moderator

23. J. Nawrocki, Requirements Eng. (1) 23 Plan of the lecture Organisational issues Structured meetings FAST Delphi method Fagan inspections

24. J. Nawrocki, Requirements Eng. (1) 24 Designer Fagan inspections Implementor Moderator Tester Review session

25. J. Nawrocki, Requirements Eng. (1) 25 Fagan inspections 1. Overview (whole team) 2. Preparation (individual) 3. Inspection (whole team) 4. Rework 5. Follow-up Designer Implem. Moderator Tester Review session

26. J. Nawrocki, Requirements Eng. (1) 26 Fagan inspections Overview (whole team) 500 not necessary Preparation (individual) 100 125 Inspection (whole team) 130 150 Rework 50 60 Follow-up - - I1I1I1I1 I2I2I2I2 Rate of progress (loc/h) Inspection session <= 2 hours 1 - 2 sessions per day

27. J. Nawrocki, Requirements Eng. (1) 27 SummarySummary RE has to support SDS Main theme: Rational Suite Structured meetings (FAST & inspections)

28. J. Nawrocki, Requirements Eng. (1) 28 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?