Applying UML and Patterns [Hardcover]

Craig Larman (Author)

Book Description

Publication Date: October 30, 1997 | ISBN-10: 0137488807 | ISBN-13: 978-0137488803 | Edition: 1st

Guides students through each step of requirements, analysis, design, and coding. Topics cover Expressing analysis and design models using the UML, a standard diagramming notation, Applying patterns to assign responsibilities and design collaborations and more. DLC: Object-oriented methods.

Editorial Reviews

Amazon.com Review

Written for the developer with previous programming and design experience, Applying UML and Patterns combines UML, software patterns, and Java to illustrate the author's own design strategy. Though author Craig Larman sometimes relies heavily on the jargon of software engineering, there's no doubt that his book contains some immediately useful ideas on software design, using the latest and greatest in software-engineering research.

This book begins by outlining a basic process of software design using iterative, object-oriented techniques. The case study used for this text is a point-of-sale (POS) system, a helpful real-world example. The book constructs use case diagrams and basic conceptual and class models for this system. The author then adds sequence diagrams to show how the POS system will do its processing and collaboration diagrams to show how objects will interact with one another. The author uses standard UML diagrams to document the design.

When it comes to refining class design, the author's experience with patterns really shines. His General Responsibility Assignment Software Patterns (GRASP) suggest guidelines for designing classes that work together effectively. Larman believes that the ability to assign responsibilities to classes effectively is one of the most important aspects of good object-oriented design. His patterns allow this to happen and provide an interesting contribution to the design process. (The author also introduces more widely used software patterns to enhance the design process.)

When it comes to coding the design, Java is the programming language of choice for this text. Further chapters discuss how to refine an initial design using an iterative process of software engineering. While it's unlikely that readers will adopt Larman's approach to software design in its entirety, his guidelines--and application of patterns to class design, all documented using UML--make this a worthwhile text for the more experienced reader. --Richard Dragan

From the Publisher

This Video Course presents an introductory course on using UML and Patterns for Object-Oriented Analysis and Design. The analogy is this, just as architects and contractors use standard plumbing and electrical blueprint notations when designing, so do programmers use UML notation and Patterns when developing new applications. --This text refers to the Turtleback edition.

See all Editorial Reviews

Product Details

• Hardcover: 507 pages
• Publisher: Prentice Hall PTR; 1st edition (October 30, 1997)
• Language: English
• ISBN-10: 0137488807
• ISBN-13: 978-0137488803
• Product Dimensions: 10.2 x 8.2 x 1 inches
• Shipping Weight: 2.6 pounds
• Average Customer Review: 4.3 out of 5 stars  See all reviews (158 customer reviews)
• Amazon Best Sellers Rank: #1,144,026 in Books (See Top 100 in Books)
  • #94 in Books > Computers & Technology > Programming > Software Design, Testing & Engineering > UML

More About the Author

Discover books, learn about writers, read author blogs, and more.

Most Helpful Customer Reviews

46 of 47 people found the following review helpful

5.0 out of 5 stars The first book you should read to learn UML! November 26, 1999

By Gavin Lim

Format:Hardcover

Craig Larman did a splendid job simplifying UML. I bought this book along with the official UML user guide and I prefer reading this book because of how it made UML look so easy. What's so impressive about this book is that the author stays with one example throughout the book, and clearly illustrates the relationships and dependencies amongst different UML diagrams and artifacts. He even shows you how to map the diagrams to actual Java code! Larman's explanations of the different design patterns is also invaluable. I haven't heard of design patterns before, and this book helped me have a deeper appreciation of patterns to create better object-oriented software.

70 of 75 people found the following review helpful

5.0 out of 5 stars Great Introduction To OO Analysis and Design December 21, 2001

By David C. Veeneman

Format:Hardcover|Amazon Verified Purchase

This book is the best introduction I have seen to object-oriented analysis and design. It explains the 'Unified Process' of analysis and design, including UML and the use of patterns. I am a big fan of this book because it emphasizes the "why"--the reason for each element of the process from a business perspective. For example, instead of simply offering a recipe for writing use cases, the book talks about why one might include or exclude specific elements to achieve specific objectives.

Those (like me) who have avoided Unified Process because it looks too rigid, bureaucratic, and form-laden will love this book. The author argues convincingly that UP is best implemented in an iterative process that looks more like Extreme Programming than the cumbersome waterfall process one typically associates with UP. Then the book shows how to implement a UP process in enough detail, with enough examples, and with enough flexibility, that a project leader can readily put this form of UP into practice.

I have avoided UP for years, but this book may have made a convert out of me. It's the first book I have seen that makes an effective business case for UP and presents a practical guide to its implementation. I have no hesitation recommending it to anyone, from novice project leaders to seasoned software architects.

38 of 39 people found the following review helpful

5.0 out of 5 stars Concise and easy-to-read February 8, 2000

By Michael F. Maddox

Format:Hardcover

Craig Larman provides the reader with simple, easy-to-follow examples of UML and pattern application, with few deep theoretical or philisophical discussions of development process. This style offers the new user of UML a good guide to applied modeling concepts, without bogging he/she down in academic arguments. If you are going to buy a single book to learn UML, I highly recommend this one, as it goes beyond simply describing the notation, and illustrates its use through simple guidelines. Other books are necessary to fully understand the complexities of UML, patterns, and design process, but this one fills a huge gap for the beginner market.