Scribd
Upload
228 views3 pages

Design Review Checklist Ver 1.1

This document is a design review checklist that contains a series of yes/no questions to evaluate a design document. It addresses whether the design meets requirements, interfaces properly internally and externally, handles errors and exceptions, is modular and maintainable, considers various conditions, and whether testing and quality factors are addressed. It also checks if the design reuse components, uses appropriate methodologies, addresses portability, and testability.

Uploaded by

swapnil_bankar
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
228 views3 pages

Design Review Checklist Ver 1.1

This document is a design review checklist that contains a series of yes/no questions to evaluate a design document. It addresses whether the design meets requirements, interfaces properly internally and externally, handles errors and exceptions, is modular and maintainable, considers various conditions, and whether testing and quality factors are addressed. It also checks if the design reuse components, uses appropriate methodologies, addresses portability, and testability.

Uploaded by

swapnil_bankar
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 3

Design Review Checklist

Project Name
Account
Reviewed Document
Reviewer/s

Role

Review Iteration Number

Review Date

Description
Yes / No / NA Remarks / Needed action
Does design address all requirements given in
Requirements Specification/Functional
Specification?
Does the design adequately address the interfaces
with respect to internal and external environment?
Does design consider parallelism issues for
critical interfaces /processes
Is a scheme used for naming of modules, data,
and interfaces? Are all modules, data, and
interfaces uniquely identified?
Are there sequence diagrams and component
diagrams to describe interfaces?
Are all referenced data defined? Are all defined
data used?
Are data grouped for efficient processing?
Is there a logical design available? Are actual
component details available?
Is effective modularity achieved? Are modules
functionally independent?
Are errors/exceptions handled effectively?
Are messages required for debugging and audits
logged?
Are there adequate provisions for audit trail?
Are the following adequately described?
Algorithms
Global data structures
Critical functions
Does design address :

Design Review Checklist

Normal operating conditions


Boundary conditions
Error conditions
Performance Issues
Compatibility Issues
Scalability issues
Environment sizing issues
Have environment set-up and data migration
aspects been considered and documented?
Is design modular and does the design address
maintainability?
Is the design required to support load balancing?
If Yes, is testing on all environments planned?
Have quality factors been explicitly assessed?
Is a traceability matrix that maps requirements to
design available?
Have alternative designs been considered and
optimum design chosen? Have the criteria for the
design choice documented?
Does the Design consider use of reusable
components from other projects?
Are appropriate design methodologies and
patterns considered?
Are portability concerns addressed in design?
Are limitations identified and documented?
Are testability concerns are addresses in the
Design

Project specific points:


Description

Yes / No / NA Remarks / Needed action

Design Review Checklist

You might also like