Alert.png The wiki is deprecated and due to be decommissioned by the end of September 2022.
The content is being migrated to other supports, new updates will be ignored and lost.
If needed you can get in touch with EGI SDIS team using operations @ egi.eu.

EGI-InSPIRE:WP5 Project Metrics

From EGIWiki
Revision as of 13:26, 2 November 2011 by Kkoum (talk | contribs)
Jump to navigation Jump to search


Current collection of quarterly metrics

The following table provides an overview of all collected metrics throughout the EGI-InSPIRE project.

The running definition of the EGI-InSPIRE SA2 metrics is available here.

TODO: Update to current metrics definition!

Metric ID Metric Task Q4 Q5 Q6
M.SA2-1 Number of software components recorded in the UMD Roadmap TSA2.1 30 30
M.SA2-2 UMD Roadmap Capabilities coverage with Quality Criteria TSA2.2 70% (18) 85% (22) 92% (25)
M.SA2-3 Number of software incidents found in production that result in changes to quality criteria TSA2.2 0 0 2
M.SA2-4 Number of quality related issues that result in changes to quality criteria (internal metric!)
TSA2.2
27 11
M.SA2-5 Number of new Product releases validated against defined criteria TSA2.3 3
41
29
M.SA2-6 Mean time taken to validate a Product release TSA2.3 4h
21.03h
10.52h
M.SA2-7 Number of Product releases failing validation TSA2.3 0
5
2
M.SA2-8 Number of new releases contributed into the Software Repository from all types of software providers TSA2.4 4
42
42
M.SA2-9 Number of unique visitors to the Software Repository TSA2.4 525
766 1184
M.SA2-10 Number of unique visits to the Repository backend TSA2.4 1663
1801 4556
M.SA2-11 Number of tickets assigned to DMSU TSA2.5 198
218
183
M.SA2-12 Mean time to resolve DMSU tickets (Median in brackets) TSA2.5 n/a1
24d (4.2d) 17.3d (11d)

1 Beginning with PQ4 this metric is not collected until appropriate reporting means in GGUS are implemented. (See for more details.)


Historic metric collections

PQ1 - PQ3

The following table provides historic metrics collected for project quarters one to three. With D5.3 the SA2 activity decided to change the metrics.

Metric ID Metric Task Q1 Q2 Q3
M.SA2-1 Number of software components recorded in the UMD Roadmap TSA2.1 0 0 30
M.SA2-2 Number of UMD Roadmap Capabilities defined through validation criteria TSA2.2 0 6 17
M.SA2-3 Number of software incidents found in production that result in changes to quality criteria TSA2.2 0 1 0
M.SA2-4 Number of new releases validated against defined criteria TSA2.3 0 1 1
M.SA2-5 Mean time taken to validate a release TSA2.3 n/a 4h 8h
M.SA2-6 Number of releases failing validation TSA2.3 n/a 0 0
M.SA2-7 Number of new releases contributed into the Software Repository from all types of software providers TSA2.4 0 1 3
M.SA2-8 Number of unique visitors to the Software Repository TSA2.4 0 507 412
M.SA2-9 Number of releases downloaded from the Software Repository TSA2.4 0 0 0
M.SA2-10 Number of tickets assigned to DMSU TSA2.5 0 8 144
M.SA2-11 Mean time to resolve DMSU tickets TSA2.5 3d 2d n/a