Skip to content
Software Architecture Guide

Data Entity/Business Function Matrix

Explanation

Section titled “Explanation”

A Data Entity/Business Function Matrix maps logical data entities to core business functions. A logical data entity is a kind of business data, such as a customer or an order. The article “Logical Data Model” explains the term further.

Each cell of the matrix uses CRUD designations. CRUD stands for create, read, update and delete. A cell tells you what a function does with an entity.

Teams also use CRUD matrices to check consistency. The matrix captures how functions use data. That record becomes a model against which the data can be checked.

The matrix helps find entities that more than one role creates. Guidance for the CA Gen tool suggests two responses:

  • Decide which single role should own the entity type.
  • Split the entity type so that each role owns one part.

Either way, the matrix makes the question visible. Without it, nobody may notice that two roles both create the same data.

Example

Section titled “Example”

Imagine a small company with three functions: Sales, Finance and Support. The rows are Customer and Invoice.

In the Customer row, Sales shows C and U. Support shows C and R. Finance shows R.

Two functions create customers. That is a signal to ask who should own the Customer entity. The team could name Sales the owner. Or it could split customers by role, for example sales customers and support contacts.

Checks

Section titled “Checks”
  • Each entity in the matrix is linked to business functions using CRUD codes.
  • Where several roles create the same entity, the document names one owner or describes a split by role ownership.
Section titled “Related”

Sources

Section titled “Sources”