Evaluation of Non-Functional Requirements for IoT Applications

Paiva, Joseane de O. V.; Andrade, Rossana M. C.; Carvalho, Rainara Maia

doi:10.5220/0010461901110119

Cited by 7 publications

(5 citation statements)

References 16 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Several studies have been conducted in the literature that have listed out the NFRs concerned with these systems. 24,33 Typically, NFRs are classified into two broad categories: 34 (1) Architectural NFRs and (2) Run-time NFRs. Architectural NFRs are those that are not directly measurable from the system's operational environment.…”

Section: Conceptsmentioning

confidence: 99%

“…As NFR conflict knowledge base for autonomous systems in particular robotic systems we rely on data collected from the existing literature (namely, References 27,28,32,33,[35][36][37][38] and by collating knowledge from domain experts. The document provided at contains the NFR conflict catalog that we have built and used in this research work.…”

Section: Nfr Conflict Identificationmentioning

confidence: 99%

See 1 more Smart Citation

SCARS: Suturing wounds due to conflicts between non‐functional requirements in autonomous and robotic systems

Roy,

Bag,

Deb

et al. 2023

Softw Pract Exp

View full text Add to dashboard Cite

In autonomous and robotic systems, the functional requirements (FRs) and non‐functional requirements (NFRs) are gathered from multiple stakeholders. The different stakeholder requirements are associated with different components of the robotic system and with the contexts in which the system may operate. This aggregation of requirements from different sources (multiple stakeholders) often results in inconsistent or conflicting sets of requirements. Conflicts among NFRs for robotic systems heavily depend on features of actual execution contexts. It is essential to analyze the inconsistencies and conflicts among the requirements in the early planning phase to design the robotic systems in a systematic manner. In this work, we design and experimentally evaluate a framework, called SCARS, providing: (a) a domain‐specific language extending the ROS2 Domain Specific Language (DSL) concepts by considering the different environmental contexts in which the system has to operate, (b) support to analyze their impact on NFRs, and (c) the computation of the optimal degree of NFR satisfaction that can be achieved within different system configurations. The effectiveness of SCARS has been validated on the iRobot Create3 robot using Gazebo simulation.

show abstract

Section: Conceptsmentioning

confidence: 99%

Section: Nfr Conflict Identificationmentioning

confidence: 99%

SCARS: Suturing wounds due to conflicts between non‐functional requirements in autonomous and robotic systems

Roy,

Bag,

Deb

et al. 2023

Softw Pract Exp

View full text Add to dashboard Cite

show abstract

“…Robotic autonomous systems consist of certain specific NFRs of concern like safety, transparency and fairness. Several studies have been conducted in the literature that have listed out the NFRs concerned with these systems [19,26] .…”

Section: Non-functional Requirements Of Robotic Systemsmentioning

confidence: 99%

“…As NFR conflict knowledge base for robotic autonomous systems we rely on data collected from the existing literature (namely, [21,22,26,[28][29][30][31][32] ) and by collating knowledge from domain experts. The document provided at 𝑔 contains the NFR conflict catalog that we have built and used in this research work.…”

Section: Nfr Conflict Identificationmentioning

confidence: 99%

SCARS: Suturing Wounds due to Conflicts between Non-Functional Requirements in Robotic Systems

Roy,

Bag,

Deb

et al. 2023

Preprint

View full text Add to dashboard Cite

Conflicts among non-functional requirements for robotic systems heavily depend on features of actual execution contexts. The main objective of this work is to design and experimentally evaluate a framework, called SCARS, providing: (a) a domain-specific language extending the ROS2 Domain Specific Language (DSL) concepts by considering the different environmental contexts in which the system has to operate, (b) support to analyze their impact on non-functional requirements, and (c) the computation of the optimal degree of non-functional requirement satisfaction that can be achieved within different system configurations. The effectiveness of SCARS has been validated on the Gazebo simulation for iRobot Create 3 robot.

show abstract

“…In a systematic mapping study [Paiva et al 2021], we focused on understanding how the NFR evaluations are conducted for IoT applications. Our string search also included the terms "Ubiquitous systems" and "Pervasive systems", as they are highly correlated with the IoT applications field.…”

Section: Related Workmentioning

confidence: 99%

Towards a Process for NFRs Evaluation in IoT Applications

Paiva

Carvalho

Andrade

2022

Anais Do XIV Simpósio Brasileiro De Computação Ubíqua E Pervasiva (SBCUP 2022)

View full text Add to dashboard Cite

The Internet of Things (IoT) is a paradigm characterized by a variety of objects that interact with each other using the internet to achieve common goals. IoT applications are more and more present in our lives, either in our homes, or on the streets, or in our work environments. These applications bring new Non-Functional Requirements highly related to the user interaction quality, such as context-awareness, synchronicity, and calmness. The evaluation of these NFRs can be challenging, because we may have to take into account qualitative and quantitative aspects. In this way, the evaluators can be confused about the steps they need to follow and the best order to perform the NFRs evaluation. After conducting a systematic mapping study about the NFR evaluation in IoT applications, we could not find a process that systematizes these activities stepby-step. Therefore, this paper proposes a process for evaluating non-functional requirements in IoT applications. This process divides the quality evaluation into two aspects, qualitative and quantitative, to capture quality measurements and subjective aspects of the IoT applications. To verify whether the established process meets the evaluators' needs, we applied 2 questionnaires with the experts and, based on the obtained results, we made some adjustments and came up with a preliminary version of the process that is presented in this paper.

show abstract

Evaluation of Non-Functional Requirements for IoT Applications

Cited by 7 publications

References 16 publications

SCARS: Suturing wounds due to conflicts between non‐functional requirements in autonomous and robotic systems

SCARS: Suturing wounds due to conflicts between non‐functional requirements in autonomous and robotic systems

SCARS: Suturing Wounds due to Conflicts between Non-Functional Requirements in Robotic Systems

Towards a Process for NFRs Evaluation in IoT Applications

Contact Info

Product

Resources

About