Module 1 (Day 1):

• course introduction;
• revision of ISEB Foundation materials;
• testing in the life cycle:
  • the waterfall model;
  • V-model;
  • spiral model;
  • pre-planned incremental delivery;
  • RAD/DSDM;
  • evolutionary model;
  • object oriented; and
  • eXtreme Programming;
• the V-model and the test phases;
• the tester/developer relationship;
• the generic test process;
• planning:
  • policy;
  • strategy;
  • project test plan (IEEE 829); and
  • phase test plan;
• specification;
• execution;
• recording;
• checking for test completion;
• testing and risk;
• product and project risks;
• quantitative and qualitative risks;
• the risk management process and stakeholders; and
• risk identification.

Module 1 (Day 2):

• risk analysis;
• risk categorisation;
• risk weighting factors;
• ISO 9126 – risk analysis;
• ongoing risk analysis;
• risk mitigation;
• risk mitigation options;
• risk and the test strategy;
• risk and test techniques;
• choosing test techniques;
• industry standards (IEC 61508, DO-178, ISO 14598/5);
• subsumes ordering of test techniques (BS 7925-2);
• test estimation and scheduling;
• expert based estimation;
• formula based estimation;
• function/test point analysis;
• roles and responsibilities;
• high-level test execution schedule;
• detailed test execution schedule;
• formal specification process;
• specifying additional tests;
• handover to testing; and
• pre-acceptance meeting.
  

Module 2 (Day 3):

• test checking and recording;
• checking for test completion;
• test progress monitoring and control;
• progress monitoring;
• test progress reporting;
• incident management (IEEE 1044 and IEEE 1044.1);
• test management tools;
• people skills:
  • individual skills;
  • test team dynamics;
• fitting testing within an organisation;
• team motivational factors.
  

Module 2 (Day 4):

• introduction to reviews;
• planning and kick-off meeting;
• planning overview;
• kick-off meeting;
• individual preparation;
• inspection tools;
• logging meeting;
• causal analysis;
• re-work, follow-up and exit;
• formal technical reviews;
• walkthroughs;
• implementing reviews.

Module 3 (Day 5):

• introduction to static analysis;
• static analysis techniques:
  • compilers;
  • code syntax;
  • data flow analysis;
  • control flow graphing; and
  • complexity measures (McCabe, lines of code, Halstead Metrics);
• static analysis testing tools;
• component testing;
• structural testing;
• white box test techniques:
  • data-flow testing;
  • branch/decision testing;
  • branch condition testing;
  • branch condition combination testing;
  • modified condition decision testing;
  • linear code sequence and jump (LCSAJ);
  • and all paths testing;
• test coverage;
• coverage and dynamic analysis;
• dynamic analysis tools;
• component integration testing:
  • top down approach;
  • bottom up approach; and
  • functional incremental approach;
• typical integration problems.

Module 3 (Day 6):

• system testing;
• functional system testing;
• black box test techniques:
  • equivalence partitioning;
  • boundary value analysis;
  • state transition;
  • cause/effect;
  • classification tree;
  • syntax testing; and
    • random testing;
• systems integration testing;
• acceptance testing:
  • requirements based acceptance testing;
  • business process based acceptance testing;
  • use cases;
  • user acceptance testing;
  • alpha testing;
  • beta testing;
  • contract acceptance testing; and
  • operational acceptance testing.
    

Module 4 (Day 7):

Non-functional testing:

• inter-relationships and balance;
• load;
• performance, volume and stress;
• security;
• usability;
• reliability, availability and recovery;
• operability:
• installability;
• configuration;
• interoperability;
• compatibility
• memory management;
• maintainability;
• conversion
• portability; and
• procedure.

Non-functional test techniques;

• performance;
• stress volumes;
• security;
  • security testing tools;
• usability:
  • static usability testing;
  • dynamic usability testing;
  • SUMI; and
  • WAMMI;
• software reliability engineering testing;
• recovery and disaster recovery testing.

Non-systematic test techniques:

• ad hoc testing;
• intuitive testing;
• error guessing;
• exploratory testing;
• testing and patterns; and
• emotional testing.

Module 4 (Day 8):

• introduction to process improvement;
• ISO 15504 (SPICE);
• Capability Maturity Model;
• Capability Maturity Model Integration;
• managing process change;
• test process improvement models:
  • TPI Model; and
  • Test Maturity Model;
• TMM and CMM;
• test tools;
• tool selection and implementation;
• course revision;
• examination hints and tips.
  

Revision Day (1 day):

The revision day comprises key slides for each topic area from the course syllabus and sample examination questions for the students to experience answering examination-type questions under exam conditions.

Students are advised to request, in advance, topic areas to be covered on the revision day as all material cannot be covered in a single day.

Objectives:

• To revise the key areas of the ISEB Practitioner Certificate In Software Testing syllabus;
• to introduce students to the type of exam questions that can be expected in the examination;
• to give students experience of answering questions under examination conditions; and
• to understand exam technique and time management issues required to pass the examination.