Phase C - Information Architecture

Information Structure Viewpoint

Examples

Effort small

Effort medium

Effort large

Architecture Phase

Artefact type

TOGAF Phase

Project Phase

Logical Architecture (Master Solution Architecture)

Related workpackage

Data Migration Diagram

admin — Tue, 02 May 2023 01:34:24 +0000

Data Migration Diagram admin Tue, 05/02/2023 - 01:34

Archimate

Data Migration Viewpoint

Mandatory

Security related?

This diagram shows how data is extracted from baseline or source location(s) and loaded into target location(s). It may show where data is transformed and/or cleansed on the way. In Phase C of the ADM, the diagram is likely to be at an overview level. Later, it may be elaborated to show which source data items map to which target data items.

Deliverable Section

Examples

Data Migration Viewpoint

Effort small

Effort medium

Effort large

Architecture Phase

Physical

Artefact type

TOGAF Phase

Project Phase

Physical Architecture (Master Solution Architecture)

Related workpackage

Data Lifecycle Diagram

admin — Tue, 02 May 2023 01:34:24 +0000

Data Lifecycle Diagram admin Tue, 05/02/2023 - 01:34

Archimate

Data Lifecycle Viewpoint

Mandatory

Security related?

Yes

The Data Lifecycle diagram is an essential part of managing business data throughout its lifecycle from conception until disposal within the constraints of the business process. The data is considered as an entity in its own right, decoupled from business process and activity. Each change in state is represented on the diagram which may include the event or rules that trigger that change in state. The separation of data from process allows common data requirements to be identified which enables resource sharing to be achieved more effectively.

Deliverable Section

Examples

Data Lifecycle Viewpoint

Effort small

Effort medium

Effort large

Architecture Phase

Artefact type

TOGAF Phase

Project Phase

Logical Architecture (Master Solution Architecture)

Related workpackage

Data Dissemination Diagram

admin — Tue, 02 May 2023 01:34:24 +0000

Data Dissemination Diagram admin Tue, 05/02/2023 - 01:34

Archimate

Information Structure Viewpoint

Mandatory

Yes

Security related?

Yes

The purpose of the Data Dissemination diagram is to show the relationship between data entity, business service, and application components. The diagram shows how the logical entities are to be physically realized by application components. This allows effective sizing to be carried out and the IT footprint to be refined. Moreover, by assigning business value to data, an indication of the business criticality of application components can be gained. Additionally, the diagram may show data replication and application ownership of the master reference for data. In this instance, it can show two copies and the master-copy relationship between them. This diagram can include services; that is, services encapsulate data and they reside in an application, or services that reside on an application and access data encapsulated within the application.

Deliverable Section

Information Structure Viewpoint

Examples

Effort small

Effort medium

Effort large

Architecture Phase

Physical

Artefact type

TOGAF Phase

Project Phase

Physical Architecture (Master Solution Architecture)

Related workpackage

Application/Data Matrix

admin — Tue, 02 May 2023 01:34:24 +0000

Application/Data Matrix admin Tue, 05/02/2023 - 01:34

Archimate

n/a

Mandatory

Yes

Security related?

Yes

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. Applications that operate on the data entities include transactional applications, information management applications, and business warehouse applications. The mapping of the Application Component-Data Entity relationship is an important step as it enables the following to take place: Assign access of data to specific applications in the organization Understand the degree of data duplication within different applications, and the scale of the data lifecycle Understand where the same data is updated by different applications Support the gap analysis and determine whether any of the applications are missing and as a result need to be created The Application/Data matrix is a two-dimensional table with Logical Application Component on one axis and Data Entity on the other axis.

Deliverable Section

Effort small

Effort medium

Effort large

Architecture Phase

Artefact type

Matrix

TOGAF Phase

Project Phase

Logical Architecture (Master Solution Architecture)

Related workpackage

Logical Data Diagram

admin — Tue, 02 May 2023 01:34:24 +0000

Logical Data Diagram admin Tue, 05/02/2023 - 01:34

Archimate

Information Structure Viewpoint

Mandatory

Yes

The key purpose of the Logical Data diagram is to show logical views of the relationships between critical data entities within the enterprise. This diagram is developed to address the concerns of: Application developers Database designers

Deliverable Section

Information Structure Viewpoint

Examples

Effort small

Effort medium

Effort large

Architecture Phase

Artefact type

TOGAF Phase

Project Phase

Logical Architecture (Master Solution Architecture)

Related workpackage

Conceptual Data Diagram

admin — Tue, 02 May 2023 01:34:23 +0000

Conceptual Data Diagram admin Tue, 05/02/2023 - 01:34

Archimate

Information Structure View

Mandatory

Yes

Security related?

Yes

The key purpose of the Conceptual Data diagram/Information Structure View is to depict the relationships between critical data entities within the enterprise. This diagram is developed to address the concerns of business stakeholders. Refer to DoE Conceptual Information Asset Model (16/489129) and develop project specific view. This view also needs to be included as part of the Information Security Assessment (ISA)

Deliverable Section

1.3.6 Architecture Summary

Examples

Information Structure View

Effort small

Effort medium

Effort large

Architecture Phase

Conceptual

Artefact type

TOGAF Phase

Conceptual Architecture (Master Solution Architecture)

Project Phase

Scope

Related workpackage

Data Entity/Business Function Matrix

admin — Tue, 02 May 2023 01:34:23 +0000

Data Entity/Business Function Matrix admin Tue, 05/02/2023 - 01:34

Archimate

n/a

Mandatory

Security related?

Yes

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 mapping of the Data Entity-Business Function relationship enables the following to take place: Assign ownership of data entities to organizations Understand the data and information exchange requirements business services Support the gap analysis and determine whether any data entities are missing and need to be created Define application of origin, application of record, and application of reference for data entities Enable development of data governance programs across the enterprise (establish data steward, develop data standards pertinent to the business function, etc.) The Data Entity/Business Function matrix shows the following entities and relationships: Data Entity Business Function Data Entity relationship to owning Organization Unit

Deliverable Section

1.3.6 Architecture Summary

Effort small

Effort medium

Effort large

Architecture Phase

Conceptual

Artefact type

Matrix

TOGAF Phase

Conceptual Architecture (Master Solution Architecture)

Project Phase

Scope

Related workpackage

Data Entity/Data Component Catalog

admin — Tue, 02 May 2023 01:34:23 +0000

Data Entity/Data Component Catalog admin Tue, 05/02/2023 - 01:34

Archimate

n/a

Mandatory

Yes

This catalog identifies and maintains a list of the data used across the enterprise, relating data entities to data components showing how data entities are structured. Its purpose is to: Identify all data used in the enterprise Encourage effective data use The Data Entity/Data Component catalog contains the following metamodel entities: Data Entity Logical Data Component Physical Data Component

Deliverable Section

Effort small

Effort medium

Effort large

Architecture Phase

Artefact type

Catalogue

TOGAF Phase

Project Phase