value_stream_map View
The value_stream_map view visualizes end-to-end customer and business value delivery streams, mapping sequential stages to enabling business capabilities, business processes, software applications, autonomous AI agents, data assets, and strategic KPIs.
Visual Projection
Value Stream Map View showing stage flow with enabling capability swimlanes and architecture realization
Purpose & Target Audience
- Target Audience: Enterprise Architects, Business Architects, Value Stream Managers, Product Directors, Transformation Leaders.
- Primary Use Cases:
- Depicting customer journeys and stage progression from trigger to value delivery.
- Identifying capability gaps and redundant applications across the value stream.
- Tracking realization of stage milestones by underlying software services and autonomous AI agents.
- Mapping data assets read and produced across delivery stages.
- Monitoring strategic KPIs and goals linked to each stage of customer value.
- Generating stakeholder traceability registers with instant CSV export.
Flow Orientations & Auto Layout
The value_stream_map view supports dual flow orientations via auto_layout:
| Layout Option | Flow Orientation | Usage & Visual Representation |
|---|---|---|
Omitted / LeftToRight (Default) | Horizontal Pipeline Flow | Stages flow left-to-right as sequential chevron cards with realization swimlanes underneath. |
TopToBottom | Vertical Progression Flow | Stages flow vertically with progression connectors and adjacent realization summary cards. |
views {
# 1. Horizontal Pipeline Flow (default when auto_layout is omitted or set to LeftToRight)
value_stream_map v_onboarding_pipeline "Customer Onboarding Pipeline" {
include vs_customer_onboarding
include stage
include capability
auto_layout LeftToRight
}
# 2. Vertical Stage Progression Flow
value_stream_map v_lending_lifecycle "Consumer Lending Lifecycle" {
include vs_consumer_lending
include stage
include capability
auto_layout TopToBottom
}
}
Supported Entity Types
| Entity Type | Role in Value Stream | Description |
|---|---|---|
value_stream | Root Stream | The top-level value stream container enclosing stages. |
stage | Journey Milestone | The sequential phases of value delivery with numeric order attributes. |
capability | Functional Enabler | Business capabilities realizing or supporting specific stages. |
process | Operational Workflow | Human and system processes executed within each stage. |
system, app | Technical System | Core IT platforms and microservices powering stage operations. |
agent | Autonomous AI Agent | AI agents and bot workers performing triage, review, or automation. |
actor | Stakeholder / Persona | Customers, operators, and employees participating in the stream. |
data_object | Information Asset | Business entities and payloads read or written at each stage. |
kpi, goal | Measurable Outcome | Performance metrics and strategic targets measuring stage success. |
Supported Relationships & Verbs
| Relationship Verb | Source Entity | Target Entity | Meaning |
|---|---|---|---|
realizes | capability, app, system, agent, process | stage, value_stream | Enabler realization of value stream stages |
serves | app, system, capability | stage, actor | System or capability servicing a stage |
flows_to | stage, app, data_object | stage, app, data_object | Material, data, or sequence flow between stages |
triggers | actor, system, stage | stage, process | Event triggering subsequent stages or workflows |
reads | app, stage, agent | data_object | Data consumption at a stage |
writes | app, stage, agent | data_object | Data artifact production at a stage |
influences | stage, capability | goal, kpi | Contribution to measurable business outcomes |
composed_of | value_stream | stage | Structural stage decomposition |
depends_on | stage, app | stage, app | Operational prerequisite dependencies |
governed_by | stage, process | policy, standard | Regulatory and compliance constraints |
Fixed Compiler-Defined Traversal
value_stream_map views feature intrinsic compiler-defined traversal: authors only need to include the target value_stream root entity. The compiler automatically resolves participating architecture entities:
- Base Stages: Stages enclosed within the included
value_stream. - Capabilities (Frontier 1): Any capability realizing the base stages (
incoming realizes). - Systems, Apps, Agents, & Processes (Frontier 2): Any app, autonomous agent, or process realizing the capabilities (
incoming realizes). - Structural Systems (Frontier 2 Sys): Enclosing parent systems of any realized apps or agents.
- Strategic KPIs & Goals (Lateral): Any KPI or goal influenced by the capabilities (
outgoing influences). - Data Objects: Any data asset read or written by apps, agents, or processes (
outgoing reads / writes). - Stage Owner Fallback: If a stage does not define an explicit
owner, it automatically inherits the parent value stream'sowner.
:::info Single Value Stream Constraint
A value_stream_map view supports exactly one value stream per view. Including multiple value streams or broad where clauses matching stages across multiple streams produces compile error NEA2019. If no value stream is resolved, compile error NEA2020 is emitted.
:::
Complete DSL Example
views {
value_stream_map customer_onboarding_value_stream "Customer Onboarding Value Stream" {
description "End-to-end customer onboarding pipeline mapping stages to enabling capabilities, systems, and KPIs."
tags ["Value Stream", "Onboarding", "Customer Experience"]
# Including the value stream automatically resolves all stages,
# enabling capabilities, apps/agents, enclosing systems, KPIs, and data objects
include vs_customer_onboarding
auto_layout LeftToRight
}
}