What it shows:
A hierarchical map connecting the high-level business capabilities and/or business services directly down to the specific application functions being deployed.
Why it’s needed:
Traceability. This proves to executive leadership that the operational goals are understood, anchoring the entire Solution Architecture Document (SAD).
When to use it:
Highly recommended for almost all new system deployments (both COTS and Custom Dev). Even if a COTS product isn’t fundamentally changing how the business operates, the specific business capability the new tool is supporting should still be mapped.
When NOT to use it:
Omit this if the solution is a backend infrastructure or hardware refresh (e.g., swapping storage arrays, upgrading network switches, patching OS versions) where the overarching application layer and business capabilities are completely untouched.
Example:
