Interpreted in the Context of Digital Health

1. Interpreted in the Context of Digital Health
Requirements Engineering Best Practice
Total 405 97% Total + 414 99% Total 384 92% Total 407 97% Total + 404 96%
Reqs. Prioritizing 252 60% Workshops 328 78% Informal Modeling + 210 50% Functional 343 82% Natural Language 374 89%
Release Planing 209 50% Feedback ± 183 44% Prototyping + 169 40% Scenarios ± 263 63% Use Cases 248 59%
Requirements Triage 206 49% Analysis ± 161 38% OOA ± 166 40% Quality 240 57% Informal Text 219 52%
Business Case 202 48% Design 149 36% Quality Checks 107 26% User Interfaces 238 57% User Stories 111 26%
Roadmapping 174 42% Creativity 142 34% SA 51 12% Processes ± 183 44% Shall Templates 94 22%
Vision ± 165 39% System Archeology 292 70% DDD 34 8% Rules 173 41% Other 37 9%
Other 1 0% Requirements Reuse 270 64% Other 36 9% Software Interfaces 157 37% UML Diagrams 245 58%
Copy/Paste 159 38% Structure 140 33% Use Case Diagrams 188 45%
Total 382 91% Delta Specification 121 29% Total + 391 93% Glossary ± 132 32% Activity Diagrams 128 31%
Reqs. Prioritizing 252 60% Standard Reqs. 81 19% Inspection + 266 63% Behavior 95 23% Class Diagrams 114 27%
Handshaking 209 50% Variability Analysis 42 10% Walk-Through + 175 42% Agents 71 17% Sequence Diagrams 89 21%
Conflict Management 167 40% Modeling-based 3 1% Peer/Advisor Review 161 38% Formal Properties 24 6% State Machines 54 13%
Strategy Alignment 125 30% Interviews + 265 63% Prototype Review 143 34% Other 26 6% Other 2 0%
Power Analysis 76 18% Document Analysis 211 50% Checklist ± 89 21% Graphical Processes 208 50%
Win-Win Negotiation 45 11% Creativity 183 44% Simulation 33 8% Total 405 97% Activity Diagrams 128 31%
Variant Analysis 31 7% Workshops 142 34% Automated Checking ± 30 7% Document 265 63% DFD 111 26%
Negotiation Analysis 29 7% Idea Castings 43 10% Other 4 1% Spreadsheet 149 36% BPMN; BPML 37 9%
Idea Databases 38 9% Database 146 35% Other 9 2%
Total 341 81% Introspection 118 28% Modeling Tool 135 32% SA Diagrams 177 42%
Change Management 243 58% Observation + 87 21% Drawing Tool 61 15% DFD 111 26%
Baselining 196 47% Surveys 50 12% Other 4 1% ERD + 94 22%
Traceability 167 40% Data Mining - 25 6% STD 62 15%
Progress Tracking 106 25% Other 12 3% User Screens 151 36%
Report Generation 60 14% Informal Drawings 139 33%
Process Measurement 55 13% Tables 67 16%
Other 3 1% Other 19 5%
3, 4
Requirements Management
Management
Product Planning Elicitation Requirement TypesAnalysis
Storage
Checking
Inquiry Specification
Stakeholder Negotiation
Notations
i4DS | Centre for Requirements Engineering | © Prof. Dr. Samuel Fricker

2. 01.10.2015i4Ds | Centre for Requirements Engineering | © Prof. Dr. Samuel A. Fricker 2
www.fi-star.eu

3. 01.10.2015i4Ds | Centre for Requirements Engineering | © Prof. Dr. Samuel A. Fricker 3
One of My Favorite Cases

4. 01.10.2015i4Ds | Centre for Requirements Engineering | © Prof. Dr. Samuel A. Fricker 4
Idea of the System

5. 01.10.2015i4Ds | Centre for Requirements Engineering | © Prof. Dr. Samuel A. Fricker 5
Requirements Engineering (RE)

6. 01.10.2015i4Ds | Centre for Requirements Engineering | © Prof. Dr. Samuel A. Fricker 6
Requirements Engineering as Hand-Off of Requirements
Formal spec
Natural Language

7. 01.10.2015i4Ds | Centre for Requirements Engineering | © Prof. Dr. Samuel A. Fricker 7
Requirements Engineering as Hand-Off of Requirements
Formal spec
Natural Language

8. 01.10.2015i4Ds | Centre for Requirements Engineering | © Prof. Dr. Samuel A. Fricker 8
State-of-the-Art (1/4): The use of specific notations and tools did NOT correlate
with RE success.
217 98%
179 95%
148 67%
110 58%
84 38%
64 34%
80 36%
52 28%
77 35%
65 34%
39 18%
21 11%
1 0%
3 2%
Drawing Tool
Other
Modeling Tool
Database
Document
Spreadsheet
Storage
Total
219 99%
176 93%
199 90%
168 89%
142 64%
104 55%
113 51%
102 54%
68 31%
43 23%
46 21%
44 23%
22 10%
14 7%
138 62%
102 54%
106 48%
79 42%
71 32%
54 29%
68 31%
44 23%
48 22%
39 21%
31 14%
21 11%
2 1%
0 0%
114 52%
88 47%
71 32%
Graphical Processes
Activity Diagrams
State Machines
Other
Class Diagrams
Sequence Diagrams
Use Case Diagrams
Activity Diagrams
Other
UML Diagrams
User Stories
Shall Templates
Use Cases
Informal Text
Total*
Natural Language
Notations
46 21%
44 23%
22 10%
14 7%
138 62%
102 54%
106 48%
79 42%
71 32%
54 29%
68 31%
44 23%
48 22%
39 21%
31 14%
21 11%
2 1%
0 0%
114 52%
88 47%
71 32%
54 29%
68 31%
40 21%
23 10%
13 7%
4 2%
3 2%
101 46%
72 38%
68 31%
40 21%
56 25%
35 19%
33 15%
28 15%
84 38%
63 33%
76 34%
61 32%
36 16%
29 15%
15 7%
4 2%
Informal Drawings
Tables
Other
STD
User Screens
DFD
ERD
Other
SA Diagrams
DFD
BPMN; BPML
Graphical Processes
Activity Diagrams
State Machines
Other
Class Diagrams
Sequence Diagrams
Use Case Diagrams
Activity Diagrams
Other
UML Diagrams
Shall Templates

9. 01.10.2015i4Ds | Centre for Requirements Engineering | © Prof. Dr. Samuel A. Fricker 9
State-of-the-Art: What does Matter? (2/4)
126 57%
71 38%
Business Case*
Problem
Solution

10. 01.10.2015i4Ds | Centre for Requirements Engineering | © Prof. Dr. Samuel A. Fricker 10
State-of-the-Art: What does Matter? (3/4)
160 72%
100 53%
Scenarios*

11. 01.10.2015i4Ds | Centre for Requirements Engineering | © Prof. Dr. Samuel A. Fricker 11
State-of-the-Art: What does Matter? (4/4)
189 86%
133 70%
Workshops*

12. 01.10.2015i4Ds | Centre for Requirements Engineering | © Prof. Dr. Samuel A. Fricker 12
How Smart is RE Practice?
The success-correlating practices rank
3, 9, and 21 out of 67 practices that are
used in at least 5% of the projects.
Natural Language 374 89%
Functional 343 82%
Workshops 328 78%
System Archeology 292 70%
Requirements Reuse 270 64%
Inspection + 266 63%
Interviews + 265 63%
Document 265 63%
Scenarios ± 263 63%
Reqs. Prioritizing 252 60%
UML Diagrams 245 58%
Change Management 243 58%
Quality 240 57%
User Interfaces 238 57%
Document Analysis 211 50%
Informal Modeling + 210 50%
Release Planing 209 50%
Handshaking 209 50%
Graphical Processes 208 50%
Requirements Triage 206 49%
Business Case 202 48%
3
9
21

13. 01.10.2015i4Ds | Centre for Requirements Engineering | © Prof. Dr. Samuel A. Fricker 13
Requirements Engineering as Experimentation together with Stakeholders
Dependent variables:
- Desired impacts of the system
Independent variables:
- Characteristics of the system
?
Usage process
and scenarios

14. System
Direct
System Context
Indirect
System Context
Management
Regulator
Interfacing
System
Interfacing
System
Support
Production
UserCustomer
Marketing
01.10.2015i4Ds | Centre for Requirements Engineering | © Prof. Dr. Samuel A. Fricker 14
Prepare Experimentation: Stakeholder and Problem Discovery

15. 01.10.2015i4Ds | Centre for Requirements Engineering | © Prof. Dr. Samuel A. Fricker 15
Prepare Experimentation: Concept Development

16. 01.10.2015i4Ds | Centre for Requirements Engineering | © Prof. Dr. Samuel A. Fricker 16
Do the Experiments: Approximate Step-wise the Real System and Context
Thought
Experiments
Laboratory
Experiments
Real-World
Experiments

17. 01.10.2015i4Ds | Centre for Requirements Engineering | © Prof. Dr. Samuel A. Fricker 17
Thought
Experiments

18. 01.10.2015i4Ds | Centre for Requirements Engineering | © Prof. Dr. Samuel A. Fricker 18
Laboratory Experiments

19. 01.10.2015i4Ds | Centre for Requirements Engineering | © Prof. Dr. Samuel A. Fricker 19
Real-World Experiments

20. 01.10.2015i4Ds | Centre for Requirements Engineering | © Prof. Dr. Samuel A. Fricker 20
Spread the Results: Communicate to Possibly Distant Late-Comers
The testers in Malaysia…
The developers that join during construction…
Real-World
Experiments

