High-level design

In small and medium-sized solutions I often show a drawing of the system’s key components, followed by a table that briefly describes each one. In those cases I usually don’t need the interfaces, structure and behavior subchapters.

If the solution architecture exposes services to external systems I always add the interfaces subchapter to describe how the interfaces map to backend components.

In larger systems, with many different technologies and subsystems (for example SAP, Dynamics etc.), I usually add the structure and behavior subchapters.