Conceptual Object Model
The Conceptual Object Model forms the starting point of the 3-level Data Management approach. When introducing the architectural 5 levels – defining the Presentation layer, the Process layer, the Business Activity layer, the Integration layer and the persistence or Data layer – the design of the Business objects used in activities should also be separated from the Data Objects in the layer in order to reach the highest flexibility and agility.
Problems and Solutions
Often a Conceptual Object Model, in the Enterprise Architects terms, is not in use. However, in order to define the Business Objects for the business activities and optimize the quality and quantity of the Business Objects Enterprise Architects uses Enterprise Objects in the Conceptual Object Model. Each Business Object of the Logical Model that modelers develop must be presented as a specialization of one Enterprise Object of the Conceptual Object Model.
This means that an omission of the Conceptual Object Model and its Enterprise Objects often results in a very difficult to maintain the Logical Object Model with an overload of different Business Objects, with different names, synonyms, but the same usage. This is specifically the case when
- A Service Oriented Architecture is used
- A lot of CotS (Commercial of the Shelf) information systems or packages are used, all with their own Data Objects in their Physical Object Models
- Resulting in a Master Data Management becomes more complex than necessary
Tools to support Conceptual Object Modeling
The following tools support the Proposition Modeling:
||designing the Conceptual Object Model|
||mapping objects from Business (Logical model) to Enterprise (Conceptual model) Objects as specializations|
Advantages of the Enterprise Architects approach
Initially, with a good Proposition Model, the components of the Proposition Model can be used to define a large part of the Conceptual Object Model. As the components of the Proposition Model are applicable on most organizations it will be clear that at the conceptual level the Conceptual Object Models of many organizations look the same, although different names are often used for the same Enterprise Objects.
- Enabling an optimized Logical Object Model in terms of quality and quantity through data mapping each Business Object on an Enterprise Object
- The SAFe™ Core Values are safeguarded and improved as follows
- 2.1 Alignment
- 2.2 Built-in Quality
- 2.3 Transparency
- 2.4 Program Execution