Bedarfsanalyse fachlicher Metadaten - Universität St.Gallen
Bedarfsanalyse fachlicher Metadaten - Universität St.Gallen
Bedarfsanalyse fachlicher Metadaten - Universität St.Gallen
Sie wollen auch ein ePaper? Erhöhen Sie die Reichweite Ihrer Titel.
YUMPU macht aus Druck-PDFs automatisch weboptimierte ePaper, die Google liebt.
96 Beitrag D<br />
11.3 Functional Map<br />
For the desk research, we picked the five best-ranked metadata repository vendors according<br />
to Gartner’s magic quadrant [Blechar 2005]: Allen Systems Group 13 (ASG),<br />
Logic Library 14 , Flashline, Computer Associates 15 (CA), and MetaMatrix 16 . Since<br />
Flashline has been acquired since the issue of the Gartner report, SAP BusinessObjects<br />
17 has been included instead. The basis for the design of the functional map<br />
formed publicly available product information and presentations for the respective<br />
products: ASG-Rochade [Lux 2010] and ASG-metaGlossary [ASG 2009], Repository<br />
Manager (formerly Logidex) [SOA 2009], CA Repository [CA 2008; CA 2009], MetaMatrix<br />
Repository (as part of MetaMatrix Enterprise Data Services Platform) [JBoss<br />
2008], and SAP BusinessObjects Metadata Management [SAP 2008].<br />
To classify the different functionality in these products, the article differentiates three<br />
basic domains: definition/sourcing, integration, and presentation. The first constitutes<br />
the ability to define and/or source metadata (e.g., lineage data from ETL tools). The<br />
second integrates different types of metadata to a new class (e.g., technical lineage<br />
data plus elements of terminology, compliance, and quality management results in<br />
process metadata). The third and last domain groups different techniques in presenting<br />
the business metadata to the user (e.g., within a stand-alone information portal).<br />
11.3.1 Definition/Sourcing Functionality<br />
Definition and sourcing (from other tools) of business metadata is the core ability of a<br />
metadata repository. In this domain, the functionality falls in three different buckets:<br />
syntax, semantic, and administrative. This depends on whether it reveals the formal<br />
relationships of data and/or systems (syntax, e.g., defining the data elements of a term<br />
to be unambiguously described), or maintains the actual content (semantic, e.g., the set<br />
of business terms), or supports the maintenance of the actual content (administrative,<br />
e.g., a workflow management functionality to regularly update and sign off new business<br />
terms).<br />
The group “syntax” comprises two functionalities: data modeling and (technical lineage).<br />
Data modeling is used to describe data in a formal way (on a conceptual, logi-<br />
13 www.asg.com<br />
14 www.logiclibrary.com<br />
15 www.ca.com<br />
16 www.redhat.com/metamatrix<br />
17 www.sap.com