Tutorial 5: Value Streams & Capability Realization
In Tutorial 4, you established NeoBank's security architecture, trust boundaries, and regulatory compliance matrices.
In modern agile and enterprise architecture frameworks (such as SAFe and BIZBOK), Value Streams represent the sequence of activities that an organization delivers to create value for a customer.
In this tutorial, you will learn how to:
- Define end-to-end Value Streams (
value_stream). - Order sequential customer touchpoints using Stages (
stage) andordernumbers. - Trace how Business Capabilities and Applications realize each stage.
- Project a dedicated Value Stream Map View (
value_stream_map) with horizontal pipeline alignment.
1. Expanding the NeoBank Workspace Layout
We will add a dedicated value stream fragment under business/:
neobank/
├── main.ea
├── strategy/
│ └── goals_kpis.ea
├── business/
│ ├── actors.ea
│ ├── capabilities.ea
│ └── value_streams.ea # [NEW] Customer value streams & ordered stages
├── application/
│ └── customer_onboarding.ea
├── technology/
│ └── environments.ea
├── security/
│ └── security_architecture.ea
└── governance/
└── policies.ea
2. Define Value Streams (business/value_streams.ea)
Create business/value_streams.ea. Here we model two core journeys: customer registration onboarding and fraud case resolution:
layer "Business Architecture" {
value_stream vs_customer_onboarding "Customer Onboarding Stream" {
description "End-to-end journey from initial digital application to account opening and wallet activation"
owner "VP Customer Operations"
stage stage_capture_app "Capture Digital Application" {
order 1
description "Applicant submits personal details and ID documents via mobile app"
relationships {
cap_digital_onboarding realizes this "Provides self-service capture"
}
}
stage stage_verify_kyc "Verify Identity & KYC" {
order 2
description "Biometric liveness check and document verification against government databases"
relationships {
cap_identity_verification realizes this "Automates document verification"
}
}
stage stage_provision_account "Provision Account & Wallet" {
order 3
description "Automated ledger account creation and initial digital wallet funding"
relationships {
cap_retail_banking realizes this "Creates core deposit accounts"
}
}
}
value_stream vs_fraud_resolution "Fraud Detection & Resolution Stream" {
description "Real-time anomaly scoring, account restriction, and investigator remediation"
owner "Head of Financial Crime"
stage stage_detect_anomaly "Detect Transaction Anomaly" {
order 1
description "Streaming ML models score every payment in real time"
relationships {
cap_transaction_scoring realizes this "Real-time transaction fraud scoring"
}
}
stage stage_freeze_account "Risk Containment & Freeze" {
order 2
description "Automated account freeze when risk score exceeds 85/100"
}
stage stage_investigate_case "Investigator Case Review" {
order 3
description "Fraud specialist conducts secondary triage and files suspicious activity report"
}
}
}
3. Project the Value Stream View (main.ea)
In main.ea, add the value_stream_map view to visualize the end-to-end customer journey pipeline and its supporting architecture enablers:
views {
// ... previous views ...
value_stream_map customer_onboarding_value_stream "Customer Onboarding Stream" {
description "End-to-end customer onboarding pipeline mapping stages to enabling capabilities and applications."
tags ["Business Architecture", "Value Stream", "Onboarding", "Customer Experience"]
include vs_customer_onboarding
auto_layout LeftToRight
}
}
4. Visual Projection: customer_onboarding_value_stream
Value Stream View showing sequential stage chevrons with capability and application realization swimlanes
Key Features Promoted in this View:
- Sequential Pipeline (
value_stream): Renders stages left-to-right usingauto_layout LeftToRightwith sequential order indicators and transition flow connectors. - Architectural Realization (
realizes): Visually stacks business capabilities, applications, and core systems directly underneath the stage milestones they enable. - Cross-Discipline Alignment: Bridges business strategy with IT execution by demonstrating how software platforms deliver tangible customer value.
5. Validate the Workspace
Run the CLI validator:
scapius validate ./neobank
Validation Successful! Workspace 'Neo Bank Enterprise Architecture' is valid.
Next Steps
With value streams and business realization in place, proceed to Tutorial 6: Data Architecture & Data Flow to model information assets, PII classifications, and data transformation lifecycles across systems.