The V-model is a software development life cycle model that defines four test levels that correspond

to four development phases: component (unit) testing with component design, integration testing

with architectural design, system testing with system requirements, and acceptance testing with user

requirements. The V-model emphasizes the importance of verifying and validating each phase of

development with a corresponding level of testing, and ensuring that the test objectives, test basis,

and test artifacts are aligned and consistent across the test levels. Therefore, an organization that

wants to follow the V-model cannot do away with integration testing, as it would break the

symmetry and completeness of the V-model, and compromise the quality and reliability of the

software or system under test. Integration testing is a test level that aims to test the interactions and

interfaces between components or subsystems, and to detect any defects or inconsistencies that

may arise from the integration of different parts of the software or system. Integration testing is

essential for ensuring the functionality, performance, and compatibility of the software or system as

a whole, and for identifying and resolving any integration issues early in the development process.

Skipping integration testing would increase the risk of finding serious defects later in the test

process, or worse, in the production environment, which would be more costly and difficult to fix,

and could damage the reputation and credibility of the organization. Therefore, the correct answer is

D.

The other options are incorrect because:

A . It is not allowed as organizations can decide on the test levels to do depending on the context of

the system under test. While it is true that the choice and scope of test levels may vary depending on

the context of the system under test, such as the size, complexity, criticality, and risk level of the

system, the organization cannot simply ignore or skip a test level that is defined and required by the

chosen software development life cycle model. The organization must follow the principles and

guidelines of the software development life cycle model, and ensure that the test levels are

consistent and coherent with the development phases. If the organization wants to have more

flexibility and adaptability in choosing the test levels, it should consider using a different software

development life cycle model, such as an agile or iterative model, that allows for more dynamic and

incremental testing approaches.

B . It is not allowed because integration testing is not an important test level and can be dispensed

with. This statement is false and misleading, as integration testing is a very important test level that

cannot be dispensed with. Integration testing is vital for testing the interactions and interfaces

between components or subsystems, and for ensuring the functionality, performance, and

compatibility of the software or system as a whole. Integration testing can reveal defects or

inconsistencies that may not be detected by component (unit) testing alone, such as interface errors,

data flow errors, integration logic errors, or performance degradation. Integration testing can also

help to verify and validate the architectural design and the integration strategy of the software or

system, and to ensure that the software or system meets the specified and expected quality

attributes, such as reliability, usability, security, and maintainability. Integration testing can also

provide feedback and confidence to the developers and stakeholders about the progress and quality

of the software or system development. Therefore, integration testing is a crucial and indispensable

test level that should not be skipped or omitted.

C . It is not allowed because integration testing is a very important test level and ignoring it means

definite poor product quality. This statement is partially true, as integration testing is a very

important test level that should not be ignored, and skipping it could result in poor product quality.

However, this statement is too strong and absolute, as it implies that integration testing is the only

factor that determines the product quality, and that ignoring it would guarantee a poor product

quality. This is not necessarily the case, as there may be other factors that affect the product quality,

such as the quality of the requirements, design, code, and other test levels, the effectiveness and

efficiency of the test techniques and tools, the competence and experience of the developers and

testers, the availability and adequacy of the resources and environment, the management and

communication of the project, and the expectations and satisfaction of the customers and users.

Therefore, while integration testing is a very important test level that should not be skipped, it is not

the only test level that matters, and skipping it does not necessarily mean definite poor product

quality, but rather a higher risk and likelihood of poor product quality.

Reference = ISTQB Certified Tester Foundation Level Syllabus, Version 4.0, 2018, Section 2.3, pages

16-18; ISTQB Glossary of Testing Terms, Version 4.0, 2018, pages 38-39; ISTQB CTFL 4.0 - Sample

Exam - Answers, Version 1.1, 2023,