View
214
Download
0
Category
Preview:
Citation preview
Index
393
A2A securityin B2B, 205, 350in mobile integration, 210, 354
Abstracts in use cases, 321Access
in data integration, 224, 362in metadata repository, 229, 368
Accounts, user, 108, 308Accounts receivable service, 129Actors in use case diagrams,
320–321Adapters
Current EnvironmentAssessment Specification,81, 287
purpose of, 190, 191Technical Integration
Architecture Specification,94, 298
Address changesonline, 152, 327retail bank strategy for, 42–43
Aggregation, 149–152Agility
composite applicationintegration for, 234
importance of, 233as requirement, 9–12in service-oriented architecture,
119Analyst usability requirements, 304APIs (application programming
interfaces), 190Application integration
Application IntegrationImplementationSpecification, 339
conclusions, 210, 355introduction, 195, 342
key participants, 195, 342patterns and services,
195–208, 342–355references, 355scope, 195, 342table of contents, 341template instructions, 340
best practices, 211overview, 185–186scenarios, 186technologies, 187–194
Application interfacesapplication integration, 190–191Application Integration
ImplementationSpecification
B2B, 205, 350ESB, 200, 345message brokers, 198, 344mobile integration, 210, 354portal integration, 207, 352
Business Integration StrategySpecification, 54, 280
Current EnvironmentAssessment Specification,82–83, 288
Process IntegrationImplementationSpecification
BAM, 255, 384process automation, 253, 382
Technical IntegrationArchitecture Specification,100, 302
Application platforms incomposite applicationintegration, 237
Application programminginterfaces (APIs), 190
30795 27 IDX pp. 393-410 r2.ps 6/25/04 2:16 PM Page 393
Application serversApplication Integration
ImplementationSpecification, 207, 352
Current EnvironmentAssessment Specification,81, 287
Architecturebusiness case for strategic
approach, 67–68business process integration, 71conclusion, 73current. See Current
environment assessmentgovernance, 72importance, 13information. See Information
integration architectureorganizational structure, 71overview, 65–67priority-setting, 72–73process. See Process integration
architectureservice. See Service integration
architecturetechnical. See Technical inte-
gration architectureAssessment. See Current
environment assessmentAssociations in use case diagrams,
320Auditing
Current EnvironmentAssessment Specification,85, 290
Technical IntegrationArchitecture Specification,109–110, 309
AuthenticationCurrent Environment
Assessment Specification,85, 290
Technical IntegrationArchitecture Specification,108, 307–308
AuthorizationCurrent Environment
Assessment Specification,85, 290
Technical IntegrationArchitecture Specification,109, 308
Automationcost reductions from, 12process integration
architecture, 167Process Integration
ImplementationSpecification, 251–253,381–382
Availabilityservice integration architecture,
120Technical Integration
Architecture Specificationcapacity planning view, 112,
310service-level requirements,
102, 107, 302, 306
B2B integrationapplication integration,
192–194Application Integration
ImplementationSpecification, 202–205,348–350
Current EnvironmentAssessment Specification,81, 288
northAmerican Logistics, 193Technical Integration
Architecture Specification,96, 297, 300
Back-end application integrationB2B, 205, 350mobile integration, 210, 354portal integration, 207, 352
Backend references in use cases,321
Balanced scorecards, 8, 20, 162,164
Baldrige Award, 164BAM (Business Activity
Monitoring)future of, 47process automation, 253,
382–384
process-driven integration,248–249, 252–255
process integrationarchitecture, 168
Banksaddress change strategy,
42–43financial services company, 68
Basic metadata, 154, 329Berglund, Anders, 141Berners-Lee, Tim, 141Best practices
application integration, 211assessment, 86business drivers and
requirements, 34composite application
integration, 240–241information integration,
229–230information integration
architecture, 156–157overview, 261–263process-driven integration,
46–47process integration
architecture, 178–179process integration technology,
257–258service integration architecture,
134–135SOA, 45–46technical integration
architecture, 113Bibliography, 387–392BODS (Business Object
Documents), 148Bottom-up approach to services,
121BPA (Business Process
Automation), 167BPEL (business process
execution language),55, 247
BPEL4WS (Business ProcessExecution Language forWeb Services), 170
BPI (Business ProcessIntegration), 166–167
394 Index
30795 27 IDX pp. 393-410 r2.ps 6/25/04 2:16 PM Page 394
BPM (Business ProcessManagement)
Current EnvironmentAssessment Specification,82, 288
process integrationarchitecture, 165–166
process integration technology,247
solutions, 47BPMI (Business Process
Management Initiative),170–171, 175
BPR (Business ProcessReengineering), 20, 162,243
Brilliantly simple solution,135–136
Broker/enterprise service busB2B, 205, 350mobile integration, 210, 354
Brokersapplication integration,
188–190Application Integration
ImplementationSpecification, 196–198,343
Current EnvironmentAssessment Specification,81, 287
Browsersas access standard, 41mobile integration for, 208
Bug fixing in service-orientedarchitecture, 120
Building permits, 235Business Activity Monitoring
(BAM)future of, 47process automation, 253,
382–384process-driven integration,
248–249, 252–255process integration
architecture, 168Business case for strategic
enterprise approach,67–68
Business costs, Business Driversand RequirementsSpecification, 272–273
Business drivers and requirementsbest practices, 34Business Drivers and
RequirementsSpecification, 27–28,267
conclusions, 33, 274cost estimates, 29, 31,
271–272introduction, 28, 270key participants, 28, 270metrics, 31, 33, 273references, 274risks, 31, 33, 274ROI, 30, 32, 272scope, 28, 270statement of purpose, 28–30,
270–271table of contents, 269template instructions, 268
customer satisfaction, 22–24efficiency and competitiveness,
21–22mergers and acquisitions, 24overview, 19–20Process Integration
Architecture Specification,172
regulatory compliance, 24–26requirements defining, 27
Business eventsDelta Airlines, 125service integration architecture,
123Service Integration
Architecture Specification,124–126, 316–317
Defining business events,122–124
Business goalsBusiness Drivers and
RequirementsSpecification, 271
Process IntegrationArchitecture Specification,172
Business imperative for enterpriseintegration
agility, 9–12business changes, 4
customer interaction, 4–5management, 8manufacturing, 5operations, 7–9organization, 8real time operations, 5–7
challenges, 16overview, 3–4ROI, 12–15
Business initiatives, 172Business integration strategy
architectural best practices,45–47
Business Drivers andRequirementsSpecification, 30
Business Integration StrategySpecification, 48, 275
conclusions, 58–59, 282introduction, 48–49, 278key participants, 49–51,
278mapping to business
strategies and initiatives,51–52, 279
metrics, 56–57, 281references, 282risks, 57–58, 282scope, 49, 278standards, 53–56, 280strategic sourcing, 52–53,
279–280strategies, 51–52, 278table of contents, 277template instructions, 276
failures in, 40–42overview, 37–40Process Integration
Architecture Specification,172
requirements, 6–7, 9success in, 42–45time for, 47–48
Business intelligence in BAM, 255,384
Index 395
30795 27 IDX pp. 393-410 r2.ps 6/25/04 2:16 PM Page 395
Business Object Documents(BODS), 148
Business Process Automation(BPA), 167
Business process executionlanguage (BPEL), 55,247
Business Process ExecutionLanguage for Web Services(BPEL4WS), 170
Business Process Integration(BPI), 166–167
Business Process Management(BPM)
Current EnvironmentAssessment Specification,82, 288
process integrationarchitecture, 165–166
process integration technology,247
solutions, 47Business Process Management
Initiative (BPMI),170–171, 175
Business process reengineering(BPR), 20, 162, 243
Business processesdescriptions, 172–173, 336integration. See Process
integration architecture;Process integrationimplementation
modeling, 247in ROI, 15
Business rulesBAM, 168Information Integration
Architecture Specification,155, 330
process flow models, 173–174
Caching in data integration, 222Calendars, 257, 386Call centers, 152, 327Canonical format
information integrationarchitecture, 139–140,148
Information IntegrationArchitecture Specification,154–255, 330
metadata repository, 229, 368Capacity planning view, 111–113,
309–310Case studies
as integration arguments,265
use cases, 131–132, 320–321Causes of variation in processes,
161Centers of excellence, 229
Also see Competency centerCentral Data Exchange initiative,
25Central Hudson Gas & Electric
Corp., message brokers at,188
Challenges of enterpriseintegration, 16
Change of addressInformation Integration
Architecture Specification,152, 327
retail bank, 42–43Changes, 4
application integration, 211costs, 14customer interaction, 4–5management, 8manufacturing, 5operations, 7–9organization, 8real time operations, 5–7strategy, 44
Check in/check out, 254CIS (customer information
system), 189Cisco Systems real time
operations, 5–7Clients in service-oriented
architecture, 120Cockpits, digital, 8
Also see dashboardsCollaborative Partner Profile
Agreement, 147Collaborative process integration,
249, 254–257, 384–386
Common Warehouse MetaModel(CWM), 147–148
Communication protocolsBusiness Integration Strategy
Specification, 54, 280Technical Integration
Architecture Specification,100, 302
Communications sessions,nonrepudiated,110–111
Competency centershigh-level sponsorship
for, 71information integration
architecture, 156for strategy development, 48,
50Competitiveness, business drivers
for, 21–22Completion points in process
flow models, 174Complexity of integration, 262Compliance and process
integration, 244, 246Components of integration,
69–71Composite application
integrationbest practices, 240–241Composite Application
IntegrationImplementationSpecification, 371
conclusions, 240, 376introduction, 238, 374key participants, 238, 374patterns and services,
239–240, 374–376references, 376scope, 238, 374table of contents, 373template instructions,
372Miami-Dade County,
235–236overview, 233–235vs. process integration, 244scenarios, 236–237
396 Index
30795 27 IDX pp. 393-410 r2.ps 6/25/04 2:16 PM Page 396
Technical IntegrationArchitecture Specification,94–95, 297
technology, 237–240CompuCredit integration
strategy, 39–40,217–218
Conceptual views, 96–98, 300Confidentiality
Current EnvironmentAssessment Specification,85, 290
Technical IntegrationArchitecture Specification,110, 309
Connected applications, 112,304, 310
Connectivityapplication integration, 187B2B, 205, 350Technical Integration
Architecture Specification,94, 298
wireless, 208Consulting costs, 31, 272Content integration tools,
81, 287Content objects in unstructured
content, 226, 365Coordination
collaborative processintegration, 255
Web services, 168–169CORBA, 118Costco process improvements,
178–179Costs
Business Drivers andRequirementsSpecification, 29, 31,271–272
in ROI, 12–14Credit check service, 129Criminal history system,
65–67CriMNet system, 65–67CRM (Customer Relationship
Management) systems,15, 22, 233
Cultural issuesBusiness Drivers and
RequirementsSpecification, 274
Business Integration StrategySpecification, 282
Culture of reuse, 265Current environment assessment
best practices andrecommendations, 86
Current EnvironmentAssessment Specification,283
application and data sourceinterfaces, 82–83, 288
conclusions, 86, 291integration diagrams, 83–84,
288integration matrix, 83, 288integration technologies,
80–82, 286–288introduction, 79, 286key participants, 80, 286purpose, 79, 286references, 291scope, 80, 286security, 85–86, 288–290table of contents, 285template instructions,
284overview, 75technology, 76–79
Custom integration, 82, 288Customer information system
(CIS), 189Customer management service,
129Customer Relationship
Management (CRM)systems, 15, 22, 233
Customerschange of address
Information IntegrationArchitecture Specification,152, 327
retail bank, 42–43customer satisfaction
improving, 22–24in ROI, 14–15
financing applications, 166Information Integration
ImplementationSpecification, 221
integration requirements, 297interaction with, 4–5record maintenance service,
129service and support systems
Central Hudson Gas &Electric Corp., 188
information integrationpatterns table, 152
Vanguard Group, 135–136Technical Integration
Architecture Specification,307
CWM (Common WarehouseMetaModel), 147–148
DashboardsBAM, 252, 255, 384General Electric, 160process improvement, 163process integration, 258
Data cleansing, 221, 223–224, 363Data flow diagrams (DFDs)
Information IntegrationArchitecture Specification,151–153, 327–328
Process IntegrationArchitecture Specification,174, 337
Data integration, 220–224,362–363
Data Integration tool, 362Data quality, 229–230Data source access, 224, 362Data source interfaces, 82–83, 288Data tools, 81, 287Data transformation. See
Translation andtransformation
Data values in metadata, 144Data warehouses, 221Database interfaces in legacy
integration, 200, 203, 346DCE (Distributed Computing
Environment), 80, 118
Index 397
30795 27 IDX pp. 393-410 r2.ps 6/25/04 2:16 PM Page 397
Decision points in process flowmodels, 174
Decision support systems, 221Defining services, 121–122Delivery service, 102, 107,
302–303Dell Inc. manufacturing
process, 5Delta Airlines business events
management, 125Delta Nervous System (DNS), 125Deming, W. Edward
process improvementinitiatives by, 161–162
TQM by, 164Deming Prize, 161Dependencies in use cases, 321Deployment in Composite
Application IntegrationImplementationSpecification, 240, 376
DescriptionsProcess Integration
Architecture Specification,172–173, 336
Service IntegrationArchitecture Specification,128, 318
Design constraints and guidance,113, 311
Design patterns, 151Design reviews, 176, 337Designers and developers
usability requirements,304
Developmentin BAM, 252, 255, 384Business Drivers and
RequirementsSpecification, 31, 272
Composite ApplicationIntegrationImplementationSpecification, 240, 376
in service-orientedarchitecture, 120
Technical IntegrationArchitecture Specification,96–97, 100, 301
DFDs (data flow diagrams)Information Integration
Architecture Specification,151–153, 327–328
Process IntegrationArchitecture Specification,174, 176, 337
DICI (District Attorney andCourts Interface), 24
Digital cockpits, 8Digital dashboards
BAM, 252, 255, 384General Electric, 160process improvement, 163process integration, 258
Directory services, 105–107, 112,305–306, 310
Discussion management, 257, 386Distributed Computing
Environment (DCE), 80,118
Distributed transactionmanagement, 221
District Attorney and CourtsInterface (DICI), 24
DNS (Delta Nervous System), 125Document type definitions
(DTDs), 142Drivers. See Business drivers and
requirementsDTDs (document type
definitions), 142
E-buy, e-make, e-sell strategy,160
E-government initiatives, 235E-mail
collaborative processintegration, 255,257, 386
mobile integration for, 208E-Permitting, 235E-R (Entity-Relationship)
diagrams, 143e-ROSI system, 23EAI (enterprise application
integration), 38, 139benefits, 54–55for latency, 214
ebXML (Electronic BusinessExtensible MarkupLanguage), 147
Eclipse framework, 174ECM (enterprise content
management), 215, 218,223, 226, 365
EDI (Electronic DataInterchange) standard,25, 193
Effectiveness measurements,43, 164
Efficiencybusiness drivers for, 21–22measuring, 164
EHS (Electronic HardwareServices) division,178–179
EII (Enterprise informationintegration) technology
Application IntegrationImplementationSpecification, 207, 352
information integration, 214,217
information integrationarchitecture, 150
Information IntegrationImplementationSpecification, 220–221,224, 362
Electronic Business ExtensibleMarkup Language(ebXML), 147
Electronic Data Interchange(EDI) standard, 25, 193
Electronic exchange for B2B, 203Electronic Hardware Services
(EHS) division, 178–179Email
collaborative processintegration, 255, 257, 386
mobile integration for, 208EMRs (enterprise metadata
repositories)CompuCredit, 217–218Information Integration
ImplementationSpecification, 229
398 Index
30795 27 IDX pp. 393-410 r2.ps 6/25/04 2:16 PM Page 398
Enterprise application integration(EAI), 38, 139
benefits, 54–55for latency, 214
Enterprise content management(ECM), 215, 218, 223, 226,365
Enterprise informationintegration (EII)
Application IntegrationImplementationSpecification, 207, 352
information integration, 214,217
information integrationarchitecture, 150
Information IntegrationImplementationSpecification, 220–221,224, 362
Enterprise metadata repositories(EMRs)
CompuCredit, 217–218Information Integration
ImplementationSpecification, 229
Enterprise Resource Planning(ERP) packages, 80
Enterprise Service Buses (ESBs)application integration,
188–190Application Integration
ImplementationSpecification, 197–200,344–345
Current EnvironmentAssessment Specification,81, 287
EntireX system, 23Entity-Relationship (E-R)
diagrams, 143ERP (Enterprise Resource
Planning) packages, 80Error rate reductions, 14ESBs (Enterprise Service Buses)
application integration,188–190
Application IntegrationImplementation
Specification, 197–200,344–345
Current EnvironmentAssessment Specification,81, 287
Ethernet as network standard, 41ETL (extract, transform, and
load) toolsin information integration,
214, 217in Information Integration
ImplementationSpecification, 220–221
EventsBAM, 255, 384Delta Airlines, 125defining business events p. 122-
124service integration architecture,
122–123Service Integration
Architecture Specification,124–126, 316–317
Expertise for integration, 13Extensible Business Reporting
Language (XBRL), 25, 142Extensible Markup Language. See
XML (Extensible MarkupLanguage)
Extensions in use cases, 321Extract, transform, and load
(ETL) toolsin information integration,
214, 217in Information Integration
ImplementationSpecification, 220–221
Failures, strategy, 40–42FedEx field force, 9Finance industry trades, 26Financial services
Cisco Systems, 5–7CompuCredit, 39–40KeyCorp, 68
Flexibility, process integration for,245
Florida state government, 89–90Flow models, 173–177, 337
Format rendering in metadatarepository, 229
Four Layer MetadataArchitecture, 144, 150
Fully integrated enterprises,reference architecture for,263–264
Functional scopeBusiness Drivers and
RequirementsSpecification, 29–30, 271
Process IntegrationArchitecture Specification,172
Functionally independentservices, 240
Functions in process flow models,174
General Electric Companymonitoring by, 8process improvement at, 160Six Sigma for, 19
General Motors Corporationdesign process, 5, 19, 21–22process improvement at, 166strategy by, 44–45
General scenarios in use cases,321
Generalized Markup Language,141
GoalsBusiness Drivers and
RequirementsSpecification, 29, 271
Process IntegrationArchitecture Specification,172
in use cases, 321Gold standards in Information
Integration, 230Goldfarb, Charles, 141Governance, architecture, 72Government organizations
composite applicationintegration, 235–236
customer satisfaction in, 23–24online bill access in, 219technical integration, 89–90
Index 399
30795 27 IDX pp. 393-410 r2.ps 6/25/04 2:16 PM Page 399
Granularity, 126, 317Groupware, 249
Hammer, Michael, 162Hardware costs, 31, 272Health Insurance Portability and
Accountability Act(HIPAA), 24, 26
Heraclitus on change, 4High-level organizational
structure and support,134
HTML as access standard, 41Hubs, message brokers for, 196,
343
IDEF in process flow models, 174,177, 337
IDEF0 (Integration Definition forFunction Modeling), 171
IDL (interface definitionlanguage) interfaces, 144
Inconsistencies in informationintegration, 214
Indexing in data integration,222
Industry compliance, 25–26Industry-specific processes, 246Information and content
integration tools, 81,287
Information design reviews,155–156, 330–331
Information integrationbest practices, 229–230Information Integration
ImplementationSpecification, 357
conclusions, 277, 368introduction, 219, 360key participants, 220, 360patterns and services,
220–229, 360–368references, 369scope, 219, 360table of contents, 359template instructions, 358
overview, 213–215scenarios, 215–216
Technical IntegrationArchitecture Specification,94–95, 297, 299
technology, 216–219Information integration
architecture, 70best practices, 156–157enterprise information
integration technology,150
Information IntegrationArchitecture Specification,323
conclusions, 156, 331data flow diagrams, 151–153,
327–328information design reviews,
155–156, 330–331introduction, 150, 326key participants, 151, 326mapping requirements, 151,
326metadata model, 152–154,
328references, 331relationship model, 154–155,
329–330scope, 151, 326table of contents, 325template instructions, 324
metadata, 142–143architecture, 143–145standards, 145–149
overview, 139–140patterns, 149XML, 141–142
Inputs in Service IntegrationArchitecture Specification,130, 319
Integration Definition forFunction Modeling(IDEF0), 171
Integration definition tools, 100,301
Integration diagrams, 83–84, 288Integration hubs, 196, 343Integration matrix, 83, 288Integration Metadata Model,
154
Integration support tools, 100,301
Integration technologiescurrent environment
assessment, 76–79Current Environment
Assessment Specification,80–82, 286–288
Integrity and delivery service, 102,107, 302–303, 306
Integrity rules, 155, 330Interaction, customer, 4–5Interface definition language
(IDL) interfaces, 144Interfaces
application. See Applicationinterfaces
Current EnvironmentAssessment Specification,81, 287
service, 201–203, 240, 346,376
Technical IntegrationArchitecture Specification,94, 298
Internal data and processes,94, 307
Inventory managementService Integration
Architecture Specification,129
supply chain in, 163ISO 9001 measurements, 162,
164–165
J2EE technology, 118Java Connector Architecture
(JCA), 55, 188, 191
Key participantsApplication Integration
ImplementationSpecification, 195, 342
Business Drivers andRequirementsSpecification, 28, 270
Business IntegrationStrategy Specification,49–51, 278
400 Index
30795 27 IDX pp. 393-410 r2.ps 6/25/04 2:16 PM Page 400
Composite ApplicationIntegrationImplementationSpecification, 238, 374
Current EnvironmentAssessment Specification,80, 286
Information IntegrationArchitecture Specification,151, 326
Information IntegrationImplementationSpecification, 220, 360
Process IntegrationArchitecture Specification,171, 336
Process IntegrationImplementationSpecification, 250, 380
Service IntegrationArchitecture Specification,124, 316
Technical IntegrationArchitecture Specification,92, 296
Key performance indicators(KPIs), 20, 31
Key Total Treasury application, 68KeyCorp integration approach,
67–68KeyServer integration platform,
68Kickoff events, 174KPIs (key performance
indicators), 20, 31
Lag time reductions, automationfor, 167
Language support, 100, 301Latencies, 214LAWS (Legislative Automated
Work Station) system, 219Legacy integration
application integration, 191Application Integration
ImplementationSpecification, 199, 347
B2B, 205, 350mobile integration, 210, 354
portal integration, 207, 352types of legacy integration,
200-201Technical Integration
Architecture Specification,94, 297
Legacy wrapping, 201–202Legislation access, 219Legislative Automated Work
Station (LAWS) system,219
Levels of authentication, 108Levi Strauss & Co. supply chain,
163Logins in authentication, 108, 308Logistics processes at General
Motors, 166
Maintainability, 103, 107, 303, 306Manageability, 103, 107, 303, 306Management
Business Drivers andRequirementsSpecification, 274
Business Integration StrategySpecification, 282
changes in, 8Information Integration
Architecture Specification,154, 329
Process IntegrationImplementationSpecification, 253, 382
support from, 265Management costs, 272Management dashboards
BAM, 252, 255, 384Information Integration
Architecture Specification,152, 327
process integration, 258Manual processes, 248Manufacturing changes, 5Margin improvement, process
improvement for, 166Markup languages, 141–142MDA (Model Driven
Architecture), 98, 101,144, 170
Measurementseffectiveness, 43, 164performance, 162, 258success, 164–165
Mergers and acquisitions, 24Message broker/enterprise service
bus, 207, 352Message brokers
application integration,188–190
Application IntegrationImplementationSpecification, 196–198,343–344
Message formatsBusiness Integration Strategy
Specification, 54, 280Technical Integration
Architecture Specification,100, 302
Messagingapplication integration, 187Composite Application
IntegrationImplementationSpecification, 240, 376
Current EnvironmentAssessment Specification,81, 287
legacy integration, 200, 203,346
process flow models, 174Technical Integration
Architecture Specification,94, 298
Meta-metamodel layer, 144Meta Object Facility (MOF), 144Metadata, 142–143
architecture, 143–145Business Integration Strategy
Specification, 54, 56, 280importance of, 140information integration, 214Information Integration
Architecture Specification,154, 157, 329
Information IntegrationImplementationSpecification, 226, 365
Index 401
30795 27 IDX pp. 393-410 r2.ps 6/25/04 2:16 PM Page 401
Metadata (cont.)standards, 145–149Technical Integration
Architecture Specification,100, 302
Metadata model, 143, 152–154,328–329
Metadata repositoriesCompuCredit, 217–218data integration, 224, 362ECM, 218Information Integration
Architecture, 156Information Integration
ImplementationSpecification, 223,225–229, 366–368
Metamodel layer, 144Methods in Service Integration
Architecture Specification,130, 319
MetricsAlso see MeasurementsBusiness Drivers and
RequirementsSpecification, 31, 33, 273
Business Integration StrategySpecification, 43, 56–57,281
Miami-Dade County, 235–236Middleware integration, 253, 382Middleware technologies
Current EnvironmentAssessment Specification,82, 288
Technical IntegrationArchitecture Specification,111
Minnesota government, CriMNetsystem, 65–67
Mobile integrationapplication integration, 192Application Integration
ImplementationSpecification, 207–210,352–354
Technical IntegrationArchitecture Specification,96, 300
Model Driven Architecture(MDA), 98, 101, 144, 170
ModelingBAM, 252, 384process automation, 253, 382
MOF (Meta Object Facility), 144Monitoring
digital cockpits for, 8Process Integration
ImplementationSpecification, 382–383
Multiple clients in service-oriented architecture, 120
Multiple process types, 249Multiple-step publishing, 149Multiple transactions, non-
repudiated actions in, 111
nAL (northAmerican Logistics),193
.NET technology, 118Nextel International, 245Non-repudiation
Current EnvironmentAssessment Specification,85, 290
Technical IntegrationArchitecture Specification,110–111, 309
North Dakota government onlinebill access, 219
northAmerican Logistics(nAL), 193
Notes in use cases, 321
OAG (Open Applications Group),147–148
OASIS (Organization for theAdvancement ofStructured InformationStandards), 146–147
Object Management Group(OMG)
CORBA, 118Four Layer Metadata
Architecture, 150MDA standards, 101for metadata, 144, 147–148UML by, 170
One-to-many publishing, 149One-to-one publishing, 149Online systems
building permits, 235customer support
change of address, 152, 327ordering, 173
legislation access, 219Ontology, 145Open Applications Group (OAG),
147–148Open interfaces, 100, 301Open Software Foundation
(OSF), 118Open Systems Interconnect (OSI)
Reference Model, 118Operational managers usability
requirements, 304Operations changes, 7–9Optimizations
cost reductions from, 14in real time, 5process optimization, 159
Orchestration, 238, 240, 376Order in process flow models,
174Order management service,
129Organization for the
Advancement ofStructured InformationStandards (OASIS),146–147
Organizational issuesBusiness Drivers and
RequirementsSpecification, 271, 274
Business Integration StrategySpecification, 282
changes, 8in integration, 13Process Integration
Architecture Specification,172
Organizational structure, 71OSF (Open Software
Foundation), 118OSI (Open Systems Interconnect)
Reference Model, 118
402 Index
30795 27 IDX pp. 393-410 r2.ps 6/25/04 2:16 PM Page 402
Outputs in Service IntegrationArchitecture Specification,130, 319
OWL (Web Ontology Language),146
Packaged application integration,81, 287
Parallel development, 120Partners
B2B, 205, 348, 350Technical Integration Archi-
tecture Specification, 297,307
Patterns and servicesApplication Integration
ImplementationSpecification, 195–208,342–355
Composite ApplicationIntegration Imple-mentation Specification,239–240, 374–376
information integrationarchitecture, 149
Information IntegrationImplementationSpecification, 220–229,360–368
Process Integration Imple-mentation Specification,250–257, 380
PerformanceKPIs, 20, 31measuring, 162, 258Technical Integration
Architecture Specification,104–105, 107, 304, 306
Perimeter security, 109, 308Persistence, 105, 107, 112,
305–306, 310Personnel costs, 272PIDX (Petroleum Industry Data
Exchange), 25Plan-Do-Check-Act cycle, 162Platforms
application, 194composite application
integration, 237
Process IntegrationImplementationSpecification, 257, 386
Point solution technology, 82, 288Portals
application integration,191–192
Application IntegrationImplementationSpecification, 206–207,351–352
Composite ApplicationIntegrationImplementationSpecification, 240, 376
Current EnvironmentAssessment Specification,81, 287
Process IntegrationImplementationSpecification, 257, 386
Technical IntegrationArchitecture Specification,94–95, 297, 299
Preconditions in use cases, 321Preferred vendors
Business Integration StrategySpecification, 53, 280
Technical IntegrationArchitecture Specification,93–94, 297–298
Primary actors in use cases, 321Priority-setting, 72–73Proactive management, 46Process improvements
at General Motors, 166for margin improvement, 166in process integration, 246in ROI, 15
Process integration architecture,159–161
benefits, 161–162, 165–166best practices, 178–179business activity monitoring,
168Process Integration Architec-
ture Specification, 333business process
descriptions, 172–173, 336
conclusions, 176, 337introduction, 171, 336key participants, 171, 336process design reviews, 176,
337process flow models,
173–176, 337references, 337scope, 171, 336table of contents, 335template instructions, 334
standards, 169–171technology, 165–169
Process integrationimplementation
best practices, 257–258vs. composite integration,
244Information Integration
ImplementationSpecification, 226, 365
Nextel International, 245overview, 243–244Process Integration
ImplementationSpecification, 377
conclusions, 257, 386introduction, 250, 380key participants, 250, 380patterns and services,
250–257, 380references, 386scope, 250, 380table of contents, 379template instructions, 378
scenarios, 246in strategy, 44, 46–47Technical Integration
Architecture Specification,94, 96, 297, 300
technology, 247–249Process models
Business Integration StrategySpecification, 54, 280
Technical Integration Archi-tecture Specification, 100,302
BPMI, 175IDEF, 177
Index 403
30795 27 IDX pp. 393-410 r2.ps 6/25/04 2:16 PM Page 403
Process models (cont.)UML Activity Diagram, 175UML Sequence Diagram, 176
Process repositories, 251–253, 382Process simulation, 21Procurement process, 53, 280Project management
Business Drivers andRequirementsSpecification, 31, 272
Process IntegrationImplementationSpecification, 255, 257,386
Project repositories, 257, 386Property tax information,
235–236Proprietary technology, 40, 262Publishing, 149Purpose in Current Environment
Assessment Specification,79, 286
Quality measurements, 164Queries in Information
IntegrationImplementationSpecification
data integration, 224, 362metadata repository, 229, 368unstructured content
integration, 226, 365
RDF (Resource DescriptionFramework), 146
Real-time managementdashboards, 258
Real time operations, 5–7BAM, 221General Electric, 160Wal-Mart, 10–11
Redundancyin application integration, 211in integration strategy, 44in TCO, 262
Reference Architecture, 263–264Registration, student, 121Regulatory compliance, 24–26Reiner, Gary, 160
Relationship model, 154–155,329–330
Rendering, 223, 226, 229,365, 368
Replicationdata integration, 224, 363metadata repository, 229, 368
Repositoriescollaborative process
integration, 257, 386competency center, 156metadata. See Metadata
repositoriesprocess, 251–253, 382
Requirementsdefining, 27integration strategy, 44in use cases, 321
Research Information ExchangeMarkup Language(RIXML), 25
Resource Description Framework(RDF), 146
Response time, 112, 304, 310Retail bank, address change
strategy by, 42–43Return on assets, 262–263Return on investment. See ROI
(return on investment)Reuse
application integration, 211in best practices, 265composite application
integration, 234, 240–241in integration strategy, 44process integration, 258
RevenuesBusiness Drivers and
RequirementsSpecification, 273
in ROI, 14Rewards in process integration,
258Risks
Business Drivers andRequirementsSpecification, 31, 33, 274
Business Integration StrategySpecification, 57–58, 282
RIXML (Research InformationExchange MarkupLanguage), 25
Road maps in strategy, 43ROI (return on investment), 12
Business Drivers andRequirementsSpecification, 30,32, 272
business process improvementsin, 15
cost reductions in, 12–14customer satisfaction in,
14–15in process improvements,
19–20revenue increases in, 14in service-oriented
architecture, 119ROI Analysis Template, 32Roles
Process IntegrationImplementationSpecification, 385
Technical IntegrationArchitecture Specification,108, 307
RosettaNet transactions, 12–14Ross, Douglas T., 171Routing
B2B, 205, 350mobile integration, 210, 354Technical Integration
Architecture Specification,94, 298
RulesBAM, 168Information Integration
Architecture Specification,155, 330
process automation, 253, 382process flow models, 173–174
Rules engines in processintegration, 247–248
Saatchi, Guido, 39–40Sacramento County government,
23–24Sarbanes-Oxley Act, 24, 246
404 Index
30795 27 IDX pp. 393-410 r2.ps 6/25/04 2:16 PM Page 404
Scalabilityservice integration architecture,
120Technical Integration
Architecture Specification,303, 306
Scheduling, 102–103, 107, 257,386
Schulte, Roy, 122–123Screen references in use cases, 321Screen/report interfaces, 200–201,
203, 346Security
Application IntegrationImplementationSpecification
B2B, 205, 348, 350ESB, 200, 345message brokers, 198, 344mobile integration, 210, 354
Composite ApplicationIntegrationImplementationSpecification, 240, 376
Current EnvironmentAssessment Specification,85–86, 288–290
Information IntegrationArchitecture Specification,154–155, 329–330
Information IntegrationImplementationSpecification
data integration, 224, 363metadata repository, 229,
368unstructured content, 226,
365Process Integration
ImplementationSpecification, 257, 386
Technical IntegrationArchitecture Specification,96, 106, 108–111, 300,307–309
Self-service Web site, 189Semantic metadata, 154, 157, 329Semantic validation, 143Semantic Web, 145
ServersApplication Integration
ImplementationSpecification, 207, 352,354
Current EnvironmentAssessment Specification,81, 287
Service Category Table, 127–128Service Definition Table, 127,
129Service integration architecture,
70best practices, 134–135defining services, 121–122event-driven design, 122–123overview, 117Service Integration
Architecture Specification,123, 313
business events, 124–126,316–317
conclusions, 132, 321introduction, 123, 316key participants, 124, 316references, 322scope, 124, 316services, 125–130, 317–319table of contents, 315template instructions, 314use cases, 131–132, 320–321
service-oriented architecture,117–121
Service Interface Table, 129, 130Service interfaces
Application IntegrationImplementationSpecification, 201–203,347
Composite ApplicationIntegrationImplementationSpecification, 240, 376
Service-level requirements,101–106, 302–306, 310
Service-oriented architecture(SOA)
adoption of, 262benefits, 119–121
for composite applicationintegration, 234
history, 117–119in integration strategy, 16,
45–46for reuse, 44
Servicesdefining, 121–122in process flow models, 174Service Integration
Architecture Specification,125–130, 317–319
Technical IntegrationArchitecture Specification,92–96
SGML (Standard GeneralizedMarkup Language), 141
Shipping management service,129
Simulation in processautomation, 253, 382
Six Sigma tool, 19, 162, 164SOA. See Service-oriented
architecture (SOA)SOAP standard, 46Software costs, 31, 272Sourcing
in Business Integration StrategySpecification, 52–53,279–280
in Information IntegrationArchitecture Specification,155, 330
SpecificationsApplication Integration
ImplementationSpecification, 195, 339
Business Drivers andRequirementsSpecification, 27, 267
Business Integration StrategySpecification, 48, 275
Composite ApplicationIntegrationImplementationSpecification, 238, 371
Current EnvironmentAssessment Specification,79, 283
Index 405
30795 27 IDX pp. 393-410 r2.ps 6/25/04 2:16 PM Page 405
Specifications (cont.)Information Integration
Architecture Specification,150, 323
Information IntegrationImplementationSpecification, 219, 357
Process IntegrationArchitecture Specification,171, 333
Process IntegrationImplementationSpecification, 250, 377
Service IntegrationArchitecture Specification,123, 313
Technical IntegrationArchitecture Specification,91, 293
SQL as access standard, 41Standard Generalized Markup
Language (SGML), 141Standards
application integration, 211Business Integration Strategy
Specification, 53–56,280
composite applicationintegration, 234
EDI, 25, 193in integration strategy, 40–41,
262MDA, 101metadata, 145–149process integration
architecture, 169–171service integration architecture,
134Web services, 46XA, 221XMI, 147–148XML-based, 25–26
Standards profiles, 98, 100–101,301–302
State governmentsCriMNet system, 65–67online bill access system, 219technical integration in,
89–90
Statement of purposeBusiness Drivers and
RequirementsSpecification, 28–30,270–271
Process IntegrationArchitecture Specification,172, 336
Strategic enterprise approach,business case for, 67–68
Strategic initiatives for efficiency,21
Strategic integration, 265Strategic sourcing, 52–53,
279–280Strategy. See Business integration
strategyStructured data integration, 216Student services, 121Success measurements, 164–165Successful operation responses in
use cases, 321Supplier integration
requirements, 93, 297Supply chain
General Motors, 166Levi Strauss & Co., 163
Synchronization, data, 224, 363Szygenda, Ralph, 21, 45, 166
Tactical initiatives, 21, 38Target systems, 155, 330Tasks in process flow models, 174TCO (total cost of ownership),
262TCP/IP as network standard, 41Technical integration
architecture, 69–70best practices, 113overview, 89–91Technical Integration
Architecture Specification,91, 293
architecture description,96–100, 300–301
architecture requirements,92–96, 296–300
capacity planning view,111–113, 309–310
conclusions, 113, 311design constraints and
guidance, 113, 311introduction, 91, 296key participants, 92, 296references, 311scope, 92, 296security, 96, 106, 108–111,
300, 307–309service-level requirements,
101–106, 302–306standards profiles, 98,
100–101, 301–302table of contents, 295template instructions, 294
Technical issuesBusiness Drivers and
RequirementsSpecification, 274
Business Integration StrategySpecification, 282
TechnologiesBusiness Integration Strategy
Specification, 54Current Environment
Assessment Specification,80–82, 286–288
Process IntegrationArchitecture, 165–169
Technical IntegrationArchitecture Specification,92–96
Temporal events, 124Testing
in information integration, 230in service-oriented
architecture, 120Texas A&M University student
services, 121Throughput in Technical
Integration ArchitectureSpecification, 112, 304,310
Top-down approach to services,121
Total cost of ownership (TCO),262
Total Quality Management(TQM), 162, 164
406 Index
30795 27 IDX pp. 393-410 r2.ps 6/25/04 2:16 PM Page 406
TP (transaction processing)monitors, 221
Trades in finance industry, 26Training, 119, 134–135Transaction processing (TP)
monitors, 221Transactions
Information IntegrationImplementationSpecification, 224, 363
Technical IntegrationArchitecture Specification,305–306, 310
capacity planning view, 112nonrepudiated, 111service-level requirements,
105, 107Translation and transformation
application integration, 187Application Integration
ImplementationSpecification, 339
B2B, 205, 350ESB, 198, 200, 345mobile integration, 210, 354
Composite ApplicationIntegrationImplementationSpecification, 240, 376
Information IntegrationImplementationSpecification
metadata repository, 229,368
unstructured content,223–224, 365
Technical IntegrationArchitecture Specification,95, 299
Triggers in use cases, 321Trunking services, 245Turnaround times, 112, 304, 310
UDDI standard, 46UML (Unified Modeling
Language) models, 144,170
activity diagrams, 175sequence diagrams, 176
Unitary logins, 108, 308University student services, 121Unstructured content integration,
216, 223, 225–226,363–365
Upper level management support,265
Usability, 103–104, 107, 304, 306Use Case Specification, 132–133Use cases, 131–132, 320–321user accounts in authentication,
108, 308User types in authentication, 108,
307
Value-Added Networks (VANs)for cost reductions, 12–14northAmerican Logistics,
193Vanguard Group customer service
system, 135–136Variation causes in process
improvement, 161Vendors
Business Integration StrategySpecification, 53, 280
current assessment, 77Technical Integration
Architecture Specification,93–94, 297–298
Version control, 254, 257, 386Views in Information Integration
ImplementationSpecification
data integration, 224, 363unstructured content
integration, 226, 365Virtual data warehouses, 227Virtual factories, 166VISA, XML Invoice Specification
by, 25
W3C (World Wide WebConsortium) formetadata, 145–146
Wal-Martphilosophies, 10–11process improvements, 162supply chain, 163
Web Ontology Language (OWL),146
Web Service ChoreographyInterface (WSCI), 56
Web Service Orchestration(WSO), 168–169
Web servicesfor adapters, 191composite application
integration, 234–237Current Environment
Assessment Specification,81, 287
for message brokers, 188for Miami-Dade County
integration, 235–236in service-oriented
architecture, 46Well-formed XML documents,
142WfMC (Workflow Management
Coalition), 170–171Wireless connectivity, 208Workflow
process integrationarchitecture, 167
Process IntegrationImplementationSpecification
automation, 253, 382collaborative process
integration, 255, 257,386
Workflow Management Coalition(WfMC), 170–171
World-class finance, CiscoSystems, 5–7
World Wide Web Consortium(W3C) for metadata,145–146
WSCI (Web ServiceChoreography Interface),56
WSDL standard, 46WSO (Web Service
Orchestration), 168–169
XA transaction managementstandard, 221
Index 407
30795 27 IDX pp. 393-410 r2.ps 6/25/04 2:16 PM Page 407
XBRL (Extensible BusinessReporting Language), 25,142
XMI standard, 147–148XML (Extensible Markup
Language)
ESB, 344importance, 140northAmerican Logistics, 193overview, 141–142service-oriented architecture,
46
XML-based integration standards,25–26
XML Gateway, 218XML Invoice Specification, 25
Zero latency, 5
408 Index
30795 27 IDX pp. 393-410 r2.ps 6/25/04 2:16 PM Page 408
Recommended