TOGAF (Enterprise Architecture)

TOGAF core concept (official original version)

What is TOGAF?

TOGAF® is a proven enterprise architecture methodology and framework used by the world's leading organizations to improve business effectiveness. It is an enterprise architecture standard that ensures consistency in standards, methodologies, and communications among enterprise architecture professionals so that we can perform enterprise architecture work in a better way, including:

Iterative process model supported by best practices

A reusable set of existing architectural assets

Methods and tools for planning, developing, implementing and maintaining enterprise architecture

What is enterprise architecture?

Enterprise Architecture (EA) is a well-defined practice for consistently using a holistic approach to enterprise analysis, design, planning, and implementation to successfully develop and execute strategy. Enterprise architecture applies architecture principles and practices to guide the business processes, data and information, and technology changes an organization needs to execute its strategy. These practices leverage all aspects of the business to identify, inspire and enable these changes, including working to understand the strategic intent of the business and then owning everything from business processes to supporting technology, partnerships, various infrastructures, recruiting and training, and more important work to achieve better business performance.

TOGAF 4 cores (4A architecture)

  • Business architecture (business architecture looks at processes [capability main line])
    description: business strategy, governance, organization and key business processes.
    L2 level, cross-department and cross-role. Horizontally across stages, vertically across roles.
  • Data architecture (see sharing for data architecture)
    description: the structure of the organization's various logical and physical data assets and data management resources.
    Scattered resources are called resources, unified assets are called assets, and empowerment is called capital.
    The value of data architecture: Lead data assets to form data capital through data architecture.
  • Application architecture (see integration for application architecture)
    description: A blueprint that describes the individual application systems being deployed, the interactions between systems, and their relationships with the organization's core business processes.
    Applications need to be integrated, and the era of standalone software is over.
    Integrated approach: bus/microservices.
    Traditional enterprises (steady-state business): use buses.
    Internet (sensitive business): use microservices.
  • Technical architecture (technical architecture depends on the platform)
    description: logical software and hardware capabilities necessary to support the deployment of business, data and application services. Including IT infrastructure, middleware, network, communications, deployment processing and some standards.
    Future information technology public platform system.
    In the past, technical routes were used to form a standardized technical environment.
    Technology platforms are now used to form a standardized technology environment.
    Build a platform/set standards/upload applications/pass data.

Guess you like

Origin blog.csdn.net/leesinbad/article/details/127658138