Objects, Components, and Frameworks with UML: The Catalysis(SM) Approach [Paperback]

Desmond Francis D'Souza (Author), Alan Cameron Wills (Author)

Book Description

ISBN-10: 0201310120 | ISBN-13: 978-0201310122 | Publication Date: October 29, 1998 | Edition: 1

This book teaches the student how to use objects, frameworks, and UML notation to design, build, and reuse component-based software. Catalysis is a rapidly emerging UML-based method for object- and component-based development. It provides a clear meaning of and systematic uses for the UML notation. "The Catalysis Approach" explains how patterns can be characterized as model frameworks. Through the application of frameworks in requirements, specifications, architectures, and designs, students will find that all models contain recurring patterns of structure, behavior, and refinement. This opens the way to building models and designs rapidly by adapting and composing both generic and domain-specific modeling frameworks.

Editorial Reviews

Amazon.com Review

After a quick introduction to the design process Catalysis, this book moves on to carefully defining objects, their attributes, operations, and collaborations. (Generally, Catalysis objects and components are "decoupled" so that they can work more independently, leading to easier reuse and customization.)

The authors then turn to modeling and design, using a spreadsheet program as their example. Next, the authors discuss component-based design, where projects are assembled with components. The book closes with an effective tour of the actual Catalysis design process, illustrated with a case study for a video-rental store. All design documents, written in the Unified Modeling Language (UML), are provided along with some useful expert advice on creating better design documents and components.

Judging from the evidence here, the Catalysis design method can offer some real advantages for today's software, which often must evolve to meet unforeseen requirements (international markets or new platforms such as the Web). Designed according to the principles outlined in the book, components and designs can offer a higher level of reuse. Even if you do not actually adopt the Catalysis process, this authoritative and admirably clear book offers a wealth of design expertise for anyone interested in being more productive with objects and UML. --Richard Dragan

Review

. . . We found Catalysis to be the first comprehensive object-oriented
methodology to unify the concepts of objects, frameworks, and
component technologies.
-- John McGehee, Senior Architect, Texas Instruments Works Project

See all Editorial Reviews

Product Details

• Paperback: 816 pages
• Publisher: Addison-Wesley Professional; 1 edition (October 29, 1998)
• Language: English
• ISBN-10: 0201310120
• ISBN-13: 978-0201310122
• Product Dimensions: 9.2 x 7.4 x 1.6 inches
• Shipping Weight: 2.9 pounds (View shipping rates and policies)
• Average Customer Review: 4.1 out of 5 stars  See all reviews (15 customer reviews)
• Amazon Best Sellers Rank: #1,964,645 in Books (See Top 100 in Books)

More About the Author

Discover books, learn about writers, read author blogs, and more.

Customer Reviews

Most Helpful Customer Reviews

24 of 24 people found the following review helpful:

4.0 out of 5 stars ***** content, *** presentation - Some brilliant stuff here, February 24, 1999

By 

Christopher (Denver, Colorado, USA) - See all my reviews

This review is from: Objects, Components, and Frameworks with UML: The Catalysis(SM) Approach (Paperback)

I have just completed this text, having read every word on every page. Now it is my time to give back to the authors; I take this review quite seriously. First, a little context (which most reviewers feel obliged to omit): I am 23, a consultant, and have designed and coded on 3 major systems (10,000+ lines of code, up to 9 months in duration). I have not yet independently led a project, but I will, this year. So I am ahead of the curve in time, but still young with much to learn.

I have owned this book for approximately 7 weeks. I have given this 800-page book between 1-4 hours of care, 5-6 days a week since its arrival. In total, I would guess 50-60 hours of reading spent (not counting the 80+ hours of spacing out/absorption). I am versed in UML, Design Patterns, OMT, and all major technologies (excluding SmallTalk). This book has just jumped to the top of my all-time-favorites list... and I almost gave up after the 3rd chapter.

These authors have discovered some key insights that will build upon the calculus of software... if the presentation were tighter, the book would be tied with Design Patterns and the UML guides in importance to our community. Put another way: if the book were more of a encyclopedia and roadmap, and less of a dissertation, the authors could have made a heck of a lot more money. But the brilliance of this book's content (read: the great clarity of insight held by its authors) cannot and will not be denied.

Part of the blame for the excessive read-time was mine, part was the editor's. I have read enough books like these to know that most sentences contain pearls of wisdom, not BS. But I found myself stumbling on paragraphs of definition and example that were built on concepts that are quite difficult to absorb. The book contains only a sparse TOC and glossary, so cross-references are between general sections... very tough to get back on your feet if you slip on Catalysis' sometimes-vague, 'concrete-free' content. My recommendation to readers is to just keep on plugging... the authors usually ram a problem from three or four different angles. (My recommendation to the authors is to develop a full Catalysis glossary with every major term and at least one strong supporting example.)

I nearly gave up after chapter 3, after being slammed by Catalysis' version of OCL invariant/constraint rules, which are meant to provide models with precise language (needed badly!). Knowing 4 programming languages didn't help; I hadn't read OCL, so attribute parameters, set notation, strange message syntax, _and_ Catalysis extensions left me bloody. I'm glad I didn't stop reading; the notation in the rest of the book was much more readable after the first battle. But this is the book's most glaring weakness. Catalysis depends on this precision, but there is no good guide for building Catalysis invariants that I can use out in the field (have to use the appendix, the UML OCL spec, and a bunch of bookmarks throughout Catalysis' chapters).

Chapter 6 made the whole book worth reading. Being able to map from a business model to code while not throwing out all efforts from analysis and design phases? I had no idea this was possible before reading about Catalysis refinement. Worth the entire book.

After Chapter 6 and the early precision-syntax wars, I realized how important this book was becoming to me. Chapter 9 tied together packages, patterns, and collaborations into a very strong argument for building frameworks (a method that will be worthwhile for businesses to explore). Chapter 10 on components is brilliant, especially to those who wish there was a cleaner component middleware on the market; here's a good start (I would read a whole book on this if the authors would write it). Having all diagrams based on UML allows you to focus on the methodology and not the tiny details (although the authors really blew it using bold type borders for minor concepts - it overrides an important aspect of UML).

The last four chapters present dozens of Catalysis "business/software patterns" that, although quite helpful, don't really map cleanly to the foundation in the first 12 chapters (and the first 12 chapters never refer to these patterns). This is symptomatic of the book's lack of cross-referencing, and, in fact, symptomatic of a bigger problem... Finishing the book, I realized that I still hadn't been presented with a 'roadmap' of the Catalysis way. How do I explain the system to my boss, and how do I direct the team (other than give them a copy of the book)?

The Catalysis process is not a rigorous methodology, it is a wise man in text form. Pearls abound, but a bit of digging is required. It is a challenge and a reward, just as any good book should be.

This doesn't mean there isn't room for improvement. Given a knife (and a nice advance) I think I could cut Catalysis down to 200 pages of essentials, and if I can do it... A cliff-notes Catalysis would be a roadmap and an encyclopedia. This current Catalysis book can be the bible, but we need the commandments first - Catalysis as-is is not rigorous enough for us to be able to quote chapter and verse in preaching, in practice, and in defense.

I believe that Catalysis being published under the Addison-Wesley series (same cover as UML guides) gives it the exposure it needs, and the fact that a design/development engineer (me) can work through this book proves that this methodology can reach the masses. It deserves to be read. But the process can be slimmed down.

9 of 9 people found the following review helpful:

5.0 out of 5 stars Best Book on UML and Process, May 4, 2001

By 

R. Williams "code slubber" (Los Angeles, CA United States) - See all my reviews
(VINE VOICE)    (REAL NAME)   

This review is from: Objects, Components, and Frameworks with UML: The Catalysis(SM) Approach (Paperback)

IMHO, this one is top of the heap. There are a number of things that set it apart: 1. it is looking at issues that surround the large scale, complex development. When people start to realize that XP doesn't have legs long enough for most projects, this will be a good place for them to turn, 2. A lot of modeling is about structure and these guys talk about structure a lot, and give you lots of ideas about some of the ways structure informs design. For instance, on the component front, they focus on the fact that component architectures are often going to be layered and that the structures are almost fractal. This is one of those books where you realize that they are talking about things that you have often wondered about but never seen covered elsewhere. 3. This books is all about components. XP doesn't even mention components really. Frameworks and components are the future. And not monolithic, swiss army knife components, but interlocking, specifically purposed components.

My minor nits: 1. better and more examples, 2. not very visual. I like really using the visual aspect of UML and getting mileage out of it as a means of making the immensely complex more navigable.

8 of 8 people found the following review helpful:

3.0 out of 5 stars The method is great the book could be improved, September 16, 1999

By 

Daniel Moth (Seattle, WA) - See all my reviews
(REAL NAME)   

This review is from: Objects, Components, and Frameworks with UML: The Catalysis(SM) Approach (Paperback)

Catalysis as a method is very powerful no doubt. Catalysis the book is a different story. I consider myself lucky in the respect that I had a subset of the method taught to me by people that have had some input to the Catalysis method (from University of Brighton, UK). I was also impressed by IS A RUNNING THROUGH EXAMPLE? A case study is desperately needed and it could easily replace some of the other material in the book. I know that if one can apply the techniques described in this book (not necessarily the full set) better more robust software will be the result. It is a shame that you need loads of time to get through the book. Given the choice I would have still bought this book but I believe there is area for improvement in the book not the method. END