21. 01.10.2015i4Ds | Centre for Requirements Engineering | © Prof. Dr. Samuel A. Fricker 21
Videos for Knowledge Transfer about Requirements and Context
Capture of requirements experiments with video.
Hard-to-replicate situations
Intuitive behaviour
Context and rationales
Limited specification skills
Primary evidence
Prohibited dialogue
Learning need
Personnel fluctuation
Late-stage RE (testing)

22. 01.10.2015i4Ds | Centre for Requirements Engineering | © Prof. Dr. Samuel A. Fricker 22
Continue Experimentation: Adapt Product and Extend to New Contexts
The surgeons who work a bit differently…
Real-World
Experiments

23. 01.10.2015i4Ds | Centre for Requirements Engineering | © Prof. Dr. Samuel A. Fricker 23
Tools: Understand Impact through User Feedback
QoE Probe
Front-end: Android, iOS
Back-end: Qlik
AppEcho
Front-end: Android
Back-end: Jira

24. 01.10.2015i4Ds | Centre for Requirements Engineering | © Prof. Dr. Samuel A. Fricker 24
User Feedback for System Evolution and Adaptation
AtosSiemens
SEnerCon

25. 01.10.2015i4DS | Centre for Requirements Engineering | © Prof. Dr. Samuel A. Fricker 25
i4Ds | CeRE: Enable Developers in Making Smart Decisions
Find the requirements video here: https://www.youtube.com/watch?v=CBsOiabbNIc

26. 01.10.2015i4Ds | Centre for Requirements Engineering | © Prof. Dr. Samuel A. Fricker 26
419 Projects < 10 23 5% Banking, Finance 98 23% Research 32 8%
10-49 39 9% Automotive, Transport 54 13% Product, Platform 87 21%
50-249 42 10% Software, IT 51 12% Bespoke 237 57%
250-4499 144 34% Government, Military 40 10% Tender 42 10%
>= 4500 168 40% Healthcare, Medical 35 8% Other 21 5%
n/a 3 1% Insurance 31 7%
Telecommunications 31 7% Prototyping 23 5%
Europe 368 88% Manufacturing, Supply 22 5% Evolutionary 39 9%
Switzerland 248 59% Other 57 14% Incremental 113 27%
Germany 69 16% Hybrid 104 25%
Other Europe 51 12% Information System 260 62% Sequential 135 32%
Americas 26 6% Software-Intensive 62 15% Other 5 1%
Asia-Pacific 25 6% Engineering 28 7%
Other 69 16% < 4 54 13%
4-9 107 26%
Completely New 149 36% 10-19 89 21%
New Features or Use 107 26% 20-49 84 20%
Changed Solution 79 19% >= 50 82 20%
Enhancement 84 20% n/a 3 1%
< 4.5 27 6%
4.5-9 97 23%
9-18 119 28%
>= 18 165 39%
n/a 11 3%
Duration (calendar months)***
Product
Category
Process (Lifecycle Model)
Size (number of staff)***
Location
Project
Industry (application domain)
Type
Innovation
Company
Size (number of employees)***

27. 01.10.2015i4Ds | Centre for Requirements Engineering | © Prof. Dr. Samuel A. Fricker 27
What Requirements Engineering had to Achieve
Total 419 100%
Shared Understanding 214 51%
Specification Quality 197 47%
Clear Scope 160 38%
Efficiency 155 37%
User Satisfaction 145 35%
Timeliness 139 33%
Fit of Solution 94 22%
Estimation Reliability 65 16%
Architecture Quality 58 14%
Cost/Benefit Analysis 26 6%
Other 4 1%
RE Constraints

28. 01.10.2015i4Ds | Centre for Requirements Engineering | © Prof. Dr. Samuel A. Fricker 28
State-of-the-Art: How Successful is Industry in Doing RE?
Too Little 181 43%
Just Enough 229 55%
Too Much 9 2%
Rather Yes 385 92%
Yes 182 43%
Likely 203 48%
Rather No 34 8%
No 18 4%
Unlikely 16 4%
Success
Requirements Engineering Amount
Product Goal Achievement
AND
OR
221 successes
189 failures

29. 01.10.2015i4Ds | Centre for Requirements Engineering | © Prof. Dr. Samuel A. Fricker 29
RE Expertise – Overall
Successful projects employed a wider variety of RE techniques and defined more
requirement types than unsuccessful ones.
0
5
10
15
20
25
30
35
Avg. Number of RE Techniques
Successful RE Other RE
+25%
0
1
2
3
4
5
6
Number of Requirement Types
Successful RE Other RE
+26%

30. 01.10.2015i4Ds | Centre for Requirements Engineering | © Prof. Dr. Samuel A. Fricker 30
Thank you!