Slide 1

1 Requirements Elicitation Slinger Jansen

Slide 2

2 1. Motivation 2. Requirements 3. Continuous RE 4. The RE Framework 7. Fundamentals of Goal Orientation 8. Documenting Goals 9. Fundamentals of Scenarios 10. Scenario Types 11. Documenting Scenarios 12. Benefits of using Goals and Scenarios 13. Fundamentals of Solutions 14. Documenting Solution Oriented Requirements 15. Integration of the Three Perspectives 16. Fundamentals of Documentation 20. Interrelation of Model Based and Textual Requirements 21. Fundamentals of Elicitation 22. Elicitation Techniques 24. Fundamentals of Requirements Negotiation 27. Fundamentals of Requirements Validation 30. Fundamentals of Requirements Management 31. Requirements Traceability 32. Prioritizing Requirements 37. RE for SPL 38. Requirements-based Testing

Slide 3

3

Slide 4

4

Slide 5

5

Slide 6

6

Slide 7

7

Slide 8

8

Slide 9

9

Slide 10

10

Slide 11

11

Slide 12

12

Slide 13

13

Slide 14

14 Gathering from external sources Customer: Extension of product features: Specialization: new attributes, process variants Completion: covering the whole workflow Interoperability: interfacing with other products Market: Product positioning Standard functionality coverage Market distinction: unique selling points Partners: Product implementation Voice of customers Partner revenue generating features

Slide 15

15 Gathering from internal sources - 1 Company board Long term product vision Major product themes Influence from portfolio and lifecycle decisions Sales Input from Request for Information (RFI) and Request for Proposals (RFP) Short term vision Marketing Sense of the market; market trends, Competitors, market analysis

Slide 16

16 Gathering from internal sources - 2 Research & innovation Functional feature innovation Technical platform innovation; prototypes with new devices Development Refactoring of architectural problems Process optimization Services Features that facilitate implementation: migration tools, business modeling tools Voice of customer Support Frequently occurring problems

Slide 17

17 Communication channels Stakeholder input channel: Specific process for each channel Educate internal stakeholders about process obligations (sales and marketing, board, etc.) Do NOT allow bypassing of product management Agenda time allocation per input channel Always give a response to every input of a market requirement Careful with explicit communication of release inclusion, best in case of development completion

Slide 18

18 Requirements gathering techniques Lead user interviews User groups Workshops Brainstorming Beta customers Prototyping Questionnaires

Slide 19

19 Lead user interviews Interviews with representatives of certain groups of stakeholders or key accounts Lead Users are users of a product that currently experience needs still unknown to the public and who also benefit greatly if they obtain a solution to these needs (von Hippel, 1986) Involved stakeholdersAdvantagesDisadvantages Lead users Product manager(s) High-quality outcomeTime-consuming Difficult to find representative lead users

Slide 20

20

Slide 21

21

Slide 22

22

Slide 23

23

Slide 24

24

Slide 25

25 User groups Groups of customers who commonly use your products and services. They provide input on product improvements, and offer feedback on their needs and desires Involved stakeholdersAdvantagesDisadvantages Members of user groups Product manager(s) High-quality outcome, focused on actual business problems Improved customer relationships Risk of dominating users Risk of complain sessions Too much focus on low-level requirements

Slide 26

26

Slide 27

27

Slide 28

28

Slide 29

29

Slide 30

30 Workshops Or: Joint requirements development sessions Requirements are jointly identified and defined by stakeholders. Cross-functional implications that are unknown to individual stakeholders are uncovered. Involved stakeholdersAdvantagesDisadvantages Relevant internal and external stakeholders Product manager(s) Uncovering cross- functional issues High-quality outcome Customer buy-in Time-consuming Danger of opinion- leadership Who commits to requirements?

Slide 31

31

Slide 32

32

Slide 33

33

Slide 34

34

Slide 35

35 Brainstorming Gathering of stakeholders and the exchange of ideas in an open atmosphere where no one risks being ridiculed for their ideas and no ideas are rejected/criticized. Involved stakeholdersAdvantagesDisadvantages Relevant internal and external stakeholders Product manager(s) Many ideasToo many ideas Difficult to create a good atmosphere where everyone is involved Difficult to get good representation of customer base

Slide 36

36

Slide 37

37

Slide 38

38

Slide 39

39

Slide 40

40

Slide 41

41 Beta customers Users who test the beta-version of a working product in a real production environment Involved stakeholdersAdvantagesDisadvantages Customers Developer(s) Account manager(s) Product manager(s) Clear requirements Mutual trust and commitment Can also be used for testing customer- specific functionality Time-consuming Difficult to get good representation of customer base

Slide 42

42 Prototyping Users can experiment with the system and point out its strengths and weaknesses of the implemented requirements. Involved stakeholdersAdvantagesDisadvantages End users Developers/designers Product manager(s) Visualization stimulates new ideas Usability issues are also included Interaction between designer and end- user lead to high- quality outcome Time-consuming High costs Not all functionalities are covered Is it already done?

Slide 43

43

Slide 44

44

Slide 45

45

Slide 46

46

Slide 47

47 Questionnaires Research instrument to get quantitative data from respondents Involved stakeholdersAdvantagesDisadvantages End usersLot of information Low costs Difficult to create good questionnaires

Slide 48

48

Slide 49

49

Slide 50

50

Slide 51

51

Slide 52

52 Selection of techniques Experience Product team Experience Customer / User lowhigh low high Fuzzy problem Teaching Catch-up Mature Fuzzy problem: Brainstorming Workshops Teaching: Prototypes Beta-customers Catch-up: Lead user interviews User groups Work in user setting Mature: Questionnaires Workshops Prototypes Based on: A.M. Hickey, A.M. Davis, "Elicitation Technique Selection: How Do Experts Do It?," 11th IEEE International Requirements Engineering Conference (RE'03), pp.169, 2003.

Slide 53

53 Demonstration of Customer voting A. Electronic voting on prepared list of requirements B. User suggestions for Facebook features Find out which profiles are visited by your friends (y:15, n: 30) Show statistics of visitors of your profile (y: 9, n: 18) Turn off game application notifications from others (y: 45) Find out who visited your profile (y:17, n: 16) Face recognition functionality to find look-a-likes (y:28, n:7)

Slide 54

54 Customer Participation Session (CPS)

Slide 55

55

Slide 56

56

Slide 57

57

Slide 58

58

Slide 59

59

Slide 60

60

Slide 61

61

Slide 62

62

Slide 63

63

Slide 64

64

Slide 65

65

Slide 66

66

Slide 67

67

Slide 68

68

Slide 69

69

Slide 70

70

Slide 71

71

Slide 72

72

Slide 73

73

Slide 74

74

Slide 75

75

Slide 76

76

Slide 77

77

Slide 78

78

Slide 79

79

Slide 80

80

Slide 81

81

Slide 82

82

Slide 83

83

Slide 84

84

Slide 85

85

Slide 86

86

Slide 87

87

Slide 88

88

Slide 89

89

Slide 90

90

Slide 91

91

Slide 92

92 Questions?