A logical view of the Profile function would look something like this. To create associations, we select a base object from the Catalog. The Profile uses what is now known as "star" and "snowflake" database schema.

Then we use the Catalog to select those objects directly associated with the base object. Thus, a position incumbent or a planner defines an object's composition and distribution by picking associated objects from the Catalog. The users could then ask the basic questions about them or combinations of them. We could establish electronic conferencing and other forms of involving and coordinating based on these associations.

The detail attributes that describe the association would be accessible through the Profile, as would the standard software unit for associated Activity objects. Using an object-oriented programming method, each software unit would also be an object in the DEM Catalog and Profile.

We can dynamically adjust the data elements associated with software systems, databases and tables, forms, publications, reports, spreadsheets, graphics, etc., from one data dictionary/glossary. We would know in advance those items effected by a change, to their degree of inclusion in the enterprise model.

This page was last updated on September 20, 1998
Please send comments or questions to roy.e.roebuck(AT)one-world-is.org.