Enterprise Architecture Research Summary (23) -- Technical Architecture stage of togaf architecture development method (Adm)

Source: Internet
Author: User
Technology Architecture 1.6)

Various Stages of Enterprise Architecture Development-Technical Architecture

1.6.1 Objectives

The purpose of the technical architecture construction phase is to map various application components defined in the application architecture into corresponding technical components, these technical components represent various software and hardware components that can be obtained from the market or within the Organization. Because the technical architecture defines the physical implementation of the architecture solution, it is strongly associated with implementation and migration planning. The technical architecture defines the baseline and target view of the technical portfolio, as well as a detailed evolution roadmap from the baseline architecture to the target architecture, and identifies key work packages in the transition process. The technical architecture is the last step to develop a collection of Architecture Information (including business architecture, information system architecture, and Technical Architecture). Therefore, it supports cost assessment in specific migration scenarios.

1.6.2 Method

In the activities of the current phase, the architecture team should consider whether there are available resources related to the technical architecture in the architecture resource library, especially the following resources:

  • Existing IT services recorded in the IT resource library or IT service catalog.
  • TOGAF Technical Reference Model (TRM ).
  • The general technical model of the organization's industry.
  • Technical models related to general system architectures, such as The reference model for integrating information infrastructure in The Open Group (III-RM ).
1.6.3 Input and Output

The input materials required in the current phase and the deliverables output in this phase are summarized as follows:

Input

Inbound

References

Architecture references

Product Information of candidate products

Non-Intrusive Input

Architecture work requirements

Capability Evaluation

Communication Plan

Intrusive Input

Enterprise Architecture organization model, including:

  • Scope of affected organizations
  • Maturity evaluation, gaps and solutions
  • Roles and responsibilities of the Architecture Team
  • Constraints on architecture work
  • BUDGET REQUIREMENTS
  • Governance and support policies

Customized architecture frameworks, including:

  • Customized architecture Method
  • Customized architecture content (deliverables and products)
  • Configuration and deployment tools

Technical Principles

Architecture statement of work passed

Architecture Vision

Architecture resource library, including:

  • Reusable Building Blocks
  • Public and available reference models
  • Organization-specific reference model
  • Organization standards

Draft Architecture Definition document, including:

  • Baseline Service Architecture Version 1.0
  • Baseline Technical Architecture version 0.1
  • Baseline data architecture Version 1.0
  • Baseline application architecture Version 1.0
  • Target Business Architecture Version 1.0
  • Target Technical Architecture version 0.1
  • Target Data Architecture Version 1.0
  • Target application architecture Version 1.0

Draft architecture requirements, including:

  • Result of Gap Analysis
  • Technical requirements from previous stages

Business, data, and application architecture components of the Architecture Roadmap

Input

Output

Deliverables in the improved and updated Architecture Vision phase, including:

  • Architecture work instruction (modify if necessary)
  • Proven technical principles or new technical principles (if any)

The updated draft Architecture Definition document includes:

  • Baseline Technical Architecture Version 1.0
  • Target Technical Architecture Version 1.0
    • Various technical components and their relationships with information systems
    • Technical platforms and Their deconstruct
    • Environment and location
    • Expected processing load and load distribution between technical components
    • Physical (network) Communication
    • Hardware and network description
  • Various views from the perspective of stakeholders

Updated architecture requirements draft, including:

  • Result of Gap Analysis
  • Requirements output from the Business Architecture and Information System Architecture phase
  • Updated technical requirements

Technical Architecture components of the Architecture Roadmap

Step 1.6.4

The steps to be performed in the current phase are summarized as follows:

  • Select reference models, perspectives, and tools
  • Development baseline technical architecture description
  • Development target technical architecture description
  • Perform Difference Analysis
  • Define roadmap Components
  • To clarify and solve the impacts of the entire architecture landscape
  • Conduct formal stakeholder review
  • Final Technical Architecture
  • Create Architecture Definition document

Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: info-contact@alibabacloud.com and provide relevant evidence. A staff member will contact you within 5 working days.

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

  • Sales Support

    1 on 1 presale consultation

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.