Today I am just trying to give you the wxtract of syllabus so that you will also not miss anything and so do I.
Note: This syllabus is ging to change by 2012 , so you got exactly 9 months to give this exam :)
This section provides a list of detailed learning objectives for the Test Manager module.
In general all parts of this syllabus are examinable at a K1 level. That is the candidate will recognize,
remember and recall a term or concept.
For this reason the table below only contains learning objectives on K2, K3 and K4 levels.
Introduction to Test Manager Syllabus – [60 minutes]
(Including revision of ISTQB® Foundation Level syllabus)
Chapter 1: Basic Aspects of Software Testing – [150 minutes]
1.2 Testing in the Software Lifecycle
· (K2) Describe how testing is a part of any software development and maintenance activity
· (K4) Analyze software life-cycle models and outline the most appropriate tasks/test activities
to be executed.(distinguish between test and development activities)
1.3 Specific Systems
· (K2) Explain by giving examples the specifics of testing systems of systems
· (K2) Explain why the three main outcomes of testing safety critical systems are required to
demonstrate compliance to regulations
1.4 Metrics & Measurement
· (K2) Describe and compare the standard testing related metrics
· (K3) Monitor testing activities by measuring the test object(s) and the test process
Chapter 2: Testing Processes – [120 minutes]
2.3 Test planning & control
· (K2) Describe, giving examples, how test strategies affect test planning
· (K2) Compare test work products and explain by giving examples relations between
development and testing work products
·(K2) Classify test control activities related to determine if test mission, strategies, and
objectives have been achieved
2.5 Test implementation & execution
· (K2) Explain the pre-conditions for test execution
· (K2) Explain by giving examples the advantages and disadvantages or early test
implementation considering different testing techniques
·(K2) Explain the reasons why users and/or customers might be included in test execution.
·(K2) Describe how the level of test logging might vary depending on test level
2.6 Evaluating Exit Criteria and Reporting
· (K2) Summarize the information necessary to collect during the test process to support
accurate reporting and evaluation against exit criteria
2.7 Test Closure Activities
· (K2) Summarize the four groups of test closure activities
· (K3) Generalize lessons learned in test closure phase in order to discover areas to improve or
repeat
Chapter 3: Test Management – [1120 minutes]
3.2 Test Management Documentation
· (K4) Outline test management documents such as Test Plan, Test Design Specification, and
Test Procedure in compliance with IEEE 829
· (K2) Describe at least 4 important elements of a test strategy / approach and which documents according to IEEE 829 contain elements of test strategy
· (K2) Illustrate how and why deviations from the test strategy are managed in the other test
3.3 Test Plan Documentation
· (K2) Summarize the IEEE 829 structure of a master test plan
· (K2) Paraphrase and interpret the topics suggested by the standard IEEE 829 structure of a
test plan with respect to tailoring to an organization, risk of a product, and risk, size and
formality of a project
3.4 Test Estimation
· (K3) Estimate the testing effort for a small sample system using a metrics based and an
experience-based approach considering the factors that influence cost effort and duration
· (K2) Understand and give examples to the factors listed in the syllabus which may lead to
inaccuracies in estimates
3.5 Scheduling Test Planning
· (K2) Explain the benefits of early and iterative test planning. Support your explanation by examples
3.6 Test Progress Monitoring & Control
· (K2) Compare the different procedures for controlling test progress
· (K2) Give at least 5 conceptually different examples about how test progress findings
influence the course of the test process
· (K4) Use findings related to the test progress observed during monitoring and control activities and measures in order to outline an action plan to improve the current test process. Suggest improvements
· (K4) Analyze test results and determine the test progress, documented into a monitoring report and a final test summary report covering all 4 reporting dimensions
3.7 Business Value of Testing
· (K2) Give examples (measures) for each of the 4 categories determining the “cost of quality”.
· (K3) For a given context list the quantitative and/or qualitative values that apply
3.8 Distributed, Outsourced & Insourced Testing
· (K2) List risks, commonalities and differences between the 3 staffing strategies (distributed,
outsourced & in-sourced testing)
3.9 Risks-Based Testing
3.9.1 Introduction to Risk Based Testing
· (K2) Explain the different ways, how risk-based testing responds to risks
· (K4) Identify risk within a project and product, and determine the adequate test strategy and
test plan based on these risks
3.9.2 Risk Management
· (K3) Execute a risk analysis for product from a testers perspective, following the specific
approach FMEA
· (K4) Summarize the results from the various perspectives on risk typically held by key project
stakeholders, and use their collective judgment in order to outline test activities to mitigate
risks
3.9.3 Risk Management in the Lifecycle
· (K2) Describe characteristics of risk management that require it to be an iterative process
· (K3) Translate a given risk based test strategy to test activities and monitor its effects during
the testing
· (K4) Analyze and report test results and determine / propose residual risks to enable project
managers to make intelligent release decisions
3.10 Failure Mode and Effects Analysis
· (K2) Describe the concept of FMEA, explain its application in projects and benefits on projects
by example
3.11 Test Management issues
· (K2) Compare the test management issues for the Exploratory Testing, Systems of Systems,
and testing safety-critical systems related to strategy, benefits and disadvantages, adequacy
and their impact on planning, coverage, and monitoring and control
Chapter 4: Test Techniques – [0 minutes]
No Learning objectives (at any K-level) apply for the test manager.
Chapter 5: Test of Software Characteristics – [0 minutes
No Learning objectives (at any K-level) apply for the test manager.
Chapter 6: Reviews – [120 minutes]
6.2 The Principles of Reviews
·
(K2) Explain the benefits of reviews compared to dynamic testing and other static testing
techniques
6.4 Introducing Reviews
· (K2) Compare review types with each other and show their relative strengths, weaknesses
·
(K3) Lead a review team through a formal review following the steps identified
·
(K4) Outline a review plan as part of a quality/test plan for a project considering review
techniques considering defects to be found, available skills of staff, and aligned with
appropriate dynamic testing approaches
6.5 Success Factors for Reviews
· (K2) Explain the risks behind not considering the technical, organizational factors and people
issues for performing reviews.
Chapter 7: Incident Management – [80 minutes]
·
(K3) Process a defect following the incident management life cycle procedure as proposed by
·
(K3) Evaluate defect reports against IEEE Standard 1044-1993 and the applied defect
·
(K4) Analyze the defect reports created over time and update the defect taxonomy
Chapter 8: Standards & Test Improvement Process – [120 minutes]
·
(K2) Summarize sources of software standards and explain its usefulness for software testing
8.4 Improving the Test Processes
· (K3) Write and test improvement plan using the generic steps involving the right persons
· (K2) Summarize the testing improvement process as defined by TMM, TPI, CTP, STEP, and
the process areas verification and validation in CMMI
·
(K2) Explain the evaluation criteria of the test improvement models TMM, TPI, CTP, STEP,
and the process areas verification and validation in CMMI
Chapter 9: Test Tool & Automation – [90 minutes]
9.2 Test Tool Concepts
· (K2) Compare the elements and aspects within each of the test tool concepts “Benefits &
Risks”, “Test Tool Strategies”, “Tool Integration”, “Automation Languages”, “Test Oracles”,
“Tool Deployment”, “Open Source Tools”, “Tool Development”, and “Tool Classification”
·
(K2) Describe why and when it is important to create a test tool strategy or road-map for your
·
(K2) Understand the different phases in test tool implementation
9.3 Test Tool Categories
· (K2) Summarize the test tool categories by objectives, intended use, strengths, risks and
examples
· (K2) Summarize specific requirements to test tools and open source test tools used for testing Safety Critical systems
· (K2) Describe important aspects and consequences of different Test Tools and their implementation, usage and effects on the test process.
· (K2) Describe when and why implementing your own tool is an option and its benefits, risks
Chapter 10: People Skills – Team Composition – [240 minutes]
10.2 Individual Skills
· (K3) Use a given questionnaire in order to determine strengths and weaknesses of team members related to use of software systems, domain and business knowledge, areas of systems development, software testing and interpersonal skills
10.3 Test Team Dynamics
· (K3) Perform a gap analysis in order to determine the required technical and soft skills for
open positions in an organization.
10.4 Fitting Testing Within an Organization
· (K2) Characterize the various organizational options and compare them with in-/out source
· (K2) Characterize the various organizational options and compare them with in-/out source and in-/off-shoring.
10.5 Motivation
· (K2) Provide example of motivating and demotivating factors for testers
10.6 Communication
· (K2) Describe by example professional, objective and effective communication in a project
from the tester perspective. You may consider risks and opportunities.
Release Notes CTFL 2011 Syllabus.pd...
Foundation Level 2010- ExamQuestion...