Thanks to the cloud chapter which actually managed to contribute as planned. May I kindly ask what the other WPL/WPAs are envisioning for the final submission? Do you need more time or are you planning to not submit at all? Would you be in favor of shifting the deliverable deadline because of missing contributions and communicating this to the EC or do you think we should submit, even if a WP did not provide a contribution? Thanks for any comments. /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: Donnerstag, 24. Oktober 2013 09:26 To: Leidig, Torsten; BISSON Pascal; Heller, Markus; daniel.gidoin at thalesgroup.com; ralli at tid.es; GLIKSON at il.ibm.com; sergg at tid.es; thierry.nagellen at orange.com Cc: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu; fiware-testbed at lists.fi-ware.eu Subject: [Fiware-testbed] Your contribution to the validation deliverable (10.5.2b) until monday, 28.10. Dear WPL & WPA colleagues (apps, cloud, data, iot, security), as planned below I would like to encourage and ask kindly for your contributions to the validation deliverable, which for your chapter the Testbed Team prepared as attached & in the testbed wiki. You will find the task for "your" chapter described in the doc - the section you have to fill is "Comments by WP leadership" for your chapter and should roughly cover answers to the questions, which I as well printed at the bottom of this email. These questions might help you find relevant and "interesting" things, the Reviews would like to know in relation to our "answer" to the validation of the use cases in phase 1. Please either directly change the DOC-file with "tracked"-changes - or contribute to the wiki where all pages from this deliverable are linked here: https://forge.fi-ware.eu/plugins/mediawiki/wiki/testbed/index.php/D.10.5.2b.Report_on_Validation_process_including_Validation_with_Use_Case_projects_front_page#Structure_of_this_Document Please finish this task until Monday, 28.10. EOB the latest. If you have any questions, please don't hesitate to ask! Thanks a lot and best regards /Thorsten Questions to be answered by WPL/WPA * What went good, what went bad during this validation? * What was the recent actions implemented which address potential challenges identified during the validation? * Which challenges did you mainly identify, coming out of this validation? * What strength can you find for your chapter and how to further build upon this strength? * What measures did you take to mitigate the situation? * Overall acceptance over all validated GE for your chapter? (find answer Q.GE.11) * How deep have they been validated for your chapter? (find answer QGE.13) * Browse through the "scenario-based answers" (doc-files) and extract some relevant quotes good ones and bad ones, touching on your chapter GEs. - the doc files are linked here: https://forge.fi-ware.eu/plugins/mediawiki/wiki/testbed/index.php/Overview_FI-WARE_validation#Validation_of_non-functional_requirements * What would you do differently in the next validation round? * What would you find interesting from the use cases to better improve the validation? De : 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] De la part de Sandfuchs, Thorsten Envoyé : lundi 14 octobre 2013 10:25 À : fiware-testbed at lists.fi-ware.eu<mailto:fiware-testbed at lists.fi-ware.eu> Cc : fiware-wpl at lists.fi-ware.eu<mailto:fiware-wpl at lists.fi-ware.eu>; fiware-wpa at lists.fi-ware.eu<mailto:fiware-wpa at lists.fi-ware.eu> Objet : [Fiware-testbed] Minutes and action points on validation deliverable submission (10.5.2b) Dear colleagues, on Friday there was a testbed-internal session which discussed how to submit D.10.5.2b (the resubmission of the validation deliverable). We have a very tight schedule to submit this deliverable with all contributions in time. For this minutes I'm taking WPL/WPA on the CC list in order to let everybody know the status. Thorsten presented the approach and explained along the lines of the presentation what content should needs to be produced. - Mainly the testbed-team will in a neutral way write what we "see", judged by the numbers - things like: "SMARTAGRIFOOD rated the integration badly in the case of the XXX chapter...." We could try to come up with first assumptions on why these ratings did take place and dig deeper - but overall WPL/WPA need to do the _content_ driven analysis. "The reason for this was ..." or "We will take this serious and already implemented the following actions ..." Background are the graphs and tables prepared by Thorsten in the presentation and pivot-tables of the XLS. - Additionally and for the deliverable the "scenario based" questionnairs in DOC format need to be analyzed and "highs" and "lows" need to be extracted for the chapters. - Stefano wanted everybody to analyze the bare-metal XLS and try to come up with "new interesting" things somebody sees in the day. This task needs to be worked on in parallel within the week of 14.10. - 18.10. - everybody to report relevant findings on the 22.10. Rough time plan: KW42 (14.-18.10): main content work, Testbed-team writing what we "see", judged by the numbers KW43 (21.-25.10): finalizing text & hand-over to WPL/WPA team - 22th of October: deadline for the content work - goal: on 23th October WPL/WPA should be able to start their work with the content analysis (you will have ~3 business days) KW44 (28.-30.10): finalizing the DOC deliverable and starting a review cycle - Please volunteer if you want to be a reviewer for this deliverable KW44 (31.10): planned submission to EC Please - if possible - directly update the wiki : https://forge.fi-ware.eu/plugins/mediawiki/wiki/testbed/index.php/D.10.5.2b.Report_on_Validation_process_including_Validation_with_Use_Case_projects_front_page#Structure_of_this_Document or the underlying pages. If unsure, just write the text in any other format and provide it ASAP to Thorsten so he can integrated it to the wiki. Find attached the updated presentation & the bare-metal data in XLS format. Assignments for writing the Analysis: - Cloud-chapter: John - Data: Clara - IoT: Salvatore - Overall FI-WARE: Stefano - Methodologie: Thorsten - Open chapters: o Apps o Security (ask Pascal) o Use Case chapters (all of them not assigned) Any questions or corrections, please let me know /Thorsten -- Thorsten Sandfuchs SAP AG | Vincenz-Priessnitz-Strasse 1 | D-76131 Karlsruhe, Germany | www.sap.com<http://www.sap.com/> Pflichtangaben/Mandatory Disclosure Statements: http://www.sap.com/company/legal/impressum.epx Diese E-Mail kann Betriebs- oder Geschäftsgeheimnisse oder sonstige vertrauliche Informationen enthalten. Sollten Sie diese E-Mail irrtümlich erhalten haben, ist Ihnen eine Kenntnisnahme des Inhalts, eine Vervielfältigung oder Weitergabe der E-Mail ausdrücklich untersagt. Bitte benachrichtigen Sie uns und vernichten Sie die empfangene E-Mail. Vielen Dank. This e-mail may contain trade secrets or privileged, undisclosed, or otherwise confidential information. If you have received this e-mail in error, you are hereby notified that any review, copying, or distribution of it is strictly prohibited. Please inform us immediately and destroy the original transmittal. Thank you for your cooperation. Please consider the environment before printing this mail! -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.fiware.org/private/old-fiware-testbed/attachments/20131029/f541377f/attachment.html>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy