UML 2.0 in a Nutshell: A Desktop Quick Reference

by Dan Pilone and Neil Pitman

Book Overview

System developers have used modeling languages for decades to specify, visualize, construct, and document systems. The Unified Modeling Language (UML) is one of those languages. UML makes it possible for team members to collaborate by providing a common language that applies to a multitude of different systems. Essentially, it enables you to communicate solutions in a consistent, tool-supported language. Today, UML has become the standard method for...

• Format: Paperback
• Language: English
• ISBN: 0596007957
• ISBN13: 9780596007959
• Release Date: July 2005
• Publisher: O'Reilly Media
• Length: 234 Pages
• Weight: 0.78 lbs.
• Dimensions: 0.3" x 6.0" x 8.9"

Customer Reviews

One of the Best UML Reference Books On the Market Today & Very Portable

When searching for a very good UML reference book last year, I happened upon the book entitled "UML 2.0 in a Nutshell" by Dan Pilone with Neil Pitman. The book, which measures a mere 8.9 by 6 by 0.8 inches, is both lightweight and highly portable; which is one of the reasons that I decided to purchase a copy. However, it was ultimately the content of the book, and not its compact size, that convinced to me that this would a very useful resource. Condensed within 216 pages, "UML 2.0 in a Nutshell" lives up to its title, as the book is an extremely informative resource in understanding the various graphical elements that comprise UML with its nine types of diagrams. The book's 12 chapters and two appendices are divided into four main parts: an introduction, static diagrams, behavioral modeling diagrams and finally, extensions and applications of UML. First Part: Introduction chapter 1: Fundamentals of UML This chapter provides a short, but good introduction to the fundamentals of UML. If you have never used UML before, this will help to introduce several key concepts of UML; but you might want to consider purchasing a UML tutorial book, such as "UML Weekend Crash Course" by Thomas A. Pender, to obtain a more hands-on approach to learning UML. Second Part: Static Diagrams Chapter 2: Class Diagrams Class diagrams are one of the most important aspects of UML. With class diagrams, the relationships between classes can be thoroughly illustrated, including the strengths of the relationships between classes. This chapter provides a precise description of the various ways that class relationships can be defined within UML: dependencies, associations, aggregations, compositions and generalizations; as well as association classes. This chapter also discusses class members (variables & methods), whether a class might be abstract or an interface, and templates. Chapter 3: Package Diagrams Classes that are contained within a common package can be illustrated within UML using package diagrams. This chapter also includes relationships between packages and use case packages. Chapter 4: Composite Structures This chapter discusses composite structures that exist during runtime, including connectors and ports, as well as collaborations. Chapter 5: Component Diagrams Components (replaceable & executable pieces of a larger system whose implementations are usually hidden) can be used in UML as either a black-box or white-box view. This chapter discusses both uses. Chapter 6: Deployment Diagrams This chapter discusses how the deployment of an application (which may include many pieces) can be illustrated within UML, including artifact instances, manifestations, nodes, devices, execution environments and communication paths. Third Part: Behavioral Modeling Diagrams Chapter 7: Use Case Diagrams This chapter documents how an actor (a person or another application) interacts with applications and their internal components. Chapter 8: Statec

A Must Have

It turns out there's more to UML than stick figures and boxes. "UML 2.0 In a Nutshell" (O'Reilly, ISBN 0596007957) by Dan Pilone and Neil Pitman is an excellent book for those new to UML and development as well as for those with a bit more experience in design and development. The book makes for a great reference. Each chapter is encapsulated and starts with a high level view of a diagram type and then digs into the implementation details. Finding specific information doesn't take very long. The chapters are well organized - just as we all hope our own use of UML will lend our own work to be. The book is more than a reference. The authors provide sage advice and discussion on common practices and potential pitfalls. UML made a big leap with its 2.0 release. I know we all have the time to read the thousands of pages of UML 2.0 specification out there; but for those of us who would appreciate a shortcut this book is it. The authors make sure to explain, succinctly, what the new release adds and changes are. They then provide an entire section on Model Driven Architecture (MDA) and a chapter on Composite Structures. The UML 2.0 updates are reason enough to read the book.

A Reference for All Levels

I approached this book with some trepidation. I did not want to get into a sales pitch about the merits of one modeling tool over others. It quickly became obvious that this book is not about tools. In fact, the opposite it true. This book is truly about the UML. While there are sparse references to some tools, the text focuses on the UML as a standard and how to effectively and pragmatically apply it to your efforts. Another concern I had when starting this book was a strict adherence to the UML. Much to my pleasure, this book takes a very pragmatic approach to modeling software systems. There are often statements indicating how "many designers do it" as opposed to the more formal approach. These situations show how making the UML work for you (as opposed to you working for the UML) does not cause any lack of clarity. In fact, it often adds to clarity and simplicity. I really appreciate the way in which the text suggests approaching adoption and use of the UML. It would be difficult to try and quickly learn and apply all of the details, of all of the diagram types, and which arrows connect what shapes. The book addresses this by suggesting that readers adopt the UML in pieces. It also suggests that not every diagram type is needed for every situation. Once again, the text emphasizes a practical approach. Although it would seem difficult to describe the graphical nature of the UML in text, the author does this quite adeptly. There is an excellent balance between figures and text. Examples are direct and meaningful. Also, the author does not dwell on how to model a software system. Instead, the focus is on how to use the UML as a modeling tool. In addition to the UML-centric chapters, the book offers additional information related to software modeling. The first chapter provides an overview of the UML. This gives readers, especially those new to the UML, a nice foundation of vocabulary and purpose. The last chapter, "Effective Diagramming," provides readers with some solid guidelines on using the UML effectively. Here the author explicitly describes "appropriate" modeling techniques (Dare I say best practices?). Appendix A provides an introduction to Model Driven Architecture (MDA). It really is a brief introduction that should kindle the reader's desire for more information. If you are feeling ambitious, you can also learn about the Object Constraint Language (OCL) described in Appendix B. The OCL is used in addition to the UML for more granular detail in describing constraints in UML models. Overall I really enjoyed this book. I highly recommend it to people trying to learn the UML for the first as well as those wanting to know what has changed since previous versions of the UML. I recommend this book to both veterans and to those new to the UML alike because of how it is written. Both groups will find the book's pragmatic approach to using the UML quickly educational and beneficial as an on-going reference.

This is exactly what I need

It is a good effort to put such a good content in just 200 pages. The book shows old UML 1.4 elements by using the 'trap' mark so you can clearly tell it is something deprecated. It is a very clear book, and you can skip to any specific diagram you are interested. Unlike most other UML books, which has more content on methodologies, this book is focus on the language (diagram) itself.