-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathprocesses.html
552 lines (470 loc) · 49.4 KB
/
processes.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="UTF-8">
<meta http-equiv="X-UA-Compatible" content="IE=edge">
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<title>IoT-Guide | Processes</title>
<link rel="stylesheet" href="assets/css/process.css">
<link rel="stylesheet" href="assets/css/bootstrap.min.css">
<link rel="stylesheet" href="https://cdnjs.cloudflare.com/ajax/libs/font-awesome/4.7.0/css/font-awesome.min.css">
</head>
<body>
<header>
<nav class="navbar navbar-expand-lg navbar-dark bg-dark">
<div class="container-fluid">
<a class="navbar-brand" href="https://dsslucas.github.io/iot-guide/about">IoT-Guide</a>
<button class="navbar-toggler" type="button" data-bs-toggle="collapse" data-bs-target="#navbarTogglerDemo02" aria-controls="navbarTogglerDemo02" aria-expanded="false" aria-label="Toggle navigation">
<span class="navbar-toggler-icon"></span>
</button>
<div class="collapse navbar-collapse" id="navbarTogglerDemo02">
<ul class="navbar-nav ms-auto">
<li class="nav-item">
<a class="nav-link" href="https://dsslucas.github.io/iot-guide/sobre">Portuguese</a>
</li>
<li class="nav-item">
<a class="nav-link" href="https://dsslucas.github.io/iot-guide/about">About</a>
</li>
<li class="nav-item">
<a class="nav-link active" aria-current="page" href="https://dsslucas.github.io/iot-guide/processes">Processes</a>
</li>
<li class="nav-item">
<a class="nav-link" href="https://dsslucas.github.io/iot-guide/techniques">Techniques</a>
</li>
<li class="nav-item">
<a class="nav-link" href="https://dsslucas.github.io/iot-guide/contact">Contact</a>
</li>
</ul>
</div>
</div>
</nav>
</header>
<section class="teoria1">
<div class="container">
<h2>Processes</h2>
<div class="d-flex">
<div class="p-2 flex-fill align-items-center">
<p>Requirements Engineering has standards for the realization of software capable of meeting the requests of its customers. Thus, the importance of establishing an execution process in order to listen, analyze, develop and validate a software emerges. Still in planning, a scenario for the process varies according to specifications, internal policies and external factors, according to Rehman et al. <a href="#ref1">[1]</a>.</p>
<hr>
<h3>Phases</h3>
<p>Even though there is a possibility that processes can be created in different ways, Pohl and Rupp <a href="#ref2">[2]</a> highlighted in their book the importance of these steps: </p>
<ul>
<li>Elicitation: phase which the requirements by stakeholders and end users are harvested, which can be based on documentation, operating systems and case studies. The following techniques can be used to perform requirements elicitation: user stories, use cases, interviews, prototypes, among others;</li>
<li>Documentation: preparation of a document containing the project plan and recording the elicited requirements, serving as a resource for consulting any doubts;</li>
<li>Validation and verification: step that have the purpose of checking if the final product is coherent with what was elaborated in the software planning phase;</li>
<li>Management: involves features that ensure the availability of requirements, enabling fast and complete maintenance, traceability and versioning.</li>
</ul>
</div>
<div class="p-2 flex-fill image">
<img src="img/to-do-list.png" alt="Book" style="width: 400px;">
</div>
</div>
</div>
</section>
<section class="teste2">
<div class="container">
<hr>
<h2>Requirements Engineering Processes that address requirements validation in the context of Internet of Things (IoT)</h2>
<p>Each process developed by different authors varies according to its specification, proposal and specific situations. We categorize the processes related to requirements validation of Internet of Things as:</p>
<ul class="nav nav-pills mb-3 justify-content-center" id="pills-tab" role="tablist">
<li class="nav-item" role="presentation">
<button class="nav-link active" id="pills-fluxograma-tab" data-bs-toggle="pill" data-bs-target="#pills-fluxograma" type="button" role="tab" aria-controls="pills-fluxograma" aria-selected="true">BPMN</button>
</li>
<li class="nav-item" role="presentation">
<button class="nav-link" id="pills-diagrama-tab" data-bs-toggle="pill" data-bs-target="#pills-diagrama" type="button" role="tab" aria-controls="pills-diagrama" aria-selected="false">Diagrams</button>
</li>
<li class="nav-item" role="presentation">
<button class="nav-link" id="pills-template-tab" data-bs-toggle="pill" data-bs-target="#pills-template" type="button" role="tab" aria-controls="pills-template" aria-selected="false">Templates</button>
</li>
<li class="nav-item" role="presentation">
<button class="nav-link" id="pills-goal-tab" data-bs-toggle="pill" data-bs-target="#pills-goal" type="button" role="tab" aria-controls="pills-goal" aria-selected="false">Goal Model</button>
</li>
<li class="nav-item" role="presentation">
<button class="nav-link" id="pills-5w1h-tab" data-bs-toggle="pill" data-bs-target="#pills-5w1h" type="button" role="tab" aria-controls="pills-5w1h" aria-selected="false">5W1H</button>
</li>
<li class="nav-item" role="presentation">
<button class="nav-link" id="pills-core-tab" data-bs-toggle="pill" data-bs-target="#pills-core" type="button" role="tab" aria-controls="pills-core" aria-selected="false">CORE</button>
</li>
</ul>
<div class="tab-content" id="pills-tabContent">
<div class="tab-pane fade show active" id="pills-fluxograma" role="tabpanel" aria-labelledby="pills-fluxograma-tab">
<div class="row flex-row">
<div class="col-md-6">
<br>
<div class="card">
<div class="card-body">
<h5 class="card-title">A Requirements Engineering Process for IoT Systems</h5>
<p class="card-text">Authors: Silva et al. <a href="#ref3">[3]</a></p>
<p class="card-text">Techniques: BPMN.</p>
<p class="card-text">Description: The authors presented a process for developing Internet of Things systems using BPMN. The process is composed by three sub-processes in accordance with ISO/IEC/IEEE 12207.</p>
</div>
</div>
<br>
<div class="card">
<div class="card-body">
<h5 class="card-title">IoT System Development Methods</h5>
<p class="card-text">Authors: Giray et al.<a href="#ref6">[6]</a></p>
<p class="card-text">Techniques: BPMN.</p>
<p class="card-text">Description: The authors carried out a study of articles already existing in the literature and carried out an evaluation in fourteen parameters, using BPMN to illustrate the functioning.</p>
</div>
</div>
<br>
</div>
<div class="col-md">
<br>
<div class="card">
<div class="card-body">
<h5 class="card-title">REM4DSPL: A Requirements Engineering Method for Dynamic Software Product Lines</h5>
<p class="card-text">Authors: Sousa et al. <a href="#ref4">[4]</a></p>
<p class="card-text">Techniques: BPMN.</p>
<p class="card-text">Description: The authors proposed the REM4DSPL method using the concepts of Requirements Engineering and Dynamic Software Product Line (DSPL). The method is composed by three phases and was represented using BPMN.</p>
</div>
</div>
<br>
<div class="card">
<div class="card-body">
<h5 class="card-title">Towards a catalog of conflicts for HCI quality characteristics in UbiComp and IoT applications: Process and first results</h5>
<p class="card-text">Authors: Carvalho et al. <a href="#ref27">[27]</a></p>
<p class="card-text">Techniques: BPMN.</p>
<p class="card-text">Description: In order to minimize the problems of inconsistency in non-functional requirements elicitation and their consequences, the authors proposed a process in which each step is completed after a document analysis using a specific method or technique. In addition, each step of the process is cataloged in a database for reference purposes. The authors used BPMN.</p>
</div>
</div>
<br>
</div>
<hr>
<h2>References</h2>
<!-- Gerais -->
<p>Icons made by <a href="https://www.freepik.com" title="Freepik">Freepik</a> from <a href="https://www.flaticon.com/" title="Flaticon">www.flaticon.com</a></p>
<p id="ref1" name="Referência 1">[1] Rehman, Tousif ur, Muhammad Naeem Ahmed Khan e Naveed Riaz: Analysis of requirement engineering processes, tools/techniques and methodologies. International Journal of Information Technology and Computer Science (IJITCS), 5(3):40, 2013. <a href="http://j.mecs-press.net/ijitcs/ijitcs-v5-n3/IJITCS-V5-N3-5.pdf" target="_blank">Click here</a> to access.</p>
<p id="ref2" name="Referência 2">[2] Pohl, K. e C. Rupp: Requirements Engineering Fundamentals: A Study Guide forthe Certified Professional for Requirements Engineering Exam - Foundation Level - IREB compliant. Rocky Nook, 2011, ISBN 9781457111921. <a href="https://www.amazon.com/Requirements-Engineering-Fundamentals-Professional-Foundation/dp/193753877X" target="_blank">Click here</a> to access.</p>
<!-- Específicas -->
<p id="ref3" name="Referência 3">[3] Danyllo Silva, Taisa Guidini Gonçalves, and Ana Regina C. da Rocha. 2019. A Requirements Engineering Process for IoT Systems. In Proceedings of the XVIII Brazilian Symposium on Software Quality (SBQS'19). Association for Computing Machinery, New York, NY, USA, 204–209. <a href="https://doi.org/10.1145/3364641.3364664" target="_blank">Click here</a> to access.</p>
<p id="ref4" name="Referência 4">[4] Amanda Sousa, Anderson Uchôa, Eduardo Fernandes, Carla I. M. Bezerra, José Maria Monteiro, and Rossana M. C. Andrade. 2019. REM4DSPL: A Requirements Engineering Method for Dynamic Software Product Lines. In Proceedings of the XVIII Brazilian Symposium on Software Quality (SBQS'19). Association for Computing Machinery, New York, NY, USA, 129–138. <a href="https://doi.org/10.1145/3364641.3364656" target="_blank">Click here</a> to access.</p>
<p id="ref6" name="Referência 6">[6] Giray, Görkem and Tekinerdogan, Bedir and Tüzün, Eray: IoT System Development Methods. 1st Edition. 2017. Chapman and Hall/CRC. eBook: 9781315155005. <a href="http://dx.doi.org/10.1201/9781315155005-7" target="_blank">Click here</a> to access.</p>
<p id="ref27" name="Referência 27">[27] R. M. Carvalho, R. M. C. Andrade and K. M. de Oliveira, "Towards a catalog of conflicts for HCI quality characteristics in UbiComp and IoT applications: Process and first results", 2018 12th International Conference on Research Challenges in Information Science (RCIS), 2018, pp. 1-6. <a href="https://doi.org/10.1109/RCIS.2018.8406651" target="_blank">Click here</a> to access.</p>
</div>
</div>
<div class="tab-pane fade" id="pills-diagrama" role="tabpanel" aria-labelledby="pills-diagrama-tab">
<div class="row flex-row" >
<div class="col-md-4">
<br>
<div class="card">
<div class="card-body ">
<h5 class="card-title">A UML-based Proposal for IoT System Requirements Specification</h5>
<p class="card-text">Author: Gianna Reggio <a href="#ref10">[10]</a></p>
<p class="card-text">Techniques: UML Diagrams.</p>
<p class="card-text">Description: The author proposed the IoTReq, a process for requirements elicitation of IoT system using UML diagrams. The author did not carry out the requirements validation in a practical context.</p>
</div>
</div>
<br>
<div class="card">
<div class="card-body ">
<h5 class="card-title">Detecting IoT Applications Opportunities and Requirements Elicitation: A Design Thinking Based Approach</h5>
<p class="card-text">Authors: Dantas et al. <a href="#ref23">[23]</a></p>
<p class="card-text">Techniques: Affinity diagrams.</p>
<p class="card-text">Description: The authors proposed a method for requirements elicitation and designing in IoT systems. The proposed process uses Design Thinking and the authors used three requirements validation techniques: brainstorming, documentation and affinity diagrams of users and customers.</p>
</div>
</div>
<br>
<div class="card">
<div class="card-body ">
<h5 class="card-title">Modeling IoT Applications with SysML4IoT</h5>
<p class="card-text">Authors: Costa et al. <a href="#ref5">[5]</a></p>
<p class="card-text">Techniques: UML Diagrams.</p>
<p class="card-text">Description: The authors investigated the resolution of critical issues that can occur in the design area, such as the diversity to perform graphic design and the lack of processes capable of getting to the details of software requirements. Thus, the authors proposed the DevProcess process using UML diagrams.</p>
</div>
</div>
<br>
<div class="card">
<div class="card-body">
<h5 class="card-title">Design Science and ThinkLets as an Holistic Approach to Design IoT/IoS Systems</h5>
<p class="card-text">Authors: Reinhard Bernsteiner e Stephan Schlögl <a href="#ref25">[25]</a></p>
<p class="card-text">Techniques: UML Diagrams.</p>
<p class="card-text">Description: The authors used the Design Science Reseach methodology and the ThinkLets tool to create detailed documentation for a system, with the help of UML diagrams and Brainstorming.</p>
</div>
</div>
<br>
<div class="card">
<div class="card-body">
<h5 class="card-title">An Improved RE Framework for IoT-Oriented Smart Applications using Integrated Approach</h5>
<p class="card-text">Authors: Kaleem et al. <a href="#ref18">[18]</a></p>
<p class="card-text">Techniques: UML Diagrams.</p>
<p class="card-text">Description: The authors proposed a process for Requirements Engineering in IoT. To perform requirements validation, the authors used UML Diagrams and brainstorming.</p>
</div>
</div>
<br>
</div>
<div class="col-md-4">
<br>
<div class="card">
<div class="card-body">
<h5 class="card-title">Key Abstractions for IoT-Oriented Software Engineering</h5>
<p class="card-text">Author: Franco Zambonelli <a href="#ref12">[12]</a></p>
<p class="card-text">Techniques: UML Diagrams.</p>
<p class="card-text">Description: The author reinforced key issues for designing an IoT system using UML diagrams.</p>
</div>
</div>
<br>
<div class="card">
<div class="card-body">
<h5 class="card-title">Conversion Method for User Experience Design Information and Software Requirement Specification</h5>
<p class="card-text">Authors: Ayumi Takeda e Yosuke Hatakeyama <a href="#ref13">[13]</a></p>
<p class="card-text">Techniques: UML Diagrams.</p>
<p class="card-text">Description: The authors proposed a process using UML diagrams, User Experience Design (UXD) and UX requirements to perform a system requirements specification in the context of IoT.</p>
</div>
</div>
<br>
<div class="card">
<div class="card-body ">
<h5 class="card-title">TrUStAPIS: A Trust Requirements Elicitation Method for IoT</h5>
<p class="card-text">Authors: Davide Ferraris e Carmen Fernandez-Gago <a href="#ref16">[16]</a></p>
<p class="card-text">Techniques: UML Diagrams and Template.</p>
<p class="card-text">Description: The authors proposed a method of requirements elicitation in the context of IoT with the aim of enhancing requirements validation. The authors used UML diagrams and JSON templates to help designing the process.</p>
</div>
</div>
<br>
<div class="card">
<div class="card-body ">
<h5 class="card-title">Specifying Functional Requirements and QoS Parameters for IoT Systems</h5>
<p class="card-text">Authors: Costa et al. <a href="#ref22">[22]</a></p>
<p class="card-text">Techniques: UML Diagrams.</p>
<p class="card-text">Description: The authors proposed the IoT-RML process for specifying and modeling requirements accurately and minimizing conflicts between requirements. The IoT-RML specifies both functional and non-functional requirements (Quality of Service) and uses the SysML language to represent the models used in the process, based on UML diagrams.</p>
</div>
</div>
<br>
<div class="card">
<div class="card-body">
<h5 class="card-title">Uma Tecnologia para Apoiar a Engenharia de Requisitos de Sistemas de Software IoT</h5>
<p class="card-text">Authors: Silva et al. <a href="#ref17">[17]</a></p>
<p class="card-text">Techniques: UML Diagrams Template.</p>
<p class="card-text">Description: The authors provided a template to fill in information about IoT processes, based on techniques SCENARI<small>oT</small> and SCENAR<small>IoT</small>CHECK, being useful for the elaboration of a software document.</p>
</div>
</div>
<br>
</div>
<div class="col-md-4">
<br>
<div class="card">
<div class="card-body ">
<h5 class="card-title">Intelligent Parking Management by Means of Capability Oriented Requirements Engineering</h5>
<p class="card-text">Authors: Hamdi et al. <a href="#ref15">[15]</a></p>
<p class="card-text">Techniques: CORE, UML Diagrams and Goal Model</p>
<p class="card-text">Description: The authors proposed a process in the context of smart cities using Capacity Oriented Requirements Engineering (CORE), serving as a basis for creating a smart parking system using UML diagrams and Goal Model to perform requirements elicitation and analysis.</p>
</div>
</div>
<br>
<div class="card">
<div class="card-body ">
<h5 class="card-title">Stakeholder Identification and Use Case Representation for Internet-of-Things Applications in Healthcare</h5>
<p class="card-text">Authors: Laplante et al. <a href="#ref24">[24]</a></p>
<p class="card-text">Techniques: UML Diagrams.</p>
<p class="card-text">Description: The authors developed an IoT software in the hospital context, through a process based on system modeling. The authors used the rich picture technique to identify stakeholders and perform functional and non-functional requirements elicitation. The authors used UML diagrams.</p>
</div>
</div>
<br>
<div class="card">
<div class="card-body">
<h5 class="card-title">IoT Composer: Composition and Deployment of IoT Applications</h5>
<p class="card-text">Authors: Krishna et al. <a href="#ref26">[26]</a></p>
<p class="card-text">Techniques: UML Diagrams.</p>
<p class="card-text">Description: The authors proposed a web interface to serve end users and help programming in IoT devices using the LOTOS Specification Language, as well as a graphical interface to meet the needs of users. The process overview was illustrated using UML diagrams.</p>
</div>
</div>
<br>
<div class="card">
<div class="card-body">
<h5 class="card-title">Horizontal Requirement Engineering in Integration of Multiple IoT Use Cases of City Platform as a Service</h5>
<p class="card-text">Author: Toshihiko Yamakami <a href="#ref21">[21]</a></p>
<p class="card-text">Techniques: UML Diagrams.</p>
<p class="card-text">Description: The author proposed a framework to help the design of IoT systems using UML diagrams. This framework has three identification stages (interaction between use cases, coordination and impact), which can be added tables, checklists or other techniques.</p>
</div>
</div>
<br>
</div>
<hr>
<h2>References</h2>
<!-- Gerais -->
<p>Icons made by <a href="https://www.freepik.com" title="Freepik">Freepik</a> from <a href="https://www.flaticon.com/" title="Flaticon">www.flaticon.com</a></p>
<p id="ref1" name="Referência 1">[1] Rehman, Tousif ur, Muhammad Naeem Ahmed Khan e Naveed Riaz: Analysis of requirement engineering processes, tools/techniques and methodologies. International Journal of Information Technology and Computer Science (IJITCS), 5(3):40, 2013. <a href="http://j.mecs-press.net/ijitcs/ijitcs-v5-n3/IJITCS-V5-N3-5.pdf" target="_blank">Click here</a> to access.</p>
<p id="ref2" name="Referência 2">[2] Pohl, K. e C. Rupp: Requirements Engineering Fundamentals: A Study Guide forthe Certified Professional for Requirements Engineering Exam - Foundation Level - IREB compliant. Rocky Nook, 2011, ISBN 9781457111921. <a href="https://www.amazon.com/Requirements-Engineering-Fundamentals-Professional-Foundation/dp/193753877X" target="_blank">Click here</a> to access.</p>
<!-- Específicas -->
<p id="ref5" name="Referência 5">[5] B. Costa, P. F. Pires and F. C. Delicato, "Modeling IoT Applications with SysML4IoT," 2016 42th Euromicro Conference on Software Engineering and Advanced Applications (SEAA), 2016, pp. 157-164. <a href="https://ieeexplore.ieee.org/document/7592792" target="_blank">Click here</a> to access.</p>
<p id="ref10" name="Referência 10">[10] Reggio, Gianna: A UML-based Proposal for IoT System Requirements Specification. Em Proceedings of the 10th international workshop on modelling in software engineering,páginas 9–16, 2018. <a href="https://dl.acm.org/doi/10.1145/3193954.3193956" target="_blank">Click here</a> to access.</p>
<p id="ref12" name="Referência 12">[12] F. Zambonelli, "Key Abstractions for IoT-Oriented Software Engineering," in IEEE Software, vol. 34, no. 1, pp. 38-45, Jan.-Feb. 2017. <a href="https://doi.org/10.1109/MS.2017.3" target="_blank">Click here</a> to access.</p>
<p id="ref13" name="Referência 13">[13] Takeda A., Hatakeyama Y. (2016) Conversion Method for User Experience Design Information and Software Requirement Specification. In: Marcus A. (eds) Design, User Experience, and Usability: Design Thinking and Methods. DUXU 2016. Lecture Notes in Computer Science, vol 9746. Springer, Cham. <a href="https://doi.org/10.1007/978-3-319-40409-7_34" target="_blank">Click here</a> to access.</p>
<p id="ref15" name="Referência 15">[15] Hamdi M.S., Ghannem A., Loucopoulos P., Kavakli E., Ammar H. (2019) Intelligent Parking Management by Means of Capability Oriented Requirements Engineering. In: Wotawa F., Friedrich G., Pill I., Koitz-Hristov R., Ali M. (eds) Advances and Trends in Artificial Intelligence. From Theory to Practice. IEA/AIE 2019. Lecture Notes in Computer Science, vol 11606. Springer, Cham. <a href="https://doi.org/10.1007/978-3-030-22999-3_15" target="_blank">Click here</a> to access.</p>
<p id="ref16" name="Referência 16">[16] Ferraris, D., Fernandez-Gago, C. TrUStAPIS: a trust requirements elicitation method for IoT. Int. J. Inf. Secur. 19, 111–127 (2020). <a href="https://doi.org/10.1007/s10207-019-00438-x" target="_blank">Click here</a> to access.</p>
<p id="ref18" name="Referência 18">[18] S. Kaleem, S. Ahmed, F. Ullah, M. Babar, N. Sheeraz and F. Hadi, "An Improved RE Framewrok for IoT-Oriented Smart Applications Using Inetgrated Approach," 2019 International Conference on Advances in the Emerging Computing Technologies (AECT), 2020, pp. 1-6. <a href="https://doi.org/10.1109/AECT47998.2020.9194173" target="_blank">Click here</a> to access.</p>
<p id="ref21" name="Referência 21">[21] T. Yamakami, "Horizontal Requirement Engineering in Integration of Multiple IoT Use Cases of City Platform as a Service," 2017 IEEE International Conference on Computer and Information Technology (CIT), 2017, pp. 292-296. <a href="https://doi.org/10.1109/CIT.2017.54" target="_blank">Click here</a> to access.</p>
<p id="ref22" name="Referência 22">[22] B. Costa, P. F. Pires and F. C. Delicato, "Specifying Functional Requirements and QoS Parameters for IoT Systems," 2017 IEEE 15th Intl Conf on Dependable, Autonomic and Secure Computing, 15th Intl Conf on Pervasive Intelligence and Computing, 3rd Intl Conf on Big Data Intelligence and Computing and Cyber Science and Technology Congress(DASC/PiCom/DataCom/CyberSciTech), 2017, pp. 407-414. <a href="https://doi.org/10.1109/DASC-PICom-DataCom-CyberSciTec.2017.83" target="_blank">Click here</a> to access.</p>
<p id="ref23" name="Referência 23">[23] Lima Dantas D., Filgueiras L.V.L., Brandão A.A.F., Machado Domingues M.C., Ferreira M.R. (2020) Detecting IoT Applications Opportunities and Requirements Elicitation: A Design Thinking Based Approach. In: Streitz N., Konomi S. (eds) Distributed, Ambient and Pervasive Interactions. HCII 2020. Lecture Notes in Computer Science, vol 12203. Springer, Cham. <a href="https://link.springer.com/chapter/10.1007/978-3-030-50344-4_7" target="_blank">Click here</a> to access.</p>
<p id="ref24" name="Referência 24">[24] N. L. Laplante, P. A. Laplante and J. M. Voas, "Stakeholder Identification and Use Case Representation for Internet-of-Things Applications in Healthcare," in IEEE Systems Journal, vol. 12, no. 2, pp. 1589-1597. <a href="https://doi.org/10.1109/JSYST.2016.2558449" target="_blank">Click here</a> to access.</p>
<p id="ref25" name="Referência 25">[25] Bernsteiner R., Schlögl S. (2017) Design Science and ThinkLets as a Holistic Approach to Design IoT/IoS Systems. In: Uden L., Lu W., Ting IH. (eds) Knowledge Management in Organizations. KMO 2017. Communications in Computer and Information Science, vol 731. Springer, Cham. <a href="https://doi.org/10.1007/978-3-319-62698-7_43" target="_blank">Click here</a> to access.</p>
<p id="ref26" name="Referência 26">[26] A. Krishna, M. Le Pallec, R. Mateescu, L. Noirie and G. Salaün, "IoT Composer: Composition and Deployment of IoT Applications," 2019 IEEE/ACM 41st International Conference on Software Engineering: Companion Proceedings (ICSE-Companion), 2019, pp. 19-22. <a href="https://doi.org/10.1109/ICSE-Companion.2019.00028" target="_blank">Click here</a> to access.</p>
</div>
</div>
<div class="tab-pane fade" id="pills-template" role="tabpanel" aria-labelledby="pills-template-tab">
<div class="row flex-row">
<div class="col-md-4">
<br>
<div class="card">
<div class="card-body ">
<h5 class="card-title">TrUStAPIS: A Trust Requirements Elicitation Method for IoT</h5>
<p class="card-text">Authors: Davide Ferraris e Carmen Fernandez-Gago <a href="#ref16">[16]</a></p>
<p class="card-text">Techniques: UML Diagrams and Template.</p>
<p class="card-text">Description: The authors proposed a method of requirements elicitation in the context of IoT with the aim of enhancing requirements validation. The authors used UML diagrams and JSON templates to help designing the process.</p>
</div>
</div>
<br>
</div>
<div class="col-md-4">
<br>
<div class="card">
<div class="card-body">
<h5 class="card-title">Uma Tecnologia para Apoiar a Engenharia de Requisitos de Sistemas de Software IoT</h5>
<p class="card-text">Authors: Silva et al. <a href="#ref17">[17]</a></p>
<p class="card-text">Techniques: UML Diagrams Template.</p>
<p class="card-text">Description: The authors provided a template to fill in information about IoT processes, based on techniques SCENARI<small>oT</small> and SCENAR<small>IoT</small>CHECK, being useful for the software document elaboration.</p>
</div>
</div>
<br>
</div>
<div class="col-md">
<br>
<div class="card">
<div class="card-body">
<h5 class="card-title">Non Functional requirement analysis in IoT based Smart Traffic Management System</h5>
<p class="card-text">Authors: Mahalank et al. <a href="#ref20">[20]</a></p>
<p class="card-text">Techniques: Template and Checklist</p>
<p class="card-text">Description: The authors adopted a framework composed by three steps, templates and checklist to help during requirements validation.</p>
</div>
</div>
<br>
</div>
<hr>
<h2>References</h2>
<!-- Gerais -->
<p>Icons made by <a href="https://www.freepik.com" title="Freepik">Freepik</a> from <a href="https://www.flaticon.com/" title="Flaticon">www.flaticon.com</a></p>
<p id="ref1" name="Referência 1">[1] Rehman, Tousif ur, Muhammad Naeem Ahmed Khan e Naveed Riaz: Analysis of requirement engineering processes, tools/techniques and methodologies. International Journal of Information Technology and Computer Science (IJITCS), 5(3):40, 2013. <a href="http://j.mecs-press.net/ijitcs/ijitcs-v5-n3/IJITCS-V5-N3-5.pdf" target="_blank">Click here</a> to access.</p>
<p id="ref2" name="Referência 2">[2] Pohl, K. e C. Rupp: Requirements Engineering Fundamentals: A Study Guide forthe Certified Professional for Requirements Engineering Exam - Foundation Level - IREB compliant. Rocky Nook, 2011, ISBN 9781457111921. <a href="https://www.amazon.com/Requirements-Engineering-Fundamentals-Professional-Foundation/dp/193753877X" target="_blank">Click here</a> to access.</p>
<!-- Específicas -->
<p id="ref16" name="Referência 16">[16] Ferraris, D., Fernandez-Gago, C. TrUStAPIS: a trust requirements elicitation method for IoT. Int. J. Inf. Secur. 19, 111–127 (2020). <a href="https://doi.org/10.1007/s10207-019-00438-x" target="_blank">Click here</a> to access.</p>
<p id="ref17" name="Referência 17">[17] Silva, Danyllo, Bruno Pedraça de Souza, Taisa Guidini Gonçalves e Guilherme Horta Travassos: Uma Tecnologia para Apoiar a Engenharia de Requisitos de Sistemas de Software IoT. Em Ayala, Claudia P., Leonardo Murta, Daniela Soares Cruzes, Eduardo Figueiredo, Carla Silva, Jose Luis de la Vara, Breno de França, Martín Solari, Guilherme Horta Travassos e Ivan Machado (editores): Proceedings of the XXIII Iberoamerican Conference on Software Engineering, CIbSE 2020, Curitiba, Paraná, Brazil, November 9-13, 2020, páginas 342–355. Curran Associates, 2020. <a href="http://cibse2020.ppgia.pucpr.br/images/artigos/9/S09_P3.pdf" target="_blank">Click here</a> to access.</p>
<p id="ref20" name="Referência 20">[20] S. N. Mahalank, K. B. Malagund and R. M. Banakar, "Non Functional Requirement Analysis in IoT based smart traffic management system," 2016 International Conference on Computing Communication Control and automation (ICCUBEA), 2016, pp. 1-6. <a href="https://doi.org/10.1109/ICCUBEA.2016.7860147" target="_blank">Click here</a> to access.</p>
</div>
</div>
<div class="tab-pane fade" id="pills-goal" role="tabpanel" aria-labelledby="pills-goal-tab">
<div class="row flex-row">
<div class="col-md-4">
<br>
<div class="card">
<div class="card-body">
<h5 class="card-title">Emotion-oriented requirements engineering: A case study in developing a smart home system for the elderly</h5>
<p class="card-text">Authors: Curumsing et al. <a href="#ref14">[14]</a></p>
<p class="card-text">Techniques: Goal Model and Questionnaire.</p>
<p class="card-text">Description: The authors developed the SofiHub to help seniors how to adapt their home to a smart home and help their routine, provide comfort, ease the effects of loneliness and reassure their families. The authors adopted a Goal Model-based process to relate emotional and system goals. The authors used questionnaires to validate the requirements.</p>
</div>
</div>
<br>
</div>
<div class="col-md-4">
<br>
<div class="card">
<div class="card-body ">
<h5 class="card-title">Intelligent Parking Management by Means of Capability Oriented Requirements Engineering</h5>
<p class="card-text">Authors: Hamdi et al. <a href="#ref15">[15]</a></p>
<p class="card-text">Techniques: CORE, UML Diagrams and Goal Model</p>
<p class="card-text">Description: The authors proposed a process in the context of smart cities using Capacity Oriented Requirements Engineering (CORE), serving as a basis for creating a smart parking system using UML diagrams and Goal Model to perform requirements elicitation and analysis.</p>
</div>
</div>
<br>
</div>
<div class="col-md">
<br>
<div class="card">
<div class="card-body ">
<h5 class="card-title">Towards Modelling and Analysis of Spatial and Temporal Requirements</h5>
<p class="card-text">Authors: Mounir Touzani e Christophe Ponsand <a href="#ref11">[11]</a></p>
<p class="card-text">Techniques: Goal Model, KAOS and GORE.</p>
<p class="card-text">Description: The authors proposed diagrams to perform requirements integration and analysis in order to detect problems in the development process phases. The authors used Goal-oriented Requirements Engineering (GORE), Keep All Objectives Satisfied (KAOS) and Goal Model.</p>
</div>
</div>
<br>
</div>
<hr>
<h2>References</h2>
<!-- Gerais -->
<p>Icons made by <a href="https://www.freepik.com" title="Freepik">Freepik</a> from <a href="https://www.flaticon.com/" title="Flaticon">www.flaticon.com</a></p>
<p id="ref1" name="Referência 1">[1] Rehman, Tousif ur, Muhammad Naeem Ahmed Khan e Naveed Riaz: Analysis of requirement engineering processes, tools/techniques and methodologies. International Journal of Information Technology and Computer Science (IJITCS), 5(3):40, 2013. <a href="http://j.mecs-press.net/ijitcs/ijitcs-v5-n3/IJITCS-V5-N3-5.pdf" target="_blank">Click here</a> to access.</p>
<p id="ref2" name="Referência 2">[2] Pohl, K. e C. Rupp: Requirements Engineering Fundamentals: A Study Guide forthe Certified Professional for Requirements Engineering Exam - Foundation Level - IREB compliant. Rocky Nook, 2011, ISBN 9781457111921. <a href="https://www.amazon.com/Requirements-Engineering-Fundamentals-Professional-Foundation/dp/193753877X" target="_blank">Click here</a> to access.</p>
<!-- Específicas -->
<p id="ref11" name="Referência 11">[11] M. Touzani and C. Ponsard, "Towards Modelling and Analysis of Spatial and Temporal Requirements," 2016 IEEE 24th International Requirements Engineering Conference (RE), 2016, pp. 389-394. <a href="https://doi.org/10.1109/RE.2016.60" target="_blank">Click here</a> to access.</p>
<p id="ref14" name="Referência 14">[14] Curumsing, Maheswaree Kissoon, Niroshinie Fernando, Mohamed Abdelrazek, Rajesh Vasa, Kon Mouzakis e John Grundy: Emotion-oriented requirements engineering: A case study in developing a smart home system for the elderly. Journal of Systems and Software, 147:215–229, 2019, ISSN 0164-1212. <a href="https://www.sciencedirect.com/science/article/pii/S0164121218301341" target="_blank">Click here</a> to access.</p>
<p id="ref15" name="Referência 15">[15] Hamdi M.S., Ghannem A., Loucopoulos P., Kavakli E., Ammar H. (2019) Intelligent Parking Management by Means of Capability Oriented Requirements Engineering. In: Wotawa F., Friedrich G., Pill I., Koitz-Hristov R., Ali M. (eds) Advances and Trends in Artificial Intelligence. From Theory to Practice. IEA/AIE 2019. Lecture Notes in Computer Science, vol 11606. Springer, Cham. <a href="https://doi.org/10.1007/978-3-030-22999-3_15" target="_blank">Click here</a> to access.</p>
</div>
</div>
<div class="tab-pane fade" id="pills-5w1h" role="tabpanel" aria-labelledby="pills-5w1h-tab">
<div class="row flex-row">
<div class="col-md-6">
<br>
<div class="card">
<div class="card-body">
<h5 class="card-title">An Evidence-Based Framework for Supporting the Engineering of IoT Software Systems Mid-stage Research</h5>
<p class="card-text">Author: Rebeca Motta <a href="#ref19">[19]</a></p>
<p class="card-text">Techniques: 5W1H.</p>
<p class="card-text">Description: The author proposed a framework using the 5W1H methodology containing three steps in order to strengthen requirements validation for an IoT device to eliminate possible weaknesses.</p>
</div>
</div>
<br>
</div>
<hr>
<h2>References</h2>
<!-- Gerais -->
<p>Icons made by <a href="https://www.freepik.com" title="Freepik">Freepik</a> from <a href="https://www.flaticon.com/" title="Flaticon">www.flaticon.com</a></p>
<p id="ref1" name="Referência 1">[1] Rehman, Tousif ur, Muhammad Naeem Ahmed Khan e Naveed Riaz: Analysis of requirement engineering processes, tools/techniques and methodologies. International Journal of Information Technology and Computer Science (IJITCS), 5(3):40, 2013. <a href="http://j.mecs-press.net/ijitcs/ijitcs-v5-n3/IJITCS-V5-N3-5.pdf" target="_blank">Click here</a> to access.</p>
<p id="ref2" name="Referência 2">[2] Pohl, K. e C. Rupp: Requirements Engineering Fundamentals: A Study Guide forthe Certified Professional for Requirements Engineering Exam - Foundation Level - IREB compliant. Rocky Nook, 2011, ISBN 9781457111921. <a href="https://www.amazon.com/Requirements-Engineering-Fundamentals-Professional-Foundation/dp/193753877X" target="_blank">Click here</a> to access.</p>
<!-- Específicas -->
<p id="ref19" name="Referência 19">[19] Rebeca C. Motta. 2019. An Evidence-Based Framework for Supporting the Engineering of IoT Software Systems. SIGSOFT Softw. Eng. Notes 44, 3 (July 2019), 22–23. <a href="https://doi.org/10.1145/3356773.3356795" target="_blank">Click here</a> to access.</p>
</div>
</div>
<div class="tab-pane fade" id="pills-core" role="tabpanel" aria-labelledby="pills-core-tab">
<div class="row flex-row">
<div class="col-md-6">
<br>
<div class="card">
<div class="card-body ">
<h5 class="card-title">Intelligent Parking Management by Means of Capability Oriented Requirements Engineering</h5>
<p class="card-text">Authors: Hamdi et al. <a href="#ref15">[15]</a></p>
<p class="card-text">Techniques: CORE, UML Diagrams and Goal Model</p>
<p class="card-text">Description: The authors proposed a process in the context of smart cities using Capacity Oriented Requirements Engineering (CORE), serving as a basis for creating a smart parking system using UML diagrams and Goal Model to perform requirements elicitation and analysis.</p>
</div>
</div>
<br>
</div>
<hr>
<h2>References</h2>
<!-- Gerais -->
<p>Icons made by <a href="https://www.freepik.com" title="Freepik">Freepik</a> from <a href="https://www.flaticon.com/" title="Flaticon">www.flaticon.com</a></p>
<p id="ref1" name="Referência 1">[1] Rehman, Tousif ur, Muhammad Naeem Ahmed Khan e Naveed Riaz: Analysis of requirement engineering processes, tools/techniques and methodologies. International Journal of Information Technology and Computer Science (IJITCS), 5(3):40, 2013. <a href="http://j.mecs-press.net/ijitcs/ijitcs-v5-n3/IJITCS-V5-N3-5.pdf" target="_blank">Click here</a> to access.</p>
<p id="ref2" name="Referência 2">[2] Pohl, K. e C. Rupp: Requirements Engineering Fundamentals: A Study Guide forthe Certified Professional for Requirements Engineering Exam - Foundation Level - IREB compliant. Rocky Nook, 2011, ISBN 9781457111921. <a href="https://www.amazon.com/Requirements-Engineering-Fundamentals-Professional-Foundation/dp/193753877X" target="_blank">Click here</a> to access.</p>
<!-- Específicas -->
<p id="ref15" name="Referência 15">[15] Hamdi M.S., Ghannem A., Loucopoulos P., Kavakli E., Ammar H. (2019) Intelligent Parking Management by Means of Capability Oriented Requirements Engineering. In: Wotawa F., Friedrich G., Pill I., Koitz-Hristov R., Ali M. (eds) Advances and Trends in Artificial Intelligence. From Theory to Practice. IEA/AIE 2019. Lecture Notes in Computer Science, vol 11606. Springer, Cham. <a href="https://doi.org/10.1007/978-3-030-22999-3_15" target="_blank">Click here</a> to access.</p>
</div>
</div>
</div>
<br>
</div>
</section>
<footer>
<div class="container d-flex justify-content-center align-items-center">
<div><li class="list-unstyled">University of Brasilia</li></div>
<div><li>Institute of Exact Sciences</li></div>
<div><li>Departament of Computer Science</li></div>
</div>
</footer>
<script src="https://unpkg.com/masonry-layout@4/dist/masonry.pkgd.min.js"></script>
<script src="assets/js/jquery-3.6.0.min.js"></script>
<script src="assets/js/popper.min.js"></script>
<script src="assets/js/bootstrap.min.js"></script>
</body>
</html>