Page 203 - DCAP305_PRINCIPLES_OF_SOFTWARE_ENGINEERING
P. 203

Unit 9: Metrics



             The process consists of 4 main phases:                                               Notes
               1.  Project Inception: Elicits the software requirements and determines the project’s goals
                 and scope. Sprints for executing iterations of the following three phases are defined
                 based on this information.
               2.  UxD Design: Designs the application’s human-computer interface.
               3.  Software Engineering: Consists of implementing the application interface and backend
                 (business and data management layers). This also called develop mentor implementation.
               4.  Quality Assurance: Performs regression and acceptance testing before customer delivery.
                                                       Software
                Project Inception   UxD Design                        Quality Assurance
                                                      Engineering
                                   User Experience     Interactive
                 Scope Definition                                      Regression Tests
                                      Design          Engineering
               Initial Requirements                    Backend
                   Gathering        Client Signoff    Development    Release Acceptance

             Metrics Program Design
             Team  members  are  off  course  responsible  for  collecting  the  data.  The  Scrum  Master  is
             the person responsible for summarizing the metrics data and makes it visible to all team
             members. Team members are the most important stakeholders of the metrics program, thus,
             the metrics results should be presented to the team members the same way as the user stories
             (requirements) are discussed and analyzed by the team.
             From the metrics standpoint, Management identified two main organizational objectives:
             1. Control the number of defects delivered to the customer.
             2. Control project time and cost.
             Based on these two goals, we used the GQM methodology to build up the Goal/Question/
             Metrics trees and determine the software metrics based on organizational objectives. Figure
             2 shows the ensuing metrics for the defects goal.



                                          Control the number of defects
                  Goal                      delivered to the customer





                                            How
               Question    Where is       effective is    How many       What types
                           the origin        the          defects are     of defects
                          of defects?                     injected?      are injected?
                                           testing?

                                                                           Pareto
                 Metric     Pareto        # defects/     # of defects    distribution
                         distribution of    # bugs       injected per     of defects
                        defects per origin                  sprint
                                                                         per origing

                 Target
                  Value      TBD             TBD            TBD             TBD
             Questions
             1. How can deign metrics program

             2. Describe the related work of matrices


                                             LOVELY PROFESSIONAL UNIVERSITY                                   197
   198   199   200   201   202   203   204   205   206   207   208