  In Requirements Engineering, requirements elicitation aims the acquisition of
information from the stakeholders of a system-to-be. An important task during
elicitation is to identify and render explicit the stakeholders' implicit
assumptions about the system-to-be and its environment. Purpose of doing so is
to identify omissions in, and conflicts between requirements. This paper offers
a conceptual framework for the identification and documentation of default
requirements that stakeholders may be using. The framework is relevant for
practice, as it forms a check-list for types of questions to use during
elicitation. An empirical validation is described, and guidelines for
elicitation are drawn.
