[ISTQB] 2.1 Software development models (K2)

LO-2.1.1 - Explain the relationship between development, test activities and work products in the development life cycle, by giving examples using project and product types (K2)

Each project is developed within a cycle and driven by a methodology respecting its aims, goals and governance. The life cycle model chosen impacts consequently when and how the testing activities will be undertaken. 

V-model is like a "double" sequential waterfall model where four tests levels are coordinated and verified throughout each stage:
- component testing is focused on functional verification of each module.
- integration testing is focused on interfaces and transactions.
- system testing is focused on the whole product.
- acceptance testing is focused on user's expectations. 

Test design and deliverable reviews can consequently begin earlier in the project lifecycle (at requirements level for example) and can be performed in parallel with development activities.

Iterative (or incremental) life cycles such as RAD, RUP and AGILE are known for their flexibility and their "rapidity" of software's delivery. 
- Testing activities are consequently performed as soon as the function/module is delivered. 
- Integration tests and systems test are executed on each iterations and require a strong configuration management. 
- The customer is finally more involved in acceptance testing. 

LO-2.1.2 - Recognize the fact that software development models must be adapted to the context of project and product characteristics (K1)

Each development model has specified stages carried out in a specific order which would best fit to project's purpose and objectives. 

Testing does not exist in isolation, it is tightly related to software development activities which would help in choosing most appropriate test levels and techniques to use.

In V Model cycle, testing execution is prepared at each development stage: 
- acceptance test preparation begins as soon as user requirements has been validated.
- system test preparation begins during functional specification and technical design and so on.
The main risk is that certain level could be omitted according to project constraints and objectives. 

In Iterative-incremental development, testing (by developer, users and testers) is integrated in the "building" stage of the product:
- The software/product delivered is tested (validation+verification) at several levels during each iteration. 
The main risk is upon regression testing which becomes increasingly important across iterations.

Finally, tests levels may be combined or reorganized according to the nature of the project and also to system architecture (COST software : component testing is not mandatory whereas user acceptance testing would be necessary) 

LO-2.1.3 - Recall characteristics of good testing that are applicable to any life cycle model (K1)

• Each development activity has its corresponding testing activity.
• Each test level has objectives specific to that level.
• Test analysis and design begin with corresponding development activity.
• Documents have to be reviewed by testers for efficient test preparation as soon as drafts are available.