CTFL_SYLL_4.0 · Question #113
In addition to thorough testing of the requirements specification, a development team aims to involve users as early as possible in the development process, using practices such as prototyping, to…
The correct answer is B. Absence-of-errors fallacy. The absence-of-errors fallacy is the mistaken belief that just because a software system is free of defects, it will meet the user's needs and expectations. Involving users early through practices like prototyping helps ensure that the development team is building the right…
Question
In addition to thorough testing of the requirements specification, a development team aims to involve users as early as possible in the development process, using practices such as prototyping, to ensure that the software systems being developed will meet the users' expectations. This approach is especially useful at mitigating the risks associated with one of the seven testing principles, which one?
Options
- ATests wear out
- BAbsence-of-errors fallacy
- CWorking software over comprehensive documentation.
- DDefects cluster together
How the community answered
(39 responses)- A5% (2)
- B79% (31)
- C3% (1)
- D13% (5)
Explanation
The absence-of-errors fallacy is the mistaken belief that just because a software system is free of defects, it will meet the user's needs and expectations. Involving users early through practices like prototyping helps ensure that the development team is building the right system that meets user expectations, not just a system that is defect-free. This approach aligns with the testing principle that emphasizes understanding the users' needs and ensuring the system fulfills them. This principle is explained in the ISTQB CTFL Syllabus v4.0.
Topics
Community Discussion
No community discussion yet for this question.