[Fiware-iot] EPICs and Features

[Farkas, Lorant (NSN - HU/Budapest)]

Dear All,
 
Attached the respective e-mail mentioned by Dénes. I just realized you might not have received it, if that is the case I apologize.
1 additional remark about themes: Ricardo, you created 2 themes for one of your GE-s and neither of them has content in it. 
Earlier recommendation is that there is 1 theme per GE:
Themes, are much more high-level or abstract than EPICs.   The frontier between Themes and EPICs is also fuzzy, but is not that relevant as the frontier between EPICs and User Stories because this last frontier is what matters to know when you may stop refining.   Indeed, we may adopt a convention regarding what to call Theme and what to call an EPIC.   For example, we may map the notion of "Theme" to the notion of Generic Enabler in FI-WARE.   Therefore, there would be a Theme linked to the "Publish/Subscribe Broker GE" which establishes as a goal that "Applications should be able to publish data and subscribe to data of their interest".  The "target usage" text in the FI-WARE Product Vision / High-level Description deliverable for a given GE may well work as the content for the description of the corresponding Theme.
So I suggest that either 
1. task leaders create 1 theme per GE that states the goal of the respective GE, with full content, if they are able to do it by EOB tomorrow or
2. task leaders do not attempt to create themes at all

Thanks & Br,
 
Lorant

________________________________

From: fiware-iot-bounces at lists.fi-ware.eu [mailto:fiware-iot-bounces at lists.fi-ware.eu] On Behalf Of Bisztray, Denes (NSN - HU/Budapest)
Sent: Wednesday, November 02, 2011 2:14 PM
To: fiware-iot at lists.fi-ware.eu
Subject: [Fiware-iot] EPICs and Features



Dear All, 

(especially Ricardo, Sabrina, Gian Piero and Thierry)

  A short follow-up from today's IoT weekly meeting on the EPICs and Features. 

1.      EPICs

Currently one component within a GE is one EPIC.

For example in the Devices Frontend GE:

Connection Protocol Adapter - FIWARE.EPIC.IoT.DevicesFrontEnd.ConnectionProtocolAdapter

Communication Protocol Abstraction Definition - FIWARE.EPIC.IoT.DevicesFrontEnd.CommunicationProtocolAbstractionDefinition

This is the bare minimum. Although a Theme is a GE, a component within a GE should be described by multiple EPICs. As an example take a look at the attached xls from Ricardo <<BacklogFiware-T5.2-v0.2.xls>> and the IoT Process Automation/Exposure GE (https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Materializing_Internet_of_Things_(IoT)_Services_Enablement_in_FI-WARE#IoT_Process_Automation.2FExposure <https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Materializing_Internet_of_Things_(IoT)_Services_Enablement_in_FI-WARE#IoT_Process_Automation.2FExposure>  ) in the wiki.

Obviously there can be tiny components, where the single feature of that component can be described by a single EPIC, but in most cases at least 3-5 EPICs should be created per component.

2.      Features

As per Juanjo's email (Monday, October 24, 2011 2:30 AM) Features are those Epics you expect to address in the first minor release. When you created the EPICs, move the ones to the Features you expect to finish in the first minor release.

Best,

Dénes

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/old-fiware-iot/attachments/20111103/b5f65b7a/attachment.html>
-------------- next part --------------
An embedded message was scrubbed...
From: "ext Juanjo Hierro" <jhierro at tid.es>
Subject: [Fiware-wpa] IMPORTANT Next steps regarding planning of first	release and sprint
Date: Mon, 24 Oct 2011 02:30:22 +0200
Size: 1991539
URL: <https://lists.fiware.org/private/old-fiware-iot/attachments/20111103/b5f65b7a/attachment.mht>
-------------- next part --------------
An embedded message was scrubbed...
From: "ext Juanjo Hierro" <jhierro at tid.es>
Subject: [Fiware-wpa] Hints and examples about entries for the FI-WARE	backlog
Date: Wed, 10 Aug 2011 18:06:46 +0200
Size: 117538
URL: <https://lists.fiware.org/private/old-fiware-iot/attachments/20111103/b5f65b7a/attachment-0001.mht>