Detail Design Review Template - Ohio Higher Ed



Purpose: The purpose of this document is to provide a guide to conduct a review of the Detailed Design artifacts.

|Project Identification |

|Project Name |Project Number |Date Created |

| | |static and the footer should reflect |

| | |the revision. > |

|Program Manager |Project Manager |

| |

|Completed by |

| |

|Category |Design Review Considerations |Yes |No |

|Design Consistency |Verify variables and function names conform to established standards. | | |

|Design Consistency |Verify variables and function are consistent. | | |

|Design Completeness |Verify the design covers all requirements. | | |

|Architectural Completeness |Verify the architectural design completely describe the system. | | |

|Architectural Completeness |Verify all specified outputs are produced. | | |

|Architectural Completeness |Verify all required inputs are furnished. | | |

|Architectural Completeness |Verify all components represent the problem solution. | | |

|Architectural Completeness |Verify all functions are completely described. | | |

|Architectural Completeness |Verify all attributes are completely described. | | |

|Architectural Completeness |Verify all interdependencies are completely described. | | |

|Architectural Completeness |Verify all exceptions are described. | | |

|Architectural Completeness |Verify all component items adhere to system constraints. | | |

|Design Entities Name |All design entities are unique and descriptive. | | |

|Initialization |Check for variable initialization. | | |

|Procedure/Method |Verify procedures/methods have input/output defined. | | |

|Procedure/Method |Verify consistency for procedures/methods. | | |

|Procedure/Method |Verify completeness for procedures/methods. | | |

|Logic |Verify program sequencing is correct. | | |

|Logic |Verify lists, etc. are in the proper order | | |

|Logic |Verify recursion unwinds properly. | | |

|Logic |Verify all loops are properly initiated, incremented, and terminated. | | |

|Logic Verification |Verify specified logic properly describe the desired system. | | |

|Logic operators |Check every logic function for proper () | | |

|Calls |Make sure the call for procedures/method is appropriate. | | |

|Calls |Check for names. | | |

|Calls |Check for inputs/outputs. | | |

|Reuse |Verify reused components are used as intended. | | |

|Reuse |Verify all methods/objects reuse are proper and that the input/output are correct. | | |

|Reuse |Check for consistency | | |

|Reuse |Check for completeness | | |

|Defect Fixes |Verify all defects recorded in the Defects Log. | | |

|Defect Fixes |Verify fix to all reported defects. | | |

|Special Cases |Check all special cases. | | |

|Special Cases |Verify empty, full, minimum, maximum, negative, and zero conditions. | | |

|Special Cases |Verify out of limits, overflow, and underflow conditions. | | |

|Special Cases |Ensure "impossible" conditions are absolutely impossible. | | |

|Special Cases |Verify consideration of all incorrect input conditions. | | |

................
................

In order to avoid copyright disputes, this page is only a partial summary.

Google Online Preview   Download