Integrating
Metrics with Software Process
• Many software developers do not collect measures.
• Without measurement it is impossible to determine
whether a process is improving or not.
• Baseline metrics data should be collected from a
large, representative sampling of past software projects.
• Getting this historic project data is very
difficult, if the previous developers did not collect data in an on-going
manner.
• The majority of software developers still do not
measure. The problem is cultural. If we do not measure there is no real way of
determining whether we are improving.
• Software project managers are concerned with more
mundane issues:
– developing meaningful
project estimates
– producing
higher-quality systems
– getting product out
the door on time
• By using measurement to establish a project
baseline, each of these issues becomes more manageable.
As the
software design is completed
– Which user
requirements are most likely to change?
– Which modules in this
system are most error prone?
– How much testing
should be planned for each module?
– How many errors (of
specific types) can I expect when testing commences?
Answers to
these questions can be determined if metrics have been collected and used as a
technical guide.
• Data
collection requires an historical investigation of past projects to
reconstruct required data.
• Metrics
computation can span a broad range of LOC metrics as well as other quality
and project-oriented metrics
• Metrics evaluation
focuses on the underlying reasons for the results obtained and produces a set
of indicators that guide the project or process.
No comments:
Post a Comment