3.6. Data Description Example    (3X2D)

This section provides a usage example for the Data Description standardization area. It is based on an existing implementation of the DRM at the Department of the Interior (DOI), for the Recreation One Stop initiative . The DOI recreation functions deliver services that make up Recreation One Stop. DOI has created various “information classes” that describe the data required for Recreation One Step – these are shown in figure 3-2:    (3X2E)

http://colab.cim3.net/file/work/das/DRM_2.0/Figure_3_2.JPG    (3YPJ)

Figure 3-2 Recreation One Stop Information Classes    (3X2G)

The above figure represents a conceptual data model, in which each information class is equivalent to Data Description’s Entity. Attributes are not represented in the conceptual data model – however, they are represented in logical data models that are derived from the conceptual data model. Names of relationships between classes are omitted from the above figure below for purposes of simplicity; however, some are generally evident (such as Customer makes-a Reservation).    (3YPE)

DOI used the International Organization for Standardization/ International Electrotechnical Commission (ISO/IEC) 11179 Metadata Registries standard for the metadata attributes that describe its data. ISO/IEC 11179 is a Metadata Registry standard that can be used by implementations based on the DRM to register and represent the metadata describing data within their data assets.    (3YPF)

Using techniques that are standard in data architecture, DOI identified those data subject areas that needed to be shared between business areas of the DOI enterprise. Figure 3-3 depicts one such example involving three “business focus areas” and the citizen. Several information classes shown earlier are evident – for example:    (3X2H)

http://colab.cim3.net/file/work/das/DRM_2.0/Figure_3_3.JPG    (3YPG)

Figure 3-3 DOI Three Business Focus Areas    (3YPK)

Common data and data sharing opportunities were also identified using identified data subject areas as a unifying mechanism across COIs, as shown in figure 3-4:    (3X2L)

http://colab.cim3.net/file/work/das/DRM_2.0/Figure_3_4.JPG    (3YPH)

Figure 3-4 COIs Identified Data Subject Areas    (3YPL)

Logical data models were also developed according to business context, using the FEA BRM. Figure 3-5 is an example of one such logical data model:    (3X2M)

http://colab.cim3.net/file/work/das/DRM_2.0/Figure_3_5.JPG    (3YPI)

Figure 3-5 FEA BRM Logical Data Models    (3YPM)

Figure 3-5 depicts a RECREATION-AREA entity along with various attributes (RECREATION-AREA LEGACY, RECREATION-AREA URL, etc.). Each attribute name is followed by its data type (e.g. “IDENTIFIER”, “TEXT”), and several relationships are shown. For example, the relationship between a RECREATION-AREA entity and a RECREATION-AREA-EVENT entity is depicted at the top right, with the relationship based on a mapping between a RECREATION-AREA identifier and an EVENT identifier.    (3X2N)