Dear all, Here brief minutes of our meeting on 1st July from 11:30 to 13:00 CET. Attendees: Annamaria, Rafaella, Riccardo (ENG), Carmen (GRASS), Peter (Fraunhofer), Carlos, Clara (ATOS), Franck (EGM) Topics & discussion (we changed the intial order to leave Labelling to the end waiting for Luigi availability): · EGM contribution into Functional sub-task · Grassroot/Fraunhofer contribution into Functional sub-task Annamaria started by recapping the work done so far in the functional part of the task (checking documentation and APIs and opening tickets to the developers for improving the quality). Then both Peter and Franck described what could be their contribution within the current context and scope of the task. In case of Fraunhofer and Grassroots the contribution will be focused in two aspects: analysis of GEs documentation file by digital mechanisms (natural language i.e.); and visualization of the labels for GEs in relation to the labelling model for the overall task. They would like also to produce an online dashboard to automate the testing process in the future. In case of EGM, they are using model based testing for NGSI specifications and interfaces, which are a subset of APIs already tested by ENG but from a different perspective, so the work is not overlapped. They already have created 51 test cases. Context Broker has been already tested and now other NGSI interfaces from other GEs are being tested. NGSI tests are quite relevant over other APIs due to the relevance NGSI has in FIWARE as standard. Due to the time constraints and few time remaining until end of the task, it is suggested for three teams (ENG, Fraunhofer/Grassroots and EGM) to work in parallel in their tasks and collect all work done in the final report. · Work plan for functional and non-functional sub-tasks The overall workplan was commented and updated (attached). Backlog is updated accordingly. Workitems can be created per month when they will be really started. No major delays but really few time to complete all the tasks until end of the task, so be pragmatic and efficient. · Publication of results: code, wiki, blogpost, etc Both functional and non-functional teams must upload all the produced code (including scripts, command lines, etc) to the GitHub, otherwise it cannot be referred publicly. It is decided to work the final report (D1.1.8.2) in Google Docs to optimize the collaboration in written. Blog post draft has been circulated by Clara and open for comments. Wiki is still pending. Clara will chair its production but she will ask for missing inputs to partners. · Feedback from Technical Committee Clara presented to the TSC the work done, especially about Labelling. The work was very well welcome and they appreciated the value of the proposal. The main concerns or suggestions were about the global label and the 7 levels of labelling. The first one was minimize when they realized that the global label expanded into the detailed labels when clicking; and the second one suggest to have A+++, A++, A+, A, B, C, D, instead of 7 levels from A to G, since psychologically and from marketing point of view it sounds better to have a A+++ as maximum level than only A. technically, for us, it would be just to adapt the tables in the document, so we will go for it. Anyway, we expect more comments from TSC, especially Juanjo proposing more changes (not received by now). · Labelling doc: status, feedback and next steps All common GEs tested both by functional and non-functional must be labelled. Everyone should read and propose changes to the current document ASAP. Governance must be aligned with the governance model of the foundation. Due to the comments from TSC, tables must be mapped to the new 7 levels. Peter will work on the visualization of the labels in the Catalogue. The labels will have to be updated after each testing phase since the GEs assessment may change in any category in each testing iteration. Automation of the process will not be feasible in this project. Actions: - Annamaria to check with Davide about what exactly must be included in the dashboard to assess the quality of academy courses - Clara to contact Jose M. Cantera for info about integration of testing in GitHub - Clara to get the person in charge of Catalogue graphics - Clara to ask access to GitHub for all QA people and creating a project for Functional part - Clara to check which links we can include in blog post. - ENG and ATOS from functional and non-functional task must to label all the common GEs, that is: Orion, Proton, Kurento, IDAS, Aeron, Wilma, KeyRock, Cepheus, Bosun, Cygnus, AuthZForce - ENG and ATOS from functional and non-functional task must to upload to GitHub all code/guidelines - Clara to set up a Doodle for a new follow up telco in first week of September - Clara to send the TOC in Google Docs of D1.1.8.2 - Clara to check with her manager the governance Best regards Clara Pezuela Head of IT Market Research and Innovation Group ARI booklet<http://atos.net/en-us/home/we-are/insights-innovation/research-and-innovation.html> Atos Spain SA Clara.pezuela at atos.net<mailto:Clara.pezuela at atos.net> +34 675 62 9974 [cid:image001.png at 01D1DBA0.B8D6CBF0] This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos group liability cannot be triggered for the message content. Although the sender endeavors to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted. Este mensaje y los ficheros adjuntos pueden contener información confidencial destinada solamente a la(s) persona(s) mencionadas anteriormente y pueden estar protegidos por secreto profesional. Si usted recibe este correo electrónico por error, gracias por informar inmediatamente al remitente y destruir el mensaje. Al no estar asegurada la integridad de este mensaje sobre la red, Atos no se hace responsable por su contenido. Su contenido no constituye ningún compromiso para el grupo Atos, salvo ratificación escrita por ambas partes. Aunque se esfuerza al máximo por mantener su red libre de virus, el emisor no puede garantizar nada al respecto y no será responsable de cualesquiera daños que puedan resultar de una transmisión de virus. -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.fiware.org/private/fiware-qualityassurance/attachments/20160711/103fc82f/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 11614 bytes Desc: image001.png URL: <https://lists.fiware.org/private/fiware-qualityassurance/attachments/20160711/103fc82f/attachment.png> -------------- next part -------------- A non-text attachment was scrubbed... Name: Work plan_QA Testing_July2016_v1.xlsx Type: application/vnd.openxmlformats-officedocument.spreadsheetml.sheet Size: 14911 bytes Desc: Work plan_QA Testing_July2016_v1.xlsx URL: <https://lists.fiware.org/private/fiware-qualityassurance/attachments/20160711/103fc82f/attachment.xlsx>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy