Skip to main content Accessibility help
×
Hostname: page-component-84b7d79bbc-dwq4g Total loading time: 0 Render date: 2024-07-27T23:17:56.689Z Has data issue: false hasContentIssue false

Chapter 2 - Bubbles and Lines—Useful Diagrams for Object-Oriented Analysis and Design

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

Published online by Cambridge University Press:  07 September 2010

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

Summary

What We'll Learn in This Chapter

Why we need each type of diagram.

How to draw each type of diagram.

How to read class diagrams drawn in other modeling notations.

How and when to use use-case diagrams, sequence diagrams, state diagrams, process models, data models, collaboration diagrams, and interface-flow diagrams.

This book is an extension of The Object Primer and in this chapter we'll extend our knowledge of object-oriented analysis-and-design techniques. This chapter is perfect for people who wish to gain a broad understanding of the analysis-and-design options that are open to them when developing a system.

There's more to object-oriented (OO) development than CRC (Class Responsibility Collaborator) models, use cases, and class diagrams. Although all three techniques are useful, they don't give you the whole picture. In this chapter we'll see several types of diagrams that help to fill in the blanks: use-case diagrams, sequence diagrams, state diagrams, interface-flow diagrams, data models, collaboration diagrams, and process diagrams. We're also going to compare the Ambler notation with other leading notations to help you understand the class diagrams that you see in other OO development books.

The Importance of Bubbles and Lines

Management is constantly talking about deliverables. These are usually, but not always, physical by-products of your development effort. Although the ultimate deliverable should be a fully functioning application that has been successfully installed and accepted by the user, interim deliverables often include project plans, analysis documents, design documents, test plans, and so on.

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