Skip to content

Instantly share code, notes, and snippets.

@leoricklin

leoricklin/res_enterprisearchitecture.md

Last active October 31, 2023 06:18
Show Gist options
  • Save leoricklin/83776506ec363d49df516e15c2f04376 to your computer and use it in GitHub Desktop.
Save leoricklin/83776506ec363d49df516e15c2f04376 to your computer and use it in GitHub Desktop.
Download ZIP
Raw
res_enterprisearchitecture.md

1.Enterprise Architecture

1.1.Guide/Book

20170427 企业IT架构转型之道：阿里巴巴中台战略思想与架构实战 Kindle电子书, https://www.amazon.cn/dp/B071KW9F7P

20190801 中台战略：中台建设与数字商业, Kindle, https://www.amazon.cn/dp/B07WPRRTPS/

20190701 企业级业务架构设计：方法论与实践 (架构师书库, https://www.amazon.cn/dp/B07WPRRVCB

企业级转型是一个很艰难的过程，它并非一个单纯的技术问题，因为转型涉及企业的方方面面，如果想走通这条路，尤其是对传统企业而言，充分认识自身、寻找适合自身的方法极为重要。笔者多年从事企业级业务架构设计与管控工作，有幸参与了一次历久弥新的企业转型工程，对业务架构在企业级项目和企业转型过程中发挥的作用深有体会，因此，笔者将对业务架构工作的感悟与自身的学习结合起来，超脱原有的工作实践和理论指导，面向可操作的一般方法论写作本书。本书希望能够成为一本让各类读者都可以读得懂的架构书，因此，书中没有让人拿捏不准的概念。殊少概念可能会因为追求易懂的效果而让部分读者觉得有失严谨，但是，“易懂”也是架构设计应当追求的目标之一。与概念较少相对应，本书的“感受”成分稍多，因为笔者相信融入“感受”比单纯写方法更容易引起读者的共鸣与思考。

Business Architecture Common Reference Model Workshop, https://cdn.ymaws.com/www.businessarchitectureguild.org/resource/resmgr/summits_and_workshops/baguild_common_ref_model_wor.pdf

  • p33, value stream / capability cross mapping

1.2.Resources

20220825 为什么需要企业架构

20210225 Software Architects: hard and soft skills needed to become a leader | Enable Architect, EN, ★★★

Software architect: hard skills needed

  • Unified Modeling Language (UML)
  • Searching for candidates with a deep knowledge of one or more programming languages essential to the business to support their long-term goals strategically. This could be anything: Java, JavaScript, Python, Ruby, Rust, Go, C, or even COBOL.
  • Manage software development practices in a collaborative and agile fashion.

Software Architect: soft skills needed,

  • Leadership
  • Problem-Solving & Conflict Resolution
  • Communication
  • Coaching & Inspiration
  • Organization
  • Prioritizing
  • Detailed Thinking
  • Creative Thinking
20200510 10年技术专家的分享：企业解决方案架构设计实践的方法、模型与思维 - InfoQ

★★★ Enterprise architecture 101 (includes numerous samples/templates), https://www.slideshare.net/jamesoni1/enterprise-architecture-10136205348
A channel with visuals on EA approaches and EA processes created on Dragon1

https://www.dragon1.com/channel/enterprise-architecture

Learn TOGAF 9.1 in 100 slides, EN, https://www.slideshare.net/sammydhi01/learn-togaf-91-in-100-slides
Building a strong Data Management capability with TOGAF and ArchiMate, EN, https://www.slideshare.net/mobile/basvg/building-a-strong-data-management-capability-with-togaf-and-archimate
Enterprise Architecture for Dummies - TOGAF 9 enterprise architecture overview, EN, https://www.slideshare.net/mobile/wintonjkt/enterprise-architecture-for-dummies-togaf-9-enterprise-architecture-overview

Togaf 9.1 basic concepts

https://www.slideshare.net/MohamedZakarya2/togaf-91-basic-concepts-81113445
TOGAF 9.1, https://www.youtube.com/watch?v=O4XtAVFJRLw&list=PLgn00WwJcEmo-m6nKFz2gh_r5l3jyqtGI&index=2

★★★ TOGAF Model using Archimate, https://www.togaf-modeling.org/

Application Architecture-Application Communication diagram, https://www.togaf-modeling.org/models/application-architecture/application-communication-diagrams.html
Data dissemination diagrams, https://www.togaf-modeling.org/models/data-architecture/data-dissemination-diagrams.html

TOGAF Learning Resources, https://togaf.gitbook.io/

TOGAF 9 - 袖珍指南, https://togaf.gitbook.io/project/

架构师训练营, https://u.geekbang.org/subject/arch/1000388

1.4.Udemy

How To Become An Outstanding Solution Architect (NT:600), https://www.udemy.com/course/how-to-become-an-outstanding-solution-architect/

New for 9.2! Part 1 Foundation Certification Training, https://www.udemy.com/course/togaf-part1/

1.5. Avancier

Avancier Methods, http://grahamberrisford.com/Avancier%20Methods.htm

AM products & techniques, http://grahamberrisford.com/AM%201%20Methods/6PRODUCTSandTECHNIQUES/AM%20products%20and%20techniques.htm

Data architecture + diagrams, http://grahamberrisford.com/AM%201%20Methods/6PRODUCTSandTECHNIQUES/DataAndInformation/AM%20Information-Data%20architecture.htm

Data structures, http://grahamberrisford.com/AM%201%20Methods/6PRODUCTSandTECHNIQUES/DataAndInformation/AM%20505%20Data%20structures%2045.pdf

Avancier Methods-Products and Techniques, http://grahamberrisford.com/AM%201%20Methods/6PRODUCTSandTECHNIQUES/AM%20products%20and%20techniques.htm

Information/Data Architecture (with TOGAF & ArchiMate artefacts), http://grahamberrisford.com/AM%201%20Methods/6PRODUCTSandTECHNIQUES/DataAndInformation/AM%20Information-Data%20architecture.htm

Architect roles and other resources, http://grahamberrisford.com/Other%20architect%20resources.htm

Mapping TOGAF to ArchiMate, http://grahamberrisford.com/00EAframeworks/03TOGAF/AMTOGpapers/TOGAF%20with%20ArchiMate%20conceptual%20framework.htm

Harmonising TOGAF concepts with ArchiMate – slide show,

####Harmonising TOGAF concepts with ArchiMate - paper

####Harmonising TOGAF diagram types with ArchiMate – slide show

####TOGAF & ArchiMate summaries & analyses ; Architecture Frameworks: TOGAF, ArchiMate, Zachman & DoDAF; , http://grahamberrisford.com/00EAframeworks/TOGAF%20with%20ArchiMate,%20DoDAF%20and%20Zachman.htm

####★★★ TOGAF diagrams mapped to ArchiMate 2.1 and 3.0 Viewpoints, http://grahamberrisford.com/00EAframeworks/03TOGAF/TOGAF%20Diagrams%20w%20ArchiMate%20and%20AM%20examples.pdf

####TOGAF building blocks & services, http://grahamberrisford.com/00EAframeworks/01Fundamentals/TOGAF%20building%20blocks%20and%20services.htm

####Building blocks and services Part2 – more detailed analysis, http://grahamberrisford.com/00EAframeworks/03TOGAF/AM%20TOGAF%204%20Building%20Blocks.htm

1.6.Van Haren

The TOGAF® Standard, Version 9.2 in 3 minutes, https://www.vanharen.net/blog/it-management/the-togaf-standard-version-9-2-3-minutes/
ArchiMate® 3.0.1 – in 3 minutes

#####An Introduction to the ArchiMate® 3.0 Specification

Using the TOGAF® 9.1 Framework with the ArchiMate® 3.0 Modeling Language, https://www.vanharen.net/blog/it-management/using-the-togaf-9-1-framework-with-the-archimate-3-0-modeling-language/

The TOGAF framework and the ArchiMate language overlap in their use of viewpoints, and the concept of an underlying common repository of architectural artifacts and models. Therefore, they have a firm common foundation. The two standards complement each other with respect to the definition of an Enterprise Architecture development process (the TOGAF standard) and the definition of an Enterprise Architecture modeling language (the ArchiMate standard). The ArchiMate 3.0 Specification supports modeling many of the architectural building blocks encountered throughout the phases of the TOGAF ADM.

Raw
res_enterprisearchitecture_archimate.md

1.OpenGroup

1.1.ArchiMate 3.0 Specification, EN

4 Generic Metamodel

5 Relationships

5.2 Dependency Relationships

  • The serving relationship represents a control dependency, denoted by a solid line.
  • The access relationship represents a data dependency, denoted by a dashed line.
  • The influence relationship is the weakest type of dependency, used to model how motivation elements are influenced by other elements.

8. Business Layer

9 Application Layer

9.5 Summary of Application Layer Elements, ★★★,

A Summary of Language Notation

A.1 Core Elements

A.2 Motivation, Strategy, Implementation and Migration Elements

A.3 Relationships

B Relationship Tables

  • (a)ccess (c)omposition (f)low a(g)gregation ass(i)gnment
  • i(n)fluence ass(o)ciation (r)ealization (s)pecialization (t)riggering ser(v)ing

C Example Viewpoints (Informative)

C.1 Basic Viewpoints in ArchiMate

C.1.1 Organization Viewpoint
C.1.2 Business Process Cooperation Viewpoint
C.1.3 Product Viewpoint
C.1.4 Application Cooperation Viewpoint
C.1.5 Application Usage Viewpoint
C.1.6 Implementation and Deployment Viewpoint
C.1.7 Technology Viewpoint
C.1.8 Technology Usage Viewpoint
C.1.9 Information Structure Viewpoint
C.1.10 Service Realization Viewpoint
C.1.11 Physical Viewpoint
C.1.12 Layered Viewpoint

C.2 Motivation Viewpoints

C.2.1 Stakeholder Viewpoint
C.2.2 Goal Realization Viewpoint
C.2.3 Requirements Realization Viewpoint
C.2.4 Motivation Viewpoint

C.3 Strategy Viewpoints

C.3.1 Strategy Viewpoint
C.3.2 Capability Map Viewpoint
C.3.3 Outcome Realization Viewpoint
C.3.4 Resource Map Viewpoint

C.4 Implementation and Migration Viewpoints

C.4.1 Project Viewpoint
C.4.2 Migration Viewpoint
C.4.3 Implementation and Migration Viewpoint
C.4 Implementation and Migration Viewpoints

1.2.ArchiMate .2.0 Specification

8 Architecture Viewpoints
8.4 Standard Viewpoints in ArchiMate
8.4.14 Implementation and Deployment Viewpoint ★★★
A POCKET GUIDE TO THE ARCHIMATE® 3.0.1 SPECIFICATION

1.2.1.Library

ARCHIMATE® STANDARD TRAINING MATERIALS V3 EDITION
★★ Case Study
ArchiSurance Case Study, Version 2
ARCHIMETAL CASE STUDY, VERSION 2

1.3.Resources

點部落, https://dotblogs.com.tw/unified_modeling_language/search?q=archimate
ArchiMate 3.0 A New Standard for Architecture -The Open Group Austin Event, July 2016
Introduction to ArchiMate 3.0, https://www.youtube.com/watch?v=ULl9lf0OZco&list=PLB8F2ECDADEE616AA

2.Draw.io

3.Archi Tool

  • https://www.archimatetool.com/ An open source modelling toolkit to create ArchiMate models and sketches. Used by thousands of Enterprise Architects throughout the world.

4.Visual Paradigm

Sparx Enterprise Architect for modeling and design, https://bellekens.com/wp-content/uploads/2017/10/Using-Enterprise-Architect-for-architecting-the-TenneT-Data-Platform.pdf
A Reference Architecture for Big Data Solutions, https://pdfs.semanticscholar.org/9dbd/b08e6175020f9e8411cee8f61523fb6dc88b.pdf
Raw
res_enterprisearchitecture_togaf.md

The Open Group TOGAF

1.1.Certification

1.2.The TOGAF® Standard, Version 9.2

2. Core Concepts

2.2 What is Architecture in the Context of the TOGAF Standard?

The TOGAF standard embraces but does not strictly adhere to ISO/IEC/IEEE 42010:2011 terminology. In addition to the ISO/IEC/IEEE 42010:2011 definition of "architecture", the TOGAF standard defines a second meaning depending upon the context:

"The structure of components, their inter-relationships, and the principles and guidelines governing their design and evolution over time."

3. Definitions
9. Phase C: Information Systems Architectures - Data Architecture
9.1 Objectives

The objectives of the Data Architecture part of Phase C are to:

  • Develop the Target Data Architecture that enables the Business Architecture and the Architecture Vision, in a way that addresses the Statement of Architecture Work and stakeholder concerns
  • Identify candidate Architecture Roadmap components based upon gaps between the Baseline and Target Data Architectures
9.3 Steps

The steps in Phase C (Data Architecture) are as follows:

9.3.1 Select Reference Models, Viewpoints, and Tools

9.3.2 Develop Baseline Data Architecture Description

9.3.3 Develop Target Data Architecture Description

9.3.4 Perform Gap Analysis

9.3.5 Define Candidate Roadmap Components

9.3.6 Resolve Impacts Across the Architecture Landscape

9.3.7 Conduct Formal Stakeholder Review

9.3.8 Finalize the Data Architecture

9.3.9 Create the Architecture Definition Document

10.Phase C: Information Systems Architectures - Application Architecture
10.1 Objectives

The objectives of the Application Architecture part of Phase C are to:

  • Develop the Target Application Architecture that enables the Business Architecture and the Architecture Vision, in a way that addresses the Statement of Architecture Work and stakeholder concerns
  • Identify candidate Architecture Roadmap components based upon gaps between the Baseline and Target Application Architectures
10.3 Steps

The level of detail addressed in Phase C will depend on the scope and goals of the overall architecture effort.

New application building blocks being introduced as part of this effort will need to be defined in detail during Phase C. Existing application building blocks to be carried over and supported in the target environment may already have been adequately defined in previous architectural work; but, if not, they too will need to be defined in Phase C.

The order of the steps in this phase as well as the time at which they are formally started and completed should be adapted to the situation at hand in accordance with the established Architecture Governance. In particular, determine whether in this situation it is appropriate to conduct Baseline Description or Target Architecture development first, as described in Part III, 18. Applying Iteration to the ADM .

All activities that have been initiated in these steps should be closed during the Finalize the Application Architecture step (see 10.3.8 Finalize the Application Architecture). The documentation generated from these steps must be formally published in the Create the Architecture Definition Document step (see 10.3.9 Create the Architecture Definition Document).

The steps in Phase C (Application Architecture) are as follows:

10.3.1 Select Reference Models, Viewpoints, and Tools

10.3.2 Develop Baseline Application Architecture Description

10.3.3 Develop Target Application Architecture Description

10.3.4 Perform Gap Analysis

10.3.5 Define Candidate Roadmap Components

10.3.6 Resolve Impacts Across the Architecture Landscape

10.3.7 Conduct Formal Stakeholder Review

10.3.8 Finalize the Application Architecture

10.3.9 Create the Architecture Definition Document

11.Phase D: Technology Architecture
11.1.Objectives
  • Develop the Target Technology Architecture that enables the Architecture Vision, target business, data, and application building blocks to be delivered through technology components and technology services, in a way that addresses the Statement of Architecture Work and stakeholder concerns
  • Identify candidate Architecture Roadmap components based upon gaps between the Baseline and Target Technology Architectures
11.3.Steps

11.3.1 Select Reference Models, Viewpoints, and Tools

11.3.2 Develop Baseline Technology Architecture Description

11.3.3 Develop Target Technology Architecture Description

11.3.4 Perform Gap Analysis

11.3.5 Define Candidate Roadmap Components

11.3.6 Resolve Impacts Across the Architecture Landscape

11.3.7 Conduct Formal Stakeholder Review

11.3.8 Finalize the Technology Architecture

11.3.9 Create the Architecture Definition Document

12.Phase E: Opportunities & Solutions
12.1.Objectives
  • Generate the initial complete version of the Architecture Roadmap, based upon the gap analysis and candidate Architecture Roadmap components from Phases B, C, and D
  • Determine whether an incremental approach is required, and if so identify Transition Architectures that will deliver continuous business value
  • Define the overall solution building blocks to finalize the Target Architecture based on the Architecture Building Blocks (ABBs)
12.3.Steps

12.3.1 Determine/Confirm Key Corporate Change Attributes

12.3.2 Determine Business Constraints for Implementation

12.3.3 Review and Consolidate Gap Analysis Results from Phases B to D

12.3.4 Review Consolidated Requirements Across Related Business Functions

12.3.5 Consolidate and Reconcile Interoperability Requirements

12.3.6 Refine and Validate Dependencies

12.3.7 Confirm Readiness and Risk for Business Transformation

12.3.8 Formulate Implementation and Migration Strategy

12.3.9 Identify and Group Major Work Packages

12.3.10 Identify Transition Architectures

12.3.11 Create the Architecture Roadmap & Implementation and Migration Plan

32. Architecture Deliverables
32. Architecture Deliverables
32.1 Introduction: Deliverables produced by executing the ADM are shown in the table below.
42. Architecture Compliance
42.5 Architecture Compliance Review Checklists
  • 42.5.1 Hardware and Operating System Checklist
  • 42.5.2 Software Services and Middleware Checklist
  • 42.5.3 Applications Checklists
THE TOGAF® STANDARD, VERSION 9.2: A POCKET GUIDE

TOGAF® 9 Standard Courseware V9 Edition

TOGAF 8.1 Standard

TOGAF Library, https://publications.opengroup.org/togaf-library

Reference Architecture

SOA

Cloud Computing Publications

Internet of Things Publications

Training Materials

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment