<?xml version="1.0"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
         xmlns:dc="http://purl.org/dc/elements/1.1/"
         xmlns:syn="http://purl.org/rss/1.0/modules/syndication/"
         xmlns="http://purl.org/rss/1.0/">




    



<channel rdf:about="http://www.ict-diva.eu/DiVA/DiVA/results/diva-deliverables/RSS">
  <title>Deliverables</title>
  <link>http://www.ict-diva.eu/DiVA</link>
  
  <description>
    
       This folder holds public project deliverables.
       
  </description>
  
  
  
            <syn:updatePeriod>daily</syn:updatePeriod>
            <syn:updateFrequency>1</syn:updateFrequency>
            <syn:updateBase>2010-07-08T23:57:01Z</syn:updateBase>
        
  
  <image rdf:resource="http://www.ict-diva.eu/DiVA/logo.jpg"/>

  <items>
    <rdf:Seq>
        
            <rdf:li rdf:resource="http://www.ict-diva.eu/DiVA/results/diva-deliverables/techreportreference.2010-02-09.9566845404"/>
        
        
            <rdf:li rdf:resource="http://www.ict-diva.eu/DiVA/results/diva-deliverables/techreportreference.2010-02-09.8872693924"/>
        
        
            <rdf:li rdf:resource="http://www.ict-diva.eu/DiVA/results/diva-deliverables/techreportreference.2010-09-09.9235154836"/>
        
        
            <rdf:li rdf:resource="http://www.ict-diva.eu/DiVA/results/diva-deliverables/techreportreference.2010-05-25.9374212311"/>
        
        
            <rdf:li rdf:resource="http://www.ict-diva.eu/DiVA/results/diva-deliverables/adaptationmetamodel1"/>
        
        
            <rdf:li rdf:resource="http://www.ict-diva.eu/DiVA/results/diva-deliverables/techreportreference.2010-09-06.6843768420"/>
        
        
            <rdf:li rdf:resource="http://www.ict-diva.eu/DiVA/results/diva-deliverables/techreportreference.2010-09-06.3048231161"/>
        
        
            <rdf:li rdf:resource="http://www.ict-diva.eu/DiVA/results/diva-deliverables/d3.1"/>
        
        
            <rdf:li rdf:resource="http://www.ict-diva.eu/DiVA/results/diva-deliverables/techreportreference.2010-09-08.9091395405"/>
        
        
            <rdf:li rdf:resource="http://www.ict-diva.eu/DiVA/results/diva-deliverables/techreportreference.2010-02-09.4130426420"/>
        
        
            <rdf:li rdf:resource="http://www.ict-diva.eu/DiVA/results/diva-deliverables/techreportreference.2009-06-30.4666661171"/>
        
        
            <rdf:li rdf:resource="http://www.ict-diva.eu/DiVA/results/diva-deliverables/techreportreference.2010-05-25.3865119317"/>
        
        
            <rdf:li rdf:resource="http://www.ict-diva.eu/DiVA/results/diva-deliverables/techreportreference.2010-05-25.9491643244"/>
        
        
            <rdf:li rdf:resource="http://www.ict-diva.eu/DiVA/results/diva-deliverables/techreportreference.2010-02-11.1964605691"/>
        
        
            <rdf:li rdf:resource="http://www.ict-diva.eu/DiVA/results/diva-deliverables/techreportreference.2010-05-25.5204790659"/>
        
    </rdf:Seq>
  </items>

