Difference between revisions of "EGI-InSPIRE:WP5 Project Metrics"
Jump to navigation
Jump to search
Line 69: | Line 69: | ||
| style="border-right: 1px solid black;" | TSA2.4 | | style="border-right: 1px solid black;" | TSA2.4 | ||
| align="center" | 525<br> | | align="center" | 525<br> | ||
| align="center" | | | align="center" | 766 | ||
|- style="background: none repeat scroll 0% 0% lightgray;" | |- style="background: none repeat scroll 0% 0% lightgray;" | ||
| M.SA2-10 | | M.SA2-10 | ||
Line 75: | Line 75: | ||
| style="border-right: 1px solid black;" | TSA2.4 | | style="border-right: 1px solid black;" | TSA2.4 | ||
| align="center" | 1663<br> | | align="center" | 1663<br> | ||
| align="center" | | | align="center" | 1801 | ||
|- | |- | ||
| M.SA2-11 | | M.SA2-11 |
Revision as of 11:19, 1 August 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.
TODO: Update to current metrics definition!
Metric ID | Metric | Task | Q4 | Q5 |
---|---|---|---|---|
M.SA2-1 | Number of software components recorded in the UMD Roadmap | TSA2.1 | 30 | |
M.SA2-2 | UMD Roadmap Capabilities coverage with Quality Criteria | TSA2.2 | 70% (18) | |
M.SA2-3 | Number of software incidents found in production that result in changes to quality criteria | TSA2.2 | 0 | |
M.SA2-4 | Number of quality related issues that result in changes to quality criteria | TSA2.2 | ||
M.SA2-5 | Number of new Product releases validated against defined criteria | TSA2.3 | 3 |
|
M.SA2-6 | Mean time taken to validate a Product release | TSA2.3 | 4h |
|
M.SA2-7 | Number of Product releases failing validation | TSA2.3 | 0 |
|
M.SA2-8 | Number of new releases contributed into the Software Repository from all types of software providers | TSA2.4 | 4 |
|
M.SA2-9 | Number of unique visitors to the Software Repository | TSA2.4 | 525 |
766 |
M.SA2-10 | Number of unique visits to the Repository backend | TSA2.4 | 1663 |
1801 |
M.SA2-11 | Number of tickets assigned to DMSU | TSA2.5 | 198 |
|
M.SA2-12 | Mean time to resolve DMSU tickets | TSA2.5 | 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 |