Tool Support. We created a few case studies to explore the usefulness of our ideas and realised that tool support is crucial for even medium-sized projects. However, we didn’t want to pursue tool development (or the extension of the existing tool) without a solid theoretical foundation. We have now reached a point where the theory is mature enough to start building tool support. We considered using the existing requirements plug-in as a starting point, but eventually abandoned the idea. There were technical and methodological
Tool Support. ADLs provide a formal description of the system, thus they can be manipulated and reasoned about in an automated fashion by software tools. This tool support determines the usefulness of an ADL to a large extent. • Active Specification: An active specification reduces possible design options.
Tool Support. Active Specification: The EAST-ADL tooling actively supports the user during specification, e.g. the tool prevents syntactically incorrect connections between components. • Multiple Views: EAST-ADL provides possibilities for multiple views on different levels of abstraction. However, it is left up to the user to ensure the consistency between the different views. • Analysis: EAST-ADL supports validation techniques such as simulation, rapid control prototyping (RCP) and hardware/software in the loop and safety analysis. Simulation requires execution of the plant model and the system model, which are supported. • Refinement: EAST-ADL provides five levels of abstraction: Vehicle Layer, Analysis Level, Design Level, Implementation Level and Operational Level. The refinement between the first three levels is explicitly supported by the current EAST-ADL tools. • Implementation Generation: Currently there is no automated transformation from EAST- ADL to an implementation language such as AUTOSAR. • Dynamism: At the moment there is no support for property-preserving refactorings of models.
Tool Support. Tool support is required to enable the user to define a configuration, validate it, execute the platform instantiation and, in if required for adopting the QualiMaster infrastructure, to adjust the Configuration Meta Model or the specification of the platform instantiation (Challenge C4, cf. D5.2 for more details). We utilize two specific tools for this purpose, namely the QualiMaster infrastructure configuration tool and EASy-Producer, a prototypical SPLE tool developed by SUH. While the QualiMaster infrastructure configuration tool supports the domain users in configuring their platform, EASy-Producer is used for defining and changing the Configuration Meta Model and the derivation process. Please note that EASy-Producer does currently not provide domain-specific capabilities, while the QualiMaster infrastructure configuration tool is a domain-specific frontend supporting the Infrastructure Users in their tasks. In this section, we give an overview on the current state of both tools and, in particular, the improvements over existing work that already have been done during the QualiMaster project. We start with the QualiMaster infrastructure configuration tool and discuss the improvements for EASy-Producer afterwards. The QualiMaster infrastructure configuration tool (QM-IC for short as in D1.2) aims at simplifying the configuration of the QualiMaster infrastructure for the infrastructure users, namely, Infrastructure Administrator, Pipeline Designer and Adaptation Manager. As described in D5.1, QM-IC tool is based on the Configuration Core, which consists of EASy-Producer. QM-IC tool is being developed in the QualiMaster project. Where possible, it reuses functionality of EASy- Producer, e.g., to load IVML or VIL models, to reason on IVML models or to execute VIL models for instantiation. However, EASy-Producer does currently not provide domain-specific capabilities required to support the QualiMaster Infrastructure Users in their tasks, in particular not for configuring data processing pipelines. Therefore, QM-IC tool acts as a domain-specific configuration frontend, which also xxxxxxx Infrastructure Users from the generic SPLE capabilities of EASy-Producer. Please note that in another application setting, a domain-specific configuration tool could allow the user to model rooms with alarm zones, fire detectors and sirens required in the alarm system case [16], or (3D) racks and stapler cranes for configuring a warehouse layout [32]. On the user interfac...
Tool Support. In this section, we discuss the current state of the tool support for adaptation in QualiMaster based on the topics discussed in this section. Akin to the introduction of Section 8, we will follow in this section the MAPE-K cycle with an additional initial step on modeling the adaptation behavior specification. • Modeling: Basically, modeling the adaptive behavior with rt-VIL relies on the Configuration (Meta) Model and the Configuration Core, i.e., EASy-Producer. As concluded in Section 7.3, the configuration support provides a solid basis for our work. Thus, we will use the VIL implementation as a basis and extend the grammar, the semantic analysis, the language infrastructure (for the type system) as well as the language execution (model) in order to realize rt-VIL on top of VIL. Initial steps in this direction have already been carried out, i.e., the extension of the grammar, the language infrastructure and semantic analysis and the language execution have been prepared, the rt-VIL grammar has been specified (see also Appendix B), and the related parser and Eclipse editor (including initial syntax-highlighting and content-assist) have been generated using xText . As rt-VIL will extend EASy- Producer with domain-independent capabilities for runtime adaptation, also VIL will be extended by common functionality and elements of both languages, such as type checking operations for VIL expressions (actually present in IVML) or functions (as a special case of VIL rules). rt-VIL will also extend the QualiMaster configuration tool, in terms of a high-level specification support using a specialized editor as well as a detailed adaptation support as requested by REQ-C-13 and REQ-C-14.
Tool Support. In this section we give a brief introduction to the functionality of the tool Reqaid. This requirements tool is an application that has been developed and used in the project Aletheia [8]. Moreover, it is currently successfully used in the EU project Smart Products [9]. The IoT-A consortium decided to use Reqaid as a tool for documenting the requirements, as it supports the specifically defined requirements process. In particular Reqaid supports the following functions: • Version Control: Requirements and use cases can be changed as often as desired by persons of the project through the whole project cycle. Reqaid has an automatic version control to ensure that no data loss occurs after modifications. • Access Rights: Access rights ensure which user groups can view or change certain information such as use cases and requirements.