</channel>

    <item rdf:about="http://www.ict-diva.eu/DiVA/results/diva-deliverables/techreportreference.2010-02-09.9566845404">        <title>D1.1: Survey and Evaluation Document of the Requirements Engineering for Dynamic Variability</title>        <link>http://www.ict-diva.eu/DiVA/results/diva-deliverables/techreportreference.2010-02-09.9566845404</link>        <description>Up till now the main body of Requirements Engineering work has been concerned with static elicitation, representation, and analysis of requirements [31, 53, 70]. However, with the recent emergence of a number of continuously dynamically changing mobile and ubiquitous systems as well as the complex dynamic system composition (such as crisis handling systems, or system construction via dynamic service acquisition) the need for consideration of dynamic change at requirements level has also emerged.   In this report we primarily consider the requirements and dynamic change from two perspectives:   1. Identifying the characteristics that are necessary to support dynamic change at requirements level;   2. Surveying present-day Requirements Engineering approaches to uncover the mechanisms via which they could handle dynamic change at the requirements level.   The report also reviews the activities needed for supporting requirements configuration management, since these   are an essential component for a transparent and controllable change management.   The results of this survey will be used to develop the DiVA Requirements Engineering approach for addressing challenges pertaining to analysis of dynamic variability (DiVA deliverables D1.2-D1.4). The preliminary outline of this approach is also sketched in this report.       Open Document</description>        <dc:publisher>No publisher</dc:publisher>        <dc:creator>RuzannaChitchyan</dc:creator>        <dc:rights></dc:rights>                <dc:date>2011-04-29T10:27:25Z</dc:date>        <dc:type>Techreport Reference</dc:type>    </item>
    <item rdf:about="http://www.ict-diva.eu/DiVA/results/diva-deliverables/techreportreference.2010-02-09.8872693924">        <title>D1.2 Framework for Identifying and Modelling of Dynamic Variability in Requirements</title>        <link>http://www.ict-diva.eu/DiVA/results/diva-deliverables/techreportreference.2010-02-09.8872693924</link>        <description>In the present document we present the first part of the DiVA RE approach which mainly focuses on answering the question on what (requirements, their justification and context) to model, as well as touches on the issue of how to restrict the proliferation of variants in requirements models. To address these questions, the DiVA RE approach proposes to:   • construct a feature tree from the input requirements text, thus identifying specific requirements that need to be modelled, and refining this tree with variations and adaptation points;   • recover the hard- and soft-goals related to the given requirements to provide a justification for them, and also to use a single goal-model for modelling the large set of potential variations;   • analyse the resultant goal/feature tree to extract the relevant context and related variability and constraints which restricts the set of potential configurations.    Open Document</description>        <dc:publisher>No publisher</dc:publisher>        <dc:creator>RuzannaChitchyan</dc:creator>        <dc:rights></dc:rights>                <dc:date>2011-04-29T10:29:39Z</dc:date>        <dc:type>Techreport Reference</dc:type>    </item>
    <item rdf:about="http://www.ict-diva.eu/DiVA/docs/D1.4%20Framework%20for%20evaluation%20of%20configuration%20alternatives%20and%20trade-offs.pdf">        <title>D1.4 Framework for evaluation of configuration alternatives and trade-offs</title>        <link>http://www.ict-diva.eu/DiVA/results/diva-deliverables/techreportreference.2010-09-09.9235154836</link>        <description>In the previous DiVA deliverables D1.2 and D1.3 we have presented the DiVA RE framework for identification and modelling of dynamic variability in user requirements and composition of system of systems using these models. In the present deliverable we continue to the refine the DiVA RE framework by: a) developing the previously outlined traceability support into a Framework for Evaluation of Configuration Alternatives and Trade-offs using the simulation results form the design/run time (as defined in the DiVA workplan); b) improving the DiVA RE framework constituents to address the shortcomings revealed as a result of their evaluation. The Evaluation Framework is based on propagating design refinements and model simulation results back to the requirements level to inform and support a scoped configuration evaluation and trade-off analysis from the stakeholder’s perspective. While DiVA RE framework evaluation provides useful input for its evolution. FMP Models: http://www.ict-diva.eu/DiVA/developer-zone/downloads/FMP.zip</description>        <dc:publisher>No publisher</dc:publisher>        <dc:creator>PhilGreenwood</dc:creator>        <dc:rights></dc:rights>                <dc:date>2010-09-13T09:37:43Z</dc:date>        <dc:type>Techreport Reference</dc:type>    </item>
    <item rdf:about="http://www.ict-diva.eu/DiVA/docs/D1.3%20Framework%20for%20Composition%20of%20Dynamic%20Variability%20in%20Requirements.pdf">        <title>D1.3 Framework for Composition of Dynamic Variability in Requirements</title>        <link>http://www.ict-diva.eu/DiVA/results/diva-deliverables/techreportreference.2010-05-25.9374212311</link>        <description>In the DiVA deliverable “D1.2: The Framework for Identification and Modelling of Dynamic Variability in Requirements” [2] we have presented the initial DiVA RE framework that supports modelling of user requirements from textual input using feature tree representations. Within such trees the commonality and variability points, as well as points of adaptation, are also identified and modelled. The present deliverable addresses two further challenges defined by the DiVA project workplan:   1 Supporting the modelling and analysis of “systems of systems” with DiVA RE framework, and   2 Supporting composition of dynamic variability with the DiVA RE models.   To address these challenges, the DiVA RE approach requires a way of identifying points of overlap in multiple requirement models, as well as a mechanism that allows composing DiVA models for different systems at such overlap points. In developing these mechanisms DiVA RE workpackage has established a collaboration with the DISCS project, whereby the graph comparison techniques incepted in DISCS are being utilised, validated, and extended for DiVA purposes, as well as continued to build on our past and current work. The present deliverable reports on this framework.</description>        <dc:publisher>No publisher</dc:publisher>        <dc:creator>MartinViktil</dc:creator>        <dc:rights></dc:rights>                <dc:date>2010-09-09T11:26:47Z</dc:date>        <dc:type>Techreport Reference</dc:type>    </item>
    <item rdf:about="http://www.ict-diva.eu/DiVA/docs/D2.1%20Transformation%20Framework.pdf">        <title>D2.1 - Transformation Framework</title>        <link>http://www.ict-diva.eu/DiVA/results/diva-deliverables/adaptationmetamodel1</link>        <description>Constructing and executing distributed systems that can automatically adapt to the dynamic changes of the environment are highly complex tasks. Non-trivial challenges include provisioning of efficient design time and run time representations, system validation to ensure safe adaptation of interdependent components, and handling of possible combinatorial explosions of adaptive system artefacts such as configurations, variant dependencies and adaptation rules. These are all challenges where current approaches offer only partial solutions. Furthermore, existing technologies are typically only provided at the implementation level which makes them complex to use.    This deliverable describes the first version of the model transformation framework in Work Package 2. As stated in the DoW the objective of WP2 is to develop a domain-specific language for adaptive system specifications, and a composition and transformation framework. The first phase of the project has mainly focused on the former part (the domain specific language for adaptive system specifications) and is described in this deliverable. The composition and transformation framework part of WP2 will be the focus in the second phase of DiVA.    This deliverable consists of three parts. The main part is the tools and metamodels developed so far. The second part is video tutorials showing the usage of these tools, while the third part is this document.    This document presents the domain-specific modelling language for adaptive system specification and the tools that support specification, model checking and design time simulation of the adaptation model of adaptive systems. The proposed approach combines aspect-oriented and model-driven principles to cope with the combinatorial explosion and provide model level representations of variants, context variables and adaptation rules. An open source Eclipse-based editor has been developed to support system specification according to the meta-model. Based on the implemented adaptation meta-model, model checking and simulation facilities are provided to prepare for safe adaptation. At runtime the adaptation models are used to drive the adaptation. The approach is validated through case studies.</description>        <dc:publisher>No publisher</dc:publisher>        <dc:creator>VegardDehlen</dc:creator>        <dc:rights></dc:rights>                <dc:date>2010-09-06T13:54:34Z</dc:date>        <dc:type>Techreport Reference</dc:type>    </item>
    <item rdf:about="http://www.ict-diva.eu/DiVA/docs/D2%202%20Transformation%20Framework.pdf">        <title>D2.2 - Transformation framework, final version</title>        <link>http://www.ict-diva.eu/DiVA/results/diva-deliverables/techreportreference.2010-09-06.6843768420</link>        <description>Constructing and executing distributed systems that can automatically adapt to the dynamic changes of the environment are highly complex tasks. Non-trivial challenges include provisioning of efficient design time and run time representations, system validation to ensure safe adaptation of interdependent components, and handling of possible combinatorial explosions of adaptive system artefacts such as configurations, variant dependencies and adaptation rules. These are all challenges where current approaches offer only partial solutions. Furthermore, existing technologies are typically only provided at the implementation level which makes them complex to use. This deliverable describes the final version of the model transformation framework in Work Package 2. As stated in the DoW the objective of WP2 is to develop a domain-specific language for adaptive system specifications, and a composition and transformation framework. This deliverable is an updated version of deliverable 2.1 which reported on the status of the work half-way through the project. The main revisions and extensions to D2.1 are: • Adaptation DSL: updated to reflect the latest developments. • Aspect framework: new section on the tools developed for architecture and aspect modelling. • Case Studies: Updated CAS case study, new section on the Thales case study and 3 new case studies. The reader of this deliverable will find all the most up-to-date information on the work carried on the WP2 transformation framework in this deliverable. This deliverable consists of two parts. The main part is the tools and meta-models developed in the context of WP2. The second part is this document.</description>        <dc:publisher>No publisher</dc:publisher>        <dc:creator>VegardDehlen</dc:creator>        <dc:rights></dc:rights>                <dc:date>2010-09-06T13:54:53Z</dc:date>        <dc:type>Techreport Reference</dc:type>    </item>
    <item rdf:about="http://www.ict-diva.eu/DiVA/docs/D2.3%20DiVA%20methodology.pdf">        <title>D2.3 - DiVA methodology</title>        <link>http://www.ict-diva.eu/DiVA/results/diva-deliverables/techreportreference.2010-09-06.3048231161</link>        <description>This deliverable explains a model-driven, iterative and test-driven methodology for developing adaptive systems using the DiVA tools and technologies. It covers the lifecycle from requirements analysis until deployment and consists of four main phases: 1. Requirements engineering 2. Modelling of the adaptation concerns 3. Modelling of runtime architecture 4. Transformation and deployment All of the phases and involved tools connect to form a coherent process, often involving semi- or fully automatic tool support where possible in the spirit of model-driven engineering. The DiVA methodology is concerned with developing the adaptive features of a system and is intended to be combined with existing tried-and-tested methodologies for development of the functional aspects of the software.</description>        <dc:publisher>No publisher</dc:publisher>        <dc:creator>VegardDehlen</dc:creator>        <dc:rights></dc:rights>                <dc:date>2010-09-06T13:57:31Z</dc:date>        <dc:type>Techreport Reference</dc:type>    </item>
    <item rdf:about="http://www.ict-diva.eu/DiVA/results/diva-deliverables/d3.1">        <title>D3.1: Survey and evaluation of approaches for runtime variability management</title>        <link>http://www.ict-diva.eu/DiVA/results/diva-deliverables/d3.1</link>        <description></description>        <dc:publisher>No publisher</dc:publisher>        <dc:creator>BriceMorin</dc:creator>        <dc:rights></dc:rights>                <dc:date>2009-06-30T19:05:00Z</dc:date>        <dc:type>Techreport Reference</dc:type>    </item>
    <item rdf:about="http://www.ict-diva.eu/DiVA/results/diva-deliverables/techreportreference.2010-09-08.9091395405">        <title>D3.3 Reference architecture - final version</title>        <link>http://www.ict-diva.eu/DiVA/results/diva-deliverables/techreportreference.2010-09-08.9091395405</link>        <description>This deliverable presents the final version of the reference architecture to support dynamic variability using model-driven engineering techniques and aspect models. This reference architecture leverages the design-models of WP2, as well as the reasoning techniques of WP4, at runtime. The purpose of this document is to provide an overview of the reference architecture, to detail the important parts of this reference architecture and give some implementation details. This document is associated with a software system, demonstrating the reference architecture, which is integrated into DiVA Studio (WP5). This document (D3.3) is an extension of D3.2. The main changes are: • The reference architecture is now based on OSGi, the former one was based on Fractal. We thus give some implementation details for OSGi (Section 6).. • Integration of the new version of SmartAdapters (weaver). In this new version, aspect models are now compiled into Java code, which makes it possible to weave aspect model at runtime, in an efficient way. We detail the compilation process of SmartAdapters as well as the new features of this weaver (Section 5). • The reference architecture now provides support for distribution and describes the architectural extensions to support distribution as well as co-existence and co-dependency. Furthermore it provides a distributed consistency framework to support distributed aspect configuration and reconfiguration (Section 8).      Open Document</description>        <dc:publisher>No publisher</dc:publisher>        <dc:creator>BriceMorin</dc:creator>        <dc:rights></dc:rights>                <dc:date>2011-04-29T11:02:32Z</dc:date>        <dc:type>Techreport Reference</dc:type>    </item>
    <item rdf:about="http://www.ict-diva.eu/DiVA/results/diva-deliverables/techreportreference.2010-02-09.4130426420">        <title>D3.2: Reference Architecture</title>        <link>http://www.ict-diva.eu/DiVA/results/diva-deliverables/techreportreference.2010-02-09.4130426420</link>        <description>This deliverable presents the first version of the reference architecture to support the dynamic variability using model-driven engineering techniques and aspect models. The purpose of the document is to provide an overview of the reference architecture, to detail some important parts of this reference architecture and give some implementation details. This document is associated with a software system, demonstrating the reference architecture on one of the DiVA case studies, to be integrated in the DiVA Studio.</description>        <dc:publisher>No publisher</dc:publisher>        <dc:creator>BriceMorin</dc:creator>        <dc:rights></dc:rights>                <dc:date>2010-02-09T08:59:12Z</dc:date>        <dc:type>Techreport Reference</dc:type>    </item>
    <item rdf:about="http://www.ict-diva.eu/DiVA/docs/D4.1%20Survey%20and%20evaluation%20of%20approaches%20for%20the%20adaptation%20reasoning%20framework.pdf">        <title>D4.1: Survey and evaluation of approaches for the adaptation reasoning framework</title>        <link>http://www.ict-diva.eu/DiVA/results/diva-deliverables/techreportreference.2009-06-30.4666661171</link>        <description>Creation of an adaptation reasoning framework for dynamic, adaptive, and distributed systems is not a trivial task. Such a framework reasons on the variability that is represented by models implementing DiVA's MDE ap-proach and which causes, due to the potential big size of such systems, an explosion of complexity.     A dynamic system operates in real-time and is in the potentially constant need to respond fast to component or context changes through global reconfiguration. Complexity explosion would, if not appropriately handled, result in unacceptable calculation costs and too long reaction time spans while deciding which of a large number of possible configuration variants is valid or even optimal.     This survey researches and evaluates existing reasoning approaches and shows ways to reduce reasoning com-plexity in the context of DiVA. Results will be the base of the later Reasoning Framework implementation of WP4 that is coupled to the concepts and implementations of the technical DiVA work packages 1, 2, and 3.</description>        <dc:publisher>No publisher</dc:publisher>        <dc:creator>MichaelHentze</dc:creator>        <dc:rights></dc:rights>                <dc:date>2009-06-30T18:33:17Z</dc:date>        <dc:type>Techreport Reference</dc:type>    </item>
    <item rdf:about="http://www.ict-diva.eu/DiVA/results/diva-deliverables/techreportreference.2010-05-25.3865119317">        <title>D4.2 Adaptation model and validation framework first version</title>        <link>http://www.ict-diva.eu/DiVA/results/diva-deliverables/techreportreference.2010-05-25.3865119317</link>        <description>This  technical report D4.2 is the follow-up to  D4.1, which holds background information about reasoning principles, algorithms and frameworks. It accompanies the ARF prototype  implementation integrated in DiVA Studio as part of WP5. Its purpose is to motivate and  explain the ARF interface and to describe its current implementation briefly.     Open Document</description>        <dc:publisher>No publisher</dc:publisher>        <dc:creator>MartinViktil</dc:creator>        <dc:rights></dc:rights>                <dc:date>2011-04-29T10:33:45Z</dc:date>        <dc:type>Techreport Reference</dc:type>    </item>
    <item rdf:about="http://www.ict-diva.eu/DiVA/results/diva-deliverables/techreportreference.2010-05-25.9491643244">        <title>D5.1 Diva Studio architecture</title>        <link>http://www.ict-diva.eu/DiVA/results/diva-deliverables/techreportreference.2010-05-25.9491643244</link>        <description>This document introduces the architecture of the D5.1 deliverable: the DiVA Studio software.     Open Document   The DiVA Studio is publicly downloadable from    http://developer.berlios.de/projects/diva-unix</description>        <dc:publisher>No publisher</dc:publisher>        <dc:creator>MartinViktil</dc:creator>        <dc:rights></dc:rights>                <dc:date>2011-05-02T12:21:24Z</dc:date>        <dc:type>Techreport Reference</dc:type>    </item>
    <item rdf:about="http://www.ict-diva.eu/DiVA/results/diva-deliverables/techreportreference.2010-02-11.1964605691">        <title>D6.1 Case Study Specification and Requirements</title>        <link>http://www.ict-diva.eu/DiVA/results/diva-deliverables/techreportreference.2010-02-11.1964605691</link>        <description></description>        <dc:publisher>No publisher</dc:publisher>        <dc:creator>DhouhaAyed</dc:creator>        <dc:rights></dc:rights>                <dc:date>2010-06-30T15:28:54Z</dc:date>        <dc:type>Techreport Reference</dc:type>    </item>
    <item rdf:about="http://www.ict-diva.eu/DiVA/results/diva-deliverables/techreportreference.2010-05-25.5204790659">        <title>D6.2 Case Study Implementation and Validation</title>        <link>http://www.ict-diva.eu/DiVA/results/diva-deliverables/techreportreference.2010-05-25.5204790659</link>        <description>This document has two purposes: the first one is to provide an evaluation plan detailing individual evaluation plans for each case study: the crisis management case study and the CRM (Customer Relationship Management) case study. The second one is to describe the case studies implementation and the evaluation of the DiVA technical results of the second period throughout the case studies.       Open the document</description>        <dc:publisher>No publisher</dc:publisher>        <dc:creator>MartinViktil</dc:creator>        <dc:rights></dc:rights>                <dc:date>2011-04-29T14:33:45Z</dc:date>        <dc:type>Techreport Reference</dc:type>    </item>




</rdf:RDF>

