Separate concerns with views
Choose stakeholder-specific views based on concerns instead of forcing one diagram to serve every audience.
The move: stop asking one view to answer every question. Stakeholder Start by naming who must use the architecture description: product leader, regulator, operations team, security architect, finance sponsor, data owner, engineering lead, or vendor partner. Concern A concern is the question that stakeholder needs answered. Examples: "Can this recover within 15 minutes?" "Where does personal data cross a boundary?" "Which investment unlocks the most value?" "Who owns the golden record?" Viewpoint A viewpoint defines how a view answers that concern: notation, scope, relationships shown, and interpretation rules. Without this, teams mistake visual polish for communicative power. Use multiple views…
Sign up free — one personalized lesson every day, matched to your role and goals.
Already have an account? Sign in