- Hardcover: 720 pages
- Publisher: Addison-Wesley Professional; 3 edition (April 30, 2007)
- Language: English
- ISBN-10: 020189551X
- ISBN-13: 978-0201895513
- Product Dimensions: 7.3 x 1.6 x 9.4 inches
- Shipping Weight: 2.6 pounds (View shipping rates and policies)
- Average Customer Review: 17 customer reviews
- Amazon Best Sellers Rank: #242,254 in Books (See Top 100 in Books)
Enter your mobile number or email address below and we'll send you a link to download the free Kindle App. Then you can start reading Kindle books on your smartphone, tablet, or computer - no Kindle device required.
To get the free app, enter your mobile phone number.
Object-Oriented Analysis and Design with Applications (3rd Edition) 3rd Edition
Use the Amazon App to scan ISBNs and compare prices.
This month's Book With Buzz: "The Lying Game" by Ruth Ware
From the instant New York Times bestselling author of blockbuster thrillers "In a Dark, Dark Wood" and "The Woman in Cabin 10" comes Ruth Ware’s chilling new novel, "The Lying Game." See more
Frequently bought together
Customers who bought this item also bought
From the Back Cover
Object-Oriented Design with Applications has long been the essential reference to object-oriented technology, which, in turn, has evolved to join the mainstream of industrial-strength software development. In this third edition--the first revision in 13 years--readers can learn to apply object-oriented methods using new paradigms such as Java, the Unified Modeling Language (UML) 2.0, and .NET.The authors draw upon their rich and varied experience to offer improved methods for object development and numerous examples that tackle the complex problems faced by software engineers, including systems architecture, data acquisition, cryptoanalysis, control systems, and Web development. They illustrate essential concepts, explain the method, and show successful applications in a variety of fields. You'll also find pragmatic advice on a host of issues, including classification, implementation strategies, and cost-effective project management.New to this new edition areAn introduction to the new UML 2.0, from the notation's most fundamental and advanced elements with an emphasis on key changesNew domains and contextsA greatly enhanced focus on modeling--as eagerly requested by readers--with five chapters that each delve into one phase of the overall development lifecycle.Fresh approaches to reasoning about complex systemsAn examination of the conceptual foundation of the widely misunderstood fundamental elements of the object model, such as abstraction, encapsulation, modularity, and hierarchyHow to allocate the resources of a team of developers and mange the risks associated with developing complex software systemsAn appendix on object-oriented programming languagesThis is the seminal text for anyone who wishes to use object-oriented technology to manage the complexity inherent in many kinds of systems.
About the Authors "
Section I: Concepts
Chapter 1: Complexity
Chapter 2: The Object Model
Chapter 3: Classes and Objects
Chapter 4: Classification
Section II: Method
Chapter 5: Notation
Chapter 6: Process
Chapter 7: Pragmatics
Chapter 8: System Architecture: Satellite-Based Navigation
Chapter 9: Control System: Traffic Management
Chapter 10: Artificial Intelligence: Cryptanalysis
Chapter 11: Data Acquisition: Weather Monitoring Station
Chapter 12: Web Application: Vacation Tracking System
Appendix A: Object-Oriented Programming Languages
Appendix B: Further Reading "
About the Author
Grady Booch is an IBM fellow and author of six best-selling books on object-oriented programming. He is world-reknowned as an originator of OO and founder of UML.
Robert A. Maksimchuk, as Research Director in the Unisys CTO Office, focuses on emerging modeling technologies to advance the strategic direction of the Unisys 3D-Visual Enterprise modeling framework. Bob brings an abundance of systems engineering, modeling, and object-oriented analysis and design expertise, in numerous industries, to this mission. He is the coauthor of the books UML for Mere Mortals and UML for Database Design, has written various articles, has traveled worldwide as a featured speaker in numerous technology forums, and led workshops and seminars on UML and object-oriented development.
Michael W. Engle is a principal member of the engineering staff with the Lockheed Martin Corporation. He has extensive technical and management experience across the complete system development lifecycle, from project initiation through deployment and support in a variety of application domains. As a systems architect, Mike employs object-oriented analysis nad design techniques in complex systems development.
Dr. Bobbi Young is a Director of Research for the Unisys Chief Technology Office. She has many years of experience in the IT industry working with commercial companies and Department of Defense contractors. Dr. Young has been a consultant mentoring in program management, enterprise architecture, systems engineering, and object-oriented analysis and design. Throughout her career, she has focused on system lifecycle processes and methodologies, and enterprise architecture.
Jim Conallen is a software engineer in IBM Rational's Model Driven Development Strategy team, where he is actively involved in applying the Object Management Group's (OMG) Model Driven Architecture (MDA) initiative to IBM Rational's model tooling.
Kelli A. Houston is a Consulting IT Specialist at IBM Rational. She is the method architect for IBM's internal method authoring method and is part of the team responsible for integrating IBM's methods.
Browse award-winning titles. See more
Top customer reviews
It's a good overview of object-oriented analysis and design and its connection to the sometimes esoteric UML diagrams that accompany the process of analyzing and designing object-oriented systems.
I think the book is good for anyone looking to learn the basic reasoning behind object-oriented analysis and design and see some brief examples relating to the theory.
I expected more from a book that comes recommended from so many people. The feeling I had at the end of each chapter is difficult to describe, but most closely resembles that of hopelessness. I was thinking to myself that maybe I didn't read it right, or maybe I accidentally skipped a page (or ten). Overall, I felt like I had learned something, but had no idea how to apply it. The book leaves you with more questions than when you started.
The author specifies many times throughout the book that he truncates or condenses information because it would be too long to fit in the book. This sacrifice of detail comes at a cost; an unnecessary cost considering how much repetitious filler information (borderline double-talk) is included in the book. The book could have been 200 pages shorter if they eliminated the fluff, and 200 times better if they used the space to take an example to completion.
I found myself wanting more information at the end of each chapter. Just when the author starts to get into finer details of an example is the moment when he condenses everything, wraps it up into something ambiguous and indecipherable, and begins on some new example. One specific case I can offer is the part of the book that uses the satellite navigation system example, and the black-box/white-box analysis with use cases and activity diagrams. When I started reading it I thought it was great. I expected by the end of the chapter I'll finally have a grasp on how to use these UML tools and analysis techniques to better organize projects and create clearer preliminary designs. He ends up condensing the diagrams, i.e., diagrams that would have been separate are now part of one big diagram. Furthermore, he only shows you partially how to create the diagram and then lists the things he would continue to do from that point, but doesn't actually show it to you. What's worse, is he tells you that he condensed the diagrams and in a real life situation he wouldn't have done this, rather he would have created separate diagrams and detailed them differently and performed the analysis in a different order.
I think the end result of reading this book is that you've gained no new skills that you can practice and incorporate into your work, because you only have this partial condensed idea of analysis and design. I got this book because I was looking for more detailed information on how to build object-oriented systems as opposed to the multitude of vague and worthless mantras found all over like, "just make everything cohesive and loosely coupled", and "SOLID". This book ended up being a very wordy version of the same vague and worthless mantras.
Together with this book, I recommend this companion books: Clean Code (Robert C. Martin), Agile Software Development - Principles, Patterns, and Practices (Robert C. Martin), UML 2 and the Unified Process 2ed. (Arlow and Neustadt).
Most recent customer reviews
Began a gardening plan to use...Read more