PO Deliverable Review Form

Identification of the deliverable or milestone
Project: EMI Deliverable or milestone identifier: D5.6.2
Title: DJRA1.6.2 Integration Work Plan and Status Report Doc. identifier: EMI-DXXX-CDSREF-Title-vx.x
Author(s): A. GIesler Due date: __

Identification of the reviewer
Name: F. Estrella Affiliation: CERN EMI Activity/External project or Institute: NA1

Review date mm/dd/yyyy
Author(s) revision date mm/dd/yyyy
Reviewer acceptance date mm/dd/yyyy

Attach the reviewed document to the deliverable page, put here a link

General comments

Hi Andre, Morris

Andre has already updated me on the difficulty of completing DJRA162 due to pending input from Area Leaders.

The first release of this report, DJRA161, was accepted with reservation. A number of issues were unresolved and there was disagreement on its scope. The recommendation from the first release review was for these unaccounted comments to be fully addressed in DJRA162.

Refer to the first section of the review wiki where I have put DJRA162 abstract, TJRA1.7 description, DJRA162 definition of integration and interoperability

DJRA162 DoW abstract, unfortunately, is not completely aligned with the scope of TJRA1.7 Integration and Interoperability. I would expect the ff to be part of DJRA162:
-continuous verification - what is the plan? how is it monitored
-agreed interfaces - what are the agreed interfaces, planning, verification
-common dependencies - what are the common dependencies, planning, verification
-interoperability - definition and verification
-interoperability within EMI
-interoperability with external systems
-verification - how is this handled? who is providing the tests? who is running the tests? infrastructure/testbeds/tools to use?
-platform dependencies

Based on TJRA1.7 description, I disagree with the ff statement from DJRA162 v0.3:
-DoW does not mention interoperability at all and therefore not addressed (see task description)
-according to the agreed definition of integration, the integration with external components is out of the scope of JRA1.7 (not only it is within the scope of the deliverable, it is not precluded by the definition)
-SA2 enables the integration of components describing guidelines and providing tools, thus these aspects were also removed from this document (the description of SA2 guidelines and tools may not be needed but how these are used in integration and interoperability tasks is essential and must be reported; it would also be good to provide a critical analysis of their usability and applicability within JRA1, this will be an important feedback to SA2)

Some specific comments on v0.3 available on wiki:
-What is the "general EMI Development and Testing Plan"
-The Executive Summary should be extended to include what has changed since the last report and the rationale behind these changes, in addition to the high level summary of the content of the document.
-The Executive Summary should include an overall critical assessment of first year integration and interoperability tasks as described in DJRA161
-We need a section on harmonisation of integration and interoperability activities (from pre EMI to EMI 2, EMI 3)
-A section specifically to cover platform/OS dependencies

I realise this is not an easy document to write. Morris, Jedrzej, PO - we should try to help as much as we can Andre..


Additional recommendations (not affecting the document content, e.g. recommendation for future work)

Detailed comments on the content

Note 1: The reviewers must list here any observation they want to track explicitly and that require interaction with the authors
Alternatively all changes must be listed in the document itself using Word change tracking features (if you use Word)
Note 2: These comments have to be explicitly addressed by the authors and the action taken must be clearly described

N Page Section Observations and Replies Is Addressed?
1 xx x.y Sequence of comments and replies separated by twiki signature and date    

Any other modification, spelling or grammatical corrections, etc must be done directly in the document using tracked changes or similar mechanisms that allows the authors to identify which correction is suggested.

Edit | Attach | Watch | Print version | History: r1 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r1 - 2011-05-22 - 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-2021 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
or Ideas, requests, problems regarding TWiki? use Discourse or Send feedback