A Step-Wise Approach for Integrating QoS throughout Software Development

Abstract

Abstract. When developing real-time systems such as avionics software, it is critical to ensure the performance of these systems. In general, deterministic Quality of Service (QoS) is guaranteed by the execution platform, independently of a particular application. For example, in the avionics domain, the ARINC 664 standard defines a data network that provides deterministic QoS guarantees. However, this strategy falls short of addressing how the QoS requirements of an application get transformed through all development phases and artifacts. Existing approaches provide support for QoS concerns that only cover part of the development process, preventing traceability. In this paper, we propose a declarative approach for specifying QoS requirements that covers the complete software development process, from the requirements analysis to the deployment. This step-wise approach is dedicated to control-loop systems such as avionics software. The domainspecific trait of this approach enables the stakeholders to be guided and ensures QoS requirements traceability via a tool-based methodology.

DiaSuite: A tool suite to develop Sense/Compute/Control applications

“…For example, interaction contracts have been recently introduced to describe interactions between components, allowing extensive programming support to be generated and new static verifications to be performed [7]. Another avenue of research is to enrich DiaSpec with non-functional concerns, such as safety [33], security [24] and Quality of Service [21], leveraging further our declarative approach to software design.…”

“…In doing so, we introduced declarations to allow the safety expert to specify at design time how errors are handled, guiding and facilitating the implementation of error handling code [33]. Also, we added Quality of Service (QoS) declarations [21] to express time constraints in entity/component communications. For each of these non-functional declarations, specific development support is generated.…”

“…For example, several ongoing projects in our research group are extending DiaSpec to address non-functional concerns such as safety [33], security [24] and Quality of Service (QoS) [21]. At the level of the compiler, these extensions have been developed by adding new grammar rules to the ANTLR DiaSpec specification and new StringTemplate files for the generation of the extension-specific code in the programming framework (e.g., containers dedicated to QoS monitoring), minimizing the impact on the compiler's code.…”

“…So far, we mainly reported on a development methodology dedicated to pervasive computing [8,10] and its generalization to the SCC paradigm [7]. Recently, we have been enriching our development methodology to address non-functional concerns such as safety [33], security [24] and Quality of Service [21]. Outline.…”

Internet of Things: From Small- to Large-Scale Orchestration

“…We illustrated this approach by introducing annotations in declarations to describe potential errors [14] or quality of service constraints [15] at the level of devices and related contexts and controllers. This extended approach to software design was applied to the avionics domain [9].…”