Enterprise Architecture Practice (32570) Week 1
Importance of EA in Business
EA (Enterprise Architecture) helps align IT and business strategies.
It provides a blueprint for managing complexity and change in organizations.
TOGAF Framework
The TOGAF ADM (Architecture Development Method) is emphasized.
Phases include: Preliminary, A (Vision), B (Business), C (Information Systems), D (Technology), E (Opportunities and Solutions), F (Migration Planning), G (Implementation Governance), H (Architecture Change Management).
Each phase outputs architecture deliverables and artifacts.
Architecture Views
Different stakeholders require different architecture views: business, application, data, and technology.
Each view helps address specific concerns (e.g., CIOs care about strategic alignment, developers care about tech stack).
Benefits of EA Practice
Improved decision-making, standardization, and IT governance.
Helps reduce redundancy, improve agility, and manage risk.
EA Maturity Models
Organizations assess their EA maturity using models such as CMMI-like levels.
Maturity affects how well EA is embedded in processes and culture.
Enterprise Continuum and Repository
Explains how reusable assets (e.g., reference models, standards) are stored and reused in architecture work.
Case Studies and Examples
Real-world EA practices (like in government or banking) were briefly mentioned.
Importance of tailoring EA to context.
🧠 Important Things to Remember
- EA = Strategy + Structure: It’s not just technical, but also about aligning business and IT.
- TOGAF ADM is foundational: Learn and memorize its 8 phases and key deliverables.
- Views matter: Use the right architecture view for the right audience.
- Start small, grow maturity: EA implementation should evolve over time.
- EA is a continuous process: Not a one-off project—needs ongoing governance.
- Tooling helps: Repositories and modeling tools are key to managing architecture artifacts.
- Communication is critical: EA professionals must bridge tech and business.