> [!tldr] A collection of tips and practices for working with [[Archimate]] - ArchiMate is a *language*. With any language, there's multiple valid ways to say the same thing. - Like most languages, ArchiMate has (Subject) (Verb) (Object) → (Active Structure) (Behavior) (Passive Structure) - ArchiMate isn't for everything! Like the [[C4 Model]], ArchiMate suggests using for-purpose languages if want to go detailed. - ArchiMate isn't for *instances* of things... yet sometimes it is used that way, even in the best practice examples. So that's confusing. - The fundamental splits: - Internal vs External - **Most views are disposable!** - The model is the truth. - Views should be *for purpose* and limited to what's necessary for a conversation. - **Services:** - ArchiMate is fundamentally **[[Service-Oriented]]**. - Services hold the value - the reason for the existence of everything that realizes it. - Services are the *external behavior* - services are accessed via **interfaces** - **Capabilities:** - Once you get low-level enough, capabilities turn into **Functions** **** # More ## Source -