[Fiware-i2nd] Early comments on item for next I2ND PhC

[Banniza, Thomas-Rolf (Thomas-Rolf)]

Dear Pier,

 please find my first feedback below (marked with 'Bz: ..').

Best regards,
Thomas

________________________________
Von: fiware-i2nd-bounces at lists.fi-ware.eu [mailto:fiware-i2nd-bounces at lists.fi-ware.eu] Im Auftrag von Garino Pierangelo
Gesendet: Dienstag, 10. April 2012 16:17
An: fiware-i2nd at lists.fi-ware.eu
Betreff: [Fiware-i2nd] Early comments on item for next I2ND PhC

Dear All,

In view of the I2ND confcall at the end of this week, I anticipate a pair of items we'll address to let you analyze them more in detail, and provide an early  feedback hopefully before the call (at least for the first one).

The first item concerns the deliverables  "Unit Testing Plan and Report" (for I2ND it is D7.5a), due by M12. Here is the proposal by Project Coordinator:
...
We should use the chapter backlogs for this purpose.  After carefully thinking we propose to adopt the following approach:

Bz: we should first discuss a general issue: if we use the chapter backlog for this purpose the backlog will be public to all interested parties.
Do we really want to have the our chapter backlog public???? In this case, we have to look for another location to store details about delivery date, completion status and so on...
- Create a comprehensive set of Features entries in the backlog describing all the features of the GE.  Some of these Features should already be there, but others would map to features already supported in baseline assets.

Bz: the feature descriptions in the 'materializing' Wiki page are already public now. Why not take them as base documents, into which we then can add links to other
(potentially public) Wiki pages of which the first might be the 'test description' (other might be the 'how to apply/use' description we might have to provide).
In this context we should also generate feature pages describing what exactly is reused/expected from a baseline asset.
- Each Feature to include a description on how the feature will be tested (how-to-test). This would mean filling a standard field of the backlog.

Bz: see comment above
- Note that since they would be features, they should have an entry on the public wiki referred from a ticket on the backlog. However, we need to discuss whether to make it part of the standard template on the wiki entry or just create a field in the ticket.

Bz: see comment above
- It would be rather useful that the how-to-test field includes a reference to tools or testing clients that automate the testing of the feature.

Bz: If the test description needs to have a references to details of the tools etc used for testing, we should include this in the test description page as defined above.
- In theory, it may be argued that description on how-to-test should also be available for Use Case stories but this would be hard to cover in the first release, overall for features already supported in baseline assets.

Bz: in many cases, a use case is a quite small piece of functionality which hardly can be accessed from a user in an isolated way. As the user probably focuses on
features we should in turn focus the test descriptions on the feature level (for sure we have to develop and test internally use case by use case, but the test descriptions
should describe tests on a more aggregate level).
...
Please provide your comments on this point in order we finalize the feedback to ProjCoord during the call on Friday.
The second item is just to inform you that there is a discussion on going with the Project Officer, to re-plan some of the FI-WARE milestones due to the delays accumulated so far by the project. We'll talk more in detail about this during the call.
BR

Pier

------------------------------------------------------------------
Telecom Italia
Pierangelo Garino
Innovation & Industry Relations - Research & Prototyping
Via G. Reiss Romoli 274, I-10148 TORINO
Tel: +39 011 228 7142

Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie.

This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks.

Rispetta l'ambiente. Non stampare questa mail se non è necessario.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/old-fiware-i2nd/attachments/20120411/ba91e78e/attachment.html>