Control Activities
Functions to be Tested and Functions not to be tested will be covered.
all the functions not to be tested, along with the reason of not testing, for example,” low risk, code reused and previously tested with 100% satisfaction”. The following scheme is recommended for listing and description of features not to be tested.
Course Material
- Identifying Project Area
- Project Proposal Template
- Software Requirements Specifications
- Functional Specification Document
- Design Document
- Design Considerations
- System Architecture
- Software Testing
- Unit Testing
- Integration and System Testing
- Control Activities
- Test Case Design and Description
- Traceability Matrix
- Chapters 13
- Department CS & IT
- Teacher
Mr. Saad Razzaq
