Matrix

The purpose of the Application/Data matrix is to depict the relationship between applications (i.e., application components) and the data entities that are accessed and updated by them. Applications will create, read, update, and delete specific data entities that are associated with them. For example, a Customer Relationship Management (CRM) application will create, read, update, and delete customer entity information. The data entities in a package/packaged services environment can be classified as master data, reference data, transactional data, content data, and historical data.

The purpose of the Application Interaction matrix is to depict communications relationships between applications. The mapping of the application interactions shows in matrix form the equivalent of the Interface Catalog or an Application Communication diagram. The Application Interaction matrix is a two-dimensional table with Application Service, Logical Application Component, and Physical Application Component on both the rows and the columns of the table. The relationships depicted by this matrix include: Application Service consumes Application Service Logical App

The purpose of this matrix is to depict the relationship between applications and organizational units within the enterprise. Business operations are performed by organizational units. Some of the operations and services performed by those organizational units will be supported by applications.

The Application/Technology matrix documents the mapping of applications to technology platform. This matrix should be aligned with and complement one or more platform decomposition diagrams. The Application/Technology matrix shows: Logical/Physical Application Components Services, Logical Technology Components, and Physical Technology Components Physical Technology Component realizes Physical Application Component relationships.

The purpose of the Application/Function matrix is to depict the relationship between applications and business functions within the enterprise. Business functions are performed by organizational units. Some of the business functions and services will be supported by applications.

The purpose of the Role/Application matrix is to depict the relationship between applications and the business roles that use them within the enterprise. People in an organization interact with applications.

The purpose of this matrix is to show the organization elements that implement each capability. The Capability/Organization matrix includes the following metamodel entities: Business Capability Value Stream Organization Unit

The purpose of this matrix is to show which actors perform which roles, supporting definition of security and skills requirements. Understanding Actor-to-Role relationships is a key supporting tool in definition of training needs, user security settings, and organizational change management. The Actor/Role matrix shows the following metamodel entities and relationships: Actor Role Actor performs Role relationships

The purpose of the Data Entity/Business Function matrix is to depict the relationship between data entities and business functions within the enterprise. Business functions are supported by business services with explicitly defined boundaries and will be supported and realized by business processes.

The purpose of this matrix is to show the capabilities required to support specific strategy statements.