Robert, See attached STORK information (Backlog-EPIC and Asset) to be uploaded in WP8.2 FI-WARE Wiki. Best regards ************************************ * Antonio García Vázquez * * (+34) 91 214 9384 * * antonio.garcia at atosresearch.eu * ************************************ From: BISSON Pascal [mailto:pascal.bisson at thalesgroup.com] Sent: miércoles, 05 de octubre de 2011 13:49 To: Fiware-security at lists.fi-ware.eu Cc: BISSON Pascal; GIDOIN Daniel; Antonio Garcia Vazquez; TRABELSI, Slim; Seidl, Robert (NSN - DE/Munich); Marton, Gabor (NSN - HU/Budapest); GIDOIN Daniel; LELEU Philippe Subject: TR: [Fiware-wpl] IMPORTANT UPDATE: Adding description of assets and refining the structure of the FI-WARE a bit further Importance: High Hi all, Please find below the detailed instructions I got from TID (Juanjo) on how to proceed regarding description of assets. Note that they have also decided to change the structure based on which references to Wiki pages containing full description of entries in the backlogs will be found. So first please check. Second, I urge each of the task leads to complete asap update of their sections of the Security Chapter according to enablers they cover. This has to be done with full support of GE owners and member of their teams. As requested yesterday I also ask them to drop me an email once done. So counting on you and them catch up on this requests asap. Regarding description of assets, I’d like also each of the team leaders to drive the process at the level of their team to get everything done by Thursday (tomorrow) EOB. Please be aware that info you upload to the Wiki will be publicly available in the meantime bear in mind it has to be meaningful to the reader (and first and foremost Use Case Project). For information necessary to our shared understanding and that you don’t want to expose to rest of the world let me inform you that there should be another wiki to be set-up for that. We will review status on our WP8 weekly audio-conf this Friday (10am-12am) . Those who are unable to attend should send an email reporting what the status of their task with respect to uploading info on the Wiki (contribution to Features backlog + contribution to the update of the Security chapter changes + assets description) Best regards, Pascal De : fiware-wpl-bounces at lists.fi-ware.eu [mailto:fiware-wpl-bounces at lists.fi-ware.eu] De la part de Juanjo Hierro Envoyé : mercredi 5 octobre 2011 12:02 À : fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu Objet : [Fiware-wpl] IMPORTANT UPDATE: Adding description of assets and refining the structure of the FI-WARE a bit further Hi all, After careful consideration, I have came with a way description of assets, the FI-WARE vision and entries of the FI-WARE backlog can be nicely structured on the Wiki and linked together. Assets are clearly linked to FI-WARE Backlog entries, so it clearly makes sense to document them closely together. Notice that many of the already identified Themes/Epics/Features/User-Stories are indeed linked to selected assets. Note that Features/User-Stories should map to assets because they correspond to concrete software development that has to be carried over assets and will lead to delivery of some new version of the asset in the course of a release or a sprint, respectively. However, while there are Themes/Epics that can be mapped to assets (still high-level to map into actual developments on the asset) others may be general to the chapter, corresponding still to topics under discussion which may potentially affect several assets. They should derive on Themes/Epics/Features/User-Stories on selected assets as a result of the discussion. We should take this into account when structuring the Wiki. Based on the above, the structure we will adopt is described as follows: * A chapter titled "Materializing the FI-WARE Vision", linked to a Wiki page, has been added to the FI-WARE Wiki, following right after the "FI-WARE Product Vision". * The Wiki page for this new chapter has been created and, for the time being, is structured as a list of subchapters, one per chapter of FI-WARE, each subchapter having its own Wiki page. * We have created each of the "Materializing the <chapter-name> in FI-WARE" Wiki pages. They contain: * An introduction section you don't need to edit. You will see it establish a link to the corresponding chapter in the FI-WARE Product Vision * A section per GE in the chapter. A template is provided for this sections that you should replicate for each GE in your chapter (at least for those for which backlog entries have been identified). The section is structured as follows: * Baseline assets: Here you should enumerate the assets that will be considered for implementing the GE. If not yet decided, please explain. For each asset, a link to a dedicated Wiki page should be created, describing the asset. * Check the general structure for this section looking at the example for the "BigData Analysis" GE in the Data/Context Management Chapter (http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Materializing_Data/Context_Management_in_FI-WARE#Baseline_Assets_3) * In order to build the Wiki page associated to an asset, you should replicate the structure for the Wiki page linked to the SAMSON asset in the "BigData Analysis GE" (http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/SAMSON_Platform) * Themes: You should add here the link to the proper Themes you had previously listed in the FI-WARE Backlog chapter * Epics: You should add here the link to the proper Epics you had previously listed in the FI-WARE Backlog chapter * Features: You should add here the link to the proper Features you had previously listed in the FI-WARE Backlog chapter * User-Stories: You should add here the link to the proper Features you had previously listed in the FI-WARE Backlog chapter * A section titled "Topics still being addressed at high-level": Here, you should add the Themes and Epics you should have produced as a result of mapping any of the following: * issues identified in the Question Mark section of the FI-WARE Product Vision. * sketched solution for integration of some assets, as a result of discussions taking place in Turin The "FI-WARE Backlog" chapter you currently find in the FI-WARE wiki home page will be deprecated and finally dropped in a matter of days. I hope that the instructions are clear. It shouldn't change much of what you had done. Of course, the wiki pages you created for the full description of backlog entries will still be valid in the new structure. And the URL links to them will still be valid so any tickets you may have created on the trackers should still work. You can take a look at how the info has been structured for the Data/Context Management chapter for reference. Don't hesitate to ask if you have any doubt. Apologizes for the delay in communicating this but I gave it a careful thought and only after some time considering different possibilities, I came with the final proposal. Best regards, -- Juanjo Hierro Chief Technologist on Software Technologies Telefonica R&D Labs email: jhierro at tid.es phone: +34 91 48 32932 www.tid.es twitter.com/JuanjoHierro Oeste 1, Planta 5. Distrito C Ronda de la Comunicacion s/n Madrid 28050 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 ------------------------------------------------------------------ This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos group liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted. Este mensaje y los ficheros adjuntos pueden contener informacion confidencial destinada solamente a la(s) persona(s) mencionadas anteriormente pueden estar protegidos por secreto profesional. Si usted recibe este correo electronico por error, gracias por informar inmediatamente al remitente y destruir el mensaje. Al no estar asegurada la integridad de este mensaje sobre la red, Atos no se hace responsable por su contenido. Su contenido no constituye ningun compromiso para el grupo Atos, salvo ratificacion escrita por ambas partes. Aunque se esfuerza al maximo por mantener su red libre de virus, el emisor no puede garantizar nada al respecto y no sera responsable de cualesquiera danos que puedan resultar de una transmision de virus. ------------------------------------------------------------------ -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.fiware.org/private/old-fiware-security/attachments/20111006/ff685a0e/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: Stork.zip Type: application/x-zip-compressed Size: 52880 bytes Desc: Stork.zip URL: <https://lists.fiware.org/private/old-fiware-security/attachments/20111006/ff685a0e/attachment.bin>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy