ectory diagram, 346, 347, 349, 350, 357,
358
Transaction model. See Service-oriented transaction
model
Transformed services
and analysis modeling, 152, 156, 161??“163, 166, 167
notation, 157??“159
Typing and profiling
analysis service source type, 116??“119
deliverables, 126??“128
discovery and analysis discipline, 16, 17, 113, 115, 153
goals of service typing and profiling, 115
namespaces, 124, 129
overview, 115
profiling, 124??“126, 129
service context, 121??“124
service structure, 119??“121
service typing, 134
typing, 115??“124
Unification analysis
and analysis modeling, 152, 160, 163, 167
atomic services, 143, 144, 159
discovery and analysis, 134, 143??“145, 153
notation, 158, 159
Universal description discovery and integration (UDDI),
181, 201, 344, 348, 349
Validate, enrich, transform, and operate (VETRO), 181
Van Steen, Maarten, 203
Vertical design approach, 264, 265
Virtualization, 2, 4, 5, 26, 27
Visualization, 2, 5, 10, 22, 25
Von Neumann, John, 320
Waterfall model, 61
Web Service Description Language (WSDL), 294, 295
Web Services Choreography Description Language
(WS-CDL), 247
Web Services Choreography Interface (WSCI), 247
Web Services for Remote Portlets (WSRP), 325
Workflow machine, 322, 323
Workflow styles, 53, 55, 56, 67
Workflows view, 67
Zachman, John, 169, 308, 311
Zachman Framework for Enterprise Architecture, 169
Zuse, Konrad, 320
Pages:
1141
1142
1143
1144
1145
1146
1147
1148
1149
1150
1151
1152
1153