Test 370: IBM Certified Specialist - Software Quality

Software Test (36%)

1. Demonstrate an understanding of the discipline of testing
2. Demonstrate in one's daily work and plans why testing is necessary
3. Apply a knowledge and understanding of the purpose of testing
4. Evaluate security requirements and differentiate different types of attacks
5. Understand the benefits, costs, and limitations of GUI test automation
6. Write test plans
7. Implement and execute test scripts
8. Determine entry and exit criteria for testing
9. Establish standards for test data
10. Perform risk analysis
11. Plan for contingency testing
12. Plan resources for test implementation
13. Define the test environment
14. Use systematic methods to determine the resources, time needed, and defect capacity of a test team
15. Identify and differentiate the types of metrics useful in the test effort
16. Identify software test tools

Software Development (28%)

1. Apply techniques for improving the efficiency of software development
2. Apply an iterative development process
3. Use a Design Review Checklist for creating, inspecting, and using designs
4. Demonstrate familiarity with the external and internal views of the Design Review Checklist
5. Apply techniques to trigger all exception cases
6. Know the purpose of inspections and how they help improve quality
7. Perform inspections on code and documentation in order to shorten the software development schedule
8. Inspect test specifications, test cases and test plans
9. Perform static analysis
10. Track and report the results of static analysis for inspections as well as to benefit future code design and implementation
11. Identify the importance and purpose of estimation

Software Quality (36%%)

1. Understand quality management systems and standards
2. Measure quality in the product maintenance phase
3. Measure the customer view of product quality, including using surveys
4. Track the ways in which a team's process and practices reduce defects
5. Track Defect Removal Efficiency (DRE)
6. Use the Whole Plan Model to ensure software quality
7. Determine the projected impact of early defect removal practices on a product's resources and schedule
8. Demonstrate an understanding of, and an ability to use, the Whole Plan Model tool
9. Measure quality processes as an overall project indicator
10. Use the metric effort indicator to track efficiency
11. Employ use cases to improve the quality of requirements
12. Define standards a team may use to qualify security requirements
13. Assess security aspects of the product design
14. Measure the effectiveness of a team's inspection process