Checklist: Architecture Overview
This checklist provides a set of questions that can be used as a guide when validating the Architecture Overview.
Relationships
Related Elements
Check Items
Is the Architecture Overview understandable?
  • Is it understandable by the target stakeholders?
  • Is it defined to the appropriate level of detail?
  • Are its concepts described in the simplest way possible?


Do architectural goals reflect and support project goals?
Are the main elements of the architecture described in sufficient detail?
Is the notation used on diagrams clear?
  • Do diagrams contain a key explaining the notation used?
  • If a standard notation like UML is used, do the diagrams follow the standards?
  • If custom notation is used, does the key clarify the meaning of colors, shapes, and icons used?
Is the Architecture Overview a reasonable abstraction of the system?
Have the main functional and non-functional requirements been factored in?
Have potential risk areas been highlighted?
  • If the architecture uses technologies that are new or high risk to implement, these have been highlighted as potential risk areas?
If alternative architectures are presented, are the pro's and cons of each clear?