Home > Store

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

View Larger Image

Objects, Components, and Frameworks with UML: The Catalysis(SM) Approach
Add To My Wish List

Register your product to gain access to bonus material or receive a coupon.

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

Book

  • Sorry, this book is no longer in print.
Not for Sale

About

Features

  • Shows how to build clear shared business models.
  • Defines essential shared vocabulary in a precise way.
  • Points out critical requirements and design decisions early while abstracting detail.
  • Uses UML as a powerful, unambiguous communication tool between analysts and designers.
  • Makes families of adaptable systems from coherent kits of pluggable components.
  • Assigns interface-centric design and composition to components.
  • Creates robust components, using techniques of precise specification and design.
  • Applies and extracts reusable frameworks for designs, specifications, and architectures.

Description

  • Copyright 1999
  • Dimensions: 7-1/4" x 9-1/4"
  • Pages: 816
  • Edition: 1st
  • Book
  • ISBN-10: 0-201-31012-0
  • ISBN-13: 978-0-201-31012-2

". . . 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

Objects, Components, and Frameworks with UML: The Catalysis Approach is where you will learn 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 you with 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, you 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.

Key Features of Catalysis:

  • Shows how to build clear shared business models
  • Defines essential shared vocabulary in a precise way
  • Points out critical requirements and design decisions early while abstracting detail
  • Uses UML as a powerful, unambiguous communication tool between analysts and designers
  • Makes families of adaptable systems from coherent kits of pluggable components
  • Assigns interface-centric design and composition to components
  • Creates robust components, using techniques of precise specification and design
  • Applies and extracts reusable frameworks for designs, specifications, and architectures

In development and use with the authorsi many clients since 1992, Catalysis has influenced the UML standard and the MicrosoftTI component-definition model as implemented in the Microsoft Repository. Its simple core, on-demand precision, and separation of concerns support component technologies and standards based on Java, CORBA, COM+, and RMODP.



0201310120B04062001

Sample Content

Table of Contents



Preface.

I. OVERVIEW.

1. A Tour of Catalysis.

Objects and Actions.

Refinement: Objects and Actions at Different Scales.

Development Layers.

Business Modeling.

Model Frameworks as Templates.

Zooming In on the Software: System Context.

Requirements Specification Models.

Components.

Assigning Responsibilities.

Object-Oriented Design.

The Development Process.

Three Constructs Plus Frameworks.

Three Levels of Modeling.

Three Principles.

Summary.

II. MODELING WITH OBJECTS.

2. Static Models: Object Attributes and Invariants.

What Is a Static Model?

Object State: Objects and Attributes.

Implementations of Object State.

Modeling Object State: Types, Attributes, and Associations.

Static Invariants.

The Dictionary.

Models of Business; Models of Components.

Static Models: Summary.

3. Behavior Models: Object Types and Operations.

Object Behavior: Objects and Actions.

More Precise Action Specifications.

Two Java Implementations of a Calendar.

Type Specification of Calendar.

Actions with Invariants.

Interpreting an Action Specification.

Subtypes and Type Extension.

Factoring Action Specifications.

State Charts.

Outputs of Actions.

Subjective Model: The Meaning of Containment.

Type Specifications: Summary.

Programming Language: Classes and Types.

4. Interaction Models: Use Cases, Actions, and Collaborations.

Designing Object Collaborations.

Actions (Use Cases) Abstract Complex Interactions.

Use Cases Are Joint Actions.

Actions and Effects.

Concurrent Actions.

Collaborations.

Uses of Collaborations.

Collaboration Specification.

Collaborations: Summary.

5. Effective Documentation.

What’s It All For?

Documentation Is Easy and Fun, and It Speeds Design.

Reaching the Documentation Audience.

The Main Documents: Specification and Implementation.

Documenting Business Models.

Documenting Component Specifications.

Documenting Component Implementations.

Summary.

III. FACTORING MODELS AND DESIGNS.

6. Abstraction, Refinement, and Testing.

Zooming In and Out: Why Abstract and Refine?

Documenting Refinement and Conformance.

Spreadsheet: A Refinement Example.

Spreadsheet: Model Refinement.

Spreadsheet: Action Refinement.

Spreadsheet: Object Refinement.

Spreadsheet: Operation Refinement.

Refinement of State Charts.

Summary.

Process Patterns for Refinement.

Pattern 6.1 The OO Golden Rule (Seamlessness or Continuity).

Pattern 6.2 The Golden Rule versus Other Optimizations.

Pattern 6.3 Orthogonal Abstractions and Refinement.

Pattern 6.4 Refinement Is a Relation, Not a Sequence.

Pattern 6.5 Recursive Refinement.

7. Using Packages.

What Is a Package?

Package Imports.

How to Use Packages and Imports.

Decoupling with Packages.

Nested Packages.

Encapsulation with Packages.

Multiple Imports and Name Conflicts.

Publication, Version Control, and Builds.

Programming Language Packages.

Summary.

8. Composing Models and Specifications.

Sticking Pieces Together.

Joining and Subtyping.

Combining Packages and Their Definitions.

Action Exceptions and Composing Specs.

Summary.

9. Model Frameworks and Template Packages.

Model Framework Overview.

Model Frameworks of Types and Attributes.

Collaboration Frameworks.

Refining Frameworks.

Composing Frameworks.

Templates as Packages of Properties.

Templates for Equality and Copying.

