Skip to main content

UML Weekend Crash Course

UML Weekend Crash Course

Tom Pender

ISBN: 978-0-764-54910-6

Nov 2002

384 pages

Select type: Paperback

In Stock



What it is: UML (Unified Modeling Language) is a graphical modeling language used to specify, visualize, construct, and document applications and software systems, which are implemented with components and object-oriented programming languages, such as Java, C++, and Visual Basic. UML incorporates the object-oriented community's consensus on core modeling concepts and provides a standard way for developers to communicate the details of system design and development. In addition to object-oriented modeling of applications, UML is also used for business-process modeling, data modeling, and XML modeling.
Purpose of modeling: Models for software systems are as important as having a blueprint for a large building, or an outline for a book. Good models enhance communication among project teams and assure architectural soundness. The more complex the software system, the more important it is to have models that accurately describe the system and can be understood by everyone. UML helps provide this via a standard for graphical diagrams. Just like an architect can understand the notations on any blueprint, UML enables software engineers and business managers to understand the design of any software system, even if the original designers have long left the company.
Organization behind it: Object Management Group (OMG) ( (UML Resource Page at OMG Web site is The OMG produces and maintains the UML standard, an internationally recognized standard. The OMG is an open membership, not-for-profit consortium that produces and maintains computer industry specifications for interoperable enterprise applications. Its membership roster (about 800) includes just about every large company in the computer industry and hundreds of smaller ones. Most of the companies that shape enterprise and Internet computing are represented on the OMG's Board of Directors.
Companies that contributed to the UML Standard: Realizing that UML would be strategic to their business, the following companies contributed their ideas to the first UML standard: Digital Equipment Corp, HP, i-Logix, IntelliCorp, IBM, ICON Computing, MCI, Microsoft, Oracle, Rational Rose, TI, and Unisys.
Companies that use UML: It is safe to say that all Fortune 1000 companies are currently using UML, or are moving toward UML to model and design their applications and systems. This includes companies from all vertical industries, from Coca Cola to Warner Brothers, from CVS Pharmacy to Lockhead Martin Aerospace. You name the company - if they have an IT department, they are using UML.


Part I-Friday Evening.

Session 1-What Is the UML?

Session 2-UML and Development Methodologies.

Session 3-How to Approach the UML.

Session 4-Defining Requirements for the Case Study.


Part II-Saturday Morning.

Session 5-Understanding the Use Case Model.

Session 6-Building the Use Case Diagram.

Session 7-Building the Use Case Narrative.

Session 8-Identifying the Use Case Scenarios.

Session 9-Modeling the Static View: The Class Diagram.

Session 10-The Class Diagram: Associations.

Part III-Saturday Afternoon.

Session 11-The Class Diagram: Aggregation and Generalization.

Session 12-Applying the Class Diagram to the Case Study.

Session 13-Modeling the Static View: The Object Diagram.

Session 14-Modeling the Functional View: The Activity Diagram.

Session 15-Applying the Activity Diagram to the Case Study.

Session 16-Modeling the Dynamic View: The Sequence Diagram.

Part IV-Saturday Evening.

Session 17-Applying the Sequence Diagram to the Case Study.

Session 18-Modeling the Dynamic View: The Collaboration Diagram.

Session 19-Applying the Collaboration Diagram to the Case Study.

Session 20-Modeling the Dynamic View: The Statechart Diagram.


Part V-Sunday Morning.

Session 21-Applying the Basic Statechart to the Case Study.

Session 22-Modeling the Extended Features of the Statechart.

Session 23-Applying the Extended Statechart Features to the Case Study.

Session 24-Modeling the Development Environment.

Session 25-Modeling the Static View: The Component Diagram.

Session 26-Modeling the Static View: The Deployment Diagram.

Part VI-Sunday Afternoon.

Session 27-Introduction to Web Development with Java.

Session 28-Analysis and Architectural Design of a Web Application.

Session 29-Design of a Web Application.

Session 30-UML Modeling Tools.

Appendix A: Answers to Part Reviews.

Appendix B: What's on the CD-ROM?



End-User License Agreement.
"...well-written...I would recommend it..." (Cvu, February 2003)
ChapterPageDetailsDatePrint Run
xiiIn sub title Reach out, you will find the following error
of if a topic should be or if a topic in the following: The publisher and I want your feedback. Please let us know of any mistakes in the book of if a topic is covered particularly well.

xiiAuthor e-mail
Readers are instructed to contact wiley at Questions for the author may be sent to

65Missing bullet
Add another bullet to the list: An association between OrderFulfillment and FillOrder.

65Missing line in Figure 6-3
In Figure 6-3, there should be a line between OrderFulfillment and FillOrder.

85Error in Figure 8-1
The arrow on the far right following the [no] path out of the decision Any unfilled quantities? should point to the end (bullseye), not to Create Back Order.

87Error in Figure 8-4
The arrow on the far right following the [no] path out of the decision Any unfilled quantities? should point to the end (bullseye), not to Create Back Order.

99Missing text in third bullet
The third bullet should read: Class level operation (underlined operation declaration): Optional. Denoted as an operation accessible at the class level; it does not require an instance (object) reference to be accessed... note the addition of does not require .

102Text error in sentence referring to Figure 9-3
Figure 9-3 illustrates three ways... not two ways...

131Text errors
The Product class (box) on the far right should be labeled Location . The multiplicity on the top left side of Order should be 0..* instead of 0..1 to agree with page 132, #5.

157Text error
The narrative for a Use Case tells you the rules and the logic required to accomplish a goal... Not the goal as in the text.

194Arrow pointing in wrong diretion
The arrow on the far right following the [no] path out of the decision Any unfilled quantities? should point to the end (bullseye), not to Create Back Order.

265Error in Figure 26-2
In Figure 26-2, remove 1..1 and 1..* This is an instance level diagram.