Non-Functional Requirements in Robotic Systems: Challenges and State of the Art

Brugali, Davide

doi:10.1109/rcar47638.2019.9044033

Cited by 4 publications

(7 citation statements)

References 39 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Researchers in Reference 33 have evaluated different NFRs that are of concern for IOT applications. There are limited works 23,24 in the existing state of the art that have tried to analyze conflicts among the NFRs specific to robotic autonomous systems.…”

Section: Nfr Conflict Analysismentioning

confidence: 99%

“…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%

“…In Reference 24, the author has reviewed different NFRs specific to robotic systems: how they are modeled and analyzed in the run‐time environment? The author has highlighted that existing state‐of‐the‐art focuses only on some specific NFRs in specific environments.…”

Section: Related Workmentioning

confidence: 99%

“… Non‐functional requirements of robotic systems Autonomous systems in particular robotic 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 24,33 34 (1) Architectural NFRs and (2) Run‐time NFRs.…”

Section: Preliminariesmentioning

confidence: 99%

See 3 more Smart Citations

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: Nfr Conflict Analysismentioning

confidence: 99%

Section: Conceptsmentioning

confidence: 99%

Section: Related Workmentioning

confidence: 99%

Section: Preliminariesmentioning

confidence: 99%

See 2 more Smart Citations

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

“…In [19] the author has reviewed different NFRs specific to robotic systems: how they are modeled and analyzed in the runtime environment? The author has highlighted that existing state-of-the-art focuses only on some specific NFRs in specific environments.…”

Section: Metamodels and Dslmentioning

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