GoalDirected Software Measurement MSE Studio

1
Goal-Directed Software MeasurementMSE Studio

• By Ryan Soulier
• Masters of Software Engineering
• Summer Independent Study

2
Overview

• Purpose
• Process followed
• Outputs
• Suggestions
• Goals
• Sample findings

3
Presentation Purpose

• Provide feedback on the GQ(I)M process
• Describe the output of the process
• Present the major findings
• Get feedback on areas of concern
• Get feedback on future improvements

4
Process Followed

• Interviewed stakeholders
• Studio Management, Professors, Matrix Roles
• Identified 3 overall goals per group
• Summarized interviews into goals, questions,
  entities, attributes
• Came up with overall goals
• Broke these down into specific measurement goals
• Reviewed list with interviewees

5
Process Followed (2)

• Developed Indicators
• Problem Indicator to help or to monitor?
• Matrix of entities/attributes with indicators
• Reviewed with Studio Manager Will Hayes
• Measurement collection
• Built matrix of entities/attributes with Forms
• Defined entities/attributes
• Defined forms
• Described process for collecting
• Reviewed current Process Handbook for changes

6
Process Followed (3)

• Review
• Review results with the SEI Group
• Circulate Questionnaire among students
• Task List
• Time Log
• Task Types
• Measurement resources
• 25 sent, 14 responded
• Final
• Make measurement handbook available
• Deliver report to SEI

7
Outputs

• Total Effort 103 hours (9.4 hrs/week avg.)
• Goals
• 9 Business Goals (3 per group)
• 22 Measurement Goals
• 17 Indicators Defined
• 6 Entities (6 currently tracked)
• 23 Attributes (15 currently tracked)
• 8 Forms (6 currently exist)
• Handbook 82 pages
• http//msepc3.sp.cs.cmu.edu/shares/Studio/Process/
  HandBook/MetricHB/

8
Handbook Contents

• Main Section (12 pages)
• Goals
• Relationship to other Processes
• Tasks
• Indicators (36 pages)
• Studio, Team, Individual
• Data Definitions (11 pages)
• Task, Time Entry, Work Product, Defect, Project,
  Course
• Forms (8 pages)
• Task Forms, Time Log, CM, Defect Log, Post-Mortem
  Questions

9
Suggestions

• Add indicator template
• Add audience, and interval
• Add place to put tables in handbook
• Indicator / data element
• Tie the entity/attributes into the GQM
• Is this the metric or the question?
• Tie the sub-goals to measurement goals
• Is this only formalizing?

10
Studio Goals

• Train students to be better software engineers
• Have students put more effort into earlier phases
  of software development
• Ensure that the amount of effort being expended
  for each core course is appropriate

11
Team Goals

• Ensure that the product delivered to the client
  is of high quality
• Ensure that the product is delivered on time
• Distribute the work load appropriately among team
  members

12
Individual Goals

• Learn how to be a better software engineer
• Work no more than necessary
• Graduate within the specified time frame

13
Task Estimations

• Business Goal Train students to be better
  software engineers
• Measurement Goal Provide data to future studios
  for estimation
• Indicator Studio Task Size and Rate Indicator
• Questions
• What are the type of tasks?
• How long do tasks take?
• Inputs Tasks, Work Product
• Forms Team Task Form, Configuration Item Form

14
Studio Task Size Rate
15
Work Product Definition

• Definition
• A work product is defined as a tangible artifact
  of the software development process.
• Attributes
• Project
• Product Type
• Actual Size
• Counted by work product type

16
Configuration Item Form

• Project
• Path
• Revision
• Revision
• Baseline
• Type

17
Course Workload

• Business Goal Ensure that the amount of effort
  being expended for each core course is
  appropriate
• Measurement Goal Show how much time is spent in
  course work versus how much was registered for
• Indicator Studio Course Workload Indicator
• Questions
• Is the workload distributed across the students
  evenly, or does it vary widely?
• Inputs Time Entry
• Forms Team Task Form, Individual Time Log Form

18
Studio Course Workload
19
Time Entry Data Definition

• Description
• A time entry is a description of an amount of
  effort spent working on a task.
• Attributes
• Engineer
• Actual Effort
• Week Completed
• Category
• Task

20
Individual Time Entry Form

• Engineer Name String
• Actual Effort Integer
• Week Completed Integer
• Category String
• Task String of a given format (...)