Classical Models: Waterfall, V-Model XT, Spiral Model

This post is a definition of terms for classical development models – including exam questions, core components, and tags.

In a Nutshell

• Waterfall and V-Model XT are plan-driven and artifact-focused.
• Spiral Model is risk-driven and iterative: each cycle reduces uncertainty through risk analysis + prototypes.

Compact Technical Description

Waterfall Model

Sequential phases:

• Analysis
• Design
• Implementation
• Testing
• Operations

Heavily documentation-based, feedback comes late.

V-Model XT

The V couples specifications (left side) with corresponding test levels (right side):

• Detailed design ↔ Module testing
• Architecture/Components ↔ Integration testing
• System requirements ↔ System testing
• User/Customer requirements ↔ Acceptance testing

Core point: Tailoring (project-specific adaptation of roles/products) must be justified and documented.

Spiral Model

Risk-driven: Each cycle comprises objectives → risks → prototype/evaluation → planning. Result is an incrementally refined product with actively managed risks.

Exam-Relevant Key Points

• Waterfall: changes late are expensive
• V-Model XT: test assignment + traceability (IHK classic)
• Tailoring: mandatory in V-Model XT
• Spiral Model: risk analysis per cycle, prototypes as core
• Artifact chain: requirement → design → test (traceability)
• Gate reviews + acceptances

Core Components

1. Phases (Waterfall)
2. Product hierarchy (V-Model XT)
3. Test level mapping in V
4. Tailoring guidelines
5. Governance (gates/milestones)
6. Risk analysis (Spiral)
7. Prototype types (feasibility/architecture/UI)
8. Planning artifacts (project/quality/test plan)
9. Traceability
10. Change management (change requests)

Practice Example (brief)

Business process in public sector with external interface

Waterfall:
- Requirements specification -> Design -> Implementation -> Testing -> Acceptance

V-Model XT:
- Specifications left
- Tests right (module/integration/system/acceptance)
- Tailoring document (e.g., no hardware products)

Spiral:
- Cycle 1: Integration risk -> Load test prototype
- Cycle 2: OAuth risk -> Auth prototype

Advantages and Disadvantages

Waterfall

• Advantages: simple planning, clear handovers
• Disadvantages: late feedback, high change costs

V-Model XT

• Advantages: high traceability, clear test assignment
• Disadvantages: documentation effort, rigid without good tailoring

Spiral Model

• Advantages: active risk management, early prototypes
• Disadvantages: higher management overhead, harder to plan for fixed price

Typical Exam Questions (with brief answer)

1. Waterfall vs. V-Model XT? V couples specification to tests + requires tailoring.
2. How do you read the V? Left side specifies, right side verifies/validates (test levels).
3. When to use Spiral Model? With high uncertainty/technology risk/many interfaces.
4. Why tailoring? Adaptation to context + audit/compliance capability.

Learning Strategy

1. Draw V from memory and assign test levels.
2. For each model type, note 2 suitable use cases.
3. Practice brief justification (regulatory/change rate/risk).

Most Important Sources

1. https://www.cio.bund.de (V-Model XT)
2. https://dl.acm.org/doi/10.1145/360248.360251