Status. Proposed design only. Nothing in this vault is DG client approval. No application, service or test has been executed; every scenario is Not executed. Fees and dates are open.
Cross-module impact matrix
Purpose
When a module changes, which scenarios to re-run. Derived mechanically from the primary step and “Needs steps” columns of Dependency-and-Regression-Table; read that table for the reason each scenario depends on a later step.
| Changed module (steps) | Scenarios affected | Scenario IDs |
|---|---|---|
| Identity and company access (01-03) | 22 | T01, T02, T03, T04, T16, T25, T26, T27, T28, T37, T38, DG07, DG09, DG20, DG21, DG22, DG24, DG25, DG26, DG27, DG28, DG29 |
| Opportunities and discovery (04-05) | 22 | T02, T05, T06, T07, T08, T13, T14, T15, T16, T21, T22, T27, T33, T39, DG03, DG05, DG22, DG24, DG26, DG27, DG29, DG37 |
| Engagement and tracking (06, 08) | 41 | T02, T03, T04, T09, T10, T11, T12, T13, T14, T15, T16, T17, T18, T19, T20, T21, T22, T23, T24, T25, T27, T28, T29, T30, T31, T32, T33, T39, DG02, DG07, DG09, DG13, DG20, DG21, DG22, DG24, DG26, DG27, DG28, DG29, DG37 |
| Notifications and administration (07, 09) | 28 | T04, T10, T11, T18, T19, T21, T22, T23, T25, T26, T28, T32, T33, T34, T35, T36, T37, T38, DG07, DG09, DG20, DG21, DG22, DG24, DG25, DG27, DG28, DG29 |
| Hardening and release (10-11) | 21 | T36, T37, T38, T39, T40, DG02, DG03, DG05, DG07, DG09, DG13, DG20, DG21, DG22, DG24, DG25, DG26, DG27, DG28, DG29, DG37 |
Every software scenario is also rechecked on the integrated build at Step-11-UAT-and-Release. Manual DG services (step 12) are independent of application changes unless a scenario is mixed (Mixed-Evidence-Disposition).
Change history
| Date | Change |
|---|---|
| 2026-10-20 | Created (bootstrap Phase 2) |