Overview

Developers using component technologies such as COM+ and Enterprise JavaBeans need to be able to define and express specifications for their components. They can do so using the Unified Modeling Language (UML), whether or not the components are being implemented internally using object technology. However, they also need a simple process that ensures specifications relate correctly to requirements. Although originally conceived as a notation for object-oriented modeling, UML has great potential for component-based systems. UML Components applies UML to the world of component architecture, demonstrating how it can be used to specify components, their interactions, and their integration into cohesive systems. This book shows readers which elements of UML apply to server-side component-based development and how to use them most effectively. Following a simple step-by-step process, the authors walk through requirements definition, component identification, component interaction, component specification, and provisioning and assembly. Throughout, the focus is on the specification of the external characteristics of components and their inter-dependencies, rather than on internal implementation. Numerous UML diagrams illustrate component specifications, and a detailed case study demonstrates important concepts and techniques. System architects, designers, programmers, and testers interested in leveraging the advantages of UML will find this a concise, practical, and insightful guide. The authors address the two great challenges of designing and constructing enterprise-scale component-based software: finding a process that can support the construction of large component systems, and making the best use of the wide range of notations and techniques found in the UML. 0201708515B04062001

Full Product Details

Author:   John Cheesman ,  John Daniels ,  John Cheesman ,  Clemens Szyperski
Publisher:   Pearson Education (US)
Imprint:   Addison Wesley
Dimensions:   Width: 18.90cm , Height: 1.10cm , Length: 23.40cm
Weight:   0.330kg
ISBN:  

9780201708516

ISBN 10:   0201708515
Pages:   208
Publication Date:   01 November 2000
Audience:   College/higher education ,  Tertiary & Higher Education
Format:   Paperback
Publisher's Status:   Out of Print
Availability:   Awaiting stock  

Table of Contents

Foreword. 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. Summary. 2. The Development Process. Workflows. The Impact of the Management Process. The Evolution of Software Processes. Accommodating Change. Workflow Artifacts. The Specification Workflow. Component Identification. Component Interaction. Component Specification. Summary. 3. Applying UML. Why Do We Need This Chapter at All? Tools. 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. Types. Structured Data Types. Interface Type. Invariants. Interface Specification. Interface Specification Package. Information Model. Operation Specification. Component Specification. Component Object Interaction. Specification, Not Implementation. Component Architectures. Summary. 4. Requirements Definition. Business Processes. Business Concept Model. System Envisioning. Use Cases. Actors and Roles. Use Case Identification. Use Case Descriptions. Quality of Service. Summary. 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. Summary. 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. Summary. 7. Component Specification. Specifying Interfaces. Operation Specification. Interface Information Models. Pre- and Postconditions. A Systematic Process. From Business Type Model to Interface Information Model. Invariants. Snapshots. 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. Summary. 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. Subcomponents. Integrating Existing Systems. Purchasing Components. Assembly. Summary. A Final Thought. References. Index. 0201708515T04062001

Reviews

Author Information

John Cheesman is Director of Enterprise Application Development for ComponentSource. He has extensive experience applying component-based development processes, tools, and standards within large corporations. John specializes in modeling, specification, and repositories, and was a key contributor to the development of the UML. He is a regular speaker at international conferences on component-based development. John Daniels is an independent consultant and trainer. A pioneer of object-oriented concepts and practices, John has applied object and component technology to a wide range of fields during the past fifteen years, from factory automation to banking. He co-developed the Syntropy method, from which the UML Object Constraint Language is directly descended. John is a frequent speaker at international conferences on object technology, components, and development processes, and is co-author of Designing Object Systems: Object-Oriented Modeling with Syntropy (Prentice-Hall, 1994). 0201708515AB04062001

Tab Content 6

Author Website:  

Customer Reviews

Recent Reviews

No review item found!

Add your own review!

Countries Available

All regions