Table of all public deliverables of the SUPERSEDE project
|ID||Deliverable name||Short description||Short name of lead participant||Delivery date||Download|
|D1.1||Feedback management and monitoring approaches||Deliverable D1.1 presents the evaluation results of relevant feedback management and monitoring approaches, as well as online sources for feedback.|
Our studies reveal that researchers and practitioners have developed several tools and methods to support feedback management and monitoring. In total, we identified, analysed and discussed more than 100 approaches. We found that there is a lack of combined approaches, which consider both end-user feedback and monitoring information for decision-making in software projects. This highlights the need for the work planned to be done within SUPERSEDE.
|University of Zurich||September 2015||Download|
|D1.2||Direct multi-modal feedback gathering techniques, v1||Deliverable D1.2 “Direct multi-modal feedback gathering techniques v1” reports on main innovations of the current solution and provides an overview of key functionalities. Documented screenshots give an impression of prototyped end-users’ Graphical User Interfaces (GUIs). Furthermore, the document provides a technical description of the underlying architecture of the implemented solution and discusses implementation details of the front-end and back-end components developed.In order to allow the integration of the provided feedback gathering tool within the use cases, this document refers to an installation guide and user manual and also provides licensing information about the developed tool solution.||FHNW||November 2016||Download|
|D1.3||Direct multi-modal feedback gathering techniques, v2||The deliverable reports on main innovations of the feedback gathering tool made from M18 to M36. The key contributions include improvements and extensions of the feedback gathering tool components and the better integration of the feedback gathering tool into the overall SUPERSEDE solution with the help of several interfaces for other SUPERSEDE WPs. The underlying architecture of the implemented feedback gathering tool and implementation details of the front-end and back-end components developed are described. Documented screenshots of feedback form variants give an impression of the Graphical User Interfaces (GUIs) displayed to the end-user as feedback sender.||FHNW||April 2018||Download|
|D1.4||Comprehensive monitoring techniques, v1||The deliverable D1.4 describes the released prototype of the SUPERSEDE Monitoring tool, providing functional and technical descriptions of its architecture and components. Moreover, an installation guide and a user manual are provided to facilitate the usage or adoption of this tool within the SUPERSEDE use cases. Main technical and scientific contributions of the implemented solution are also described in this document with the aim to emphasize its novelties and innovations.||UPC||November 2016||Download|
|D1.5||Comprehensive monitoring techniques, v2||The deliverable D1.5 “Comprehensive monitoring techniques, v2” is the second deliverable of Task T1.3 “Development of comprehensive monitoring techniques”, and provides the results of the activities conducted in this task at M36. The key artefact of D1.5 is the final version of the monitoring system and its constituent monitoring tools.||UPC||April 2018||Download|
|D2.1||Data management v1||Deliverable D2.1 provides insights on the definition of the Big Data Management Platform for SUPERSEDE.|
Driven by the set of system requirements and functional areas, a conceptual reference architecture has been designed, whose goal is to target all the functional areas concerning SUPERSEDE. Such architecture, named Bolster, is a refinement of the well-known λ- architecture for big data systems.
The outcome of this deliverable provides a baseline to start the implementation of the big data platform for SUPERSEDE, and to leverage it in the work packages that there exist more dependencies with
|D2.2||Data management plan – 2nd version||The second version of the data management plan corresponds to the first software release in WP2. There are two main outcomes as part of this deliverable:|
A more detailed description on the architecture presented in the firs data management plan, and its specificities within SUPERSEDE. The description of a part of the Big Data governance protocol, which will provide adaptable and flexible mechanisms to store feedback and monitoring data.
|D2.3||Data Management v3||Deliverable D2.3 „Data Management v3“ concerns tasks T2.1 and T2.2 and corresponds to the second data management software release in WP2. There are two main outcomes as part of this deliverable:|
1. Scientific innovations on data management that present an approach for supporting the integration of data coming from different data sources, e.g., user feedback and data monitoring, by means of an integration-oriented ontology. Moreover, the approach deals with the evolution of data sources in such context.
2.An update to the software solution to support the scientific innovations.
|D2.4||Data Analysis||Deliverable D2.4 concerns tasks T2.3, T2.4 and T2.5, which were jointly developed by UPC, FBK and FNHW, and corresponds to the first data analysis software release in WP2. The main outcomes of this deliverable are as follows:|
1. A technological sound basis for Big Data analysis, specifically real-time monitoring data.
2. A technological sound basis for multi-modal user feedback analysis.
3. Demo prototypes showcasing the functionalities of (1) and (2).
|D2.5||Data Analysis v2||Deliverable D2.5 concerns tasks T2.3, T2.4 and T2.5, which were jointly developed by UPC, FBK, FHNW&UZH, and SIEMENS and corresponds to the second data analysis software release in WP2. The main outcomes of this deliverable are:|
1. An update to the platform for Big Data analysis, specifically ECA rules and CEP engine.
2. Ontologies related to the CEP and data analysis.
3. An approach for feedback-based ontology linking.
4. Event-log analysis.
5. Demo prototypes showcasing the functionalities of (1), (3), and (4).
|D3.1||Requirements for methods and tools||In this deliverable we present the results of a thorough use case (UC) analysis, which has been performed during the first three months of the project.|
Following a systematic approach, the analysis focused on an investigation of the as-is situation for all the three UCs, which concern the SIEMENS’ ECO System Platform for a smart city, the SEnerCon’s energy saving app, and the ATOS’ SMART Player for sport event webcasting. A first set of user stories were formulated that are the basis for further discussion and for the definition of to-be scenarios, which will include methods and tools to be developed in SUPERSEDE.
|D3.2||DM processes v1||This deliverable has the objective of describing the analysis of the decision making processes that are currently performed in the different SUPERSEDE use cases in order to cope with the problems related to the evolution and adaptation of running systems.|
A state-of-the-art analysis has been performed in order to identify the decision making methods proposed and evaluated in the recent literature. Then a suitable modelling language has been identified for the description of the decision making processes and of the different decision making tools
|D3.3||DM processes v2||Deliverable D3.3 is a joint deliverable of tasks T3.1 Building a catalogue of DM processes, and T3.2 Modelling DM processes. Both tasks were performed along three iterations, the last one ending at the time this deliverable is due, i.e. month M28.|
The previous deliverable of T3.1 is D3.1 Requirements for methods and tools (M3). D3.1 was ded- icated to the analysis of the requirements for the whole SUPERSEDE tool-suite that were elicited from the three project UCs. The results of T3.1 described in D3.3 concern revised and additional require- ments for the SUPERSEDE DMGame tool at support of software evolution, which were derived from the experience of the UCs validation and from a specific usability evaluation activity performed during the second and beginning of third year of the SUPERSEDE project.
The previous deliverable of T3.2 is D3.2 DM processes, v1 (M11), which presented the analysis of decision-making processes in the three project UCs, considering both software evolution and dynamic adaptation. The results of T3.2 described in D3.3 concern revised models of decision-making processes that are enabled thanks to the DMGame tool and the decision-making techniques for dynamic adapta- tion, which were developed and integrated in the project tool-suite. Results from the evaluation activities performed in the parallel task T3.1 have been taken into account in T3.2, together with the result of a specific quasi-experiment aiming at evaluating the use of gamification in the collaborative requirements prioritisation process enabled by the DMGame.
|D3.4||DSS for software evolution – v1||The deliverable D3.4 – DSS for software evolution – v1 is the first deliverable of task T3.3 Defining DSS for software evolution. It includes two parts:|
a) a description of the techniques used for the developed DSS,
b) the source code of the software implemented in the context of task T3.3.
|D3.5||DSS for software evolution v2||The deliverable D3.5 – DSS for software evolution – v2 is the concluding deliverable of task T3.3 Deﬁning DSS for software evolution. It complements and ﬁnalises the deliverable D3.4 – DSS for software evolution – v1). The deliverable includes two parts: a) a description of the techniques used for the developed DSS, b) the source code of the software implemented in the context of task T3.3.||Delta||April 2018||Download|
|D3.6||Methods and techniques for runtime DM, v1||This document is a technical report that accompanies the M18 software release of the SUPERSEDE DM support for dynamic adaptation and personalization framework. This framework computes adaptation actions aiming at recovering the supervised system back to its normal operation, upon the eventual detection of deviations on the system itself or of its influencing environment, during the supervision cycles of the MAPE-K control-loop. This framework not only provides DM suggestions for adapting a supervised external system, but also for reconfiguring the SUPERSEDE platform itself, concretely the monitoring and feedback- gathering frameworks.||ATOS||November 2016||Download|
|D3.7||Methods and techniques for runtime DM v2||This deliverable reports the improvements done to the DMGame tool form M18 to M36. For this, we provide functional and technical (e.g. architectural) descriptions of the overall framework, its components and adopted baseline technologies. It also describes the structure of the source code and provides instructions to build, deploy, and manage the prototype, targeting developers who are interested on extending (or customizing) its features, but also end-users aiming at applying it for the adaptation of their supervised systems.||FBK||April 2018||Download|
|D4.1||Methods and tools to enact software evolution v1||The objective of this deliverable is to determine the related works available for software release planning using optimization algorithms. With this objective in mind, this deliverable will be based on performing an academic literature review, a selection of a framework of optimization algorithms for the future implementation, and a market study to determine the available tools for release planning.|
The second objective of D4.1 is the description of the architecture for the tool that will be produced as part of the T4.1. This architectural description will include precise description of the architectural decisions made (such as the selection of technologies), and architectural views including other components from the scientific WPs to show the feasibility of the scientific WPs integration.
|D4.2||Methods and tools to enact software evolution, v2||This is the second deliverable of T4.1 which corresponds to the description of the first release of the proof of concept software implementation. In this deliverable we report on the advances and evolution of the architecture, and the decisions made related to the development process of the software evolution tool named as Replan. In this deliverable we will also provide technical information related to the deployment and installation requirements of this tool.||UPC||November 2016||Download|
|D4.3||Methods and tools to enact software evolution (v3)||In this deliverable (D4.3) we provide details of the final version of the RePlan tool together with the improvements made in the tool. We also provide technical information related to the changes made related to the deployment and installation of the tool.||UPC||April 2018||Download|
|D4.4||Methods and tools to enact software adaptation and personalization v1||This document provides a first specification (both functional and technical) of the Software Adaptation and Personalization Enactment framework (hereafter the Enactment framework). This framework collaborates with other Supersede frameworks in supporting run-time adaptation and personalization of software systems, driven altogether by the MAPE-K feedback loop.||ATOS||January 2016||Download|
|D4.5||Methods and tools to enact software adaptation and personalization, v2||This document is a technical report that accompanies the M18 software release of the SUPERSEDE Dynamic Adaptation and Personalization Enactment framework, named as DAPPLE. This framework manages the runtime dynamic adaptation and personalization enactment of adaptive systems, by applying adaptation actions suggested by the Decision Making, during supervision cycles of the MAPE-K control-loop. This report describes this software prototype, providing functional and technical (e.g. architecture) descriptions of the overall framework, its components and adopted baseline technologies. It also describes the structure of the source code and provides instructions to build, deploy, and manage the prototype, targeting developers who may be interested on extending (or customizing) its features, but also end-users aiming at applying it on the enactment of variability on their supervised adapted systems.||ATOS||November 2016||Download|
|D4.6||Methods and tools to enact software adaptation and personalization v3||This document is a technical report that accompanies the M36 final software release of the SUPERSEDE Dynamic AdaPtation and PersonaLization Enactment toolset, named as DAPPLE. This toolset manages the runtime dynamic adaptation and personalization enactment of adaptive systems, by applying adaptation actions suggested by the Decision Making (DM) tool, during supervision cycles of the MAPE-K control-loop.|
This report describes this software final release, providing functional and technical (e.g. architecture) descriptions of the toolset, its components and adopted baseline technologies. It also describes the structure of the source code and provides instructions to build, deploy, and manage the toolset, targeting developers who may be interested on extending (or customizing) its features, but also system administrators aiming at applying it on the enactment of variability on their supervised target adaptive systems (i.e. operational systems that require runtime adaptation to recover their normal operation after observed deviations caused by enviromental influences).
|D4.7||Feedback-gathering and monitoring reconfiguration techniques v1||This deliverable is organised into two main parts. The first part (sec. 3), describes the results produced in T4.3, which includes: an analysis of the needs for feedback gathering reconfiguration, which is performed with the use of scenarios inspired from the three project’s use cases; definitions of feedback gathering method configuration and reconfiguration; and a description of an approach to support the design of a reconfigurable feedback gathering method, as well as of feedback gathering methods that can reconfigure autonomously at run-time. For this last aspect monitoring requirements are used.|
The second part (sec. 4), describes the results produced in T4.4. It includes: an analysis of the needs for monitoring reconfiguration in SUPERSEDE; a set of definitions useful to describe the problem of monitoring reconfiguration; types of solutions as emerging from a state-of-the art analysis; and an early architecture.
|D4.8||Feedback-gathering and monitoring reconfiguration techniques, v2||This deliverable corresponds to the implementation results at month 18 of SUPERSEDE project of tasks T4.3 (Feedback-gathering reconfiguration) and T4.4 (Monitoring reconfiguration). These tasks consist of enacting, in an automated manner, the reconfiguration of the SUPERSEDE tools for gathering feedback from the user and for monitoring data (e.g. changing the frequency in which data is collected, modifying the format in which the feedback is requested to the end-user, etc.). These reconfigurations may be required because of changes in requirements, changes in the context, adaptations or evolution of the system; and are triggered by the Decision Making Process (WP3) following the SUPERSEDE lifecycle loop. In this deliverable we describe the first release of the proof of concept platform that implements such a reconfiguration solution, named reconfiguration enactment tool. In particular we provide implementation and technical details as well as documentation to install and use the software, accompanied with the links for downloading it.||UPC||November 2016||Download|
|D4.9||Feedback-gathering and monitoring reconfiguration techniques, v3||This deliverable reports the improvements done to the reconfiguration enactment tool for the feedback-gathering and monitoring tools from M18 to M36. For this, we provide functional and technical (e.g. architectural) descriptions of the overall framework of the enactment tool, its components and adopted baseline technologies. It also describes the structure of the source code and provides instructions to build, deploy, and manage the final tool solution, supporting developers in adopting, extending (or customizing) its features. The reconfiguration enactment tool introduced in this deliverable is publicly released under Apache License v2 on the SUPERSEDE GitHub repository.||FBK||April 2018||Download|
|D5.3||Requirements and architecture for the integration framework||SUPERSEDE offers a complete set of functionalities aimed at improving the feedback communication between end-users and application developers, and enabling the evolutionary and dynamic maintenance of these applications, based on collected user-feedback and runtime application data. This holistic approach is supported by a set of components mutually collaborating to enact the common SUPERSEDE processes. As the SUPERSEDE components do not work in isolation, they require an environment that enables them to: a) interact with the others in a coordinated manner, exchanging information, reacting to incoming events or producing them; b) interact with the end users, getting input from them, and presenting to them concrete information using a common user interface; c) interact with external services provided by third parties, including those provided by the SUPERSEDE use cases‘ platforms. This document provides the final public functional and technical specification of the SUPERSEDE platform that provides the functionality outlined above. The platform consists of the different SUPERSEDE components, embedded and integrated within the Integrated Framework (IF) and interfaced by the Front-End (FE), which is the facade between the components and the end-users. Concretely, this document focuses on the IF and FE, since the specifications for individual components will be delivered elsewhere by the responsible development teams||ATOS||July 2017||Download|
|D5.5||Tool Suite Implementation, v2||This report provides a functional and technical description of the second version of the SUPERSEDE Tool Suite Implementation software. The tool suite has been created by integrating components released by work-packages WP1, WP2, WP3 and WP4 at M18 into a single system by means of two base frameworks, the Integration Framework (IF) and the Front-End (FE).||DELTA||December 2016||Download|
|D5.6||Tool Suite Implementation, v3||This report provides a functional and technical description of the third release of the SUPERSEDE Tool Suite Implementation software. The tool suite has been created by integrating components released by work-packages WP1, WP2, WP3 and WP4 between M18 (October 2016) and M30 (October 2017) into a single system by means of two base frameworks, the Integration Framework (IF) and the Front-End (FE).||ATOS||October 2017||Download|
|D5.7||Tool Suite Implementation, v4||This document is the final report of a series that reported on the software frameworks, namely, the Front-end (FE) framework and the Integration Framework (IF), that were developed to aggregate all the SUPERSEDE components into a common platform. These frameworks succeeded on providing a seamlessly integrated and holistic solution, so its end-users were offered with a common SUPERSEDE interface to the entire workflow for software evolution and dynamic adaptation methods.||ATOS||April 2018||Download|
|D7.1||Dissemination Plans v1||This document is the core document for all envisaged communication and dissemination activities of the SUPERSEDE consortium throughout the project lifetime. At the same time this document lists all dissemination activities undertaken in the first six months of the project.||SEnerCon||September of 2015||Download|
|D7.2||Dissemination Plan, v2||This document is the second version of the dissemination plan for communication and dissemination activities of the SUPERSEDE consortium. It details the achievement of the project dissemination goals, e.g. by reaching the scientific community with important scientific publications; disseminating project results to the broad public through social media; or participating in conferences. This document also provides an outlook on the continuation of dissemination activities beyond the project end.||SEnerCon||May 2018||Download|
|D7.6||IPR Plan||This document describes a practical plan for the management of intellectual property rights (IPR) in SUPERSEDE. The goal of Task 7.4 is to define exploitation and IPR plan. Only the IPR Plan is covered by this document. It is worth to be noticed that the preparation of this deliverable has offered the occasion to all the partners, and especially the industrial partners, to exchange their ideas on this critical matter for defining suitable exploitation strategies.||SIEMENS||May 2015||Download|