mapping between iso 9126 on software product quality metrics and ...

More documents

Recommendations

Info

the ISO 12207 software life cycle processes. Forexample, within the “verification process” (of the“supporting processes”) 59 metrics can be applied(measured). As an example, Appendix A shows adetailed structure of the software product internalquality metrics’ names and where they can be measuredduring the software life cycle processes or activitiesalong with the corresponding characteristic andsubcharacteristic for each of those metrics. In thisappendix, only the software life processes/activitieswhich have internal quality metrics are mentioned.However, from Figure 4 we can note that there is nometrics which could be measured during 4 out of 5primary life cycle processes. This means that there is noany metric from ISO <strong>9126</strong> external quality metricscould be useful during the acquisition, supply,operation, and maintenance primary life cycleprocesses. Moreover, there is no metrics which could bemeasured during 3 out of 8 of the supporting life cycleprocesses; that is, documentation, configurationmanagement, and audit processes.5. Primary Life Cycle Processes 6. Supporting Life Cycle Processes5.1 Acquisition (0 Metric)6.1 Documentation (0 Metric)5.2 Supply (0 Metric)6.2 Configuration Management (0 Metric)5.3 Development6.3 Quality Assurance (2 Metrics)(1 Metric in Software Qualification6.4 Verification (59 Metrics)Testing activity)6.5 Validation (13 Metrics)5.4 Operation (0 Metric)6.6 Joint review (59 Metrics)5.5 Maintenance (0 Metric)6.7 Audit (0 Metric)6.8 Problem Resolution (4 Metrics)Figure 4: The ISO <strong>9126</strong>-3 Internal Quality Metrics and where they could be measured in the SLCP.3.2 EXTERNAL QUALITY METRICSWithin the ISO <strong>9126</strong>-2 on software product externalquality metrics, there is 110 metrics. These metrics canbe applied during the software life cycle. Externalquality defined in ISO <strong>9126</strong>-1 as the totality ofcharacteristics of the software product from an externalview. It is the quality when the software is executed,which is typically measured and evaluated while testingin a simulated environment with simulated data usingexternal metrics. During testing, most faults should bediscovered and eliminated. However, some faults maystill remain after testing. As it is difficult to correct thesoftware architecture or other fundamental designaspects of the software, the fundamental design usuallyremains unchanged throughout testing [12].Figure 5 shows the number of external qualitymetrics which can be applied (measured) during each ofthe ISO 12207 software life cycle processes. Forexample, within the “operation process” of the “primaryprocesses”, 93 metrics can be applied (measured).5. Primary Life Cycle Processes 6. Supporting Life Cycle Processes5.1 Acquisition (0 Metric)6.1 Documentation (0 Metric)5.2 Supply (0 Metric)6.2 Configuration Management5.3 Development(0 Metric)(7 Metrics in Software Integration activity)6.3 Quality Assurance (14 Metrics)(100 Metric in Software Qualification Testing activity)6.4 Verification (0 Metrics)(7 Metrics in System Integration activity)6.5 Validation (47 Metrics)5.4 Operation (93 Metric)6.6 Joint review (0 Metric)5.5 Maintenance (48 Metric)6.7 Audit (0 Metric)6.8 Problem Resolution (1 Metric)Figure 5: The ISO <strong>9126</strong>-2 External Quality Metrics and where they could be measured in the SLCP.3.3 QUALITY IN USE METRICSWithin the ISO <strong>9126</strong>-2 on software product quality inuse metrics, there is 15 metrics. These the 15 metricscan be applied during the software life cycle. Quality inUse defined in ISO <strong>9126</strong>-1 as the user’s view of thequality of the software product when it is used in aspecific environment and a specific context of use. Itmeasures the extent to which users can achieve theirgoals in a particular environment, rather than measuringthe properties of the software itself. The term ‘user’
efers to any type of intended users, including bothoperators and maintainers, and their requirements canbe different. [12].Figure 6 shows the number of quality in use metricswhich can be applied (measured) during each of the ISO12207 software life cycle processes. For example,during the “software qualification testing” activity ofthe “development process” of the “primary processes”,12 metrics can be applied (measured).5. Primary Life Cycle Processes 6. Supporting Life Cycle Processes5.1 Acquisition (0 Metric)6.1 Documentation (0 Metric)5.2 Supply (0 Metric)5.3 Development(12 Metric in Software Qualification Testing activity)5.4 Operation (15 Metric)5.5 Maintenance (0 Metric)6.8 Problem Resolution (0 Metrics)6.2 Configuration Management(0 Metric)6.3 Quality Assurance (0 Metrics)6.4 Verification (0 Metrics)6.5 Validation (11 Metrics)6.6 Joint review (0 Metrics)6.7 Audit (0 Metric)Figure 6: The ISO <strong>9126</strong>-4 Quality in Use Metrics and where they could be measured in the SLCP.4. DISCUSSION OF THE MAPPINGIn ISO <strong>9126</strong>-3, there are some external quality metrics –as in Table 1 - which have been referred to be appliedduring the “integration” activity of the “developmentprocess” of the “primary processes”. But, within the“development” process, there are two activities relatedto the “integration”, that is, “system integration” and“software integration”. However, this document (ISO<strong>9126</strong>-3) did not specify during which “integration”activity those metrics can be applied (measured).Table 1: Some External Quality Metrics.1- Estimated latent fault 2- Incorrect operationdensityavoidance3- Failure density 4- Availabilityagainst test cases5- Failure resolution 6- Mean down time7- Fault density 8- Mean recovery time9- Fault removal 10- Restartability11- Mean time <strong>between</strong>failures (MTBF)12- User supportfunctional consistency13- Breakdown 14- Restore effectiveness15- Failure avoidance 16- RestorabilityIt is clearly noted that through the ISO 12207“organizational processes” none of the 195 qualitymetrics - found in ISO <strong>9126</strong> series of internationalstandards - can be applied (measured).As mentioned in ISO <strong>9126</strong>-1, the quality in usemetrics should be measured during the execution of thesoftware product in an actual working environment.However, in Figure 6 we can see that there is 12 metricswhich could be measured through the “softwarequalification testing” activity. But since ISO 12207mentioned that the “software qualification testing”activity is a part of the “development process” Thus, it’sstrange and make no sense to measure the 12 metricsThe “joint review process” of the “supportingprocesses” consists of three activities; one of theseactivities is the “technical reviews” activity. The“technical reviews” activity contains one task that is,“Technical reviews shall be held to evaluate thesoftware products or services under consideration andprovide evidence that: a) they are complete . . . ” [9].Now, if we go back to Figure 4, we will find that thereis 59 internal quality metrics that could be measuredduring the “joint review” process. Whereas, fromFigures 5 and 6, it is seen that there is no any externalquality or quality in use metrics that can be appliedduring “joint review” process.5. CONCLUSIONThe current edition of the ISO <strong>9126</strong> consists ofinventories of proposed metrics to measure the qualityof the internal, external, and in-use software product.However, for each of these metrics there is a crossreferenceon where it could be applied (measured)during the ISO 12207 software life cycle processes andactivities. This paper provided a <strong>mapping</strong> <strong>between</strong> thosetwo standards to investigate the cross-references<strong>between</strong> them. Based on this <strong>mapping</strong>, the followingcomments and suggestions for the upcoming new ISO25000 series of standards (SQuaRE) can be concluded:- There is no any metric can be measured duringthe “organizational processes”.- A number of external quality metrics wherementioned in ISO <strong>9126</strong>-2 to be measured duringthe “integration” activity. However, within theISO 12207 there are two activities labeled“system integration” and “software integration”.This will make the user of the ISO <strong>9126</strong>confused.
Page 1 and 2: MAPPING BETWEEN ISO 9126</s
Page 3: The ISO 12207 software life cycle p
Page 7 and 8: APPENDIX AISO 9126

mapping between iso 9126 on software product quality metrics and ...

Create successful ePaper yourself

Delete template?

Save as template?