What do you think?
Rate this book
A Uml Pattern Language
A UML Pattern Language pairs the software design pattern concept with the Unified Modeling Language (UML) to offer a tool set for software professionals practicing both system modeling and software development. This book provides: a collection of patterns in the domain of system modeling, including those that are useful to management, operations, and deployment teams, as well as to software developers; a survey of the development of patterns and the UML; a discussion of the underlying theory of the patterns and instructions for using the language; a thorough exploration of the design process and model-driven development. A UML Pattern Language recognizes that design and modeling have become equal partners with programming and coding in the enterprise of software development. Providing both an understanding of the work of design and the way patterns and the UML combine to facilitate design.
257 pages, Paperback
First published February 10, 2000
6 people want to read
Ratings & Reviews
Friends & Following
Create a free account to discover what your friends think of this book!
Community Reviews
Displaying 1 of 1 review
February 17, 2016
I bought this book thinking it was about describing patterns with UML. Having now read it, I know that actually it's... well, that's a bit harder to say.
The book has 3 sections: the first is a quick introduction to the UML (v1) and the basic elements of UML diagrams; the third section is a potted history of UML and the evolution of patterns. These two are all very well, but the middle section is a puzzle.
The author defines a set of "patterns " for UML style and generally how to do work, but the concept of a "pattern" is stretched so far as to be pretty meaningless. On the one hand, the style patterns are either trivial ('write descriptions along lines not across them') or ridiculous (ASCII text representations of UML diagramming symbols). On the other hand, he describes high-level working practises that are kind of pattern-like (define As-Is and To-Be models, partition work into chunks, ... but which are so generic that by that standard any form of work practise could be elevated as a pattern.
I'm mystified what the audience of this book is supposed to be (other than "people who buy UML or Pattern books, without being able to flick through them first"). The first section is too shallow to be useful, the third section is background information, and the middle section identifies some pattern-like scenarios without really providing much in the way of useful, actionable guidance.
The book has 3 sections: the first is a quick introduction to the UML (v1) and the basic elements of UML diagrams; the third section is a potted history of UML and the evolution of patterns. These two are all very well, but the middle section is a puzzle.
The author defines a set of "patterns " for UML style and generally how to do work, but the concept of a "pattern" is stretched so far as to be pretty meaningless. On the one hand, the style patterns are either trivial ('write descriptions along lines not across them') or ridiculous (ASCII text representations of UML diagramming symbols). On the other hand, he describes high-level working practises that are kind of pattern-like (define As-Is and To-Be models, partition work into chunks, ... but which are so generic that by that standard any form of work practise could be elevated as a pattern.
I'm mystified what the audience of this book is supposed to be (other than "people who buy UML or Pattern books, without being able to flick through them first"). The first section is too shallow to be useful, the third section is background information, and the middle section identifies some pattern-like scenarios without really providing much in the way of useful, actionable guidance.
Displaying 1 of 1 review