High-level descriptions of the current IT landscape — systems, integrations, portfolios. A knowledge base of reference materials used to rationalize the landscape, manage asset lifecycle, and plan new initiatives.
Artifacts
| Artifact | Status | Owner | Last Reviewed |
|---|---|---|---|
| Application Landscape Diagram | Current | Enterprise Architect | 2026-Q1 |
| Application Inventory | Current | Portfolio Manager | 2026-Q1 |
| Personal Data Flow Map | Needs Review | Data Protection Officer | 2025-Q2 |
Application Inventory
| Application | Owner | Lifecycle | Last Updated |
|---|---|---|---|
| Payment Gateway | Payments Team | Current | 2026-05-12 |
| Payment Ledger | Payments Team | Current | 2026-04-28 |
| Fraud Detection Engine | Payments Team | Current | 2026-05-30 |
| Customer Portal | Customer Experience | Current | 2026-06-01 |
| ACME Mobile App | Customer Experience | Current | 2026-05-20 |
| Order Service | Order Management | Current | 2026-05-15 |
| Inventory Service | Order Management | Current | 2026-04-10 |
| Product Catalog | Order Management | Current | 2026-03-10 |
| Identity Provider (IdP) | Identity & Access | Current | 2026-03-22 |
| Notification Service | Platform Engineering | Current | 2026-02-18 |
| API Gateway | Platform Engineering | Current | 2026-04-18 |
| Data Warehouse | Data Platform | Current | 2026-04-05 |
| ERP System (SAP) | Finance IT | Current | 2025-12-15 |
| HRIS (PeopleSoft) | HR Systems | Current | 2025-10-01 |
| Legacy Payments (COBOL) | Payments Team | Phase-out | 2025-09-01 |
Integration Points
| Integration | Exposed By | Data Carried |
|---|---|---|
| Payment API (REST) | Payment Gateway | Payment Transaction |
| Payment Events (Kafka topic: payment.*) | Payment Gateway | Payment Transaction |
| Order Events (Kafka topic: order.*) | Order Service | Order Record |
| Identity Token Endpoint (OIDC) | Identity Provider | Customer Record |
| Inventory API (gRPC) | Inventory Service | — |
| ERP Integration (SOAP/ESB) | ERP System | Financial Transaction |
Data Objects & Classification
| Data Object | Classification | Processing Purpose | Legal Basis |
|---|---|---|---|
| Customer Record | Personal | Contract Fulfilment | GDPR Art. 6(1)(b) |
| Payment Transaction | Personal | Contract Fulfilment | GDPR Art. 6(1)(b) |
| Order Record | Personal | Contract Fulfilment | GDPR Art. 6(1)(b) |
| Employee Record | Special Category | Legal Obligation | GDPR Art. 6(1)(c) |
| Analytics Event | Personal | Legitimate Interest | GDPR Art. 6(1)(f) |
| Financial Transaction | Internal | — | — |
| Product Data | Public | — | — |
| Fraud Signal | Internal | — | — |
Source: acme-model.ttl — queried via Application Landscape and Data Flow templates in acme-deliverable-templates.ttl
Relevant Viewpoints
| Viewpoint | Purpose | Key Question | Completeness |
|---|---|---|---|
| Application Landscape | Informing, Deciding | "What applications do we have, who owns them, and how do they connect?" | Complete |
| Data Flow Map | Informing, Governing | "Where does personal data flow, and is each flow justified?" | Needs Review |
Governance
- Governed by
- Enterprise Architect + Portfolio Manager
- Review cadence
- Quarterly (reconciled against ServiceNow CMDB)
- Authoritative source
- ServiceNow CMDB (application inventory), manual curation (diagrams)
- Staleness threshold
- Flagged if quarterly reconciliation missed or 6 months without update
- Lifecycle
- Long-lived — continuously maintained, never retired (evolved)
- Escalation path
- Portfolio Manager → Enterprise Architect → Technology Council
Inter-Type Relationships
- Landscapes provide environment for → Outlines, Designs
- Standards eventually shape → Landscapes
- Visions guide evolution of → Landscapes
- Considerations influence evolution of → Landscapes