* Context Analysis:
* The scenario involves tight integration, architectural design, and data transformations, requiring detailed and structured approaches.
* Access to architectural documents and experienced testers (former developers) aligns with model- based and white-box techniques.
* Evaluation of Options:
* A. Model-based and white-box:
* Correct. Model-based testing leverages design documents, while white-box testing uses internal knowledge for detailed integration testing.
* B. Experience-based and black-box:
* Incorrect. This is less structured and doesn't utilize available design documentation or tester expertise.
* C. Risk-based and non-functional:
* Incorrect. Risk-based testing focuses on high-priority areas but doesn't leverage the design documents for integration specifics.
* D. Requirements-based and functional:
* Incorrect. While functional testing is relevant, requirements-based testing does not utilize internal system knowledge effectively.
* Syllabus Alignment:
* ISTQB emphasizes model-based and white-box testing as appropriate for systems with complex integrations (TM-1.2.6).
References:
ISTQB Advanced Level Test Management Syllabus (TM-1.2.6)