A component is a distinct major part of a software system. Components can be reused to accelerate development, assessed for business-criticality and support needs, and shown as connected parts of an enterprise architecture. section 8.7 section 10.4 section 11.2.7
When reviewing an enterprise system:
- Identify components critical to customer service and continuity, then ask who can help if each fails. section 10.4
- Match support coverage to gaps in team experience or availability; avoid paying for coverage the team does not need. section 10.4
- Map major components and their connections at a high level; leave implementation details for separate, more detailed maps. section 11.2.7
Mapping a profile service
A top-level diagram can show a File Microservice connected to the user-profile module for profile photos without specifying whether they communicate through an API, queue, or shared directory. section 11.2.7
Use the architectural diagram as a visual example of major components and their connections. section 11.2.7









