
- Forum
- Testing
- Software Testing
- Tech Spec Review Checklist
Tech Spec Review Checklist
This is a discussion on Tech Spec Review Checklist within the Software Testing forums, part of the Testing category; Friends, I need to create a review checklist for the technical specification(from client). Please let me know what areas we ...
-
07-20-2006, 03:02 AM #1
- Join Date
- Jul 2006
- Answers
- 1
Tech Spec Review Checklist
Friends,
I need to create a review checklist for the technical specification(from client). Please let me know what areas we need to check and if any one have one please share it with me..
Thanks & Regards,
Anand M
-
The broader classification you have to check for is
DESIGN REFERENCE
DESIGN APPROACH
SOFTWARE PROGRAM REQUIREMENTS
PROBLEM AREAS
-
Yes as mentioned by caradoc the broader aspects of review checklist must have the above items. I would tell you some sub items to be paced in DESIGN REFERENCE of your review checklist. They are
What are the applicable Specification/Proposal Paragraphs?
What design data is required?
Is all data available?
Assumptions made when data is not available
-
Some review items under the heading SOFTWARE PROGRAM REQUIREMENTS are as below:
SOFTWARE PROGRAM REQUIREMENTS:
Was a simplified flow chart and description provided?
Were methodologies addresses?
Function generation
Initialization parameters
Data table layout
Subroutine linkage
Runtime vs spec requirement
Total memory vs spec requirement
-
Code Review Checklist
Standards Related:
1.Does the code follow the coding conventions of the organization?
2.Does the code follow any coding conventions that are platform specifics?
Style Related:
1.Are unhealthy programming constructs being used in the program?
2.Is there usage of specific idiosyncrasies of a particular machine architecture or a given version of an underlying product?
3. Is sufficient attention being paid to readability issues like indentation of code?
Miscellaneous:
1.Have you checked for memory leaks?
Documentation Related:
1.Is the code adequately documented, especially where the logic is complex or the section of code is critical for product functioning?
2.Is appropriate change history documented?
3.Are the interfaces and the parameters thereof properly documented?
Last edited by admin; 05-07-2010 at 10:01 AM.
-
Sponsored Ads

Reply With Quote





