JRA1 Deliverable Review Form

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

General comments

The page header starts with the word TITLE. I presume this should be replaced with the actual title.

Fixed -- LorenzoDini - 16-Dec-2010

Most of the tool descriptions appear to have been taken directly from the providers description of the tool - which is obviously very subjective.

This document was due at PM2 therefore cannot include many details about the work done in the last 6 months. The aim of this first version is to give a state of the art description of the tools available on the market (before their evaluation and selection) and to describe the initial project situation. A new revision of this deliverable will be prepared in May 2011 which will include the evalusation of the tools and their selection, the progress of the last 6 months in using and integrating the tools and a time-line for the next 2 years about the evolution of such tools. -- LorenzoDini - 16-Dec-2010

This document depends heavily upon the quality of the questionnaire used for the survey - but the questionnaire is not included.

Added as Appendix A -- LorenzoDini - 16-Dec-2010

I am not sure what it means for SA2 to choose "a set of tools" ... "for adoption" as described in the conclusions. Apart from VCS (which has been excluded), and ETICS if chosen, there is not much role for central support.

Tools include ETICS, the various requirement, bug, incident and release trackers, all the metrics generation, extraction, storage and visualization tools, dashboards, the build and test infrastructure, the repositories and in general anything required by the software engineering and QA process -- LorenzoDini - 16-Dec-2010

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

Detailed comments on the content

These are all in the document itself

All tracked changes except the ones mentioned below have been applied, the terminology has been also improved -- LorenzoDini - 16-Dec-2010

One could argue that this is true of all tools and not just of VCS.
Unifying the tools is a requirement of the project and it was explicitly asked by the PEB, unifying the VCS is not and it does not bring large benefits -- LorenzoDini - 16-Dec-2010

Did your survey ask what people found wrong with their current tools. If not your requirements are heaviliy biased in favour of tools currently being used.
The goal is not how to improve each single tools used by each middleware distribution. The main goal is to find a single tool which covers as much as possible the requirements of ALL distributions. Obviously this cannot be done by improving all life for all distributions. It is done by compromises. -- LorenzoDini - 16-Dec-2010

This section appears to have been lifted from a web page provided by ETICS - this is suggested by too many uses of words such as "easy", "popular"
Again this appears to have been lifted from Maven advertising
Yes, they are the descriptions provided by the tool. The same as the other tools. This gives an overview for the people who do not know these tools at all. In the next version we will provide our evaluation with pro/cons -- LorenzoDini - 16-Dec-2010

Various comments about the survey data The data has been displayed as it was collected. Even if it is not perfect at 100%, it is anyway enough to understand the tools used. -- LorenzoDini - 16-Dec-2010

-- FloridaEstrella - 08-Dec-2010