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:

1. Define end-to-end Value Streams (value_stream).
2. Order sequential customer touchpoints using Stages (stage) and order numbers.
3. Trace how Business Capabilities and Applications realize each stage.
4. Project a Data Flow View (data_flow) that tracks customer PII and transactions across the journey.

---

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_processes.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:

neobank/business/value_streams.ea

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. Extend the Application Model with Transaction Data

Update application/customer_onboarding.ea to add payment ledger services and transaction records:

neobank/application/customer_onboarding.ea (excerpt)

    system system_payments "Payment Hub Platform" {
        description "Instant payment gateway and transaction router"
        criticality "Mission-Critical"
        status "Active"

        app app_instant_pay "Instant Payments API" {
            tier "Tier-1"
            internet_facing true
            relationships {
                this flows_to system_core_banking "Posts cleared payments"
                this writes data_ledger_tx "Persists debit/credit ledger transactions"
            }
        }

        app app_aml_monitor "Streaming AML Fraud Monitor" {
            description "Kafka streaming analytics engine evaluating real-time transaction anomalies"
            tier "Tier-1"
            relationships {
                this reads data_ledger_tx "Inspects live payment stream"
            }
        }
    }

    data_object data_ledger_tx "Core Ledger Transaction Record" {
        description "Double-entry accounting transaction record persisting debits, credits, and timestamps"
        classification "Confidential"
    }

---

4. Add the Data Flow View (main.ea)

In main.ea, add the data_flow view to project the customer data lifecycle across value stream stages:

neobank/main.ea (excerpt)

    views {
        // ... previous views ...

        data_flow data_flow_view "Customer & Ledger Data Flow" {
            description "Data lifecycle showing customer KYC profiles, payment transactions, and protective encryption controls across stages."
            tags ["Data Architecture", "PII", "Data Flow", "Value Streams"]

            include customer
            include app_mobile_banking
            include app_instant_pay
            include system_core_banking
            include app_aml_monitor
            include data_customer_record
            include data_ledger_tx
            include control_card_tokenization

            auto_layout LeftToRight
        }
    }

---

5. Visual Projection: data_flow_view

Data flow view tracing customer KYC data and transaction records across value stream stages

Key Features Promoted in this View:

• Data Lifecycle Tracking (data_flow): Highlights how data objects are created, read, modified, and persisted by applications across sequential stages.
• Privacy & Security Badges: Flags data objects marked with pii true or classification "Restricted" and visually correlates them with the protective security controls that govern them.
• Stage Realization: Connects upstream customer journey touchpoints down to concrete database persistence events.

---

6. 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 data lifecycles in place, proceed to Tutorial 6: AI Agents in EA to model autonomous AI agents, copilots, and streaming integration topologies.