Business Objects: Origins, Definition, 4 Core Traits & Enterprise Architecture Value

Origin of Business Objects

Research shows no clear origin for "Business Object" in international standards or academic systems. Enterprise architecture, data governance, and software engineering literature more commonly reference Business Entity or Business Information without a systematic Business Object definition.

In China, the concept was largely promoted by Huawei and subsequently adopted by many large enterprises in digital transformation and data governance practices, especially at data architecture Layer 3 (L3) where Business Objects serve as a key link connecting business with data, processes with systems.

The closest formal international reference appears in IBM's 2021 documentation for its enterprise integration platform:

Business Objects are logical structures encapsulating business data and metadata, shareable and reusable across modules, used to describe business concepts and their data content. — IBM Official Documentation

This suggests the domestic Business Object concept was inspired by IBM's enterprise modeling and SOA methods, then localized and methodologicalized through Huawei's enterprise architecture and data governance practices, becoming a vital tool for data architecture design and governance implementation.

Definition of Business Objects

Based on Huawei's enterprise architecture methodology, Business Objects are defined as:

Business Objects are abstract representations of core elements—people, events, things, places—with independent significance in the business domain, identifiable and instantiable, serving as bridges between business processes, data governance, and information system design.

Business Objects exhibit cross-layer characteristics in the enterprise architecture system:

In Business Architecture

As abstract representations of core business elements, they depict people, events, things, and places involved in business activities.

They clearly describe inputs, outputs, and key deliverables at each process stage, enabling unified business information expression.

In Data Architecture

Upward : Connect business domains (L1) and subject domains (L2), unifying business language and information boundaries.

Downward : Support logical entities and physical data models (L4/L5), guiding database and information system design.

Horizontally : Bind Data Owners, achieving a "one data one source, one source multiple uses" data governance closed loop.

Business Objects reside at data architecture L3, acting as a critical bridge. This abstraction layer is the core step in transforming business concepts into data assets, providing a standardized foundation for subsequent data modeling, sharing, and governance.

Core Characteristics of Business Objects

Combining Huawei's methodology and international enterprise modeling practice, Business Objects must satisfy four core characteristics across business, data, and system layers:

1. Indispensable People, Events, Things, Places in Business Operations and Management

Business Objects are core units of business operation, identifiable via commercial design and value streams, and aligned with the enterprise business capability framework.

Each Business Object typically has corresponding business processes, organizational management mechanisms, and IT system management capabilities.

Management responsibility for each Business Object must be clear with distinct boundaries to support cross-department and cross-system collaboration.

2. Unique Identity Identification

Every Business Object must have a unique identifier (ID) to accurately distinguish instances.

Unique identification supports precise retrieval and cross-domain referencing , ensuring consistency and sharing capability in distributed environments.

The unique identifier is the foundation for data governance and traceable data asset management.

3. Relative Independence with Attribute Description

Business Objects can exist independently, be acquired, transmitted, used, and generate business value, whereas logical data entities often depend on Business Objects.

They possess lifecycle and state-change characteristics; core identity remains unchanged even as state evolves over time.

Objects may establish association relationships but not subordinate relationships; each must have attributes describing its own characteristics.

In management practice, Business Objects can be split as needed based on management responsibility or business requirements.

4. Generally Master Data and Transaction Data with Concrete Instances

Business Objects must have tangible instances, typically belonging to master data or transaction data.

These objects usually require explicit data definitions, architecture standards, and metric monitoring for effective management.

Report data or pure calculation results are generally not considered Business Objects because they lack independent business value.

Value and Role of Business Objects

In enterprise architecture and data governance practice, Business Objects are the intersection of business, data, and systems .

1. Delineating Business Responsibility Boundaries

Business Objects are the minimum granularity of enterprise data asset management and the natural division unit for business responsibility boundaries.

Through Business Objects, responsibility ownership can be clarified in cross-department, cross-domain data governance, avoiding duplicate construction and information silos.

Unified Business Object definitions help maintain cross-domain information consistency, enabling end-to-end business collaboration.

2. Clarifying Data Ownership

Each Business Object's data instances must have a clear Data Owner (responsible department and specific individual).

Binding Business Objects to Data Owners establishes a traceable governance mechanism, supporting the "one data one source, one source multiple uses" data management goal.

This mechanism is a key foundation for moving data governance from institutionalization to operationalization and auditability.

3. Guiding IT System Design

Business Objects are core units for logical data models and service-oriented design:

Through Business Object modeling, natural alignment between business and systems is achieved, improving reusability and consistency of information system construction.

Reference:

https://www.ibm.com/docs/zh/mfci/7.6.2?topic=structure-business-objects