The design of the software architecture is driven by two types of requirements: Functional Requirements specify what the software system does, while Non-Functional Requirements (NFRs) express desired qualities, called Non-Functional Properties (NFPs). This paper illustrates three research challenges for addressing NFRs in the engineering process of autonomous robotic systems related to identification, modeling, and analysis of robotic-specific NFRs, reports on partial state-of-the-art solutions currently documented in the literature, discusses possible steps to overcome current limitations.
(2019). Non-functional requirements in robotic systems: Challenges and state of the art . Retrieved from http://hdl.handle.net/10446/170355
Non-functional requirements in robotic systems: Challenges and state of the art
Brugali, Davide
2019-01-01
Abstract
The design of the software architecture is driven by two types of requirements: Functional Requirements specify what the software system does, while Non-Functional Requirements (NFRs) express desired qualities, called Non-Functional Properties (NFPs). This paper illustrates three research challenges for addressing NFRs in the engineering process of autonomous robotic systems related to identification, modeling, and analysis of robotic-specific NFRs, reports on partial state-of-the-art solutions currently documented in the literature, discusses possible steps to overcome current limitations.| File | Dimensione del file | Formato | |
|---|---|---|---|
|
2019RCAR NFR Robotics.pdf
Solo gestori di archivio
Versione:
postprint - versione referata/accettata senza referaggio
Licenza:
Licenza default Aisberg
Dimensione del file
179.6 kB
Formato
Adobe PDF
|
179.6 kB | Adobe PDF | Visualizza/Apri |
Pubblicazioni consigliate
Aisberg ©2008 Servizi bibliotecari, Università degli studi di Bergamo | Terms of use/Condizioni di utilizzo
