UML Components: A Simple Process for Specifying Component-Based Software (Paperback)

John Cheesman, John Daniels

  • 出版商: Addison Wesley
  • 出版日期: 2000-10-28
  • 售價: $1,560
  • 貴賓價: 9.5$1,482
  • 語言: 英文
  • 頁數: 208
  • 裝訂: Paperback
  • ISBN: 0201708515
  • ISBN-13: 9780201708516
  • 相關分類: UML
  • 立即出貨(限量)







Breakthrough UML 1.3 techniques for defining component architectures and enhancing component development.

  • Start-to-finish processes for enterprise-class component specification and implementation.
  • Using UML notation to create more effective server-side component designs.
  • Includes rules, guidelines, examples, and a detailed case study.

The Unified Modeling Language (UML) has gained acceptance as the de facto standard for modeling object software systems -- and, with this book, UML proves itself as an architectural description language, as well. Leading component developers John Cheesman and John Daniels show how to use UML 1.3 to specify and design any mid-to-large-size system utilizing server-side component technologies -- and, along the way, introduce powerful rules and guidelines for enhancing any component architecture. First and foremost, UML Components focuses on process: design processes for producing large-scale component-based systems that can be implemented through existing project management processes. Second, the book offers detailed, expert techniques for using UML 1.3 notation and diagrams to create component specifications that can support change, by allowing for easy substitution as new business problems and technical opportunities arise. The book includes detailed coverage of the Object Constraint Language, practical techniques for configuring and using UML tools, and a complete, start-to-finish case study.

John Cheesman is Director of Process Architecture for the Sterling Software Application International Group and a Senior Member of Technical Staff on the Sterling Software technical ladder. He was a contributor to the original UML standard. John Daniels is an independent consultant and trainer. He is joint author, with Steve Cook, of Designing Object Systems (Prentice Hall, 1994).

Back to Top


Table Of Contents


Preface. 1. Component Systems.


Component Goals.
Component Principles.
Component Forms.
Example: Microsoft Word.
What a Component Isn't.

Component and System Architectures.
System Architectures.
Component Architectures.

Specifying Contracts.
Usage Contracts.
Realization Contracts.
Interfaces versus Component Specifications.

Model Levels.

2. The Development Process.


The Impact of the Management Process.
The Evolution of Software Processes.
Accommodating Change.

Workflow Artifacts.
The Specification Workflow.
Component Identification.
Component Interaction.
Component Specification.


3. Applying UML.



Why Do We Need This Chapter at All?

Extending UML with Stereotypes.
Precision, Accuracy, and Completeness.
UML Modeling Techniques.
Business Concept Model.
Use Case Model.
Use Case Diagrams.
Use Case Descriptions.
Use Case Instances.
Inclusions, Extensions, and Variations.

Business Type Model.
Structured Data Types.
Interface Type.

Interface Specification.
Interface Specification Package.
Information Model.
Operation Specification.

Component Specification.
Component Object Interaction.
Specification, Not Implementation.

Component Architectures.

4. Requirements Definition.



Business Processes.
Business Concept Model.
System Envisioning.
Use Cases.
Actors and Roles.
Use Case Identification.
Use Case Descriptions.
Quality of Service.


5. Component Identification.



Identifying Interfaces.
Identifying System Interfaces and Operations.
Make a Reservation.
Take Up Reservation.

Identifying Business Interfaces.
Create the Business Type Model.
Refine the Business Type Model.
Define Business Rules.
Identify Core Types.
Create Business Interfaces and Assign Responsibilities.
Allocating Responsibility for Associations.

Creating Initial Interface Specifications.
Existing Interfaces and Systems.
Component Specification Architecture.
System Component Specifications.
Business Component Specifications.
An Initial Architecture.


6. Component Interaction.



Discovering Business Operations.
Some Simple Interactions.
Breaking Dependencies.

Maintaining Referential Integrity.
Component Object Architecture.
Controlling Intercomponent References.

Completing the Picture.
Refining the Interfaces.
Factoring Interfaces and Operations.


7. Component Specification.



Specifying Interfaces.
Operation Specification.
Interface Information Models.
Pre- and Postconditions.

A Systematic Process.
From Business Type Model to Interface Information Model.
Exactly What Does a Postcondition Guarantee?

Specifying System Interfaces.
Business Rule Location.

Specifying Components.
Offered and Used Interfaces.
Component Interaction Constraints.
Inter-Interface Constraints.

Factoring Interfaces.

8. Provisioning and Assembly.



What Do We Mean by Target Technology?
Components Realize Component Specifications.
Realization Mappings and Restrictions.
Operation Parameters.
Error and Exception Handling Mechanisms.
Interface Inheritance and Interface Support.
Operation Sequence.
Interface Properties.
Object Creation.
Raising Events.

Application Architecture Correspondence.
Business Components.

Integrating Existing Systems.
Purchasing Components.
A Final Thought.

Index. 0201708515T04062001

Back to Top