landscape View

The landscape view is the primary macro-level projection in Scapius. It visualizes the entire enterprise architecture or large cross-domain ecosystems across strategic layers (Business, Application, and Technology).

---

Visual Projection

Enterprise Landscape View showing multi-layer cross-cutting dependencies

---

Purpose & Target Audience

• Target Audience: Enterprise Architects, Chief Architects, CTOs, Engineering Leadership.
• Primary Use Cases:
  • Understanding cross-layer dependency flow from business processes down to physical infrastructure.
  • Rationalizing application portfolios across business units.
  • Communicating enterprise-wide cloud modernization roadmaps.
  • Identifying critical Single Points of Failure (SPOFs) in macro architectures.

---

Supported Entity Types

The landscape view typically aggregates high-level entities from all layers:

Entity Type	Layer	Role in Landscape View
capability	Business / Strategy	Business capabilities realized by systems and processes.
actor	Business	Human roles and customer archetypes initiating interactions.
process	Business	Core end-to-end workflows executed across the enterprise.
system	Application	Macro-level enterprise platforms and systems.
app	Application	Key customer-facing or core transactional applications.
environment	Technology	Hosting accounts, Kubernetes clusters, and cloud regions.
infrastructure	Technology	Major database clusters, messaging backbones, and compute fleets.
goal	Motivation	Strategic objectives driving the landscape.

---

Supported Relationships & Verbs

Relationship Verb	Source Entity	Target Entity	Typical Representation
realizes	system, process	capability, goal	Upward realization edge
serves	system, app, process	actor, system	Dependency service edge
flows_to	system, app	system, app	Cross-system data integration edge
hosts	environment, infrastructure	system, app	Deployment assignment edge
depends_on	system, app	system, infrastructure	Critical operational dependency
migrates_to	system (Legacy)	system (Target Cloud)	Transformation trajectory edge

---

Filtering & Layout Recommendations

• Recommended Layout: auto_layout TopToBottom (highlights vertical layer dependencies).
• Common Predicates:
  • include system where tier == "Tier-1": Focus on mission-critical systems only.
  • exclude where time == "Eliminate": Omit retired legacy systems.
  • include where layer == "Application" || layer == "Business": Scope view to software architecture.

---

Complete DSL Example

views {
    landscape v_enterprise_core "Enterprise Core Landscape" {
        # Include all macro systems and capabilities
        include capability
        include actor
        include process
        include system
        include environment

        # Focus relationships on serving and realization
        include_verb realizes outgoing
        include_verb serves both
        include_verb hosts

        # Suppress internal low-level edges
        exclude_verb governed_by

        # Top-down hierarchical layout
        auto_layout TopToBottom

        # Visual highlights
        style system where criticality == "Mission-Critical" {
            css_class "critical-system-glow"
        }
    }
}