V-model
Although variants of the V-model exist, a common type of V-model uses four test l
evels, corresponding to the four development levels. The four levels used in this syllabus are:component (unit) testing;integration testing;system testing;acceptance testing.In practice, a V-model may have more, fewer or different levels of development and testing, depending on the project and the software product. For example, there may be component integration testing after component testing, and system integration testing after system testing. Software work products (such as business scenarios or use cases, requirements specifications, design documents and code) produced during development are often the basis of testing in one or more test levels. References for generic work products include Capability Maturity Model Integration (CMMI) or ‘Software life cycle processes’. Verification and validation (and early test design) can be carried out during the development of the software work product
evels, corresponding to the four development levels. The four levels used in this syllabus are:component (unit) testing;integration testing;system testing;acceptance testing.In practice, a V-model may have more, fewer or different levels of development and testing, depending on the project and the software product. For example, there may be component integration testing after component testing, and system integration testing after system testing. Software work products (such as business scenarios or use cases, requirements specifications, design documents and code) produced during development are often the basis of testing in one or more test levels. References for generic work products include Capability Maturity Model Integration (CMMI) or ‘Software life cycle processes’. Verification and validation (and early test design) can be carried out during the development of the software work product
No comments:
Post a Comment