2. Testing throughout the Software Life Cycle. 2.1. Software Development models.
ISTQB. Foundation Level.
2. Testing throughout the Software Life Cycle.
2.1. Software Development models.
2.1.1. V-model (Sequential Development model)
2.1.2. Iterative-incremenatl Development model.
2.1.3. Testing with a Life Cycle model.
Термины: Commercial Off-The-Shelf software, V-model, Iterative development model, validation, verification.
Commercial Off-The-Shelf software: See off-the-shelf software
Off-the-shelf software: A software product that is developed for the general market, i.e. for a large
number of customers, and that is delivered to many customers in identical format.
V-model: A framework to describe the software development lifecycle activities from requirements
specification to maintenance. The V-model illustrates how testing activities can be integrated into
each phase of the software development lifecycle.
Iterative development model: A development lifecycle where a project is broken into a usually large number of iterations. An iteration is a complete development loop resulting in a release (internal or external) of an executable product, a subset of the final product under development, which grows from iteration to iteration to become the final product.
Validation: Confirmation by examination and through provision of objective evidence that the
requirements for a specific intended use or application have been fulfilled.
Verification: Confirmation by examination and through provision of objective evidence that specified requirements have been fulfilled.
2.1.1. V-model (Sequential Development model)
Четыре основных уровня тестирования:
Валидацию и верификацию, и разработку тестов можно делать, пока продукт в разработке.
2.1.2. Iterative-incrementаl Development model
Вес делается за короткие циклы разработки - требования, дизайн, разработка и тестирование системы. В каждую итерацию можно (и нужно) тестировать на нескольких уровнях.
При этом крайне важно регрессить, что ничего не сломалось то, что было сделано во всех предыдущих итерациях. Валидируют и верифицируют по ходу каждой итерации.
2.1.3. Testing with a Life Cycle model
Какова бы ни была модель, всегда есть признаки хорошего тестирования:
Контрольные вопросы:
2.1.1. Explain the relationship between development, test activites and work products in the development life cycle, by giving examples using project and product types.
2.1.2. Recognize the fact that software development models must be adapted to the context of project and product characteristics.
2.1.3. Recall characteristics of good testing that are applicable to any life cycle model.
2. Testing throughout the Software Life Cycle.
2.1. Software Development models.
2.1.1. V-model (Sequential Development model)
2.1.2. Iterative-incremenatl Development model.
2.1.3. Testing with a Life Cycle model.
Термины: Commercial Off-The-Shelf software, V-model, Iterative development model, validation, verification.
Commercial Off-The-Shelf software: See off-the-shelf software
Off-the-shelf software: A software product that is developed for the general market, i.e. for a large
number of customers, and that is delivered to many customers in identical format.
V-model: A framework to describe the software development lifecycle activities from requirements
specification to maintenance. The V-model illustrates how testing activities can be integrated into
each phase of the software development lifecycle.
Iterative development model: A development lifecycle where a project is broken into a usually large number of iterations. An iteration is a complete development loop resulting in a release (internal or external) of an executable product, a subset of the final product under development, which grows from iteration to iteration to become the final product.
Validation: Confirmation by examination and through provision of objective evidence that the
requirements for a specific intended use or application have been fulfilled.
Verification: Confirmation by examination and through provision of objective evidence that specified requirements have been fulfilled.
2.1.1. V-model (Sequential Development model)
Четыре основных уровня тестирования:
- Component (or unit) testing.
- Integration testing.
- System testing.
- Acceptance testing.
Валидацию и верификацию, и разработку тестов можно делать, пока продукт в разработке.
2.1.2. Iterative-incrementаl Development model
Вес делается за короткие циклы разработки - требования, дизайн, разработка и тестирование системы. В каждую итерацию можно (и нужно) тестировать на нескольких уровнях.
При этом крайне важно регрессить, что ничего не сломалось то, что было сделано во всех предыдущих итерациях. Валидируют и верифицируют по ходу каждой итерации.
2.1.3. Testing with a Life Cycle model
Какова бы ни была модель, всегда есть признаки хорошего тестирования:
- Для каждой активности программистов есть соответствующая активность тестеров.
- Каждый уровень тестирования имеет специфические для этого уровня цели тестирования.
- Анализ и разработка тестов для данного уровня должны начинаться во время соответствующей деятельности программистов.
- Тестеры должны ревьюить документов и прототипов.
Контрольные вопросы:
2.1.1. Explain the relationship between development, test activites and work products in the development life cycle, by giving examples using project and product types.
2.1.2. Recognize the fact that software development models must be adapted to the context of project and product characteristics.
2.1.3. Recall characteristics of good testing that are applicable to any life cycle model.