Data Interoperability Lectures & Workshops

The Data Interoperability Workshops are a significant addition to the Data Interoperability Lectures. Section 10 in the lectures course forms the overall process flow for achieving interoperable data environments. In this Workshops version of the course, the workshops apply this overall process flow and students actually create a working model of data interoperability by researching a case-study, understanding and determining areas of shared data, building models about the shared data, and then generating an actual database schema of that shared data. Back home, students are then able to immediately put their learning and practice to work. The workshops are described in the following table.

Data Interoperability Workshops



Identify the set of missions that frame the essence of the enterprise. The collection of missions should be the business, no fewer and no extra.



Identify and describe the organizations of the enterprise charged with executing the missions.



Completely assign organizations to missions, and functions to mission-organizations so that all areas of the enterprise are addressed. There should be no useless organizations or any undone missions.



Identify and describe the functions of the enterprise charged with executing the missions within the context of enterprise organizations. There may be multiple versions of the same functions because of style reasons.



Completely assign organizations to missions, and functions to mission-organizations so that all areas of the enterprise are addressed. There should be no uncovered mission, organizations and functions.


Database Domains

Identify and describe the data intensive areas necessary to fulfill the missions of the enterprise. Every mission must have at least one database domain. These lead to the discovery of data elements, tables, and database objects. Connect data to missions.


Database Objects

Identify the non-redundant set of database objects from across a set of "nouns" within the database domain diagrams. Database objects have tables, columns, states and processes. These are the data transformers of the enterprise.


Information Needs

Identify every key information need within mission area and fully describe each. These link the actual databases and information systems to the missions-organizations and functions.


Resource Lifecycle Analysis

Identify, describe, and determine the life cycles for the critical resources of the enterprise. Resources are what define the enterprise. Resource life cycles transform the enterprise. Databases and information systems are the agents of changes and materialize the information needs required to satisfy missions.


Data Elements Workshop

Identify, analyze, and record data elements that have surfaced through database domains, information needs, etc., analysis. Data elements are employed throughout data models in define-once, use many-times constructs.


Specified Data Model

Identify, analyze, and record data model templates that can be commonly used across data models. These templates support standardized data structures and processes across database schemas in support of building interoperable database designs.


Implemented Data Model

Create a database schema from one or more specified data model templates to meet the need of one or more business information systems. These form the set of all database data models in the enterprise independent of how they are physically deployed.


Operational Data Model

Create from implemented data models or import SQL schema from one or more legacy databases. These models are those that actually operate against business information systems through views in support of creating and modifying corporate memory.


View Data Models

Create a data exchange specification between a business information system and a database schema. These are the bridge between data and process models. Views enable data renaming, virtual data creation, and the formation of XML schemas for technology independent data exchanges.


Business Information Systems

Identify, describe, and specify business information systems, and then specify view data models as interfaces to operational data models.


SQL Generation and Application Generation

Generate a SQL schema for a particular specified, implemented, and operational data model. Import into the ER Modeler, DeZine, and display the data model. Export the model and re-import into the metabase.


Forward Engineering

Create an operational data model schema and DDL from existing metadata. This enables the creation of new database designs from existing metadata. More of the define once, use many times strategy.


Reverse Engineering Workshop

Create an interoperable data model from a collection of legacy database schemas. Create supporting upper levels of specified data models and/or data element models. Generate an operational data model and schema DDL of the interoperable data model.


For Sales and Corporate: 1-301-249-1142

Whitemarsh Information Systems Corporation

 Bowie, Maryland 20716 USA

Copyright 1981 - 2020 Whitemarsh Information Systems Corporation
Proprietary Data, All rights Reserved