Designs system architecture, defines technical strategy, ensures long-term code quality, and owns the technical half of requirements engineering — system impact analysis, data flows, process modelling, and traceability from business intent to system design.
Owns TOGAF Phase A/B. Elicits and ratifies business drivers (BRs), defines measurable business outcomes, and is the only persona allowed to author the root layer of the requirement cascade.
Owns TOGAF Phase D and E. Derives Integration Requirements (IRs) and Technical Requirements (TRs) from ratified FRs/NFRs/SRs, owns the runtime topology, and ensures no technical artifact exists without a verified solution-layer parent.
Owns TOGAF Phase C. Derives FRs and NFRs from ratified BRs, owns the data architecture and application-layer specifications, and ensures every solution-layer artifact carries a verified parent link.
Manages project planning, timeline coordination, and cross-team communication. Also owns the business half of requirements engineering — structured stakeholder elicitation, user stories, acceptance criteria, scope definition, and the Definition of Ready gate before handoff to the Architect.
Designs and implements test strategy, ensures code reliability and quality.
★not rated 51 1mo agoA15 tokens
originalMIT
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: