Wonder Club world wonders pyramid logo
×

UML Components: A Simple Process for Specifying Component-Based Software Book

UML Components: A Simple Process for Specifying Component-Based Software
UML Components: A Simple Process for Specifying Component-Based Software, 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 impl, UML Components: A Simple Process for Specifying Component-Based Software has a rating of 4.5 stars
   2 Ratings
X
UML Components: A Simple Process for Specifying Component-Based Software, 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 impl, UML Components: A Simple Process for Specifying Component-Based Software
4.5 out of 5 stars based on 2 reviews
5
50 %
4
50 %
3
0 %
2
0 %
1
0 %
Digital Copy
PDF format
1 available   for $99.99
Original Magazine
Physical Format

Sold Out

  • UML Components: A Simple Process for Specifying Component-Based Software
  • Written by author John Cheesman
  • Published by Addison-Wesley, October 2000
  • 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 impl
  • 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 impl
Buy Digital  USD$99.99

WonderClub View Cart Button

WonderClub Add to Inventory Button
WonderClub Add to Wishlist Button
WonderClub Add to Collection Button

Book Categories

Authors

Forewordxi
Prefacexiii
Chapter 1Component Systems1
1.1Component Goals1
1.2Component Principles2
1.3Component Forms4
1.3.1Example: Microsoft Word6
1.3.2What a Component Isn't7
1.4Component and System Architectures9
1.4.1System Architectures10
1.4.2Component Architectures13
1.5Specifying Contracts16
1.5.1Usage Contracts18
1.5.2Realization Contracts20
1.5.3Interfaces versus Component Specifications21
1.6Model Levels22
1.7Summary23
Chapter 2The Development Process25
2.1Workflows26
2.2The Impact of the Management Process28
2.2.1The Evolution of Software Processes28
2.2.2Accommodating Change29
2.3Workflow Artifacts31
2.4The Specification Workflow33
2.4.1Component Identification33
2.4.2Component Interaction35
2.4.3Component Specification35
2.5Summary36
Chapter 3Applying UML37
3.1Why Do We Need This Chapter at All?37
3.1.1Tools38
3.2Extending UML with Stereotypes39
3.3Precision, Accuracy, and Completeness39
3.4UML Modeling Techniques40
3.5Business Concept Model43
3.6Use Case Model44
3.6.1Use Case Diagrams45
3.6.2Use Case Descriptions45
3.6.3Use Case Instances47
3.6.4Inclusions, Extensions, and Variations47
3.7Business Type Model48
3.7.1Types49
3.7.2Structured Data Types51
3.7.3Interface Type52
3.7.4Invariants54
3.8Interface Specification55
3.8.1Interface Specification Package55
3.8.2Information Model57
3.8.3Operation Specification57
3.9Component Specification59
3.9.1Component Object Interaction61
3.9.2Specification, Not Implementation62
3.10Component Architectures63
3.11Summary64
Chapter 4Requirements Definition67
4.1Business Processes68
4.2Business Concept Model69
4.3System Envisioning71
4.4Use Cases71
4.4.1Actors and Roles72
4.4.2Use Case Identification73
4.4.3Use Case Descriptions77
4.4.4Quality of Service80
4.5Summary81
Chapter 5Component Identification83
5.1Identifying Interfaces84
5.2Identifying System Interfaces and Operations86
5.2.1Make a Reservation86
5.2.2Take Up Reservation87
5.3Identifying Business Interfaces88
5.3.1Create the Business Type Model88
5.3.2Refine the Business Type Model89
5.3.3Define Business Rules90
5.3.4Identify Core Types92
5.3.5Create Business Interfaces and Assign Responsibilities92
5.3.6Allocating Responsibility for Associations94
5.4Creating Initial Interface Specifications96
5.5Existing Interfaces and Systems97
5.6Component Specification Architecture98
5.6.1System Component Specifications99
5.6.2Business Component Specifications99
5.6.3An Initial Architecture100
5.7Summary101
Chapter 6Component Interaction103
6.1Discovering Business Operations104
6.1.1Some Simple Interactions106
6.1.2Breaking Dependencies109
6.2Maintaining Referential Integrity112
6.2.1Component Object Architecture112
6.2.2Controlling Intercomponent References113
6.3Completing the Picture115
6.4Refining the Interfaces116
6.4.1Factoring Interfaces and Operations119
6.5Summary119
Chapter 7Component Specification121
7.1Specifying Interfaces121
7.1.1Operation Specification123
7.1.2Interface Information Models123
7.1.3Pre- and Postconditions125
7.2A Systematic Process128
7.2.1From Business Type Model to Interface Information Model129
7.2.2Invariants131
7.2.3Snapshots132
7.2.4Exactly What Does a Postcondition Guarantee?134
7.3Specifying System Interfaces135
7.3.1Business Rule Location136
7.4Specifying Components137
7.4.1Offered and Used Interfaces138
7.4.2Component Interaction Constraints139
7.4.3Inter-Interface Constraints141
7.5Factoring Interfaces142
7.6Summary144
Chapter 8Provisioning and Assembly147
8.1What Do We Mean by Target Technology?147
8.2Components Realize Component Specifications149
8.3Realization Mappings and Restrictions150
8.3.1Operation Parameters150
8.3.2Error and Exception Handling Mechanisms151
8.3.3Interface Inheritance and Interface Support154
8.3.4Operation Sequence155
8.3.5Interface Properties155
8.3.6Object Creation155
8.3.7Raising Events156
8.4Application Architecture Correspondence157
8.4.1Business Components158
8.5Subcomponents160
8.6Integrating Existing Systems162
8.7Purchasing Components163
8.8Assembly164
8.9Summary165
8.10A Final Thought166
References167
Index169


Login

  |  

Complaints

  |  

Blog

  |  

Games

  |  

Digital Media

  |  

Souls

  |  

Obituary

  |  

Contact Us

  |  

FAQ

CAN'T FIND WHAT YOU'RE LOOKING FOR? CLICK HERE!!!

X
WonderClub Home

This item is in your Wish List

UML Components: A Simple Process for Specifying Component-Based Software, 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 impl, UML Components: A Simple Process for Specifying Component-Based Software

X
WonderClub Home

This item is in your Collection

UML Components: A Simple Process for Specifying Component-Based Software, 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 impl, UML Components: A Simple Process for Specifying Component-Based Software

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

X
WonderClub Home

This Item is in Your Inventory

UML Components: A Simple Process for Specifying Component-Based Software, 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 impl, UML Components: A Simple Process for Specifying Component-Based Software

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

WonderClub Home

You must be logged in to review the products

E-mail address:

Password: