With this catalog, users could query the object classes as deeply as they were disaggregated/categorized.
The software unit controlling an object's transactions would be accessible through the catalog, as would the detailed attributes of each enterprise object (either shared data or object-specific data).
The TEMM Catalog would serve as a Table of Contents to the enterprise management environment.
The DEMIS uses each software unit, an object, to process a specific transaction within an activity. This reduces the need for complex, multilevel menus for functional processes, work centers, and tasks. The TEMM Catalog guides the user to the transaction. The DEMIS provides standardized and shared software units among activities. Thus, transaction modeling and development of software are simpler. The reliance on large software design projects would diminish. We can apply object-oriented programming techniques to software units, modularizing down to the transaction level.