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-rnpqb Total loading time: 0 Render date: 2024-07-27T23:15:11.750Z Has data issue: false hasContentIssue false

Chapter 3 - Improving Your Design—A Class-Type Architecture

from Part II - OBJECT-ORIENTED ANALYSIS, DESIGN, AND ARCHITECTURE

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

Why we need a class-type architecture, and more to the point, why we need a five-layer class-type architecture.

The implications of the architecture for both system development and for project management.

What each layer is really all about and how it fits in with the other layers.

Users want systems that are better, faster, and cheaper. Not only do they want new systems that conform to these requirements, they also want systems that are adaptable and modifiable. You might get lucky and get new requirements that are easy to meet, but I wouldn't want to count on it. Without a well-thought-out architecture in place you will probably not be able to develop applications in a timely and efficient manner that meet the demands of your users.

The class-type architecture presented in this chapter meets these goals.

As an object-oriented developer you need to have an overall game plan as to how you intend to design your system. The class-type architecture described in this chapter provides you with an excellent strategy for organizing the classes of your application to increase both its extensibility and maintainability. I don't claim that this architecture is detailed enough for the needs of your organization. I do claim, however, that it does provide an approach to partitioning your applications that leads to a significantly better design.

Type
Chapter
Information
Building Object Applications that Work
Your Step-by-Step Handbook for Developing Robust Systems with Object Technology
 , pp. 85 - 116
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
×