A
Abbreviations, eliminated in XML,
81
Abstraction levels, for data management planning,
129
in XML framework transactions,
195,
196
Acronyms, eliminated in XML,
81
Adjectives of electronic business,
201,
221
Advanced languages, in XML component hierarchy,
89
Ambiguity, eliminating via XML grammar,
79
Ampersand (&) character,
93
contextual searches of unstructured documents using,
255
in portal navigation,
244,
245
component of EAI solution,
283
requiring expertise of programmers and program architects,
284
Application code base, reducing via XSLT,
108
Application data interchange, direct benefits through XML,
353
Application developers, ,
Visual Studio .NET for,
210
Application efficiency, increasing via XML,
23–24
Acord in insurance industry,
211–213
Billing information from existing system,
136
capacity management with XML,
347–349
chemical industry structure,
328–330
credit card industry structure,
328
Envera for chemical industry,
213–217
legacy application conversion,
55–57
legacy application maintenance reduction,
349
legacy code maintenance burden for cash-management system,
226–228
media company XML/EAI implementation,
279–280
medical data administration,
343
metadata management example,
62–68
Microsoft implementation of unstructured metadata,
357–358
moving data between Lotus Notes and mainframe applications in EAI,
273
moving data from personnel to payroll applications,
289–290
payroll and personnel systems migration,
150–154
pharmaceutical data-quality evolution,
262–263
producing innovating XML-based IT savings,
354–357
RosettaNET in electronic component industry,
196–200
sending payroll data to personnel department via EAI implementation,
275
XML-based portal technologies,
256–259
XML framework for chemical industry,
191
XML framework for publishing house,
189–190
Application portfolio,
130
Application programming interfaces (APIs),
174,
363
Application scanners,
130
effects of portal technologies on,
235
evolution from stovepipe to web service-based architectures,
230
expanding data management’s role in,
26
in XML component hierarchy,
89
Architectural data work,
142
Architectural evolvability and maintenance, enhanced via portal technology,
248–250
Architectural flexibility, of XML-based portal technology,
247–248
Architectural requirements
conversion mistakes due to incomplete,
61
Architecture-based understanding, importance in data engineering,
133
Architecture component, as main output of EAI implementation process,
292
Architecture description markup language (ADML),
87,
119–120,
363
Arcs, specifying link direction of travel,
102–103
Artificial intelligence research,
318
As-is implemented assets,
135,
307
Associative learning methods,
318
in legacy system reengineering,
148
and major change in data-storage statistics,
150
associating with particular URIs,
89
ordering system example,
91–92
properly specified in well-formed documents,
90
single way to express in XML,
76
Attribute specification,
79
combining in data reengineering,
148
matching primary/foreign keys,
144
rate of data mapping during reengineering,
143
renaming in legacy environments,
169
in RosettaNET Implementation Framework,
199
Authorization decision,
146
Authorization information, exchanging,
146
Automated communication, and value of XML frameworks,
188
Automated data-management facilities,
339
Automated metadata extraction methods,
170,
172
Automated metadata management,
352
Automated schema submission,
208
Automated services, role of WSDL, UDDI, and SOAP in providing,
88
Automated XML conversion process,
58,
180–181
B
Bad habits, encouraged by HTML,
41
Barriers to entry, lowering via XML frameworks,
194
Baseline architecture, underestimating value of,
61
Batch parsing capabilities,
248
B2B application example,
53
Best practices, lack of organizational implementation of,
299
Big bang approach,
vs. phased approach,
298
Binary-only data representation formats, XML not replacement for,
85
BizTalk message structure,
207
BizTalk specification,
205
Bottom-up development,
132
of future data-management operations,
344
preferable for short-term payoffs,
353
Bridge engineering analogy,
126–134
Brittleness, of complicated data structures,
141
in EAI implementations,
274
in ERP implementation,
226
Business case, for EAI implementation,
284–285
Business concepts, high-level in RosettaNET dictionaries,
197
Business dictionary, in RosettaNET,
197–198
Business engineering,
346
contribution of understood data structures to,
346
Business intelligence,
29
Business objects, libraries in ebXML,
200
Business-practice analysis,
155
Business-practice realignment,
355
Business-process reengineering,
307–310
relationship to systems reengineering,
310–311
final definitions stored in ebXML,
202
as hierarchical structures,
155
integration and exchange via BizTalk,
206
metamodels included in ebXML,
201
models in XML framework repositories,
190
PeopleSoft Administer Workforce,
356
remodeling to improve resource efficiencies,
314
shared repositories in ebXML for,
200
standardized in XML frameworks,
190–191
standardized with AL3/Acord,
213
Business requests, interpretation in terms of framework concepts,
221
ability of XSLT to model,
107
for data transformation,
31
extracting in code reduction process,
266
in XML-based portal technologies,
244
Business-to-business commerce
Envera Hub as transaction clearinghouse for,
213
Business transactions, improving efficiency via XML,
23–24
in legacy system migration projects,
171
responsibility for maintaining rules for transforming data items/structures,
176
C
Call center volumes, reducing via XML data conversion,
55
Candidate hypotheses, in legacy system migration projects,
173
Capabilities-maturity model (CMM),
184,
343,
363
Cascading Style Sheets (CSS),
105,
363
CASE-like functionality,
11,
13
for automated XML conversion,
180–181
creating data definition language files with,
261
extracting metadata automatically in entity-relationship diagram notation,
170
in PeopleSoft database design,
356
Cash-management system example,
226–228
low implementation rate of,
299
Center for Information Management (DoD),
342
Change management, streamlining via XML conversion,
57–62
Change propagation effects, estimating with XML,
350–352
Character encoding standards,
77
UTF for XML documents,
45
Envera Hub as XML framework for,
213–217
intraindustrial structure and communication,
328
XML/EAI implementation in,
279
expressing singleton tags without,
76
Chunk-sized EAI projects,
295
Civil engineers, advantages over data engineers,
127
Claims submission and processing, with Acord,
212–213
Clarity, relative importance over file size,
80
of servers in XML frameworks,
219
COBOL/CICS code, in legacy system example,
227
Coding standards, in measurement of data-engineering tasks,
143
Collaboration Protocol Agreements (CPAs),
190
in implementation steps for ebXML,
204
Collaborative Partner Profiles (CPP),
203
Commercial off-the-shelf (COTS) software, use in EAI projects,
272
Common data models, missing in Oracle CPG project,
298
Common data vocabularies, using XML-based portals,
266
in tightly coupled EAI integrations,
281–282
use important in EAIE,
292
Common Object Request Broker Architecture (CORBA),
274
Company names and profiles, in XML framework repositories,
190
in Registry and Repository metamodel of ebXML,
202
shared repositories in ebXML for,
200
of investing in metadata,
13
Complex tag modifications,
30
of interrelated ebXML standards,
203
of organizational data systems,
16
of XML as barrier to adoption,
22
Component metadata, interconnections among,
345
XML tools and technologies,
164–168
Conceptual structure decomposition,
138
Confederated components model, in portal navigation,
246
Configuration management,
10
Connectivity multiplier,
217
Consistent user interface,
241
provided via portal technologies,
238,
266
Content, difficulty locating in search engines,
41
Content re-architecting,
59
Content summaries, using resource description framework (RDF),
110–111
addition in XML conversion process,
65
searches using XML-based portal technology,
254
Contextual extensions,
139
Conversion example,
64–65
Cooperative computing, .NET and,
209
Core technologies, lacking support in Oracle CPG EAI implementation,
299
Corruption, avoiding in XML frameworks,
194
via business process reengineering,
308
Cost of entry, into Internet/industry networks,
336
Cost savings, by converting applications to XML,
54
of EAI implementation,
272
of implementing interfaces and transformations with XML,
352
of incremental modifications
vs. systems reengineering,
305
of initial investment in XML technology,
330
of maintaining custom electronic data interchange solutions,
16
of managing excess/unused data,
151
of out-of-band communication,
330
of poor data structures at individual-attribute level,
139
of poor systems and business processes,
314
of production reduced with XML frameworks,
218
recurring maintenance,
286
of tightly coupled
vs. loosely coupled integration,
282
of training with portal technologies,
237
of underestimating data-mapping times,
144
Credit card company applications,
55
Cringely, Robert X.,
40,
82
Cross-referencing data,
64
Cryptographic protocols, supported by ebXML,
201
client-side implementation with XSLT on server side,
110
Customer information, validating with excess data,
151
Customer relationships, strengthened with XML frameworks,
218
Cut-overs, phasing during implementation,
157–158
Cycle times, reduced with XML frameworks,
218
D
as combinations of facts and meanings,
reuse and velocity of,
358
self-perpetuating nature of,
136
understanding based on context and metadata,
321
yielding information about hidden trends,
135
Data abstraction-layer approach,
183
Data access frequency,
139
Data access options, of DOM parsers,
39
via XML-based portal technologies,
257
resolving differing priorities,
341
affected by day-to-day systems projects,
124
bottom-up development of,
132
component of EAI solution,
283
as component of enterprise architecture,
133
high-level enterprise model of,
131
requiring expertise of data managers,
284
using XBP to maintain,
247
Data/architecture evolution, contribution of understood data structures to,
346
importance of understanding before managing,
233
Data attribute system component of record,
139
Data automation, via XML-based portal technology,
259–260
Data backup and recovery,
13
Data Blueprint example,
57
Data-capture requirements,
151
Data-centric data structures,
177,
345
effectiveness linked to enforcement mechanism,
343
Data change management procedures,
11
Data-communication layer, in BizTalk,
207
Data constraints, in XML schemas,
94–95
Data design, good principles of,
78,
79
Data engineering and bridge engineering analogy,
126–134
data-mapping case study of,
148–158
intersection between XML and,
123–125
poorly applied in EAI implementations,
275
tasks associated with,
123
typical XML first steps in,
125
XML-based data structures in organizational data architecture,
126–144
Data-engineering challenges,
134
Data-engineering tasks, measurement of,
134,
143–144
Data entity and attribute definitions,
11
division into transactions with XML frameworks,
194–196
Data-exchange systems, benefits proportional to number of
participants in network,
336
Data formats, standardized in XML frameworks,
188
Data granularity type,
139
resolutions with XML-based portal technologies,
241,
243
Data integration patterns,
11
Data integration requirements,
139
Data interchange, on internal organizational level,
325–326
Data-interchange capabilities
at low end of market,
331
and similarities with Internet,
336–337
Data logistic networks,
244
Data management assessment,
27
Data management challenges,
2–4
Data-management challenges
data standardization,
342
expanding DM mission,
341
greater payoff for preparation,
351,
359
increasing data access and provisioning,
342
increasing volume, scope of data,
341,
357
understanding data structures as XML,
341
understanding growth patterns,
342
value representations,
342
Data management (DM),
363
efficiency gain resulting from appropriate,
140
expanded role with increased XML use,
29–31
extending to unstructured data,
254–256
importance of good practices in EAI,
271
inclusion of unstructured data in,
235
increasing scope and volume of,
357–359
integrating with XML operations,
62
interactions with XML,
26–31
need for planning and strategy simultaneously with XML work,
128
semantics as stumbling block for,
189
use of XML in support of,
48–68
XSLT stylesheet transformation of interest to,
108
Data-management maturity measurement (DM3),
183–184,
299
estimating rapid results based on,
353
Data-management policy, available through templates,
344
Data management practices
supported by XML design goals,
81
real-world application examples,
256–259
XML-based portal technology opportunities for,
253–256
Data-management technologies, processing XML data with,
173
Data manipulation, programmatic,
13
and data packrat phenomenon,
151
yielding information about hidden trends,
135
in Acord XML framework,
212
generic in XML-generation tools,
180
in XML conversion process,
58
Data modeling, XML failing to replace,
83
Data-movement problems,
339
Data naming standards,
11
in legacy structure evolution process,
261
with XML-based portal technology,
257
Data program coordination,
184
Data-quality engineering,
134
via XML-based portal technologies,
241
Data quality issues, role of XML-based portal technology in resolving,
259–260
Data-quality portal example,
262–263
Data-rationalization tools,
184
Data retention criteria,
11
Data scrubbing, in EAI implementation,
285
engineering issues with,
124
Data selectivity, via XPath,
97,
98–99
Data sources, conceptual indexing of,
management obstacles to,
133
via XML-based portal technologies,
250–251
in contextual extensions decomposition,
139
Data storage requirements, changing in legacy system migrations,
150–151
Data-structure perspective,
vs. data-field perspective in EAI implementations,
290
Data-structure transformations, via XML in reengineering process,
311
as appropriate focus in data
complicated nature of,
141
data-centric
vs. document-centric,
176–177
implementing wrapping of,
347
importance of good design to daily enterprise work,
125
including nested data structures outside enterprise,
345
management unwillingness to invest in evaluation of,
124
moving in entirety in EAI implementations,
289–290
need for well-architected,
322
organizing format in legacy systems,
169
process usage in legacy systems,
169
Data support operations, ,
13,
184
avoiding overemphasis in EAI implementations,
288
burden reduced via XML,
30
replacing legacy systems based on,
350
without application code via XSLT,
108
and measurement of data-engineering tasks,
143
supported by XML schemas,
94–95
Data understanding, role of XML in,
311
Data update probability,
139
Data validation, reduced effort with XML schemas,
95
Data velocity, increasing with XML support,
358
Data volume, reduced with XML,
358
Data warehouse tables, populating,
348
Database design, PeopleSoft example,
356
Database management system (DBMS),
363
requiring long-term payout time,
352
Database-querying programs,
320
Databases, differences from XML,
82
Datalogix, purchase by Oracle,
297
Decompositions, in data engineering process,
138
Default values, for attribute names,
91
Defect prevention management,
12
Defense Information Systems Agency (DISA),
237–238
Defined level data-management maturity,
184
in domain-specific languages,
279–280
Department of Defense (DoD), controversy over role of data administration in,
342–343
Design objects, managing concurrently with schemas,
167
Design quality, criteria of,
140
Develop Workforce component,
157,
357
Developer tools, in .NET,
210
and outsourcing of EAI projects,
272
reduced via portal technology,
236,
243
Developmental maturity, five levels of DM3,
184
Diagnosis phase, in business process reengineering,
309
Diagnostics, faster with XML,
81
Digital marketplaces, requiring long-term payout times,
352
Disassembly work, avoiding in XML/EAI implementations,
290
Disruptive technologies, and reengineering process,
311–312
Distributed Component Object Model (DCOM),
274
Distribution channels, benefits of Envera on,
213
Document-centric data structures,
177
appropriate for XML databases,
177
Document comparison and conversion,
39
Document level message exchange,
174
Document names, mapping by integration servers,
174
Document sizes, factors determining in XML,
80
Document subsections, ability of XSLT to work with,
107–108
Document tracking and analysis, with XML frameworks,
219
Document transfer, between organizations with BizTalk,
205
integrated with XML frameworks,
218
via XML mediation severs,
174
Document type definitions (DTDs),
90–91,
363
attribute names in,
91–92
transitioning to XML schemas from,
96
Domain-specific XML languages, in support of EAI,
279–280
consequences for data-management professionals,
339–340
and need to demonstrate short-term payback,
344
among XML converters,
178
in support of metadata,
247
Drag-and-relate interaction metaphor, in portal navigation,
244–245
Duplication of efforts, reducing via XML conversion,
56
E
requiring long-term payout times,
352
Early adopters, of XML and Internet,
331
use in XML/EAI implementation,
278
ebXML Messaging Service,
204
ebXML technical architecture,
202
Economies of scale, as advantage of XML frameworks,
188
business-to-business with Envera Hub,
214
due to appropriate data management,
140
via reengineering efforts,
314
Electronic business framework, ebXML as lingua franca for,
200,
204
Electronic component industry, RosettaNET and XML frameworks for,
196–200
Electronic data interchange (EDI), 364
supported by XML frameworks,
218
Electronic data interchange (EDI) solutions,
16
XML not replacement for,
84–85
associating with particular URIs,
89
Elements, number restricted in HTML,
105
managing via XML-based portal technologies,
235
search capabilities with XML-based portal technologies,
253
Encryption, as advantage of XML frameworks,
219
Enforcement mechanisms, crucial to success of data management,
343
Engineering-based approach, of EAIE,
291–293
Engineering principles,
32
Enterprise application integration (EAI),
75, 364
avoiding technical-level solutions,
287
data-architecture
vs. technical
effectiveness dependent on semantic information about data structures,
276
engineering-based approach (EAIE),
291–293
generalized approach to integration,
290–291
importance of good data management practices in,
271
importance of scalability to,
293–295
making business case for,
284
perceived quality of implementations,
288
processing efficiency of,
288
product differentiation in,
288
resource efficiencies in,
291
steps in successful development,
293
support lacking in Oracle CPG project,
299
unit responsiveness as goal of,
288
with XML integration servers,
174
Enterprise application integration Engineering (EAIE),
291–293
as combination of data, process, and technology architectures,
133
proper means of developing,
131
Enterprise data assets,
11
Enterprise data integration, ,
185
Enterprise resource planning (ERP),
124, 364
implementing to resolve legacy code resource burden,
225–226
moving data from legacy system to,
169–170
repurposing metadata,
154
requiring long-term payout times,
352
use in Oracle CPG project,
296
use of XML frameworks to standardize vendor participation,
194
uses of metadata expressed in XML,
156–157
Entity-relationship diagram (ERD) notation,
170,
320, 364
Envera Clearinghouse,
214
Error handling, integrating with XML editors,
164
European Union (EU), certification to do business in,
155
addition of new features requiring systems reengineering,
305
XML trend of building on,
103
Expensive-to-maintain code, reducing,
266
Extensibility, with XML schemas,
94
Extensible Markup Language (XML),
41, 365
supported by framework servers,
218
facilitating inter-industry network communication,
335
modifying repositories using,
129
XML name and structure changes managed via,
175
Extensible Stylesheet Language (XSL),
104, 365
Extraction queries, automating,
156
I
IMI Order Management software,
296
Implementation/maintenance costs, reduced via portal technology,
236,
243
Implementation time, reduced via portal technology,
236,
243,
252–253
Incremental modifications,
vs. systems reengineering,
305
content in HTML search engines,
41
metadata in conversion process,
64
in XML conversion process,
60
Individual data points,
14
Indus Enterprise Asset Management,
296
Industrial engineering,
308
Industrial espionage,
194
Industry-level data interchange,
328–332
Industry-specific XML frameworks
Industry trade groups,
334
Industry vocabularies,
279
Industry-wide communication, as advantage of XML frameworks,
188
affected by day-to-day systems projects,
124
focus on low-level
vs. high-level aspects,
127
Information engineering,
132
Information-engineering principles, use of XML-based portals to implement,
228–235
Information location, improving via XML,
24–26
in XML framework repositories,
190
standardizing via XML frameworks,
191
in XML framework transactions,
195
Information reuse, repositories enabling,
21–22
Information technology industry, use of RosettaNET by,
198
Infrastructure capacity, reducing upgrade need for,
347
Initial level data-management maturity,
184
extracting metadata from legacy systems,
168–173
standardized in XML frameworks,
191
Input trees, in XSLT,
107
Insurance carrier applications,
55
Insurance industry, Acord as XML framework specific to,
211–217
Integrated management,
12
of applications and business partners with XML frameworks,
218
of applications in BizTalk,
204
creating demand for portal services,
267–268
of disparate applications with XML-based portals,
314
enhanced opportunities with XML-based portal technologies,
250–253
facilitated with use of domain-specific languages,
280
generalized approach in EAI implementations,
290–291
growth of total market for,
286
increased depth with XML-based portal technology,
251
with Internet via XSLT browser,
108–110
loosely or tightly coupled in EAI implementations,
281–282
of modeling and transformation features,
183
from multiple data sources/stores in XML portal technologies,
246
of organizational data and metadata via portal technology,
247–248
of supply chains with XML frameworks,
218
wider scope with portal technologies,
251–252
of XML at browser level,
48–50
Integration technology, total market for,
286
Inter-industry connectivity,
332–333
Interconnections between applications,
51
Interindustry communication, facilitated by ebXML,
204
Internal query-integration capabilities,
182
machine navigation of semantic content via UDDI,
116
mean cost of access decreasing,
331
usability of XML over,
73–75
Internet compatibility,
74
Internet congestion, reducing via XML,
23–24
and evolution of organizational data systems,
323–325
and internal organizational data interchange,
325–326
and intra-industry communications,
331
Internet portals,
vs. XML-based portals,
223–224
Internet protocol (IP), 364
Internet-protocol layer, security at,
145
types available through UDDI,
117
Internet service providers (ISPs),
323
between competing XML frameworks,
222
in insurance industry with Acord,
212
on inter-industry level,
335
promoted by ebXML information model,
201
Intra-industry communication, XML in,
330–332
management via RosettaNET PIPs and clusters,
198
standardizing via XML frameworks,
191
ISO-9000 certification,
155
consumed by legacy code maintenance costs,
234
cut at organizational level,
359
IT maintenance costs, direct benefits through XML,
353
reducing burden via XML migration,
176
IT savings, producing with XML,
354–357
IT spending distribution, by activities,
285