Best Practices in Software Measurement: How to Use Metrics to Improve Project and Process Performance

by ; ; ;
Format: Hardcover
Pub. Date: 2004-11-15
Publisher(s): Springer-Verlag New York Inc
List Price: $69.95

Rent Textbook

Select for Price
There was a problem. Please try again later.

Rent Digital

Rent Digital Options
Online:30 Days access
Downloadable:30 Days
$23.40
Online:60 Days access
Downloadable:60 Days
$31.20
Online:90 Days access
Downloadable:90 Days
$39.00
Online:120 Days access
Downloadable:120 Days
$46.80
Online:180 Days access
Downloadable:180 Days
$50.70
Online:1825 Days access
Downloadable:Lifetime Access
$77.99
*To support the delivery of the digital material to you, a digital delivery fee of $3.99 will be charged on each digital item.
$50.70*

New Textbook

We're Sorry
Sold Out

Used Textbook

We're Sorry
Sold Out

Summary

The software business is challenging enough without having to contend with recurring errors. One way repeating errors can be avoided is through effective software measurement. In this volume, Ebert and his co-authors offer practical guidance built upon insight and experience. They detail knowledge and experiences about software measurement in an easily understood, hands-on presentation and explain such current standards as: ISO 15939 (the general measurement standard), ISO 19761 (the COSMIC Full Function Points standard), and CMMI (the Capability Maturity Model). Coverage also includes several case studies, from Global 100 companies such as Alcatel, Deutsche Telekom, and Siemens. This combination of methodologies and applications makes the book ideally suited for professionals in the software industry. Besides the many practical hints and checklists readers will also appreciate the large reference list, which includes links to metrics communities where project experiences are shared. Further information, continuously updated, can also be found on the web site related to this book: http://metrics.cs.uni-magdeburg.de

Author Biography

Christof Ebert is director software coordination and process improvement of Alcatel S.A, Paris, France, and IEEE Software associate editor-in-chief Reiner Dumke is professor of software engineering at the university of Magdeburg, Germany, and speaker of the German informatics society (GI) expert group on metrics Manfred Bundschuh is IT quality manager with AXA Service AG, Cologne, Germany as well as president of DASMA e.V., the German metrics organization Andreas Schmietendorf works as chief architect within the development center of Deutsche Telekom AG in Berlin, Germany, and is an active member in the German informatics society society (GI) and the Central Europe Computer Measurement Group (CECMG)

Table of Contents

