Skip to main content
Version: 0.7.0

Information object

Definition​

An information object is a business-significant body of information with stable meaning and identity in the model.

Boundaries​

It describes information meaning, not necessarily a table, file, or JSON document. In an early profile, a data name may remain an integration label. A separate object is needed for reuse, ownership, lifecycle, or impact analysis.

Enterprise specializations​

  • Business object — a domain concept, such as Customer case.
  • Data object — its persistent technical representation, such as a CRM record.
  • Message — a transferred representation, such as the CaseCreated event.

A data object or message “represents” a business object.

Minimum characteristics​

  • definition and business meaning;
  • owner;
  • sensitivity or data class where needed;
  • authoritative source when defined.

Relationships​

A process operates on information, and an integration transfers it. Systems can be authoritative sources or consumers through refined relationships.

Example​

INFO-CUSTOMER-CASE is the customer case; in the enterprise profile it has a CRM record and a case-created event as representations.

Common mistakes​

  • treating every field as an object;
  • mixing business meaning with message format;
  • declaring several authoritative sources without a reconciliation rule.