Landscapes are part of the [[CSVLOD]] model, representing **IT-focused structures**. The result of Technology Optimization. They help achieve understanding/analysis of the existing IT landscape. What assets exist, how they relate, & how they're used. > [!question] Questions > - What systems, databases, and infrastructure are in use? > - How are these things connected & what info flows between them? > - How do these support business capabilities? Landscapes are typically _graphical_ in nature, often using specialized tools like [[Archimate]]. They're built by architects for the purposes of _rationalizing_ the assets and manage their lifecycle (and the implications of sunsetting technologies). # Concerns Landscapes are often used for things they shouldn't be used for, and are at the wrong level of detail (i.e. too much detail). They are better for _capturing knowledge_ than for strategic planning. # Types ## Landscape Diagrams Commonality: **Essential** Landscape diagrams have a lot of names. They are the quintessential "box and arrows" diagrams. They often use [[Archimate]], or will simply borrow conventions from [[UML]]. These may be the vaguest types of [[Enterprise Architecture Artifacts]] covered in the book. They may be [[Enterprise Architectural Layers|layered]] or not. They may focus on only data, or only applications, or only infrastructure, or cover any mix of them. > [!NOTE] Examples > ![[Pasted image 20240601233348.png]] ## Inventories Commonality: Common Asset inventories are basically tabular lists of assets (applications, infrastructure, databases). It is what it sounds like. It looks like what you'd expect. Columns cover things like owner, cost, lifetime, purpose, models, tech stack, problems/risks, etc. > [!note] Example (table below) | Item | Type | Owner | Purpose | Cost | Docs | | ------------- | ----------- | ------ | ------------------- | ---- | ------ | | Microsoft 365 | Application | Jill | Standard file usage | $-- | (link) | | Oracle DB123 | Database | Jeremy | Security Logs | $- | (link) | ## Enterprise System Portfolios Commonality: Common An Enterprise System Portfolio is basically just a [[Business Capability Models]] with supporting systems listed as well. These seem very heavily overlapped with [[EA Standards#Technology Reference Models]]. Again this book splits hairs with categories. Color coding often relates to lifecycle phases and "strategic fit", where things marked as "strategic" are expected to grow. > [!note] Example > ![[Pasted image 20240601234921.png]] ## IT Roadmaps Commonality: Common These are just IT-focused [[EA Visions#Roadmaps]]. They'd be aimed at the CIO, not the CEO. Nuff said. ## Others - **Asset Roadmaps** - basically inventories, but looking out into the future. - **IT Target States** - just [[EA Visions#Target States]] for IT. - **Enterprise Data Portfolios** - structured high-level mapping of essential data to relevant business capabilities, also list where the data is & who owns it. **** ## Source - [[The Practice of Enterprise Architecture]] - https://eaonapage.com/ ## Related - [[CSVLOD]] - [[Enterprise Architecture of the PDW]] - [[Diagram Types (index)]]