Wondershare EdrawMind
MindMap Gallery TOGAF9.2 Enterprise Architecture Planning and Design Reading Notes 2 Mind Map
- 31
TOGAF9.2 Enterprise Architecture Planning and Design Reading Notes 2 Mind Map
TOGAF9.2 Enterprise Architecture Planning and Design reading notes, architecture design principles: first determine the relationship, then determine the content, architecture design steps: make assessments, draw blueprints, find routes, and strengthen control.
Edited at 2023-10-25 11:08:07
- bacteria
This is a mind map about bacteria, and its main contents include: overview, morphology, types, structure, reproduction, distribution, application, and expansion. The summary is comprehensive and meticulous, suitable as review materials.
- Plant asexual reproduction
This is a mind map about plant asexual reproduction, and its main contents include: concept, spore reproduction, vegetative reproduction, tissue culture, and buds. The summary is comprehensive and meticulous, suitable as review materials.
- Reproductive development of animals
This is a mind map about the reproductive development of animals, and its main contents include: insects, frogs, birds, sexual reproduction, and asexual reproduction. The summary is comprehensive and meticulous, suitable as review materials.
TOGAF9.2 Enterprise Architecture Planning and Design Reading Notes 2 Mind Map
- bacteria
This is a mind map about bacteria, and its main contents include: overview, morphology, types, structure, reproduction, distribution, application, and expansion. The summary is comprehensive and meticulous, suitable as review materials.
- Plant asexual reproduction
This is a mind map about plant asexual reproduction, and its main contents include: concept, spore reproduction, vegetative reproduction, tissue culture, and buds. The summary is comprehensive and meticulous, suitable as review materials.
- Reproductive development of animals
This is a mind map about the reproductive development of animals, and its main contents include: insects, frogs, birds, sexual reproduction, and asexual reproduction. The summary is comprehensive and meticulous, suitable as review materials.
- Recommended to you
- Outline
#7033 TOGAF9.2 Enterprise Architecture Planning and Design
1.0 Introduction: Digital Transformation and Enterprise Architecture
1.1 The rules of enterprise digital development stages
1.2 The overall connotation of enterprise digital development
1.3 The top-level design role of enterprise structuring
1.4 How to carry out digital architecture work
1.5 The process of digital top-level design
2.0 Enterprise Architecture Standards
2.1TOGAF9.2 Overview
Architectural design principles: first determine the relationship, then determine the content
Architecture design steps: evaluation, blueprint drawing, route finding, and strong control
Enterprise architecture standards: concept, method, technical guidance, type, continuous examination, ability
Enterprise: a cross-functional, cross-business, cross-region, and cross-system complex organization
1. Enterprise structure
(1) Four cultures: acceptance, creation, use and maintenance
(2) Two practices: iteration and reuse
2. Architecture = components, component relationships, governance (principles, strategies, evolution)
3. The meaning of the four major structures:
Business architecture defines interaction (division of labor)
Data architecture definition sharing (classification, standards)
Application architecture customization integration (partitioning)
Technical architecture support (public support: platform infrastructure)
enterprise architecture
a blueprint
One purpose: guiding business optimization
(1) Guide the design as a whole and aggregate fragmented processes
(2) How to respond quickly when local business changes rapidly (capability-oriented planning method: goal--capability--composition--implementation)
2.2ADM architecture development method
Architecture development method: One preparation, one center, eight steps and one method
One preparation: preparation at the top level (consensus)
Preparatory stage
Finding consensus: environment and deliberative mechanism (democracy or autocracy)
To commit to: resources
Setting principles: business driven, unified standards
Tailoring: Architecture deliverables (actually it is impossible to cut at this stage, it is all iterated in the process)
Output: Architecture request document (project application letter)
One center: demand-centered (what business problem the architecture ultimately solves)
Eight steps:
(1) Vision A sets goals: what kind of business capabilities should be created (summary)
(2) Architecture definition capabilities: capability requirements (just a blueprint, not implementation)
B business interaction: business division of labor (components), business collaboration (process)
C application integration: system division of labor (function), system integration (interface)
C data sharing: data definition, classification, sharing
D technical support: platform infrastructure
Gap = target architecture (future tobe) - baseline architecture (current situation asis)
(3) E. Implementation plan (Gap-->Plan), F. Migration route finding (roadmap)
(4) G governance ensures (implemented compliance) and H changes become the norm
2.2.3 Demand management
Requirements Management: Project Long-Term (Iterative Process)
Architecture development is driven by demand, and demand is driven by business
Demand mining: one relies on asking (research), the other relies on pushing (reverse value marketing)
2.2.4 Architecture Vision Phase
(Test points below)
Vision sets goals: what kind of business capabilities should be created (gathering and sharing, summarizing the vision)
Output: Architecture work statement (project implementation plan)
(1) Vision: It can be expressed with a rough architecture diagram (four major architectures)
XX (2) Business scenario technology: used to clarify requirements (prototype method: flow chart)
(3) Stakeholders: What to pay attention to and communicate well
XX (4) Business transformation readiness assessment: whether you are ready for change (for example: solving consensus issues) --> Assessment model
Business transformation readiness assessment--->Risk (Risk assessment-->Risk response strategy formulation-->Risk response-->Residual risk elimination)
Scenario: Senior management expresses concerns about the implementation of enterprise architecture and considers using "Business Transformation Readiness Assessment" technology to solve it
Gather and share, define the vision (expressed in a rough architecture diagram), and determine the scope (plan: architecture work statement)
How to build consensus: use business scenario method to describe (prototype method) and use visual communication (rough architecture diagram)
2.2.5.0 Review of the first day of course
2.2.5 Business architecture defines interaction
(1) Connotation: Guided by business strategy, describe the operation of the business from an overall perspective
(2) Dimension: Target division of labor (business functions/components) Collaboration (process, service)
(3) Business architecture design steps: impression
(4) Three forms/architecture expressions of views: directory (list) matrix (two-dimensional relationship) graph
(5) Value stream
Example--Insurance company business: Market management-->Product R&D and management-->Business development-->Insurance and underwriting-->Post-insurance and claims settlement (Level 0 process, value stream)
End-to-end: closed loop, from receiving requirements to satisfying requirements
(6) Business architecture design: first find the main value stream (end-to-end), and then sort out the corresponding management, control and support system
2.2.6 Information system architecture
Information system architecture = application architecture data architecture
Data schema configuration sharing: Share Type Source ...
Data architecture design steps: impression
Data architecture elements: data domain/subject domain view (first-level classification), data subject (second-level classification), data entities, data flow relationships
Application architecture definition integration: application/function division integration relationship
Application/function: derived from business functions (consistent with business architecture)
2.2.7 Technical architecture
D technical architecture design support (container): infrastructure (computing, storage, network) public platform (middleware)
General modes: left standard, right safety, lower facility, upper platform
Requirements: The technical architecture must meet the requirements from business, data, and applications.
Technical Reference Model: TRM
2.2.8 Opportunities and Solutions
E landing plan:
(1) Determine projects (integrate BCD gaps and remove duplicates), group them (project groups), determine methods (outsourcing or self-made), determine priorities (value and cost), determine dependencies, and determine transition structure
(2) Success factors: people (willingness of key roles), things (don’t reinvent the wheel, integrate with the status quo), business value (appropriate sacrifice of technical attributes, make compromises)
(3) Output:
Transition architecture: Corresponding to milestones (business value), the intermediate state of the architecture
Implement the migration plan (high-level, initial version)
(4) ABB (Architecture Building Blocks) -->SBB (Solution Building Blocks)
2.2.9 Migration planning
F migration route
(1) Further confirm the previous stage of work: determine priorities (value * risk * cost), determine dependencies, determine resources, and determine the transition structure (business value allocation)
Outputs: Implementation of migration plan (formal) Architecture contract (architectural requirements)
2.2.10 Implement governance
Governance as a guarantee
(1) Goal: Ensure the consistency of projects and architecture, and the consistency of IT and business
(2) Basis (Architecture Contract: Generated in Phase F) Means (Compliance Review: Checklist) Governance Object (Project or Sub-Architecture)
(3) Four elements of governance: organization, system/process, assessment tool
2.2.11 Architecture change management
F Architecture changes become normal: ensure that the architecture responds to business changes (follows the normal change process) and realizes business value
3.0 Chapter 3 ADM Architecture Development Wizard and Best Practice Technology
Techniques (32 practical techniques) Guidance (4 types of wizards: iteration, tailoring, scope, guidance)
3.1Key points of ADM
four guides
1. Cutting
1. Tailoring: ADM is universal and needs to be tailored to meet the needs of the enterprise. The sequence of stages is adjusted:
(2) Adjust according to corporate/business principles
1) Requires the use of mature business suites to quickly respond to business. Determine the information system architecture/technical architecture first, and then determine the business architecture.
(1) Adjust according to whether there are structured assets
1) There is no accumulation before (no business cases), set the vision first, and then determine the detailed structure (use willingness to build consensus and organize everyone to define the detailed structure) --> Goal first
2) There is previous accumulation (with business cases), baseline first, then goals, and iterative development on this basis
(3) Consider adjusting ADM for compatibility with other frameworks
2. Scope (division)
(1) Dimensions:
Breadth (business, application, data, technology)
Depth (strategic architecture - long-term summary view, segmented architecture, capability architecture: incremental, transitional architecture)
Length: Timeline
3. Iteration: overall iteration, local iteration, single iteration
Baseline first (bottom-up): unclear goals and rich architectural assets
Goals first (top-down): strategic goals are clear; leaders do not want past practices to continue into the future
4. Guidance
(1) Guide security architecture design: security architecture design requirements come from four major architectures
(2) Guide SOA design: guide service design with four major architectures (business interaction-->business services)
3.2 List of 32 best practice technologies
Cutting in the preparatory stage
3.3 Detailed explanation of 32 best practice technologies
superior
Principle: Define as early as possible in the preliminary stage
Three levels: enterprise principles/IT principles/architectural principles
Four contents: the name should be clear, the statement should be unambiguous, the value should be based on the basis, and the conflict should be based on the impact.
Five standards: easy to understand for users, robust for complex, complete for coverage, consistent for conflicts (safety and convenience), stable for changes
Principle example: roughly understand the meaning (select corresponding principles in simulated scenarios during the exam)
Schema Repository: Database
Architecture work request (preparatory stage): analogous to Party A’s project application
Architecture work statement (Phase A): Analogous to the project plan submitted by Party B
Architecture definition document (qualitative view) Architecture requirements specification document (quantitative standard)
Gap Analysis: 2D Table
middle
The following exam focus
----Stakeholder mapping table/stakeholder map (map): Stakeholders-->Concerns (demands)-->Viewpoints/angles-->Views (for communication)
Exam: The vision phase addresses communication and building consensus such as stakeholder mapping.
Viewpoint (Manager): Market Management-->Product Research and Development-->Business Exhibition-->Insurance and Underwriting-->Post-Insurance and Claims Settlement
Viewpoint (insurance users): Business development --> Insurance and underwriting --> Post-insurance and claims settlement
Down
Architecture Building Blocks (ABB) guide the EF phase Solution Building Blocks (SBB)
Capability-based planning: Define goals (large capabilities) --> Define capability requirements (small capabilities) --> Define capability increments --> Define implementation (Solution SBB --> ABB)
Architecture contract: A requirement and agreement of the architecture on the project. The F phase is generated and the G phase is confirmed.
Architecture changes: In order to adapt to changes and ensure business value. Follow the change process (change request --> impact assessment --> change implementation)
3.4 Course Review
4.1 Overview of architectural content framework
4.2 Architecture content division
4.3 Content Metamodel: Architectural Terminology
Unified concept and unified classification (content framework model)
Basic elements: directory, matrix, graphics
Building blocks: reusable components/functions (payroll management), including ABB, SBB
Product: intermediate process output
Deliverables: Outputs agreed in the contract
Picture reference: PDF file (1 question in the exam)
5.1 Enterprise continuous sequence
Lian (continuous series) Kao (reference model)
Architecture reuse: reuse and accumulation (knowledgeable)
Continuous series: abstract --> concrete (architectural asset classification)
Architecture Continuous Architecture: Infrastructure (TRM) --> Common Architecture (III-RM) --> Industry Architecture (ETOM, ARTS) --> Specific Organizational Structure
Solutions Continuum: Basic Solutions --> Generic Solutions --> Industry Solutions --> Organization-Specific Solutions
Reference model:
1) TRM (application platform infrastructure) --> technical architecture
2) Integrated Information Infrastructure Reference Model III-RM (Application Integration Relationship) --> Application Architecture
Architecture repository:
Original model (terminology) Architectural landscape (blueprint: architectural state of the enterprise at a specific point in time) Reference library (model, output) Standard information library (storage standards) Governance log (record) Architectural capabilities (organization/role/skills) Requirements repository solution Solution landscape (solution building blocks)
6.1 Enterprise architecture capability building
Two understandings: ADM capability-based planning (business capabilities), treating architectural capabilities as business capabilities
Example: Capacity-Based Planning (ADM)
1) Goal: Build an architectural capability
2) Capability definition: business capabilities (architecture design/architecture control/...) application capabilities (architecture design tools, architecture asset library) data capabilities (architecture data definition, classification) technical capabilities (servers, etc.)
3) Capability increment: transitional architecture
4) Building blocks
6.2 Architecture Committee: The role of the Architecture Committee
Architecture Committee:
1) Cross-functional coordination of conflicts, setting principles, making decisions, and assuming final responsibility (preparation)
2) As a sponsor (sponsor)
3) Test point: The role of the architecture committee (sub-architecture consistency, identification of reusable components)
6.3 Enterprise Architecture
Architecture compliance:
1) Basis (Architecture Contract) Tool (Checklist)
2) How to follow the rules? Management and control coaching (architects and examination projects, participation in technology selection)
Architecture contract: the agreement that the architecture meets the standards, generated in the F phase, confirmed and used in the G phase
Architecture Governance: Solving Consistency Issues
Enterprise Architecture Maturity Model (ACMM): Level 0-5 High
Architecture skills: decision-making, design, control/governance, other
7.1.1 Background driving force
7.1.2 Evaluation strategy
7.1.3 Evaluation results
7.1.4 Suggestions for improving capabilities
7.2 Architectural Vision Example
7.3 Business architecture design
7.3.1 Practice topics
1. Business structure
1) Three elements of business architecture: goals, division of labor (business functions: reuse), collaboration (horizontal interaction, vertical management and control: end-to-end)
2) Architecture design focus: first find the main value chain
3) Three views
Value chain view: find the value chain and identify the main business line
Business capability component view: imitate and draw the company's business
Business process view: end-to-end (based on value chain decomposition), process standard: BPM
4) Business structure: TOGAF ARIS BPM PCF (APQC) BIZBOK (value stream) Lean management
7.4 Application architecture design
2. Application architecture
1) Basis: business structure --> transition to informatization
2) Consistency issue: mapped by business architecture: business function --> application or application function, business interaction (process) --> application integration relationship
3) View: Application view Application function view Application integration view
4) Unification and separation issues: Application construction needs to adapt to the management and control model (strong or weak)
7.5 Data architecture design
3. Data architecture
1) Goal: To meet the needs of data services and serve as the basis for data governance (data transfer)
2) Basics: Data classification (subject domain view) Asset inventory Data flow
7.6 Technical architecture design
4. Technical architecture
1) View type: overall frame view, detailed component view, platform view
7.7 Planning route design
8.1 Architecture control positioning
Architecture control
Enterprise architecture management = enterprise architecture design (setting standards) enterprise architecture control (governance: system construction, project management)
Four things: setting standards (architecture design), setting mechanisms (construction of architecture management and control system), managing projects (doing governance), and generating and optimizing architecture.
8.2 Architecture management model
8.3 Enterprise Architecture Management and Control Organization
8.4 Enterprise architecture management and control capabilities (process and system)
8.5 Architecture evaluation mechanism
9.1TOGAF9.2 certification drill
1
2
9.2-Certification drill-scenario questions:
1. General background: 132
1) Certainty (positioning): Reorganization of capabilities (self-needs adjustment, corporate mergers and acquisitions)
2) Three more (forms): multi-region, multi-service, multi-system
3) Second transformation (direction): the organization moves toward agility and the system moves toward centralization
Vision test points:
1), Scenario 1: Senior management is concerned (concerned), uses business transformation readiness assessment technology, and does risk management
2) Scenario 2: Everyone is concerned (how to reach consensus with relevant stakeholders)
1) Clarify requirements: business scenario technology
2) Build consensus: stakeholder mapping table/stakeholder map (map)
Stakeholders-->Concerns (Requirements)-->Viewpoints/Angle-->View (for communication)-->How to solve?
3. Iteration: overall iteration, local iteration, single iteration
Baseline first (bottom-up): unclear goals and rich architectural assets
Goals first (top-down): strategic goals are clear; leaders do not want past practices to continue into the future
3
Consensus issues: friendly consultation and scientific communication
Exam: about 3 weeks
Reading: doing questions, looking up books