Naming convention many data administrators are familiar with. The representation class is equivalent to the class word of the prime/class The representation term describes the data element’s representation class. Of possible valid values of a data element). A complete logical data element must include a form of representation for the values in its data value domain (the set
The next step in forming data element names takes place at the logical level. These value meanings areĭefined but do not have a specific form of representation (Figure 2). DECs also contain conceptual domains, which are composed of value meanings. From the examples above, we can form the DECs tree height and country identifier. DECs are named by combining the object class term and the When applied to data element names, these are called object class term and property term. A property is something that describes all objects in theĮach of these components has its own name. An object class represents an idea, abstraction or thing in the real world, such as tree or country. At this stage, a set of concepts exists as entities or objects (called object classes), which, with the assignment of properties,īecome data element concepts (DECs). Name development begins at the conceptual level (See Figure 1). Should decide the form of identifier best suited to its individual requirements.
Universal database naming conventions iso#
Both the identifier and at least one name are considered necessary to comply with ISO 11179-5.
ISOġ1179-5 discusses assigning this identifier at the International registry level. Since many names may be associated with a single data element, it is important to also use a unique identifier, usually in the form of a number, to distinguish each data element from any other. Provision for identification of synonymous names is made through sets of name-context pairs in the element description. Other names may be used by reports or EDI files.
Universal database naming conventions software#
However, within physical systems, names are subject to constraints imposedīy software limitations. Names derived in this way serve as the primary means of identification for elements external to systems that process them. Components are envisioned as a set of building blocks that can be assembled into data elements, and serve to ensure that the end product, the total set of data elements, is as discrete and Naming conventions must reflect this multiplicity.Īfter the conceptual components are developed by a process of specification from the highest conceptual level, a representation term is assigned which may in turn be derived from a structure set or
Also, one data element may have many names depending on context of use. The rules by which these component names are combinedĪre a data element naming convention. Each component contributes its name, or part of its name, to the final products. Using the Zachman Framework, for instance, the highest levels of definition are contained in theīusiness view development progresses to the implemented system level.Ĭomponents are defined and combined differently at each level. Objects at each level are called data element components their names become name components. Levels progress from the most general (conceptual) to the most specific (physical). This article is based on the informationĭata elements are ideally the result of a process of development, involving several levels of abstraction. Part 5 of this standard is Naming and Identification Principles for Data Elements. The International Standard ISO 11179, Information Technology-Specification and Standardization of Data Elements describes a set of rules for developing naming conventions together with standardsįor data classification, attribution, definition and registration. Maximizing understanding of information both within and outside their organization. When gathered into a repository or data registry, this collection of meta data assists users to achieve efficient use and reuse of data while Of the data element, in a concise manner. These names will inform the user about the contents of the data value domain (the set of possible valid values for a data element), and the usage What we call a naming convention is a collection of rules, which, when applied to data, results in a set of dataĮlements named in a logical and standardized way. Naming conventions for data elements are part of the toolset of data administrators.
0 kommentar(er)
