[Fiware-iot] EPICs and Features

[Bisztray, Denes (NSN - HU/Budapest)]

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 ) 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/20111102/3636df14/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: BacklogFiware-T5.2-v0.2.xls
Type: application/vnd.ms-excel
Size: 72704 bytes
Desc: BacklogFiware-T5.2-v0.2.xls
URL: <https://lists.fiware.org/private/old-fiware-iot/attachments/20111102/3636df14/attachment.xls>