Thanks, For IDAS we can use same label for all, as it is same team who has been solving the issues Best regards Clara Pezuela Head of IT Market Research and Innovation Group ARI booklet<https://atos.net/wp-content/uploads/2017/01/atos-ari-2016.pdf> Atos Spain SA Clara.pezuela at atos.net<mailto:Clara.pezuela at atos.net> +34 675 62 9974 [cid:7206F4B45C675D4FA60A576B4DAED2AE at mail.sis.atos.net] From: Davide Dalle Carbonare [mailto:davide.dallecarbonare at eng.it] Sent: Friday, July 13, 2018 4:10 PM To: Pezuela, Clara <clara.pezuela at atos.net> Cc: fiware-qualityassurance at lists.fiware.org Subject: Re: [Fiware-qualityassurance] FW: Calculation of labels from Jira system information Dear Clara, all I finalized the computation of labels for: - Time to Taking charge - Time to Fix based on the values extracted from JIRA and sent by Fernando (those computed starting from 01/06/2018) values and labels are reported in the shared plan ... dedicated tab. notes: - IDAS is not extracted by agent as we have it reported in the plan ... I used for all the same "total" value ... but it's not the best (and fair) solution - I assume the tickets for CKAN are all related to the Extension - FastRTPS, OpenMTC, AEON, Domibus ... don't have tickets extracted then it's not possible to compute a label (N/A) BR Davide Il giorno lun 9 lug 2018 alle ore 15:59 Pezuela, Clara <clara.pezuela at atos.net<mailto:clara.pezuela at atos.net>> ha scritto: Clara Pezuela Head of IT Market Research and Innovation Group ARI booklet<https://atos.net/wp-content/uploads/2017/01/atos-ari-2016.pdf> Atos Spain SA Clara.pezuela at atos.net<mailto:Clara.pezuela at atos.net> +34 675 62 9974 [cid:7206F4B45C675D4FA60A576B4DAED2AE at mail.sis.atos.net] From: Fernando López Aguilar [mailto:fernando.lopez at fiware.org<mailto:fernando.lopez at fiware.org>] Sent: Monday, July 09, 2018 2:30 PM To: Pezuela, Clara <clara.pezuela at atos.net<mailto:clara.pezuela at atos.net>>; Davide Dalle Carbonare <davide.dallecarbonare at eng.it<mailto:davide.dallecarbonare at eng.it>> Cc: Juanjo Hierro <juanjose.hierro at fiware.org<mailto:juanjose.hierro at fiware.org>>; Stefano De Panfilis <stefano.depanfilis at fiware.org<mailto:stefano.depanfilis at fiware.org>> Subject: Re: Calculation of labels from Jira system information Dear Clara, Davide. I made this weekends some data mining exercises in order to calculate the data: Enabler: Wirecloud, time_response_mean (days): 18.8637327619, time_resolve_mean (days): 27.2212468719, number of tickets: 259 Enabler: Cosmos, time_response_mean (days): 8.34445374888, time_resolve_mean (days): 13.8321993457, number of tickets: 374 Enabler: KeyRock, time_response_mean (days): 6.54871874457, time_resolve_mean (days): 10.9949430115, number of tickets: 420 Enabler: Wilma, time_response_mean (days): 3.07550645766, time_resolve_mean (days): 4.64403935185, number of tickets: 69 Enabler: Kurento, time_response_mean (days): 9.42922432025, time_resolve_mean (days): 16.4366517857, number of tickets: 63 Enabler: XML3D, time_response_mean (days): 8.35534450617, time_resolve_mean (days): 22.3762905093, number of tickets: 18 Enabler: Orion, time_response_mean (days): 5.17465439583, time_resolve_mean (days): 10.8755968455, number of tickets: 500 Enabler: IDAS, time_response_mean (days): 27.8432632844, time_resolve_mean (days): 40.4312291397, number of tickets: 156 Enabler: AuthZForce, time_response_mean (days): 9.47683822633, time_resolve_mean (days): 23.4024373253, number of tickets: 53 Enabler: Knowage, time_response_mean (days): 4.60199061343, time_resolve_mean (days): 9.23932355967, number of tickets: 9 Enabler: IoT Discovery, time_response_mean (days): 37.2371361754, time_resolve_mean (days): 67.0049164601, number of tickets: 15 Enabler: CKAN, time_response_mean (days): 58.46777904, time_resolve_mean (days): 69.977822214, number of tickets: 56 Enabler: IoT Broker, time_response_mean (days): 55.9307778826, time_resolve_mean (days): 59.5831073343, number of tickets: 19 Enabler: Cygnus, time_response_mean (days): 6.27685349772, time_resolve_mean (days): 11.8470262476, number of tickets: 59 Enabler: FogFlow, time_response_mean (days): 29.8296372222, time_resolve_mean (days): 32.8519560185, number of tickets: 1 Enabler: STH-Comet, time_response_mean (days): 21.2571295197, time_resolve_mean (days): 22.7458391204, number of tickets: 2 Enabler: SpagoBI, time_response_mean (days): 6.35502825912, time_resolve_mean (days): 15.3894008715, number of tickets: 51 Enabler: Privacy, time_response_mean (days): 3.95124268519, time_resolve_mean (days): 3.95145833333, number of tickets: 1 Enabler: Business Ecosystem, time_response_mean (days): 17.6664506944, time_resolve_mean (days): 147.686226852, number of tickets: 1 Enabler: Augmented Reality, time_response_mean (days): 27.7372792328, time_resolve_mean (days): 55.2231035053, number of tickets: 7 Enabler: Kiara, time_response_mean (days): 2.83773286458, time_resolve_mean (days): 14.1721643519, number of tickets: 4 Enabler: Aeon, time_response_mean (days): 10.388258559, time_resolve_mean (days): 37.5298553241, number of tickets: 2 Enabler: FastRTPS, time_response_mean (days): 0, time_resolve_mean (days): 0, number of tickets: 0 Enabler: OpenMTC, time_response_mean (days): 0, time_resolve_mean (days): 0, number of tickets: 0 Enabler: Domibus, time_response_mean (days): 0, time_resolve_mean (days): 0, number of tickets: 0 Enabler: Fives, time_response_mean (days): 0, time_resolve_mean (days): 0, number of tickets: 0 I did neither create a service or assign the data to the monitoring service. I just have the code in my machine due to I do not want to expend more time on it. The calculus is taking into account since the beginning of the received tikets until now and the date difference is direct different between created date and resolved date and created date and response date. We have pending some uncategorised tickets (386) which represents 16% of the current data. If there is some GE missing let me know and we can generate the data as well. Best regards, Fernando Fernando López Aguilar FIWARE Cloud & Platform Senior Expert M. +49 1522 2600767 fernando.lopez at fiware.org<mailto:fernando.lopez at fiware.org> www.fiware.org<https://www.fiware.org/> Twitter: @fiware<https://twitter.com/fiware> @flopezaguilar<https://twitter.com/flopezaguilar> On 3. Jul 2018, 17:09 +0200, Pezuela, Clara <clara.pezuela at atos.net<mailto:clara.pezuela at atos.net>>, wrote: Dear Fernando and Stefano, In order to calculate the overall labels for each GE, we need to get these values for following two criteria: Time to Taking charge Label Value Base Measures Formula A+++ < 1 Date of taking charge of each defect (TD) Date open for each defect (OD) Total number of Closed defects (D) ∑(TD-OD)/D A++ 1 - 3,7 A+ 3,8 - 6,5 A 6,6 - 9,3 B 9,4 - 12,1 C 12,2 - 15 D > 15 Time to Fix Label Value Base Measures Formula A+++ < 1 Date of fix for each defect (FD) Date of taking charge of each defect (TD) Total number of Closed defects (D) ∑(FD-TD)/D A++ 1 - 4,7 A+ 4,8 - 8,5 A 8,6 - 12,3 B 12,4 - 16,1 C 16,2 - 20 D > 20 Could you please give us these values for all GEs in the Catalogue (exclude incubated)? Otherwise, we will not be able to include them as criteria for quality. Maybe Veronika may help. A summary table as a coming back result would be perfect. Thanks!! Clara Pezuela Head of IT Market Research and Innovation Group ARI booklet<https://atos.net/wp-content/uploads/2017/01/atos-ari-2016.pdf> Atos Spain SA Clara.pezuela at atos.net<mailto:Clara.pezuela at atos.net> +34 675 62 9974 [cid:8935FE76D9824202AE6AA1CDBD71BAB5] 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. 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. __________________________________________________________________________________________ You can get more information about our cookies and privacy policies on the following links: - http://forge.fiware.org/plugins/mediawiki/wiki/fiware/index.php/FIWARE_Privacy_Policy - http://forge.fiware.org/plugins/mediawiki/wiki/fiware/index.php/Cookies_Policy_FIWARE Fiware-qualityassurance mailing list Fiware-qualityassurance at lists.fiware.org<mailto:Fiware-qualityassurance at lists.fiware.org> https://lists.fiware.org/listinfo/fiware-qualityassurance 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/20180713/ed181b77/attachment-0001.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 4664 bytes Desc: image001.jpg URL: <https://lists.fiware.org/private/fiware-qualityassurance/attachments/20180713/ed181b77/attachment-0001.jpg>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy