Home

Deliverables

Mon, 08/31/2009 - 12:50 — Richard Bubel

Scientific Deliverables

The list of published scientific deliverables:

  1. Deliverable 5.1 - Requirement Elicitation: elicits requirements representative to the theoretical and practical challenges that the envisioned method has to solve. We describe the selected requirements in form of detailed scenarios. Furthermore, the collected scenarios already may sketch the results of the envisioned solutions.
  2. Deliverable 1.1.a - Report on the Core ABS Language and Methodology: Part A: contains the definition of the core ABS language, an abstract executable modeling language intended to form the basis for extensions later that will support evolvability, features, and further concepts relevant for the modeling and analysis of software families.
  3. Deliverable 1.1.b - Report on the Core ABS Language and Methodology: Part B: reports the development of the HATS methodology as part of Task 1.1. Specifically this report describes a high level view of the HATS methodology, identifies relevant work tasks to each phase in the method and shows how work tasks’ contributions are related to the phases.
  4. Deliverable 2.2.a - First Report on Feature Selection and Integration: consists of an investigation of possible techniques that may help bring the abstract notion of features down to the concrete level of program code. These include context oriented programming, multiple dispatch, trait-based programming and delta modeling. We summarize these techniques and refer to publications investigating them more thoroughly.
  5. Deliverable 3.1.a - First Report On Evolvable Systems: reports on the investigations pursued in the setting of Task 3.1. The goal of this task is to analyze and model fundamental aspects of system and component evolution, formally pin down and compare the concepts, construct scenarios, and build formal execution models that can be subjected to evaluation, theoretical examination, comparison, and simulation.
    6. Period 2
  6. Deliverable 5.2 - Evaluation of Core Framework (supplementary models): tests the expressive power of the ABS language and HATS methodology in the case studies. The activities include extensive requirement analysis of the scenarios defined in Task 5.1. This task closely cooperates with the activities of Task 1.1, so that the requirement analysis drives the design of the innovative software development method developed in Task 1.1. It forms the basis for verification of Milestone M1.
  7. Deliverable 4.2 - Resource Guarantees: reports on the basic framework for resource usage analysis (a.k.a. cost analysis) of ABS programs as well as a series of advanced issues which aim at improving the efficiency, the accuracy and the applicability of the proposed framework. Besides, we have studied the verification of the resource bounds obtained by the resource usage analyzer by using the KeY system.
  8. Deliverable 1.2 - Full ABS Modelling Framework (supplementary code): reports on the definition of the full ABS language, an abstract executable modeling language intended for modeling and analysis of software product families. 
  9. Deliverable 2.2.b - Final report on Feature Selection and Integration: reports an investigation of possible techniques that may help bring the abstract notion of features down to the concrete level of program code. These include platform modeling, feature model- ing, views, feature Petri nets, context-oriented programming, multiple dispatch, trait-based programming and delta modeling.  As a main contribution of this deliverable, we propose a generalization of delta modeling. The approach is influenced by earlier delta modeling publications, by the AHEAD methodology and by trait-based pro- gramming. The published delta modeling formalism gives rise to a new design methodology, which is to become part of the HATS methodology.
  10. Deliverable 2.5 - Verification of Behavioral Properties: reports on a program logic for the HATS modeling language ABS. The program logic is based on symbolic execution and used to reason about functional behavior of ABS programs. We present further work on possible optimization concerning compositionality and full abstraction which promise a significantly better automation. We report further on our results concerning incremental verification and introduce a variety of techniques suitable to reduce redundancy and minimize the need for redoing analyses when an ABS program is changed locally. Also an analysis to detect and prove absence of dead-locks is presented. 
  11. Deliverable 3.1.b - Final report on Evolvable Systems: reports on the investigations pursued in the setting of Task 3.1. The goal of this task is to analyze and model fundamental aspects of system and component evolution, formally pin down and compare the concepts, construct scenarios, and build formal execution models that can be subjected to evaluation, theoretical examination, comparison, and simulation.
  12. Deliverable 3.4 - Evolvability at Bytecode Level: This deliverable reports on the development of runtime code evolution at the bytecode level through the use of software transformation techniques in the style of monitor inlining. The deliverable also reports on an experiment showing how deductive techniques can be used to automatically refine ABS models into bytecode.
    13. Period 3
  13. Deliverable 2.1 - Configuration Deployment (Paper Appendix): The report develops the lowest levels of a flexible architecture upon which to base models in ABS, an abstract executable modeling language intended for modeling and analysis of software product families. This lowest level of ABS models captures deployment concerns, such as the underlying concurrency and interaction models as well as an abstract failure model for the language, are considered.

Dissemination and Project Management

  1. Deliverable 6.4 - Dissemination Plan: This document is the current version of the dissemination plan. It is meant to be a living document that is updated regulary during the whole project duration but at least once in each reporting period. Over time, experiences in disseminating the HATS project results and new dissemination opportunities in general will require changes to the dissemination plan.
  2. Deliverable 7.2.a - Biannual Management Report (t6, t12, t18): The biannual management report is given by the project coordinator as presentation synchronized with the annual meeting and project review. 
  3. Deliverable 7.3 - Project Quality Plan: This document is the current version of the project quality plan detailing the measurements taken to ensure high scientific quality. It is meant to be a living document that is updated regularly during the whole project duration but at least once in each reporting period. Over time, experiences in conducting the HATS project will prompt changes to the project quality plan.
    4. Period 2
  4. Deliverable 6.2 - Exploitation strategy: presents the partial result of Task 6.2 (Exploitable Strategy), which is concerned with the preparation of a technology usage plan for the HATS project. The goal of this task is to maximize the opportunities for market adoption of the project results