DNA1.3.3 - Technical Development Plan

Technical Development Plan: This deliverable provides the details of the technical development plan for all EMI services. It contains an initial status assessment, a list of known requirements and their prioritization and a plan with deliverables and milestones for each Product Team. The plan contains the details for the first year of development and longer-term high-level plans for the following years. It is revised periodically and at least every twelve months with increasing level of details. It is coordinated by the Technical Director, but requires input and active engagement from all WP leaders and Product Team leaders (M11).
This is the second, final update of Technical Development plan.
This is an update of DJRA1.4.2 (M12)

P1 external reviewers' report on D1.3.2 Technical Development Plan (M11)
This deliverable is an update of D1.3.1 and now includes a discussion about how customer requirements are tracked and managed during software development. Once again, the document is mainly forwardlooking but it does show how plans have changed during the first year and how some components have had their stack membership modified. This document shows how Cloud computing has already had an impact on the technical development planning. The consortium should justify how such decisions were made. The tables in this document are text and load much more quickly, making the document much easier to use.

NA1/PTB internal

• 16/04/12 Outcome of a two-month-long PTB process to define Y3 high level objectives was uploaded (Y3-objectives.xls)
• 16/04/12 v0.1 of DNA1.3.3 is available. This version is ready for TOC review.
• 3/05/12 v0.6 is a complete document ready for project review.
• 20/05/2012 v0.7 is delivered as a revision partially addressing the reviewer's comments

Review tracking

• 17/04/2012 ToC v0.1 received
• 20/04/2012 ToC v0.4 sent to Diana and PEB for review - deadline 25/04
• 03/05/2012 v0.6 sent to Diana, Andrea and PEB for review - deadline 09/05
• 15/05/2012 Reminder sent to reviewers
• 15/05/2012 Florida sent her review
• 16/05/2012 Andrea, Valerio and Diana sent their reviews
• 21/05/2012 Balazs: The reviewers have already received my mail with my review responses. This is just to summarize the status of the DNA1.3.3: With the latest version v0.7 i tried to address all review comments that was possible to be done during the limited time i had (i explained in my review response what was done and what was not possible to be done). I believe the latest version is good enough to be sent to Brussels (actually, i think it is better than the two previous versions DNA1.3.1 and DNA1.3.2). Please note that the coming days due to other more urgent and also extremely delayed duties of mine i will not be able to dedicate time to the deliverable. The maximum i could do is to make very small changes here and there but nothing more than one hour of work altogether. The first day when i could work a bit more on the deliverable would the the 28th May when i return from CHEP, New York but i guess that is already too late.
• 22/05/2012 Florida sent her comments on v0.7
• 22/05/2012 Valerio "There's not much to answer. Balazs agreed with most of what we pointed out, but it seems there's no time to integrate the changes in the document. We agree this puts us in a risky position for the review. Please Balazs do your best to at least address the major comments, like explaining what is the rationale behind the objectives prioritization."
• 22/05/2012 Diana "I have no further comments, except to share the general concerns and hope you can find some time for a few high level considerations, as outlined below by Florida. "
• 27/05/2012 Final pdf uploaded to CDS
• 28/05/2012 Oxana delivered a new version with many improvements along the requests of the reviewers.
• 29/05/2012 Final pdf uploaded to CDS

Reviewers

• Diana Cresti (NA2, INFN)
• Andrea Ceccanti, Valerio Venturi (SA1, INFN)
• Project Office (NA1, CERN)

-- AlbertoDiMeglio - 27-May-2012