2012/11/12 by Corentin Burnay, Burnay, Corentin, Ivan Jureta +3
Business, Management and Accounting · Computer Science · #Advanced Software Engineering Methodologies #Business Process Modeling and Analysis #FOS: Computer and information sciences #Software Engineering (cs.SE) #Software Engineering Research
paper · pdf · doi:10.48550/arxiv.1211.2620
openalex publication_date 2012/11/12 · openalex created_date 2016/06/24 · openalex updated_date 2026/07/28
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.