Hardcover: 800 pages
Publisher: Pearson; 3 edition (August 8, 2009)
Product Dimensions: 7.2 x 1.8 x 9.3 inches
Shipping Weight: 3.2 pounds (View shipping rates and policies)
Average Customer Review: 3.8 out of 5 stars See all reviews (25 customer reviews)
Best Sellers Rank: #469,023 in Books (See Top 100 in Books) #30 in Books > Computers & Technology > Programming > Software Design, Testing & Engineering > UML #555 in Books > Textbooks > Computer Science > Software Design & Engineering #574 in Books > Computers & Technology > Programming > Software Design, Testing & Engineering > Object-Oriented Design
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).