Difference between revisions of "EGI-InSPIRE:WP5 Project Metrics"
Jump to navigation
Jump to search
Line 2: | Line 2: | ||
The following table provides an overview of all collected metrics throughout the EGI-InSPIRE project.<br> | The following table provides an overview of all collected metrics throughout the EGI-InSPIRE project.<br> | ||
The running definition of the EGI-InSPIRE SA2 metrics is available [[InSPIRE-SA2:Metrics Definition|here]]. | |||
{| cellspacing="0" cellpadding="5" style="border: 1px solid black;" | {| cellspacing="0" cellpadding="5" style="border: 1px solid black;" |
Revision as of 18:49, 9 May 2011
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.
Metric ID | Metric | Task | Q1 | Q2 | Q3 | Q4 | Q5 |
---|---|---|---|---|---|---|---|
M.SA2-1 | Number of software components recorded in the UMD Roadmap | TSA2.1 | 0 | 0 | 30 | 30 |
|
M.SA2-2 | Number of UMD Roadmap Capabilities defined through validation criteria | TSA2.2 | 0 | 6 | 17 | 70% (18) |
|
M.SA2-3 | Number of software incidents investigated in a post-mortem found in production that result in changes to quality criteria | TSA2.2 | 0 | 1 | 0 | 0 | |
M.SA2-4 | Number of new product releases validated against defined criteria | TSA2.3 | 0 | 1 | 1 | 3 |
|
M.SA2-5 | Mean time taken to validate a product release | TSA2.3 | n/a | 4h | 8h | 4h |
|
M.SA2-6 | Number of releases failing validation | TSA2.3 | n/a | 0 | 0 | 0 |
|
M.SA2-7 | Number of new product updates contributed into the Software Repository from all types of software providers | TSA2.4 | 0 | 1 | 3 | 4 |
|
M.SA2-8 | Number of unique visitors to the Software Repository | TSA2.4 | 0 | 507 | 412 | 525 |
|
M.SA2-9 | Number of unique visits to the Repository backend | TSA2.4 | 0 | 0 | 0 | 1663 |
|
M.SA2-10 | Number of tickets assigned to DMSU | TSA2.5 | 0 | 8 | 144 | 198 |
|
M.SA2-11 | Mean time to resolve DMSU tickets | TSA2.5 | 3d | 2d | n/a | n/a1 |
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 |