Value-Driven Analysis and Design (VDAD)

VDAD Process | Practices | Why VDAD? (User Stories) | Tools | Background | Glossary

Process Continuation

TL;DR: Iterate over Steps 1 to 7.

Iterate over Steps and Process

As indicated in the following process illustration, neither the individual steps nor the entire VDAD process should be conducted a linear, unidirectional way.

It is necessary to iterate over the individual steps and the process as a whole in order to evolve the produced artifacts in each step. Each step may yield new insights that are relevant for subsequent steps. For example, while stakeholders of different kinds learn about domain context, requirements, and system capabilities, they might want to reprioritize and/or elicit additional values.

Steps might further have bidirectional dependencies. For instance, while understanding the domain, new stakeholders might be found. An analysis of these stakeholders might bring new insights about the domain (Steps 1 and 2).

Process Navigation

• Overview
• Step 1: Aquire Domain Understanding
• Step 2: Identify Stakeholders
• Step 3: Identify Values per Stakeholder
• Step 4: Prioritize Values
• Step 5: Make Digitalization Decision
• Step 6: Derive New and Adjust Existing Requirements
• Step 7: Design Software Architecture

This work is open source and licensed under a Creative Commons Attribution 4.0 International License. Open on GitHub.