💡 Enterprise Architecture Foundations

🪕 1. Enterprise Architecture (EA)

application architect
solutions architect
enterprise architect

🪕 2. A Career in Enterprise Architecture

🤲🏻 Think like an architect

developers vs architect, IT staff + Business
Architects consider tools and resources beyond software development to create business solutions.

🤲🏻 Application architect - Design of application

write codes, POC, communicate with dev teams
doc designs to new systems, track changes to designs, serve as subject matter exports

🤲🏻 Solution architect - Support of business

Solutions architects spend time on both application and enterprise-level concerns.
fitting/coordinating, pluggin systems, system integrations
project align to standard; risk, cost, complexity; reuse, broad prospective

🤲🏻 Enterprise architect - Strategic decisions

Enterprise architecture is focused on strategic questions, such as what to build and why.
Enterprise Architecture Management System (EAMS)

🪕 3. Enterprise Architecture Frameworks and Practices

polyglot 多种语言 dev

🤲🏻 TOGAF

The Open Group Architecture Framework (TOGAF)
Framework for developing enterprise architectures
Based on TAFIM
4 Architecture Domains
- Business: Organization, strategy, process
- Data: Management, migration, and governance
- Application: Descriptions of individual systems and integrations
- Technical: Hardware, software, networking
Architectural Development Method (ADM): The ADM is designed to be adapted, and it can be iterated over repeatedly using only the phases necessary for a particular architecture change.

enterprise continuum (连续体)
togaf certification (level 1, 2)
preliminary 初步, governance 治理
A: loop starts
B: Change
C: Model of needed changes: data, integration
D: choice of database, specific protocol, blueprints 蓝图 for implementation
E: How and What?
F: Primoritize work effect into sub-projects
G: Build the solution
H: Tend to ongoing requirements. Phase H handles small changes and large, where large changes may require a partial or complete re-iteration of the ADM cycle.

🤲🏻 Zachman: from Abstractions 抽象化 to Value

Developed by John Zachman at IBM
Formal method for classifying knowledge
6 x 6 matrix:
- what, how, where, who, when, why
- executive, business mangement, architect, engineer, technician, enterprise
The transformation of an abstract idea through more detailed ideas to a real thing is called Reification化身.

The Zachman Framework is an enterprise ontology 本体论 and is a fundamental structure for Enterprise Architecture which provides a formal and structured way of viewing and defining an enterprise. The ontology is a two dimensional classification schema that reflects the intersection between two historical classifications.

Zachman is focused on identifying the different viewpoints that might be relevant for different purposes while TOGAF is focused on the process of developing architectures.

🤲🏻 Agile architecture

Waterfall, prior to Agile, is the most common method for developing software.
drawbacks of 缺点 waterfall
Agile methodology
- collaboration between roles
- light documentation for guiding development
- cyclical process 循环过程
- sprints
Scaled Agile Framework

🪕 4. Establishing an EA Organization

🤲🏻 The EA value proposition 主张

🤲🏻 The role of EA in an enterprise

who and how?
solution director, dev management, architect

🤲🏻 Integrating EA with process: ITIL and ITSM

ITIL: Information Infrastructure Technology Library
- Service Strategy
- Service Design
- Service Transition
- Service Operation
- Continual Service Improvement
ITSM: IT service management

Information Technology Service Management are the activities that are performed by an organization to design, plan, deliver, operate and control information technology services offered to customers.

🤲🏻 Creating an EA organization

EA Managers duty:
- Mange Architects
- Report to Chief Architect
- Hire Architects
- Assign work
- Collaborate with stakeholder teams
BI, data architecture
executive artifacts, development artifacts