Skip to content
/ EA Public

principles, guidelines, practices and samples for building up EA (enterprise architecture)

License

Notifications You must be signed in to change notification settings

yasenstar/EA

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Enterprise Architecture (EA) — Principles, Practices & Modeling Patterns

GitHub stars License: GPL-3.0

"Architecture is the bridge between a business dream and a firm decree."

This repository serves as a professional knowledge base and methodology guide for Enterprise Architects. It moves beyond theory to provide hands-on architectural modeling practices, patterns, and samples across the full enterprise stack.


🎯 My Architectural Philosophy

I follow two core principles in building an Enterprise Architecture Practice:

  1. The Tree of Knowledge (Fundamentals First): As knowledge is like a semantic tree, we must understand the trunk and big branches (fundamental principles and core metamodels) before moving to the leaves (tool-specific details).
  2. Connective Intelligence: Architecture has no value in a silo. My practice focuses on building "Connective Intelligence"—linking Strategy, Business, Data, Application, and Technology layers into a unified, traceable model.

🛠 Architectural Modeling Practices

My work emphasizes rigorous Standard-based Modeling. I specialize in translating complex frameworks into actionable models using industry-standard tools.

1. Unified Modeling with ArchiMate®

I leverage the ArchiMate 3.2 Specification to create consistent, stakeholder-oriented views.

  • Layered Viewpoints: Strategic, Business, Application, and Technology layers.
  • Traceability: Mapping Business Drivers to Requirements and eventually to Physical Infrastructure.
  • Patterns: Developing reusable modeling patterns for common transformation challenges.

2. Integrated Security Architecture (SABSA + ArchiMate)

I focus on aligning SABSA (Sherwood Applied Business Security Architecture) with EA frameworks. This involves modeling:

  • Contextual, Conceptual, and Logical Security Architectures.
  • The "Security Overlay" within standard EA models to ensure "Security by Design."

3. Ontology & Knowledge Graphs

Moving beyond static diagrams, I explore the use of OWL/RDF and Protégé to build EA Ontologies, enabling:

  • Semantic search within the architecture repository.
  • Automated relationship checking and logical reasoning across the model.

📂 Key Practice Repositories

Project Focus Tooling
ArchiMetal Practice Step-by-step transformation case study. Archi (ArchiMate)
ArchiSurance Practice Comprehensive insurance domain modeling. Archi, FreePlane
ArchiMate SABSA Risk-driven security architecture alignment. Archi, Protege, JSON
EA Ontology Building a semantic knowledge graph of ArchiMate. Protégé, SPARQL

🏛 The EA Content Map

Core Domains

  • Business Architecture: Capability Mapping, Value Streams, and Organization Modeling.
  • Information/Data Architecture: Data Objects, Flows, and Ownership.
  • Application Architecture: Component Landscapes and Integration Patterns.
  • Technology Architecture: Infrastructure, Virtualization, and Cloud realization.

Specialized Topics

  • Integration: API-led connectivity and event-driven architecture patterns.
  • Tooling Mastery: Advanced usage of Archi, Sparx Systems Enterprise Architect, and Essential Project.

📺 Learning Resources


🤝 Support & Connect

I am an EA practitioner focused on transforming business complexity into clear, actionable models. If you find these patterns useful, feel free to support the project:

"Buy Me A Coffee"

About

principles, guidelines, practices and samples for building up EA (enterprise architecture)

Topics

Resources

License

Code of conduct

Stars

Watchers

Forks

Releases

No releases published

Sponsor this project

  •  

Packages

No packages published

Languages