Design Review Checklist
The purpose of this checklist is to ensure the quality of design specifications by checking for
inconsistencies and violations of design principles.
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.
15.
16.
17.
18.
19.
20.
21.
22.
23.
24.
25.
26.
27.
28.
29.
30.
31.
Is there a level 0 physical data flow diagram of the proposed system?
Does the DFD violate any of the data flow diagramming rules (e.g. no data flows directly between 2
data stores)?
Is there a list of identifies inputs and outputs that need to be designed?
For each item on the input/output list, is it perfectly clear exactly which data flow(s) it corresponds to
on the proposed physical DFD?
Are there at least 2 prototype input (screen or form) designs?
Are there at least 2 prototype output (report) designs?
For each prototype input and output, is it clear what medium (e.g. paper, electronic, etc.) is being used?
For each prototype input and output, does the choice of medium make sense given the intended use and
audience of the input or output?
For each prototype input and output, is the layout of all the elements clearly shown?
For each prototype input and output, is it clear if and how color and highlighting are used?
For each prototype input and output, is it shown with actual data?
Is the terminology consistent across all the prototype inputs and outputs?
Is the use of color consistent across all the prototype inputs and outputs?
Is the placement of common elements (e.g. navigation buttons, etc.) consistent across all the prototype
inputs and outputs?
Is there an over-use of color or other visual techniques (e.g. blinking) on any of the prototype inputs or
outputs?
Is there any evidence of designer bias in the design of any of the prototype inputs or outputs?
On all the prototype inputs and outputs, is the right administrative information (e.g. page numbers,
dates, etc.) shown properly?
On all the prototype inputs and outputs, are page breaks and screen breaks handled appropriately?
On the prototype inputs, could any of the items that the user has to type in be eliminated (e.g. through
checkboxes, menus, etc.)?
Does the overall interface description address how the user navigates around the system, including
how they get from one screen to another, or how the system is started and shut down?
Does the overall interface description address what mechanisms are used for user communication with
the system (e.g. menus, commands, etc.)?
Does the overall interface description address mechanisms for system security?
Does the overall interface description address the design of error messages, status messages, and user
prompts?
Does the overall interface description address how help will be provided?
Is an ER diagram included and does it appear to be correct?
Do all the data items entered on the prototype inputs correspond to something on the ER diagram?
Do all the data items shown on the prototype outputs correspond to something on the ER diagram?
Are there at least 2 logic models, representing 2 different processes, and do they appear to be correct?
Are the logic models consistent with the level 0 DFD?
Does the usability assessment plan call for the system to be tested by real users?
Does the usability assessment plan specify what measures will be used and what values of those
measures will be considered “acceptable”?