Reviews are integral part of Software life cycle and must be done at each milestone during course of software development. More effective is the review process better would be the code quality & lesser would be the cost of development. In order to assist development team with key areas to be taken care of as part of review process, below is the checklist for review of various documents during software life cycle:
| Function Specification Review Checklist: | |
| 1 | Is FS document is in proper format and understandable? |
| 2 | Is requirements clear? |
| 3 | Check if functionality can impact existing behavior or support existing data? |
| 4 | Is FS document is in proper format and understandable? |
| 5 | Interface and information of satellite application mentioned? |
| 6 | Scenarios & Sample data provided & clear? |
| 7 | Queries mentioned as part of QA sheets are closed? |
| 8 | Assumptions are defined and communicated to client? |
| 9 | Is FS document is in proper format and understandable? |
| Impact Analysis (IA) & Level Of Effort (LOE) Review Checklist: | |
| 1 | Impacted code of each functionality mentioned? |
| 2 | Complexity of required change & LOE are justifiable? |
| 3 | UT cases effort percentage justifiable? |
| 4 | Documentation effort quoted & justifiable? |
| Technical Specification Review Checklist: | |
| 1 | Is mapping of each requirement in FS defined? |
| 2 | Are required Code Design changes detailed? |
| 3 | Is Interface with other application is defined and signed off? |
| 4 | Database design changes – check for existing design, keys, indexes, schema nomenclature e.t.c. |
| 5 | Database populate script – regressions taken care off, default values mentioned e.t.c. |
| 6 | Boundary conditions mentioned? |
| 7 | Dependencies with satellite applications taken care off |
| 8 | Support & reasoning for best possible solution provided by developer in case alternative solutions available? |
| Test Review Checklist: | |
| 1 | 100% Coverage |
| 2 | Prerequisite of any test case mentioned? |
| 3 | Regression and Boundary condition test cases mentioned? |
| 4 | Simulators & test stubs usage – in case of dependencies with satellite application. |
| Requirement Traceability Matrix (RTM) Checklist: | |
| 1 | Mapping to all documents (functionality wise) is fulfilled? |
| 2 | RTM document and references updated after changed FS? |
| Code Review Checklist: | |
| 1 | Mapping to all TS sections completed? Check for missing implementation? |
| 2 | Coding guidelines followed? |
| 3 | Quality of Code – Is Code optimized and well structured? |
| 4 | Proper Code comments provided? |
| 5 | Best practices at code level must be used? |
| 6 | UT cases executed successfully? |
| Delivery Review Checklist: | |
| 1 | Code base lining done? |
| 2 | Delivery is fully validated? |
| 3 | Package installation done locally before sending to client? |
| 4 | Anti-Virus scan on delivery package done? |
| 5 | Is Nomenclature of package files correct & well communicated? |
| 6 | Installation document provided? |
(Visited 267 times, 1 visits today)
