Applying UML and Patterns
|
| |
ISBN |
0130925691 |
|
Release Date |
13 July 2001 |
|
Page |
656 |
|
Category |
UML |
|
Tags |
uml,
applying uml and patterns,
design patterns,
design pattern,
applying uml,
larman,
patterns,
pattern,
craig larman,
"applying uml and patterns",
applying,
applying uml patterns,
"applying uml",
uml patterns,
applying uml and pattern,
uml and patterns,
uml distilled,
uml pattern,
arm,
uml bible,
apply,
uml and pattern,
uml case study,
uml 2,
head first design patterns,
|
|
This book @Amazon |
View |
|
Description
Good software starts with a good design, and the subtitle of Applying UML and Patterns, "An Introduction to Object-Oriented Analysis and Design (OOA/D) and the Unified Process" reinforces that that's what this book is about.
The first edition of Applying UML and Patterns became a standard. The second edition uses the unified process (UP) as the iterative process within which OOA/D is introduced, and extends the case study used in the first edition. Other changes have been made to reflect the growing consensus on the most effective ways to work with OOA/D and patterns.
Although you will learn UML, this isn't what Applying UML and Patterns is all about. It's designed to teach you to think of software as a collection of objects with properties and to manipulate the relationships between them. This is far more profound.
The case study enables Craig Larman to carry the design through to Java code. In practice, you will need a basic understanding of OO programming to benefit from Applying UML and Patterns, though you needn't know Java--you can implement the designs in the OO language of your choice with equal facility.
When it comes right down to it, Applying UML and Patterns is all about providing you with a language in which to think about software design. This is quite different from learning a language in which to code a design.
A facility with OOA/D will enable you to design and discuss programs independent of code, to produce more elegant and maintainable software, and to take a 30,000-foot view of the way your software interacts with the world. In effect, it can shift your viewpoint from that of a mechanic to that more sophisticated viewpoint of an engineer. |
|
