volume_mute

Two Reasons Interviews Fail for Domain Knowledge

publish date: 2026/06/06 20:00:12.789413 UTC

volume_mute

Interviews can be difficult for eliciting domain knowledge for two specific reasons. Identify both reasons.

Domain specialists are always too busy to participate in interviews

Domain specialists use terminology and jargon that is specific to their domain, which requirements engineers may misunderstand

Interviews always take too long for domain knowledge topics

Some domain knowledge is so familiar to stakeholders that they assume it is obvious and don't think to mention it

Domain knowledge can only be captured in mathematical notation

Correct Answer

(1) Domain specialists use terminology and jargon that is specific to their domain, which requirements engineers may misunderstand

(2) Some domain knowledge is so familiar to stakeholders that they assume it is obvious and don't think to mention it

Explanation

Two reasons interviews fail for domain knowledge: (1) Domain specialists use precise, subtle jargon that requirements engineers may misinterpret. (2) Some domain knowledge is so fundamental that stakeholders assume it is common knowledge and don't mention it — for example, a librarian assumes everyone knows all acquisitions are catalogued before being shelved.

Reference

Software Engineering, Ian Sommerville, 9th edition

Quizzes you can take where this question appears

Requirements Elicitation and Analysis