Knowledge · Framework · SDLC · FDD3

Plan by Feature

Lock down the scope before writing code. Functional and non-functional requirements get checklisted per function — security, performance, accessibility all reviewed. Test cases define what "done" looks like before implementation starts (TDD). The user checkpoint is a mandatory approval gate where the consolidated plan is reviewed before any code is written.

Metadata

FDD3 PLAN

Steps

Showing 3 of 4

  1. 1 Functional Requirements

    per-function checklists, acceptance criteria

  2. 2 Non-Functional Requirements

    security, performance, accessibility

  3. 3 Test Cases & Fixtures

    TDD assertions, fixture data

Deliverables

  • Functional requirements checklist per function
  • Non-functional requirements (performance, security, accessibility)
  • Test plan with cases, fixtures, and assertions
  • Consolidated plan for user review

Example Outputs

  • FR: 'Package.Create must validate tenant ownership before insert'
  • NFR: 'Package list API responds < 200ms for 1000 packages'
  • Test: 'TestCreatePackage_InvalidTenant_Returns403'
  • Fixture: 3 tenants, 10 packages, 5 delivery events in YAML