mh-cto-sdlc-arch-drivers

Architectural drivers are identified by analyzing Phase 2 and 3 artifacts, such as NFR specifications and constraint inventories, to detect which requirements constrain the architecture. This process flags structural risks before decomposition begins.

Non-functional requirements can make architectures hard to test when they introduce conflicting drivers or structural constraints. Applying a testability lens during driver identification detects these gaps and flags risks before they impact the system design.

The best way to flag conflicting architectural constraints is to review NFR specs and design system registries through a testability lens. This detects conflicting drivers and gaps in constraints, outputting a structured markdown document with recommendations.

Yes, you need a constraint inventory to assess architectural risks accurately. The analysis requires text-based artifacts like the NFR spec, constraint inventory, and design system registry from previous phases to identify drivers and generate implementation constraints.

A limitation of detecting architectural drivers from text-based artifacts is that the process relies entirely on the completeness of Phase 2 and 3 inputs. It handles text-based decision-making but cannot identify risks missing from the initial NFR spec or constraint inventory.