Search keyword in element

Applying Business Object Model (BOM) to (operational) source applications

- master and reference data must comply with the BOM. - Transactions must comply with the BOM, which concerns the granularity of quantities and frequencies (time aspect). - Interpretation of source data according to BOM definitions​

Architecture

Abstract business object for different types of specialized architectures. The architecture is thereby enriched with a number of sub-dimensions.

Business Object

Naming Conventions Usage: Singular noun. For example: Invoice, policy, Fault report Logical name. Avoid technical names.

Object model Building blocks

The object model describes the building block concept as defined within the architectural process. Building blocks are communicative concepts between architects themselves and between architecture and the various stakeholders such as developers and administrators. In addition, also internal services and possibly external stakeholders such as suppliers or chain partners. The model consists of a limited set of concepts with mutual relationships. This model has been developed into an ArchiMate business object diagram. The concepts in the objects and definition diagram are then worked out in detail and thus describe the frameworks of the building blocks.

Role-Business Object-Matrix

Business object model

Overview of the business objects relevant when working with an architecture repository. A brief definition is given for each business object in the description.

Convention conceptual datamodel

This diagram is a viewpoint for developing a conceptual data model. This viewpoint indicates which types of object types and connector types can be used when drawing up a conceptual data model. A few principles apply to the conceptual data model:
  • Conceptual data model is for multiple stakeholders (including non-ICT professionals) and should be simple in design.
  • Conceptual data model has been developed in ArchiMate (business layer).
  • Only the stereotypical Business Object is used for the conceptual data model.
  • The conceptual model has a hierarchical structure based on domains.
  • If this reduces the complexity, multiple diagrams can be created for a domain.
  • The conceptual model is related to the logical data model. See the hybrid meta data model for this.
  • The conceptual model can be related to, for example, the other data management business functions within Example.

Detail business process architecture modeling

In the detail of the business process for architectural modeling, a number of connections are made clear. Which business objects are relevant to this process (in both reading and writing), which roles are involved in this detailed process.

Object model Building blocks

The object model describes the building block concept as defined within the architectural process. Building blocks are communicative concepts between architects themselves and between architecture and the various stakeholders such as developers and administrators. In addition, also internal services and possibly external stakeholders such as suppliers or chain partners. The model consists of a limited set of concepts with mutual relationships. This model has been developed into an ArchiMate business object diagram. The concepts in the objects and definition diagram are then worked out in detail and thus describe the frameworks of the building blocks.