Page 197 - SOFTWARE TESTING & QUALITY ASSURANCE
P. 197

Software Testing and Quality Assurance



                           4.   Quality Evaluation Effort:  It measures the developer’s effort that is being spent on internal
                               quality evaluation activities.
                           5.   Defect Detection Efficiency: It measures how many defects were detected in a particular phase.

                           6.   Defect Removal Rate:  It measures the total number of defects detected and resolved  over a
                               period of time.
                           7.   Defect Age Profile: It measures the total number of defects that have not been resolved over a
                               period of time.
                           8.   Defect Density: It identifies the defect-prone parts of the system.
                           9.   Complexity: It measures the complexity of the code in a particular program.


                          Did you know?   Scientific Systems, Inc. along with the Air Force Business Research Management
                                        Center developed software quality indicators to improve the management
                                        capabilities of personnel responsible for monitoring software development projects.
                          The important measure for a project’s success is quality. Products with high quality would result in
                          customer satisfaction‚ while poor quality products result in customer dissatisfaction. Quality measures
                          should help in identifying the problems, and suggesting corrective actions which must be implemented.
                          They should not be time consuming or dependent on extensive software training. The quality measures
                          should be flexible, clearly defined, easy to calculate, and straightforward to interpret.


                          Did you know?   Hewlett Packard (HP) was a leader in software quality metrics.



                                      Prepare a list of software quality metrics that can be used for measuring the quality of
                                      software.

                          13.3   Summary

                          •   The contribution of software quality metrics is to assess if the development process follows the
                              software quality requirements. The quantitative analysis reduces subjectivity in the assessment of
                              software quality.
                          •   There are various organizational structures available, each of them having its own positives and
                              negatives in it. Some of the common examples are organizational structure for a small project with
                              test team always  reporting to the development manager  or the quality assurance team or test
                              group reporting to the executive management.
                          •   Metrics are certain rules used to measure some features or traits of a software entity .The main aim
                              of the software quality metrics is to evaluate whether the software quality requirements are being
                              met throughout the development cycle of the software product.
                          13.4   Keywords

                          Code Coverage: An analysis method that determines which parts of the software have been executed
                          and which part is still remaining by the test case suite.

                          Coupling:  The extent to which each program module depends on the other module to function
                          effectively
                          Cyclometric Complexity:  It is one of the software metrics  used to indicate the complexity of the
                          program.

                          Function Point Analysis: Function Point Analysis is a reliable metrics that helps in estimating projects,
                          managing change of scope, measuring productivity and communicating functional requirements.



                          190                     LOVELY PROFESSIONAL UNIVERSITY
   192   193   194   195   196   197   198   199   200   201   202