 | |
| |
Objects, Components, and Frameworks with UML : The Catalysis(SM) Approach
 |
Author: Desmond Francis D'Souza, Alan Cameron Wills
List Price: $49.95
Our Price: Click to see the latest and low price
ISBN: 0201310120
Publisher: Addison-Wesley Pub Co (19 October, 1998)
Edition: Paperback
Sales Rank: 31,937
Average Customer Rating: 4 out of 5
|
Customer ReviewsRating: 5 out of 5
Alltime favorite
This is one of my alltime favorites.
If you always felt annoyed by the lack of coherence in UML, then buy this book to read about a comforting and coherent approach.
If you're looking for a book on applying standard UML diagramming techniques, then you shouldn't buy this book. Catalysis people would probably call this an 'import with modifications'. They modify some of the UML language in order to present you a more coherent way of looking at software and software development.
If you're looking for a book that would help you using your UML tools in a useful way, then you shouldn't read this book. I've never been able to find a tool that supports the Catalysis approach.
If you wonder if Catalysis is still alive, then I'd say: join the crew. There isn't really a living Catalysis community, and the authors seem to have gone numb after writing this book.
Rating: 3 out of 5
Interesting Concepts, But Overall A Little Disappointing
This book had the potential to be a 5 star book but alas it comes up short. The concepts that the authors attempt to relate are things that most people could use in their software development: static and behavioral object modeling, abstraction, components, packages, architecture, and frameworks. The problem is the Catalysis Approach. Unfortunately, many of the terms and diagrams used are similar in name but different in meaning from what is typically written in UML. I have numerous other books published by Addison Wesley on object modeling - Design Patterns and Refactoring to name a couple - and they tend to lean more toward the Rational or Unified Process. It is very difficult to take the information that the authors present in Catalysis and see how it relates to the work of the GOF without a lot of translating. This is not to say that there is not room for other processes or methodologies in the software community; however, the average engineer sitting at his desk is going to have a hard time mining the information in this book because of the presentation. Catalysis may be a very effictive process, but it should be examined to see if it can use UML in ways that most software developers are accostumed to seeing.
Rating: 1 out of 5
confusing and incoherent
If you know a lot about UML, don't read this book. If you know nothing about UML, don't read this book. If you have picked up a few UML books but never finished any of them, you won't be able to fininsh this one either. There are use case diagrams that are not UML's use case diagrams. There are static diagrams that are not UML's static diagrams. Joint actions are use cases. Type spec is degenerate collaboration. Collaborations are refinement of use cases...This book is full of this kind of slightly off definitons and NOTHING NEW.
Similar Products
· Problem Frames: Analyzing and Structuring Software Development Problems
· Software Architecture in Practice, Second Edition
· Software Project Management: Readings and Cases
· A Discipline for Software Engineering
· UML Components: A Simple Process for Specifying Component-Based Software (The Component Software Series)
| | | | | |
| |
