A data element is defined in the context of the meta data as an atomic entity with the following characteristics:

1. by a data element name one identifies
2. a clear data element definition has
3. a which the data class has one or more representation terms to describe
4. optionally a listing of the permitted values has
5. optionally a list of synonyms in andernen Metadataverzeichnissen has

Data elements can be discovered and analyzed as application programs, files and narrative concepts manually or semiautomatically are examined and judged on their relevance.

Data element name

In a formal Datadictionary the requirement often exists that no two data elements have the same data element name. In some Datadictionary gives however possibilities, to the data element name e.g. with a module prefix for one from several application modules to qualify.

In a data base-supported Datadictionary becomes the fully qualified data element names a primary key or alternative key of a data element table.

Data element definition

A data element definition into one in Prosa formulated description of the data element, which describes the semantics or meaning of the data element.

A good definition is

1. Precisely: I.e. .formuliert in words with an exact meaning. Words with several meanings (homonyms) should avoided
2. Concisely: A definition should correspond to that shortest possible formulation.
3. Not : The term is defined, should not be used not in the definition.
4. Clearly: The definition should differentiate a data element from other data element over divorce-free.

Purpose and use of data elements (example)

In an enterprise data model the for example following data elements can be present:

• Cost centre
• Account executive
• Customer

Data element is documented by a sentence by attributes. Exemplarily in following table per data element a clear data element identification, the associated domain, short, is specified central and long designation, as well as a left on the verbal definition and explanation in the enterprise data model documentation. The domain is needed, if from the data element columns are to be derived. The field names are defined in the data element and selected here here e.g. by the form generator.

Model-relevant columns, in particular key columns (primary key, secondary key) should lead away themselves to possibility from a documented data element. It is to be noted that the relations between the list of all data elements and the list of all columns does not have to be necessary 1:1. A table the cost calculation vouchers contains can e.g. two columns have

• Transmitter cost centre
• Receiver cost centre

which both to the same data element cost centre refer and the respective cost centre postings take up. In the further this data element and the associated columns are normally used in a multiplicity of tables in the data model. From this reason a Datadictionary for the inquiry of these relations makes available a statement on the use.

Such a data element catalog is part of the Sytemdokumentation. It is to be added meaningfully it as appendix to the data processing concept.

See also

• ISO/CInternational Electronical Commission 11179 specification Metadataverzeichnis
• Meta data

External one left

• Association for Enterprise integration
• Federal XML Developer's Guide
• ISO/CInternational Electronical Commission 11179 standard (lake ISO/CInternational Electronical Commission 11179-3: 2003 clause 3.3.36)

Articles in category "Data element"

We found here 12 articles.