[Fiware-cloud] Fw: [Fiware-wpl] IMPORTANT UPDATE: Adding description of assets and refining the structure of the FI-WARE a bit further

[Alex Glikson]

All,

The Wiki has been restructured a bit, and now the Epics are listed at 
https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Materializing_Cloud_Hosting_in_FI-WARE 
(pointing to the same individual Epic pages as before).
Also, we need to start providing details about the baseline assets that 
will be used for each GE (linked from the same page mentioned above). An 
template for describing each an asset can be found at 
https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/SAMSON_Platform
.
Please, proceed with updating both.

Regards,
Alex

----- Forwarded by Alex Glikson/Haifa/IBM on 05/10/2011 09:12 PM -----

From:   Juanjo Hierro <jhierro at tid.es>
To:     "fiware-wpl at lists.fi-ware.eu" <fiware-wpl at lists.fi-ware.eu>, 
"fiware-wpa at lists.fi-ware.eu" <fiware-wpa at lists.fi-ware.eu>
Date:   05/10/2011 12:01 PM
Subject:        [Fiware-wpl] IMPORTANT UPDATE: Adding description of 
assets and refining the structure of the FI-WARE a bit further
Sent by:        fiware-wpl-bounces at lists.fi-ware.eu



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
_______________________________________________
Fiware-wpl mailing list
Fiware-wpl at lists.fi-ware.eu
http://lists.fi-ware.eu/listinfo/fiware-wpl
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/old-fiware-cloud/attachments/20111005/2d1729a8/attachment.html>