[Fiware-testbed] Status and potential next steps towards validation planning with use case projects

[Sandfuchs, Thorsten]

Hi,
Sorry there was a misplacement of layout information on my previous mail - corrected.

Best,
                                                                /Thorsten

From: fiware-testbed-bounces at lists.fi-ware.eu [mailto:fiware-testbed-bounces at lists.fi-ware.eu] On Behalf Of Sandfuchs, Thorsten
Sent: Montag, 3. September 2012 10:43
To: fiware-testbed at lists.fi-ware.eu
Subject: [Fiware-testbed] Status and potential next steps towards validation planning with use case projects

Dear colleagues,
In order to prepare the topic of "validation planning and execution" for our next PHC on Wednesday, I would like to take the time to subsume the status and the potential next steps.

Find attached the commented version of Paolos "FI-WARE evaluation approach" the document outlines not only the process given on the wiki page (https://forge.fi-ware.eu/plugins/mediawiki/wiki/testbed/index.php/Testbed_V1_Validation_Plan<https://forge.fi-ware.eu/plugins/mediawiki/wiki/test%0d%0aValidation_Plan>) it as well introduces potential feature coverage matrix and further documentation for the use case projects in order to document validation.

If you have further comments and suggestions, please contribute directly in the document or comment via email.

As we want to have first validation results by M18, I think we have to approach the use case projects rather sooner than later.

Potential next steps would be (as outlined in the wiki & the document) to firstly approach the WPA/WPL meeting and introduce the overall plan. Then subsequently the use case projects and start with the first phases of the validation process:

1.  Validation Preparation phase (to be carried out before validation execution)
Duration: ~1-2 month
Purpose: Plan validation (concrete timing, scope and initial scenario)
DoW: " be defined with the support of FI-WARE partners participating in this task and should contain the technology requirements as well as the functional and non-functional requirements to be validated. Such test plans will be mapped versus the functionality offered by the FI-WARE instance under test in order to establish a coverage matrix."
A separate template for the validation plan will be provided by the Testbed team
Send validation plan to testbed coordinator
Recommendation: bi-weekly call with testbed coordinator, get formal green-light by testbed team for platform readiness & scenario suitability
2. Introduction to FIWARE platform and testbed phase (optional)
Duration: 1-2 weeks
Schedule meeting with Testbed coordinator and complete va lang=EN-GB>
Testbed gives system endpoints and needed access information to the team and gives general introduction to the infrastructure
During second validation phase, this phase might be optional
Recommendation: UC to schedule Kick-off meeting with all FIWARE WPL/WPA for this validation phase, outlining the envisioned scenario

Any questions, don't hesitate to ask.

                                                                                /Thorsten

From: fiware-testbed-bounces at lists.fi-ware.eu<mailto:fiware-testbed-bounces at lists.fi-ware.eu> [mailto:fiware-testbed-bounces at lists.fi-ware.eu]<mailto:[mailto:fiware-testbed-bounces at lists.fi-ware.eu]> On Behalf Of Paolo Zampognaro
Sent: Freitag, 27. Juli 2012 18:37
To: fiware-testbed at lists.fi-ware.eu<mailto:fiware-testbed at lists.fi-ware.eu>
Subject: [Fiware-testbed] Validation Activity: contribution

Hi Thorsten,

as anticipated in Phc I have tried to reason about the Validation activity inside our WP.
In order to gather ideas in a coherent way I have put all in a document (see attachment) exclusively because this helps me to have a logical thread.
Basically I have tried to:
-       Give an overview about the evaluation process in FI-WARE with respect our validation must be placed.
-       Identify the metrics in order to produce the validation results
-       Define a template each Use Case should fill in order to produce its validation results
-       Foresee a section where to aggregate the validation data and execute further analysis

I will continue to readjust it in the next days because I'm sure there are still a lot of things to modify but this draft could be a starting point to improve the discussion.

< MsoNormal>Cheers,

Paolo





Ing. Paolo Zampognaro
Software Engineer
Direzione Centrale Ricerca & Innovazione
paolo.zampognaro at eng.it<mailto:paolo.zampognaro at eng.it>

Engineering Ingegneria Informatica spa
Via Gianturco, 15 - 80146 Napoli
Tel. +39-081.6103524
Mob. +39-3451227587
Fax. +39-081.6103200
www.eng.it<blocked::http://www.eng.it/><span lang=IT style='font-size:7.5pt;font-family:"Verdana","sans- >

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/old-fiware-testbed/attachments/20120903/ef59b565/attachment.html>