DJRA1.6.2 - Integration Work Plan and Status Report

This deliverable contains the detailed work plan of the integration activities and objectives compliant with the overall EMI Technical Development Plan and aligned with the work-plans of other tasks within this work package. The plan is released early in the project life and updated every year including a status report on the achievements of the past 12 months compared to the planned objectives. (M12)

This is an update of DJRA1.6.1 Integration Work Plan and Status Report (M3)

This deliverable is within the scope of TJRA1.7 : This task consists in the continuous verification of the integration of the EMI services and components, their respect of the agreed interfaces and of the agreed common dependencies. It also includes the definition and verification of the interoperability criteria within the EMI services stack and with external systems. The main success criteria of this task are the successful hand over of integrated sets of components to SA1 for further inclusion in the EMI releases and the verified interoperability with the external systems foreseen in the Technical Development Plan.

DJRA162 v0.3 definitions: Integration refers to a setup where one software component inherently uses another component to provide a dedicated functionality. Interoperability, on the other hand, within an EMI task means that one component is interoperable with another if both integrating the same interface

JRA1 internal

  • 2011-03-28 : Morris uploads initial TOC (based on previous version) for discussion with JRA1.7 leader (André)

  • 2011-03-28 : Andre uploads proposal of a revised TOC removing some unnecassary sections from old TOC. Has to be discussed.

  • 2011-04-14 : Andre uploads revised TOC reflecting the structure given by review from Balasz and the area work plan template

  • 2011-05-18 : Andre uploads incomplete draft version

  • 2011-05-25 : Andre uploads draft version for review

Schedule

  • Author sends ToC to PEB 08-Apr
  • Author sends high quality complete WP-leader approved first draft of deliverable for review 18-May
  • Reviewers send comments on first draft 22-May
  • Author sends second draft for reviewers' acceptance 24-May
  • Reviewers acceptance of second draft or critical comments that must be addressed in the final draft 26-May
  • Author sends final draft to PO 27-May

Review tracking

  • 25/05/11 v0.4 sent to J.K. Nilsen, C. Aiftimiei, PEB for review; deadline 27/05
  • 26/05/11 J. K. Nilsen review comments received
  • 26/05/11 F. Estrella provided answers to comments related to Interoperability sections
  • 26/05/11 C. Aiftimiei review comments received
  • Revised documents addressing reviewers' comments expected 30/05
  • 27/05/11 A. Giesler adressed Jon's comments in review v0.5: Draft version(adresses Jon's review).
  • Pending A. Giesler's replies to Cristina's comments
  • 30/05/11 J. K. Nilsen has accepted v0_5_JKN_Adressed
  • 30/05/11 Andre has addressed Cristina's comments
  • 01/06/11 Cristina has accepted revised document from Andre.
  • Pending consolidated clean version for final (critical only) PEB review
  • 01/06/11 André provided version for final PEB review v0.7
  • Final call for critical comments only by COB 02/06
  • Final pdf uploaded to CDS
  • Warning, important PO observations and future work considerations (050611): There are a number of things we should consider (if Andre still has the energy to address some of them before noon 06/06; otherwise this is future work)
    1. I am missing the overall integration strategy and planning. The due dates provided are those of the technical objectives. When would integration testing happen? What is the plan wrt continous verification? What is needed (guidance, guidelines, policies, tools, oversight, etc) to facilitate integration, testing and continuous verification?
    2. Chapter on Work Organisation and Resources: It is v good this is included as it puts the work in context with other activities and resources. It would benefit if we clarified in this chapter that JRA17 is responsible for the overall coordination and oversight of integration and testing, providing guidelines and suggestions, coordinating related work with SA2 (policies and tools) and related work with SA1 (hand-over of integrated components, checking of deployment requirements and OS dependencies). And indeed, the actual integration and testing are done by the PTs.
    3. External systems: External dependency is not part of the deliverable but within the scope of JRA1.7 (purpose text re-worded)
    4. Technical objectives related to Interoperability: Added where missing (work plan and the table of objectives). DONE.

Reviewers

Edit | Attach | Watch | Print version | History: r29 < r28 < r27 < r26 < r25 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r29 - 2011-06-07 - unknown
 
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    EMI All webs login

This site is powered by the TWiki collaboration platform Powered by PerlCopyright &© 2008-2020 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback