!delivrables.png!



h1. WP1: Requirements and Architecture

*Leader:* [PetalsLink|soceda:Partners]



















|| Id || Name || Type || Status ||
| D1.1.1 | [Requirements of the project|^D1-1-1_Requirements_v0.9.pdf] | Document | (/) (T0+15) |
| D1.2.1 | [Overall Framework Model|^D1-2-1_Overall Framework Model-V1.0.pdf] | Document | (/) (T0+12) |
| D1.2.2 | SocEDA Framework Architecture | Document | _pending (T0+36)_ |


h1. WP2: Federated Middleware Layer

*Leader:* [INRIA/Sophia|soceda:Partners]



















|| Id || Name || Type || Status ||
| D2.1.1 | [Social Service Modelling |^D2.1.1 Social Service Modeling.pdf] | Document | (/) (T0+9) |
| D2.1.2 | [Social-aware Event Modelling and Matching|^D2-1-2_Social_Event_Matching_04.pdf] | Document | (/) (T0+18) |
| D2.2.1 | [Esper Engine versus requirements|^SocEDA D2.2.1 EsperEngine.pdf] | Document | (/) (T0+18) |
| D2.2.2 | A POC to illustrate Esper engine | Implementation | _pending (T0+24)_ |
| D2.2.3 | [Identification of requirements to support distributed CEP|^D2.2.3-Identification of requirements to support distributed CEP.pdf] | Document | (/) (T0+18) |
| D2.2.4 | SocEDA distributed CEP engine | Specification and Prototype | _pending (T0+36)_ |
| D2.3.1 | [Requirements to support reliable and efficient event brokering|^D2.3.1 Relevant state of the art in publish-subscribe mechanism in federated multioverlay environments.pdf] | Document | (/) (T0+12) |
| D2.3.2 | [SocEDA federated middleware specification|^SocEDA-D2.3.2- SocEDA federated middleware specification and implementation FINAL.pdf] and [implementation V1|soceda:Sources] | Document and Prototype | (/) (T0+18) |
| D2.3.3 | SocEDA federated middleware specification and implementation V2 | Document and Prototype | _pending (T0+36)_ |
| D2.4.1 | [Detailed SOTA of workflow adaptation/flexibility|^D2.4.1 Detailed state of the art of workflow adaptation-flexibility.pdf] | Document | (/) (T0+9) |
| D2.4.2 | [Adaptation Service (AdS) specification according to the workflow engine used in the ESBs|^D2.4.2_Adaptation Service _AdS_ specification according to the workflow engine used in the ESBs.pdf] | Document | (/) (T0+18) |
| D2.4.3 | [AdS implementation V1|^D2.4.3_Adaptation_service_implementation.pdf] | Implementation | (/) (T0+24) |
| D2.4.4 | Ads implementation V2 | Implementation | _pending (T0+36)_ |


h1. WP3: Monitoring and Governance

*Leader:* [Thales Communication|soceda:Partners]

| D3.2.2 | [Specification of the governance infrastructure v2|^D3.2.2 – Specification of the governance infrastructure v2.0.pdf] and [implementation v1 |http://research.petalslink.org/display/easiergov/Binaries] | Document and Prototype | (/) _(T0+18)_ |
| D3.2.3 | Specification of the governance infrastructure v3 and implementation v2 | Document and Prototype | _pending (T0+36)_ |
| D3.2.4 | [Web-based administration console|http://] | Implementation | _pending (T0+36)_ |


h1. WP4: Design Tool

*Leader:* [France Telecom|soceda:Partners]



















|| Id || Name || Type || Status ||
| D4.1.1 | [Relevant SOTA in CEP system|^D4.1.1 Relevant state of the art in Esper CEP system.pdf] | Document | (/) (T0+9) |
| D4.1.2 | [Esper CEP interface specification|^D4 1 2- Esper CEP interface specification and implementation V1.pdf] and implementation V1 | Document and Prototype | (/) (T0+12) |
| D4.1.3 | [Esper CEP interface specification and implementation V2|^SocEDA-D4 1 2-CEPEditor-Specifications.pdf] | Document and Prototype | (/) (T0+18) |
| D4.1.4 | Extension of the CEP Editor for mashup and events | Document and Prototype | _pending (T0+36)_ |
| D4.2.1 | [Identification of requirements to support mashup composition tool|^D4.2.1 Relevant state of the art in mashup composition tool.pdf] | Document | (/) (T0+6) |
| D4.2.2 | [Specification of mashup composition tool|^D4.2.2 - Specification of mashup composition tool .pdf] | Document | (/) (T0+12) |
| D4.2.3 | [Web based tool SolutionV0|http://research.petalslink.org/download/attachments/2425500/MashupTool_NoConditions.mpg?version=1&modificationDate=1338820844000] | Implementation | (/) (T0+18) |
| D4.2.4 | [Android UI Designer|^SocEDAD4.2.4.pdf]\\ | Document | (/) _(T0+24)_ |
| D4.2.5 | Web-based tool specification and solution V1 | Document and Prototype | _pending (T0+36)_ |


h1. WP5: Integration and Validation

*Leader:* [ActiveEon|soceda:Partners]



















|| Id || Name || Type || Status ||
| D5.1.1 | [Integrated SocEDA documentation(fr)|^D5.1.1 SocEDA-delivrablesT018.dot.pdf]\\
[Integrated SocEDA documentation(eng)|^D5.1.1 SocEDA-delivrablesT018_eng.dot.pdf]\\
[Downloads|http://research.petalslink.org/display/soceda/Binaries]\\ | Document and Prototype | (/) (T0+18) |
| D5.1.2 | Integrated SocEDA platform and documentation updated | Document and Prototype | _pending (T0+36)_ |
| D5.1.3 | Assessment and delivery of the SocEDA integrated platform | Document | _pending (T0+36)_ |
| D5.2.1 | SocEDA open-source package | Packaging | _pending (T0+18)_ |
| D5.2.2 | SocEDA open-source package updated | Packaging | _pending (T0+36)_ |
| D5.3.1 | [Use case description|^D5.3.1 Use case description.pdf] | Document | (/) (T0+9) |
| D5.3.2 | [Use case architecture using the SocEDA platform|^D5.3.2-UC_architecture_using_SocEDA_platform_crisis.pdf] | Document | (/) (T0+18) |
| D5.3.3 | Use case prototype | Prototype | _pending (T0+30)_ |
| D5.3.4 | Use case tuned prototype and report | Document and Prototype | _pending (T0+36)_ |
| D5.4.1 | [Use case description|^D5.4.1–Use_Case_description.pdf] | Document | (/) (T0+14) |
| D5.4.2 | [Use case architecture using the SocEDA platform|^D5.4.2–Use_case_architecture_using_the_SocEDA_platform.pdf] | Document | (/)  (T0+25) |
| D5.4.3 | Use case prototype | Prototype | _pending (T0+30)_ |
| D5.4.4 | Use case tuned prototype and report | Document and Prototype | _pending (T0+36)_ |