[Fiware-security] FIWARE - backlog review

[Wolfgang.Steigerwald at telekom.de]

Hello Pascal,

I checked the spread sheet and found one issue, but I don't know why the other points are in red. For the future it would be better to say what is wrong instead to say there is something wrong. I'm sure the effort to find what is wrong was higher than to change something, especially if you don't find the issue. For the future I hope the way issues are reported are more clear, otherwise I think about to vote for leaving the project. There are cost cuttings, unclear communication in conjunction with the high efforts to manage EU-Projects. May be you can discuss this on your next management calls.

Best regards

Wolfgang


Von: fiware-security-bounces at lists.fi-ware.eu [mailto:fiware-security-bounces at lists.fi-ware.eu] Im Auftrag von BISSON Pascal
Gesendet: Dienstag, 26. Februar 2013 19:48
An: Seidl, Robert (NSN - DE/Munich); Susana Gonzalez Zarzosa; DI CERBO, Francesco; GIDOIN Daniel
Cc: 'fiware-security at lists.fi-ware.eu'
Betreff: [Fiware-security] TR: FIWARE - backlog review
Wichtigkeit: Hoch

Dear Task leads,

This email with the last review of Manuel regarding the Wiki/Tracker update please have a look at remaining issues pointed by Manuel and take necessary steps to get them addressed/fixed.

Many thanks in advance and hoping with your support we could improve and get finally our wiki/tracker update be assessed as good enough to be finally released !!!. Our all hope !!!

Thanks in advance.

Best Regards,
Pascal

PS: Get you task members /colleagues involved whenever appropriate.
PS2: @Xavier/ Orange please interact with Daniel as SecMon GE owner to discuss and agree on your update regarding Roadmap, Wiki and Tracker ... since so far you were not so present nor visible Xavier

De : MANUEL ESCRICHE VICENTE [mailto:mev at tid.es]
Envoyé : mardi 26 février 2013 12:22
À : BISSON Pascal
Objet : FIWARE - backlog review

Hi Pascal,

Find attached a new review of possible errors.
The rate improved, but is far from  others chapters, around 5 - 7% rate

I had a look at the errors most of them come from the variability your team is mapping the general enablers into the reference.
For example for Security Monitoring I find:
                "Security Monitoring"
                "Security_Monitoring"
                "SecurityMonitoring"
                "Security-Monitoring"

I've found for all of them, there was some without whitespaces, which I've chosen for consistence validations.  I copy the mapping below, which I thing will help you:

To the left is the Column 12 (without spaces, which I use as key for the mapping)
To the right, the chain I look for in Column 13

        "AccessControl" = "AccessControlGE"
        "ContextbasedSecurityCompliance" = "Context-basedSecurityAndCompliance"
        "DataHandling" = "DataHandling"
        "IdentityManagement" = "IDM"
        "Optionalsecurityservices"  = "OptionalSecurityEnablers"
        "Privacy" = "Privacy"
        "SecurityMonitoring" = "SecurityMonitoring"

If hope you find acceptable this mapping.

Kind regards,
Manuel


----------------------------
Manuel Escriche Vicente
Agile Project Manager/Leader
FI-WARE Initiative
Telefónica Digital
Parque Tecnológico
C/ Abraham Zacuto, 10
47151 - Boecillo
Valladolid - Spain
Tfno: +34.91.312.99.72
Fax: +34.983.36.75.64
http://www.tid.es<http://www.tid.es/>


________________________________

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 --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/old-fiware-security/attachments/20130226/c652e1eb/attachment.html>