Most (if not all) [[Enterprise Architecture Frameworks]] I've found pitch [[Enterprise Architecture]] as a layered thing. What is _not_ always common, though, is the quantity of those layers - and what they are. Here's a cross section of sources. [[UAF]] doesn't really call them "layers". Instead they are based around "domains", which have various "aspects". Frankly UAF seems overly complicated. # EA Layers According to Who | Layer | EA as a Strategy | [[Archimate]] | [[UAF]] | FEAF | [[CSVLOD]] | | :--------------------- | :--------------: | :------------------------: | :------------------------: | :------------------: | -------------------------- | | Strategy | | ✅ | ✅ | "Goals & Objectives" | | | Business Process Layer | ✅ | ✅ | "Operational" & "Services" | ✅ | ✅ | | Data/Info | ✅ | (covered by _Application_) | | ✅ | ✅ | | Application | ✅ | ✅ | | ✅ | ✅ | | Technology | ✅ | ✅ | | | “Integration” & “Security” | | Physical | | ✅ | | ✅ | “Infrastructure” | | Implementation | | ✅ | "Projects" | | | There's also the **Domains**, which are essentially layers, as presented in [[The Practice of Enterprise Architecture]]: ![[IMG_1213 Medium.jpeg]] This is business, infrastructure, integration, data, applications, and business. # Example Contents | Business | Capabilities, processes, value streams, roles, | | -------------- | ---------------------------------------------------------------- | | Applications | Application functions & relations | | Data | The conceptual and logical objects, master data sources, schemas | | Integration | Interfaces, protocols, ETL platforms, messaging services | | Infrastructure | Servers, switches, cloud, system software | | Security | Firewalls, identity management, cryptographic methods | **** # More ## Source - [[Enterprise Architecture as a Strategy]] ## Related