1 Introduction 1(8)
2 Making Metrics a Success - The Business Perspective 9(26)
2.1 The Business Need for Measurement
9(4)
2.2 Managing by the Numbers
13(9)
2.2.1 Extraction
13(4)
2.2.2 Evaluation
17(3)
2.2.3 Execution
20(2)
2.3 Metrics for Management Guidance
22(7)
2.3.1 Portfolio Management
22(2)
2.3.2 Technology Management
24(2)
2.3.3 Product and Release Planning
26(1)
2.3.4 Making the Business Case
27(2)
2.4 Hints for the Practitioner
29(3)
2.5 Summary
32(3)
3 Planning the Measurement Process 35(14)
3.1 Software Measurement Needs Planning
35(1)
3.2 Goal-Oriented Approaches
36(4)
3.2.1 The GQM Methodology
36(2)
3.2.2 The CAME Approach
38(2)
3.3 Measurement Choice
40(2)
3.4 Measurement Adjustment
42(1)
3.5 Measurement Migration
43(2)
3.6 Measurement Efficiency
45(1)
3.7 Hints for the Practitioner
45(2)
3.8 Summary
47(2)
4 Performing the Measurement Process 49(14)
4.1 Measurement Tools and Software e-Measurement
49(1)
4.2 Applications and Strategies of Metrics Tools
50(6)
4.2.1 Software process measurement and evaluation
50(1)
4.2.2 Software Product Measurement and Evaluation
51(3)
4.2.3 Software Process Resource Measurement and Evaluation
54(1)
4.2.4 Software Measurement Presentation and Statistical Analysis
54(1)
4.2.5 Software Measurement Training
55(1)
4.3 Solutions and Directions in Software e-Measurement
56(5)
4.4 Hints for the Practitioner
61(1)
4.5 Summary
62(1)
5 Introducing a Measurement Program 63(18)
5.1 Making the Measurement Program Useful
63(1)
5.2 Metrics Selection and Definition
63(3)
5.3 Roles and Responsibilities in a Measurement Program
66(2)
5.4 Building History Data
68(1)
5.5 Positive and Negative Aspects of Software Measurement
69(3)
5.6 It is People not Numbers!
72(2)
5.7 Counter the Counterarguments
74(1)
5.8 Information and Participation
75(1)
5.9 Hints for the Practitioner
76(3)
5.10 Summary
79(2)
6 Measurement Infrastructures 81(14)
6.1 Access to Measurement Results
81(1)
6.2 Introduction and Requirements
81(5)
6.2.1 Motivation: Using Measurements for Benchmarking
81(1)
6.2.2 Source of Metrics
82(1)
6.2.3 Dimensions of a Metrics Database
83(1)
6.2.4 Requirements of a Metrics Database
84(2)
6.3 Case Study: Metrics Database for Object-Oriented Metrics
86(7)
6.3.1 Prerequisites for the Effective Use of Metrics
86(1)
6.3.2 Architecture and Design of the Application
87(1)
6.3.3 Details of the Implementation
88(2)
6.3.4 Functionality of the Metrics Database (Users' View)
90(3)
6.4 Hints for the Practitioner
93(1)
6.5 Summary
94(1)
7 Size and Effort Estimation 95(20)
7.1 The Importance of Size and Cost Estimation
95(1)
7.2 A Short Overview of Functional Size Measurement Methods
96(4)
7.3 The COSMIC Full Function Point Method
100(3)
7.4 Case Study: Using the COSMIC Full Function Point Method
103(3)
7.5 Estimations Can Be Political
106(1)
7.6 Establishing Buy-In: The Estimation Conference
107(1)
7.7 Estimation Honesty
108(1)
7.8 Estimation Culture
108(1)
7.9 The Implementation of Estimation
109(2)
7.10 Estimation Competence Center
111(2)
7.11 Training for Estimation
113(1)
7.12 Hints for the Practitioner
113(1)
7.13 Summary
114(1)
8 Project Control 115(18)
8.1 Project Control and Software Measurement
115(3)
8.2 Applications of Project Control
118(12)
8.2.1 Monitoring and Control
118(6)
8.2.2 Forecasting
124(2)
8.2.3 Cost Control
126(4)
8.3 Hints for the Practitioner
130(1)
8.4 Summary
131(2)
9 Defect Detection and Quality Improvement 133(24)
9.1 Improving Quality of Software Systems
133(2)
9.2 Fundamental Concepts
135(3)
9.2.1 Defect Estimation
135(2)
9.2.3 Defect Detection, Quality Gates and Reporting
137(1)
9.3 Early Defect Detection
138(4)
9.3.1 Reducing Cost of Non-Quality
138(2)
9.3.2 Planning Early Defect Detection Activities
140(2)
9.4 Criticality Prediction - Applying Empirical Software Engineering
142(4)
9.4.1 Identifying Critical Components
142(2)
9.4.2 Practical Criticality Prediction
144(2)
9.5 Software Reliability Prediction
146(4)
9.5.1 Practical Software Reliability Engineering
146(2)
9.5.2 Applying Reliability Growth Models
148(2)
9.6 Calculating ROI of Quality Initiatives
150(4)
9.7 Hints for the Practitioner
154(1)
9.8 Summary
155(2)
10 Software Process Improvement 157(24)
10.1 Process Management and Process Improvement
157(3)
10.2 Software Process Improvement
160(10)
10.2.1 Making Change Happen
160(3)
10.2.2 Setting Reachable Targets
163(3)
10.2.3 Providing Feedback
166(2)
10.2.4 Practically Speaking: Implementing Change
168(1)
10.2.5 Critical Success Factors
169(1)
10.3 Process Management
170(5)
10.3.1 Process Definition and Workflow Management
170(3)
10.3.2 Quantitative Process Management
173(1)
10.3.3 Process Change Management
174(1)
10.4 Measuring the Results of Process Improvements
175(2)
10.5 Hints for the Practitioner
177(2)
10.6 Summary
179(2)
11 Software Performance Engineering 181(22)
11.1 The Method of Software Performance Engineering
181(2)
11.2 Motivation, Requirements and Goals
183(2)
11.2.1 Performance-related Risk of Software Systems
183(1)
11.2.2 Requirements and Aims
184(1)
11.3 A Practical Approach of Software Performance Engineering
185(8)
11.3.1 Overview of an Integrated Approach
185(1)
11.3.2 Establishing and Resolving Performance Models
185(2)
11.3.3 Generalization of the Need for Model Variables
187(2)
11.3.4 Sources of Model Variables
189(1)
11.3.5 Performance and Software Metrics
190(2)
11.3.6 Persistence of Software and Performance Metrics
192(1)
11.4 Case Study: EAI
193(5)
11.4.1 Introduction of a EAI Solution
193(1)
11.4.2 Available Studies
194(1)
11.4.3 Developing EAI to Meet Performance Needs
195(3)
11.5 Costs of Software Performance Engineering
198(1)
11.5.1 Performance Risk Model (PRM)
198(1)
11.6 Hints for the Practitioner
199(2)
11.7 Summary
201(2)
12 Service Level Management 203(14)
12.1 Measuring Service Level Management
203(1)
12.2 Web Services and Service Management
204(5)
12.2.1 Web Services at a Glance
204(2)
12.2.2 Overview of SLAs
206(1)
12.2.3 Service Agreement and Service Provision
207(2)
12.3 Web Service Level Agreements
209(5)
12.3.1 WSLA Schema Specification
209(1)
12.3.2 Web Services Run-Time Environment
210(1)
12.3.3 Guaranteeing Web Service Level Agreements
211(1)
12.3.4 Monitoring the SLA Parameters
212(1)
12.3.5 Use of a Measurement Service
213(1)
12.4 Hints for the Practitioner
214(2)
12.5 Summary
216(1)
13 Case Study: Building an Intranet Measurement Application 217(8)
13.1 Applying Measurement Tools
217(1)
13.2 The White-Box Software Estimation Approach
218(3)
13.3 First Web-Based Approach
221(1)
13.4 Second Web-Based Approach
222(1)
13.5 Hints for the Practitioner
223(1)
13.6 Summary
223(2)
14 Case Study: Measurements in IT Projects 225(18)
14.1 Estimations: A Start for a Measurement Program
225(1)
14.2 Environment
226(3)
14.2.1 The IT Organization
226(1)
14.2.2 Function Point Project Baseline
226(3)
14.3 Function Point Prognosis
229(1)
14.4 Conclusions from Case Study
230(11)
14.4.1 Counting and Accounting
230(1)
14.4.2 ISO 8402 Quality Measures and IFPUG GSCs
231(2)
14.4.3 Distribution of Estimated Effort to Project Phases
233(1)
14.4.4 Estimation of Maintenance Tasks
234(1)
14.4.5 The UKSMA and NESMA Standard
235(1)
14.4.6 Enhancement Projects
236(1)
14.4.7 Software Metrics for Maintenance
237(1)
14.4.8 Estimation of Maintenance Effort After Delivery
238(1)
14.4.9 Estimation for (Single) Maintenance Tasks
239(1)
14.4.10 Simulations for Estimations
239(2)
14.4.11 Sensitivity analysis
241(1)
14.5 Hints for the Practitioner
241(1)
14.6 Summary
242(1)
15 Case Study: Metrics in Maintenance 243(16)
15.1 Motivation for a Tool-based Approach
243(1)
15.2 The Software System under Investigation
244(1)
15.3 Quality Evaluation with Logiscope
245(6)
15.4 Application of Static Source Code Analysis
251(3)
15.5 Hints for the Practitioner
254(2)
15.6 Summary
256(3)
16 Metrics Communities and Resources 259(10)
16.1 Benefits of Networking
259(1)
16.2 CMG
259(1)
16.4 COSMIC
260(1)
16.6 German GI Interest Group on Software Metrics
261(1)
16.7 IFPUG
261(1)
16.8 ISBSG
262(3)
16.9 ISO
265(1)
16.10 SPEC
266(1)
16.11 The MAIN Network
266(1)
16.12 TPC
267(1)
16.13 Internet URLs of Measurement Communities
267(1)
16.14 Hints for the Practitioner and Summary
268(1)
Glossary 269(10)
Literature 279(12)
Index 291

An electronic version of this book is available through VitalSource.

This book is viewable on PC, Mac, iPhone, iPad, iPod Touch, and most smartphones.

By purchasing, you will be able to view this book online, as well as download it, for the chosen number of days.

Digital License

You are licensing a digital product for a set duration. Durations are set forth in the product description, with "Lifetime" typically meaning five (5) years of online access and permanent download to a supported device. All licenses are non-transferable.

More details can be found here.

A downloadable version of this book is available through the eCampus Reader or compatible Adobe readers.

Applications are available on iOS, Android, PC, Mac, and Windows Mobile platforms.

Please view the compatibility matrix prior to purchase.