Files
SlpSoftware/aidlc-docs/features/redesign-modern-timetravel/inception/plans/unit-of-work-plan.md
T
SluijsensandClaude Sonnet 5.5 1047c738b5 AI-DLC: inception en ontwerp voor redesign B/E met contactformulier
Requirements, application design (incl. concept-API-contract voor het contactformulier), units en functional design voor U1.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
2026-11-09 21:06:25 +01:00

1.4 KiB

Unit of Work Plan — redesign-modern-timetravel

Steps

  • Analyze requirements, execution plan and application design for decomposition
  • Resolve decomposition question (asked interactively)
  • Generate inception/application-design/unit-of-work.md
  • Generate inception/application-design/unit-of-work-dependency.md
  • Generate inception/application-design/unit-of-work-story-map.md (requirements-to-unit map; User Stories were skipped)
  • Validate unit boundaries and dependencies
  • Ensure all requirements (FR/NFR) are assigned to units

Question (asked interactively, 2026-11-09)

Question 1 — Order of the last two frontend units

  • A) Form first (U4 before U5)
  • B) E first (U5 before U4)
  • C) In parallel
  • X) Other

Decomposition approach (from the execution plan, confirmed)

  • Single repository, brownfield, monolith SPA: units are logical modules delivered sequentially, each with its own design/code/test cycle. Branch feature/redesign-modern-timetravel, commits per unit, one PR at the end.
  • Frontend units U1-U5 here; external units X-a..X-f are built by the CMS builder (SLS Software - CMS, feature contact-forms-module in SlpModularCms) and tracked here only as dependencies.
  • Order (user decision): U1 → U2 → U3 → U4 → U5. The form (U4) works against a mock/contract client until the CMS endpoint exists.