Skip to main content Accessibility help

We use cookies to distinguish you from other users and to provide you with a better experience on our websites. Close this message to accept cookies or find out how to manage your cookie settings.

Close cookie message
×
Hostname: page-component-84b7d79bbc-fnpn6 Total loading time: 0 Render date: 2024-07-27T23:18:26.352Z Has data issue: false hasContentIssue false

Chapter 6 - Measuring and Improving the Quality of Your Work—Object-Oriented Metrics

from Part III - OBJECT-ORIENTED CONSTRUCTION

Published online by Cambridge University Press:  07 September 2010

Scott W. Ambler
Scott W. Ambler
Affiliation:
AmbySoft Inc., Toronto
Get access

Summary

What We'll Learn in This Chapter

What metrics are and why they're important for object-oriented (OO) development.

Which metrics work for OO and which ones don't.

What metrics to use for estimating projects, improving your development efforts, selecting the right tools, and improving your development process.

How to use metrics effectively on your OO development projects.

Project managers are constantly inundated with questions about the status of their project. How good is our design? Can we start coding now? How long will the project take? How big is the project? How much will it cost? How many people do we need? Questions that are difficult, if not impossible, to answer with any certainty without taking measurements of specific factors that address these issues. But what should you measure? A good question.

One of the reasons, very often the main reason, that firms move into object orientation is that they want to improve the quality of the applications that they develop. They want systems that are easier to maintain. They want systems that are easier to extend. They want to develop systems better, faster, and cheaper. The question is “How do you know that you've succeeded?” In this chapter we'll see that metrics are used to answer this question.

There are a lot of object-oriented (OO) development environments and techniques available to you. Although this sounds good, the problem is that it isn't always clear which ones are the best ones for you.

Type
Chapter
Information
Building Object Applications that Work
Your Step-by-Step Handbook for Developing Robust Systems with Object Technology
 , pp. 171 - 196
Publisher: Cambridge University Press
Print publication year: 1997

Access options

Get access to the full version of this content by using one of the access options below. (Log in options will check for institutional or personal access. Content may require purchase if you do not have access.)

Save book to Kindle

To save this book to your Kindle, first ensure coreplatform@cambridge.org is added to your Approved Personal Document E-mail List under your Personal Document Settings on the Manage Your Content and Devices page of your Amazon account. Then enter the ‘name’ part of your Kindle email address below. Find out more about saving to your Kindle.

Note you can select to save to either the @free.kindle.com or @kindle.com variations. ‘@free.kindle.com’ emails are free but can only be saved to your device when it is connected to wi-fi. ‘@kindle.com’ emails can be delivered even when you are not connected to wi-fi, but note that service fees apply.

Find out more about the Kindle Personal Document Service.

Available formats
×

Save book to Dropbox

To save content items to your account, please confirm that you agree to abide by our usage policies. If this is the first time you use this feature, you will be asked to authorise Cambridge Core to connect with your account. Find out more about saving content to Dropbox.

Available formats
×

Save book to Google Drive

To save content items to your account, please confirm that you agree to abide by our usage policies. If this is the first time you use this feature, you will be asked to authorise Cambridge Core to connect with your account. Find out more about saving content to Google Drive.

Available formats
×