Design Document Review Form

Design Review
rvuDesign
SQAP v2.1+
Document Number & Version
Guidance
SDLC Stage
Planning
Design
Integration & Test
Requirements
Development
Installation & Acceptance
Technical
Quality Assurance
Review Type
End-user
Review...
Review...
Review...
Review Scope
Full Review
Complete contents of
deliverable are reviewed
Update Review
Review is limited to changes since last
version of deliverable
Reviewer Concurrence
Unqualified Concurrence
Reviewer Signature
Deliverable is fully acceptable
Substantial Concurrence
Deliverable is acceptable, but could be improved as noted
NO CONCURRENCE
Deliverable is NOT acceptable: Issues as noted
Reset
Comments
Design Review: End-user Review
Concur
Minor
Issues
DO
Not
NOT
Reviewed
Concur
The table structure shown in the Physical Database Description (PDD)
accurately represents the desired storage structure.
The field definitions shown in the PDD accurately represent the fields
needed in this application
The core application design elements accurately represent the common
functions expected to be available for each data area.
The access control permissions for each data entry area are accurately
described.
The summary listing screens for each data area are accurately described.
The data entry & detail display screen layouts and business rules for each
data area are accurately described.
The simple, predefined, and ad hoc searches for each data area are
accurately described.
The predefined reports for each data area are accurately described.
The predefined operations for each data area are actually described.
NOTE: This page is not applicable for Technical or QA review
Comments
Done
Design Review: Technical Review
Concur
Minor
Issues
DO
Not
NOT
Reviewed
Concur
The table structure described in the Physical Database Description (PDD)
is relationally compliant to at least the Third Normal Form.
The PDD accurately describes all fields, their default values, formats,
range limitations, "Tip Help", and business rules for the application.
The access control mechanisms described in the design document are
compatible with the default capabilities of the target development tools.
The design elements for the core application functions are specified at a
level sufficient for development to begin.
The summary listing forms and associated business rules for each data
area are specified at a level sufficient for development to begin.
The data entry & detail display forms and associated business rules for
each data area are specified at a level sufficient to begin development
The simple, predefined, and ad hoc searches for each data area are
specified at a level sufficient for development to begin.
The predefined reports for each data area are specified at a level sufficient
for development to begin.
The predefined operations for each data area are specified at a level
sufficient for development to begin.
NOTE: This page is not applicable for End-user or QA review
Comments
Done
Design Review: Quality Assurance Review
Concur
Minor
Issues
DO
Not
NOT
Reviewed
Concur
A design constraints compliance statement is included in the design
document.
A physical database description is made available separately, and included
by reference in the design document.
Specific sets of design elements are in place for each data area identified
in the design document.
One or more End-user reviews for this deliverable have been completed.
One or more Technical reviews for this deliverable have been completed.
All End-user and Technical reviews indicate substantial or unconditional
concurrence.
A Requirements Traceability Matrix Report indicates the traceability matrix
is valid for the SPMP/CIP, Requirements, and Design documents.
NOTE: This page is not applicable for End-user or Technical review
Comments
Done
Design Review: Reviewer Comments
Reviewer Comments / Issues
Done