[Fiware-security] TR: D2.1a "FI-WARE Requirements Backlog" - Security Tracker to be updated accordingly

[BISSON Pascal]

Dear Task leads and GE owners,

Could you please have a look at this demand I got from Carlos regarding issues faced on the Security backlog.

In order to solve all these issues I would ask you to correct all entries that relate to GE(s) you owns as task leads.

Would appreciate if you could have it done not later than by next Monday EOB.

As for entries that don't relate to any of your GE I will address them and do of course on Monday to check everything has been corrected.

Best regards,
Pascal

PS: As usual and in case of any problems you may face on this drop me an email.
-----Message d'origine-----
De : CARLOS RALLI UCENDO [mailto:ralli at tid.es] 
Envoyé : lundi 16 janvier 2012 12:20
À : GIDOIN Daniel; BISSON Pascal
Cc : JUAN JOSE HIERRO SUREDA
Objet : D2.1a "FI-WARE Requirements Backlog" - Security Tracker to be updated accordingly

Dear Daniel and Pascal,

As you indeed know, deliverable D2.1a "FI-WARE Requirements Backlog" is actually delivered to the EC as an Excel-snapshot of our Backlog tracker.

Once our tool processed such WPs on-line backlog trackers, we've got an Excel book that we have reviewed to correct typos, mistakes and make some quality assessment.

In principle, we should have been able to correct the major issues in the Excel and therefore send to the European Commission.

However, we DID NOT correct anything in the on-line tracker so we need your cooperation on this point to solve all issues definitely. This way they will not happen anymore in future snapshots (D2.1b, D2.1c ...) and also we ensure to apply the right conventions and methodology ASAP.

In order to ease this task, find attached in this e-mail two Excel sheets. The file ended "reviewed" should have everything you need to correctly update your WP backlog tracker.
Just go to your WP specific sheet and check line-by-line the issues highlighted in red color. You will find an extra column at the right end with the explanation on how to solve each specific mistake. If you still doubt how one concrete mistake should be solved, then go to the file "updated" and check the new value we have addressed to that specific field.

Thanks for your actions and, please, do confirm back to me once the tracker is updated accordingly.
Best regards,
--
-------------------------------------------------------
Carlos Ralli Ucendo (ralli at tid.es)
Cell: +34696923588
Telefónica I+D SAU
Madrid, Spain
-------------------------------------------------------


Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra política de envío y recepción de correo electrónico en el enlace situado más abajo.
This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at http://www.tid.es/ES/PAGINAS/disclaimer.aspx
-------------- next part --------------
A non-text attachment was scrubbed...
Name: D2.1.a Requirements_Backlog revised.xlsx
Type: application/vnd.openxmlformats-officedocument.spreadsheetml.sheet
Size: 330297 bytes
Desc: D2.1.a Requirements_Backlog revised.xlsx
URL: <https://lists.fiware.org/private/old-fiware-security/attachments/20120118/ec223dd1/attachment.xlsx>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: D2.1.a Requirements_Backlog_updated.xlsx
Type: application/vnd.openxmlformats-officedocument.spreadsheetml.sheet
Size: 327903 bytes
Desc: D2.1.a Requirements_Backlog_updated.xlsx
URL: <https://lists.fiware.org/private/old-fiware-security/attachments/20120118/ec223dd1/attachment-0001.xlsx>