EMI Quality Model
Introduction
The EMI Quality Model helps to evaluate the EMI software product and process quality. It helps to set quality goals for software products and processes. The EMI Quality Model uses
ISO/IEC 9126 Software Engineering – Product Quality
to identify a set of characteristics that need to be present in EMI software products and processes to be able to meet EMI quality requirements. EMI quality requirements are based on DCIs quality requirements, like the
UMD Quality Criteria
, and internal project objectives that influence qualitative aspects of the EMI software, as specified in the
EMI DoW.
For each software characteristic, a set of associated metrics and KPIs are identified. Metrics and KPIs are defined in detail in the EMI Metrics Specification.
The EMI Quality Model also defines a measurement plan. The measurement plan identifies which set of metrics and KPIs should be evaluated for each stage of the software lifecycle and how often. The results of the evaluation are reported in the corresponding metrics report. Templates for the different types of the metrics reports are also provided.
SA2.2 is responsible for maintaining the EMI Quality Model.
EMI Metrics Specification
The EMI Metrics Specification is a list of the metrics and KPIs currently calculated within EMI to evaluate the quality of the EMI software product and processes.
SA2.4 is responsible for maintaining the EMI Metrics Specification.
EMI Metrics Report Specification
For the third year of the project, metrics reports will be calculated every quarter and will be included in the activity quarterly reports. The metrics to be calculated are specified in the
Quarterly report - Metrics template. The list of metrics to be calculated is:
- General metrics showing the status at the end of the quarter (summary table + detailed reports):
- Release:
- Products per supported platform (SL5 x86_64 and x86, SL6 x86_64, Debian6 x86_64)
- SW licenses (already 100%)
- Test plans (already 100%)
- Compliance:
- Debian compliance
- EPEL compliance
- RPMlint errors * Products released in EPEL
- EMT metrics issues tracking EPEL compliance
- IPV6 compliance
- Documentation:
- Missing mandatory documents * Documentation issues
- Security:
- EMI 1 and EMI 2 updates released during the quarter (A summary table per update + detailed reports aggregating all updates)
- Testing:
- Test reports (always 100%)
- Mandatory tests
- Regression tests for fixed defects
- Functional tests for new functionality
- Certification:
- Passed certification checks
SA2.7 is responsible for generating the metrics reports.
EMI Metrics Report Archive
- EMI 1
- EMI_1_planning_MetricsReport : This report is not available since user requirements and technical objectives were not tracked in EMI 1.
- EMI_1_CodeTest_MetricsReport
: This report generated on the 16.05.2011 doesn't follow the EMI Quality Model yet. It is the best approximation to understand the status of the EMI 1 release though.
- EMI_1_general_MetricsReport: NA
- EMI 1 Updates: Reports for updates 1-8 do not exist. Reports available for updates 9-14, these reports ARE NOT COMPLETE because some metric graphs have not been produced yet.
- EMT_MetricsReport
- EMI 2
Logbook
- 22.06.2012: Page updated to describe the metrics report specification for the 3rd year of the project.