[Fiware-wpl] VERY IMPORTANT: Coordination of FI-WARE backlog related activities

[Juanjo Hierro]

On 28/07/11 03:24, Juanjo Hierro wrote:

 *   Parallel to UC projects running the process described above, FI-WARE should, own its own, work in defining entries for the FI-WARE backlogs.   Whether they will be still generic ("themes" or "epics") or already detailed as to be ready for implementation will depend on how clear we have things regarding the GEs in each of the chapters.  There are three different types of entries that FI-WARE chapter teams should be able to generate from now until the Turing meeting (as a first milestone)
    *   Entries related to new functional or non-functional features we need to implement in an asset adopted as baseline for the development of the reference implementation of a given GE (or part of it), in order to cover the gap between what that given asset supports at the time it is contributed by a given partner to the project and what it should support to actually become (part of) a reference implementation of the given GE.
    *   Entries related to new functional or non-functional features we wish to implement in an asset adopted as baseline for the development of the reference implementation of a given GE (or part of it), in order to further evolve it and therefore, evolve the corresponding GE (since GEs specifications may evolve over time and offer different functionality in subsequent releases of FI-WARE)
    *   Entries related to integration of assets, in those cases where an asset has to be combined with other assets to build the reference implementation of a given GE.  Note that these entries are different than those ones related to implementing interfaces/protocols, etc in an asset implementing (part of) a GE, in order to support integration with another GE, because interfaces/protocols enabling integration of GEs should be part of their open specifications and, therefore, should be considered a particular case of points 1. or 2.


  A very IMPORTANT note: entries in the backlog should not describe what the assets adopted as baseline already provide, but what must, should, could be developed in those assets (see MoSCoW priority field in the attached template for FI-WARE backlog entries).   Remember that entries in the backlog are about "work to be done".

  The second release of the FI-WARE High-level Description (Product Vision) should include a dedicated section per GE elaborating on the asset selected as baseline, which mostly will contain links to existing documentation which explains what the asset already provides today (user's/programmers guide, etc)

  Best regards,

-- Juanjo.

________________________________
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/fiware-wpl/attachments/20110728/62b52f52/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jhierro.vcf
Type: text/x-vcard
Size: 429 bytes
Desc: not available
URL: <https://lists.fiware.org/private/fiware-wpl/attachments/20110728/62b52f52/attachment.vcf>