Design Review: A process or meeting during which a system, hardware, or software design is presented to project personnel, managers, users, customers, or other interested parties for comment or approval. Types include critical design review, preliminary design review and system design review.Quality assurance team member leads design review. members from development team and QA team participate in the review.
Input Criteria: Design document is an essential document for the review. A checklist can be used for the review.
Exit Criteria: It includes the filled and completed checklist with the reviewers comments and suggestions and the re-verification whether they are incorporated in the documents.
Code Review: A meeting at which software code is presented to project personnel, managers, users, customers, or other interested parties for comment or approval. QA team member(in case the QA team is only involved in black box testing then the development team lead chairs the review team) leads code review. Members from development team and QA team participate in the review.
Input Criteria: The Coding Standards Document and the Source file are the essential documents for the review. A checklist can be used for the review.
Exit Criteria: It includes the filled and completed checklist with the reviewer's comments and suggestions and the re-verification whether they are incorporated in the documents.
Friday, October 1, 2010
Verification Strategies - Reviews - Design Review and Code Review
Posted by Sunflower at 10/01/2010 11:02:00 AM
Labels: Bugs, Code, Code Review, Criteria, Defects, Design, Design Review, Organization, Process, Reviews, Software, Software testing, Strategies, Verification
Subscribe by Email |
|
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment