Business architecture gives stakeholders a shared way to discuss how an organization creates value before choosing technical architecture. In modernization planning, it connects desired outcomes to products, domains, value streams, and the teams responsible for them. section 16.1.1 section 6.5
A product taxonomy is one way to design this architecture. It helps define team accountability and ownership, then shape software architecture around them. Its building blocks can include internal or external products, platforms used by multiple products, domains and subdomains, and the activities through which teams discover and deliver product enhancements. section 6.5
Connect an outcome to the organization
Suppose the target is for every team to deploy changes daily within two years. A modernization strategy can connect that outcome to a product-centric operating model, then show the identified value streams and team responsibilities before presenting migration patterns. Different audiences may need different levels of technical detail. section 16.1.1
Keep the map useful rather than complete. Define only enough detail to support the next objective, such as a modernization slice deliverable in three to six months. Publish updates regularly as products, ownership, and priorities evolve; do not have a central architecture team produce a fixed plan for others to implement. section 6.5
