SEARCH
0-9 A B C D E F G H I J K L M N O P Q R S T U V W X Y Z
Prev | Current Page 287 | Next

Michael Bell

"Service-Oriented Modeling (SOA): Service Analysis, Design, and Architecture"

This case is slightly similar to the previous Use Case D, in which an entity swap
is required.
Now, the analysis solution proposition that is depicted in Exhibit 8.8 corresponds to Use
Case E??™s requirements. This Exhibit, however, shows the recommended formal analysis deliverable.
Consider the illustrated five activities by which this mission was accomplished:
1. Composite service CO2 and its component services A3 and A4 were subtracted from
composite service CO1.
2. Atomic services A5 and A6 were decomposed from composite service CO3.
3. Composite service CO3 was transformed to atomic service A-CO3.
4. Atomic services A5, A6, and A-CO3 were unified under the name A-CO3.
5. The final goal has been achieved: Atomic service A-CO3 was aggregated in composite
service CO1.
USE CASE F: REUSABILITY STRATEGY. Exhibit 8.9 represents Use Case F, in which clusters
CL1 and CL2 intersect and the resulting overlapping section encircles composite service CO1.
164 Ch. 8 Service-Oriented Analysis Modeling
CO2
CO3 CO1 A-CO3
A1
A2
A3 A4
A5
A6
1
2 3
4
5
EXHIBIT 8.8 USE CASE E: COMBINED ANALYSIS OPERATIONS
A1
CL1
CL2
CO1 CO2
EXHIBIT 8.9 USE CASE F: REUSABILITY STRATEGY
In addition, Use Case F illustrates the aggregation of two services??”atomic service A1 and
composite service CO2??”into the composite service CO1. Note that since A1 and CO2 are part
of the composite service CO1, they all reside in the intersected sections produced by clusters
CL1 and CL2 as well.


Pages:
275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299