Package Semantics.

Down to Basics with Templates.

Summary of Model Framework Concepts.

IV. IMPLEMENTATION BY ASSEMBLY.

10. Components and Connectors.

Overview of Component-Based Development.

The Evolution of Components.

Building Components with Java.

Components with COM+.

Components with CORBA.

Component Kit: Pluggable Components Library.

Component Architecture.

Defining Cat One-A Component Architecture.

Specifying Cat One Components.

Connecting Cat One Components.

Heterogeneous Components.

Pattern 10.1 Extracting Generic Code Components.

Pattern 10.2 Componentware Management.

Pattern 10.3 Build Models from Frameworks.

Pattern 10.4 Plug Conformance.

Pattern 10.5 Using Legacy or Third-Party Components.

Summary.

11. Reuse and Pluggable Design Frameworks in Code.

Reuse and the Development Process.

Generic Components and Plug-Points.

The Framework Approach to Code Reuse.

Frameworks: Specs to Code.

Basic Plug Technology.

Summary.

Pattern 11.1 Role Delegation.

Pattern 11.2 Pluggable Roles.

12. Architecture.

What Is Architecture?

Why Architect?

Architecture Evaluation with Scenarios.

Architecture Builds on Defined Elements.

Architecture Uses Consistent Patterns.

Application versus Technical Architecture.

Typical Four-Tier Business Architecture.

User Interfaces.

Objects and Databases.

Summary.

V. HOW TO APPLY CATALYSIS.

13. Process Overview.

Model, Design, Implement, and Test-Recursively.

General Notes on the Process.

Typical Project Evolution.

Typical Package Structure.

Main Process Patterns.

Pattern 13.1 Object Development from Scratch.

Pattern 13.2 Reengineering.

Pattern 13.3 Short-Cycle Development.

Pattern 13.4 Parallel Work.

14. How to Build a Business Model.

Business Modeling Process Patterns.

Pattern 14.1 Business Process Improvement.

Pattern 14.2 Make a Business Model.

Pattern 14.3 Represent Business Vocabulary and Rules.

Pattern 14.4 Involve Business Experts.

Pattern 14.5 Creating a Common Business Model.

Pattern 14.6 Choose a Level of Abstraction.

Modeling Patterns.

Pattern 14.7 The Type Model Is a Glossary.

Pattern 14.8 Separation of Concepts: Normalization.

Pattern 14.9 Items and Descriptors.

Pattern 14.10 Generalize and Specialize.

Pattern 14.11 Recursive Composite.

Pattern 14.12 Invariants from Association Loops.

Video Case Study: Abstract Business Model.

Video Business: Use Case Refinement.

Pattern 14.13 Action Reification.

15. How to Specify a Component.

Patterns for Specifying Components.

Pattern 15.1 Specify Components.

Pattern 15.2 Bridge Requirements and Specifications.

Pattern 15.3 Use-Case-Led System Specification.

Pattern 15.4 Recursive Decomposition: Divide and Conquer.

Pattern 15.5 Make a Context Model with Use Cases.

Pattern 15.6 Storyboards.

Pattern 15.7 Construct a System Behavior Spec.

Pattern 15.8 Specifying a System Action.

Pattern 15.9 Using State Charts in System Type Models.

Pattern 15.10 Specify Component Views.

Pattern 15.11 Compose Component Views.

Pattern 15.12 Avoid Miracles, Refine the Spec.

Pattern 15.13 Interpreting Models for Clients.

Video Case Study: System Specifications.

System Context Diagram.

System Specification.

Using Model Frameworks.

16. How to Implement a Component.

Designing to Meet a Specification.

Pattern 16.1 Decoupling.

Pattern 16.2 High-Level Component Design.

Pattern 16.3 Reifying Major Concurrent Use Cases.

Pattern 16.4 Separating Facades.

Pattern 16.5 Platform Independence.

Pattern 16.6 Separate Middleware from Business Components.

Pattern 16.7 Implement Technical Architecture.

Pattern 16.8 Basic Design.

Pattern 16.9 Generalize after Basic Design.

Pattern 16.10 Collaborations and Responsibilities.

Pattern 16.11 Link and Attribute Ownership.

Pattern 16.12 Object Locality and Link Implementation.

Pattern 16.13 Optimization.

Detailed Design Patterns.

Pattern 16.14 Two-Way Link.

Pattern 16.15 Role Decoupling.

Pattern 16.16 Factories.

Pattern 16.17 Observer.

Pattern 16.18 Plug-Points and Plug-Ins.

Video Case Study: Component-Based Design.

Appendix A: Object Constraint Language.
Appendix B: UML Perspective.
Appendix C: Catalysis Support Tools, Services, and Experiences.
Notes.
Glossary.
Index. 0201310120T04062001

Updates

Submit Errata

More Information

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.

Overview


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information


To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.

Surveys

Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.

Newsletters

If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information


Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.

Security


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.

Children


This site is not directed to children under the age of 13.

Marketing


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information


If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.

Choice/Opt-out


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information


Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents


California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure


Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.

Links


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact


Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice


We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020


Other Things You Might Like

Programming: Principles and Practice Using C++

Programming: Principles and Practice Using C++, 3rd Edition

Programming: Principles and Practice Using C++

Programming: Principles and Practice Using C++, 3rd Edition

Object-Oriented Thought Process, The

Object-Oriented Thought Process, The, 5th Edition