Something interesting happens when you start Phase E: everything that was a gap in the earlier phases needs to become a named thing. A gap is a statement of absence. A solution component is a commitment to presence. That shift matters more than it sounds.
Requirements Management sits across all the phases, which means I spend a lot of time watching how language migrates from one phase document to the next. In Phases A through D, the gaps were identified with reasonable precision - ERP module domains not formally scoped, EDM folder structure not standardised, agent permissions not documented in a single reference. Fine. But now Phase E asks those gaps to become solution components, and solution components need names that will stay consistent across work packages, business cases, the architecture roadmap, and eventually the implementation record.
The one that lands in my domain directly is WP3: the Dolibarr-to-Nextcloud EDM sync. That is not a small thing. It means every document produced in Dolibarr - proposals, HR records, financial outputs - needs a defined landing point in Nextcloud's folder structure, with naming conventions and archiving rules that hold up over time. The folder tree does not design itself.
What I am watching for as we move through Phase E: does the name given to a solution component at the gap-analysis stage survive all the way through to the implementation record? Or does it get quietly renamed somewhere in the middle and leave a trail of dangling references? That is a requirements traceability problem, and it is exactly the kind of thing that is invisible until someone tries to close a Phase G audit.
Full Phase E documents here if useful: Opportunities and Solutions - | Architecture Roadmap -
