Databases Reference
In-Depth Information
initialization through a rate grid rather than in the form of a
classic input field. In this case, it is convenient, at the time of
logical modeling, to specify these user interface components
in view of preparing their realization in the software.
10.6.4.
Data documentation
Data documentation, following the ISO/CEI 11179
norm,
10
is managed by a data repository under the control of
the MDM system. The model of this repository takes the
description of logical data and enriches them with the meta-
data defined in ISO/CEI 11179.
10.6.5.
Naming rules
The data naming used for logical modeling must
immediately be reusable in the software, that is to say in the
XML (XSD) data schemas. We could opt for a more
independent approach to logical data naming, but that would
mean managing a translation at the time of production of
XML schemas, which would make the chain of production
more complex. The isolation of the modeling vis-à-vis
technical solutions is already acquired by the upstream
semantic (business) and pragmatic (organization) models
that enable this technical adherence to be admitted in the
logical models. In reality, the adherence is low, since the
possibilities in data naming in XML schema are not
restrictive. A CAMEL
11
case, with extended labels (without
white space or accented characters) is generally adopted.
Putting in place a dictionary of prefixes enabling certain types
of reference and master data to be distinguished is recommended:
date (dt), label (lb), identifier (id), number (no), etc.
10
. http://metadata-standards.org/11179/
11
. i.e. using upper and lower cases to distinguish terms, e.g.
ProductName, DataSource, costOfTheInitialDisaster, etc.
