Object-Oriented Software Engineering Using UML, Patterns, and Java 3rd Edition

This is NOT a book on Unified Modeling Language (UML). It's not a book on Object Constraint Language (OCL). It's also not a book on Capability Maturity Models (CMM), Class-Responsibilities-Collaborators (CRC) cards, Decision Representation Language (DRL), Extreme Programming (XP), Gantt charts, Issue-Based Information Systems (IBIS), Joint Appication Design (JAD), Key Process Areas (KPA), the Liskov Substitution Principle, Model-View-Controller (MVC) architectural styles, Nonfunctional Requirements (NFR) Frameworks, Object Design Documents (ODD), PERT charts, the Questions-Options-Criteria (QOC) model, Requirements Analysis Documents (RAD), Royce's methodology, Software Configuration Management Plans (SCMP), System Design Documents (SDD), Software Project Management Plans (SPMP), the Unified Software Development Process, User Manuals, V-Models, Work Breakdown Structures (WBS), or any of the myriad other tools introduced in the book.This IS a book to introduce newly-minted programmers to the kind of things, tools, and processes they can look forward to (with either anticipation or dread) in the real world of software development. As the authors state on page viii of the Preface:"We have observed that students are taught programming and software engineering techniques in isolation, often using small problems as examples. As a result, they are able to solve well-defined problems efficiently, but are overwhelmed by the complexity of their first real development experience, when many different techniques and tools need to be used and different people need to collaborate."It's been many years since I was involved in major software development projects (and those were all in the military). But, this book seems to have covered everything that all new programmers need to know so that they aren't simply lost when they enter their first software project. The readers certainly won't be experts in the things covered, but they'll at least have a good grounding and be able to bootstrap themselves from there (especially since the authors provide "Further Readings" and a Bibliography at the end of each chapter). For instance, on page 71, under Further Readings, they list three works on UML: one of which is the 566 page official specification, "OMG Unified Modeling Language Specification."Overall, this is an excellent book for anyone who is just entering the software development world. I rate it at 5 stars out of 5.As a side note, Florida State University (FSU) uses this book in its COP 3331: "Object-Oriented Analysis and Design" course.

It was a requirement and a necessity for my graduate class.

This product was needed to help me get through a very tough class. It got here faster than expected and in good shape.

We have various copies of this book in our offices - its a great book for software engineering and a must read for any software engineer, computer scientist or project manager. The material is thick and dives deep into the topic - but very much well worth it.

Used it as main textbook for one of my classes. It was really challenging. A great book for learning object oriented software engineering.

This book was required reading for a course I took at Johns Hopkins Medicine. While not entirely relevant to the course I took and rather expensive, it was very well-written. Really difficult to navigate on Kindle, however. I really wish I had purchased the hard copy of this book. And I am a clinical informaticist.

Great introduction to everything that a senior level, or graduate computer science/engineering major will see in industry as a software engineer.

Received as Posted