In layman's terms, architecture is the organized design of component elements to optimize the functionality, performance, feasibility, cost, and user experience of the entire structure or system.

ISO defines architecture as "the basic structure of a system, embodied in the components that make up the architecture, the interrelationships between the components, and the principles that govern its design and evolution."

Architecture design work is usually carried out within different scopes of the organization (enterprises, business lines, projects, etc.) and at different levels of the information system (infrastructure, application architecture, data architecture, etc.)

business structure

Technology Architecture

data architecture

Application architecture

It is the basis of data management

Target

component

member

Data architecture design document

Build a smooth bridge between business strategy and technology implementation

Leverage the business advantages brought by new technologies to strategically help organizations quickly change products, services and data

Translate business requirements into data and application requirements to ensure that valid data can be provided for business process processing

Ensure business and IT technology are aligned

Manage complex data and information and deliver it across the enterprise

Provide support for enterprise reform, transformation and adaptability

Data storage and processing needs

Design a structure and plan that meets the enterprise's current and long-term data needs

Define the current state of data in your organization

Provides a standard business vocabulary for data and components

Ensure data architecture is consistent with corporate strategy and business architecture

Describe the organization's data strategy needs

High-level data integration outline design

Integrated Enterprise Data Architecture Blueprint

Use data architecture components (master blueprint) to define data requirements, guide data integration, manage data assets, and ensure that data project investments are consistent with corporate strategy

Work with, learn from and influence stakeholders involved in improving business and IT system development

Build an enterprise data language through data architecture and common data vocabulary

business structure

Technology Architecture

data architecture

Application architecture

In addition to being committed to their own architecture design and implementation work, different types of architects must also understand the architectural requirements that are closely related to them, because each architecture does not exist in isolation and either affects other architectures or is subject to other architectures.

Architectural frameworks provide a way of thinking about and understanding architecture. They represent an overall "architecture of architectures"

The most famous enterprise architecture framework is the Zachman Framework developed by John Zachman

Zachman framework

Data architecture defines standard terminology and design of elements important to an organization

The design of enterprise data architecture includes business data description, such as data collection, storage, integration, movement and distribution

Enterprise data architecture description must include enterprise data model (such as data structure and data specification) and data flow design

Enterprise data model

Data flow design

If the architecture is not properly managed, it will slowly become damaged. The system will gradually become more complex and less scalable, thus posing risks to the organization.

A quality-oriented approach is consistent with traditional data architecture work, where architectural quality is accomplished incrementally

Architectural tasks are broken down into projects, performed by architects or delegated projects

Usually architects need to master the overall architecture and make continuous investment in governance, standardization, and architecture development as long-term goals.

Use innovative technology and data to drive innovation

Often no exhaustive considerations are required, and business logic and cutting-edge technologies that have not been extensively proven can be applied

This approach often requires the architect to liaise with IT professionals in the organization who lack interaction

Roadmaps help organizations measure and develop solid project plans that align with business needs and opportunities, external requirements, and available resources.

Organizational data architecture using data models and their related specifications must be flexible enough to adapt to future needs

Building an architecture-level data model should not only have an overall view of the enterprise, but also have a definition that can be fully understood within the enterprise.

Activity

Products to be deployed in the next 1 to 2 years

Products to be deployed in the next two years

It is necessary to follow the principles of minimizing interference and maximizing useful information.

Clear and consistent instructions

All chart objects match the description object

Clear and consistent line direction

Consistent crosshatch display method

Consistent object properties

linear symmetry

such as enterprise data models, enterprise-wide data flows, and roadmaps

Lack of management support

Lack of trust from managers

Incorrect decisions by management

Lack of evidence of success

Lack of experienced project managers

cultural shock

single dimensional perspective