For research and development of an approach for automatically answering why-questions (why-QA) a data collection was created. The data set was obtained by way of elicitation and comprises a total of 395 why-questions. For each question, the data set includes the source document and one or two user-formulated answers. In addition, for a subset of the questions, user-formulated paraphrases are av...

AbstrAct There BLOCKINare BLOCKINmany BLOCKINmethods BLOCKINin BLOCKINthe BLOCKINarea BLOCKINof BLOCKINdata BLOCKINwarehousing BLOCKINto BLOCKINdefine BLOCKINrequirements BLOCKINfor BLOCKINthe BLOCKINdevelopment BLOCKINof the most appropriate conceptual model of a data warehouse. There is no universal consensus about the best method, nor are there accepted standards for the conceptual modeling ...

This paper shows how the task of assistance to fact-finding has gradually become central to the field of meeting browsing. Requirements elicitation studies could not lead alone to a precise specification, because they depend on the preliminary assumptions of each study. Therefore, user studies were gradually focused towards the most promising task, namely fact finding or verification in multime...

Experts in requirements elicitation use a wide variety of diverse elicitation techniques to understand users’ needs. Less experienced elicitation practitioners frequently use the same technique repeatedly, often because it is the only one they know or they do not know when to use alternative techniques. The authors are constructing a tool that aids less experienced analysts in selecting the mos...

We present a case study that exemplifies an extension of AWARE, a goal oriented requirement elicitation technique, for a collaborative document management system. The case concerns a multinational fast growing Management Consulting company. The system serves both marketing activities and actual work of the variegated consultant community. The system is loaded at “Zero-cost” by the consultants w...

Medical errors are now recognized as a major cause of untimely deaths or other adverse medical outcomes. To reduce the number of medical errors, the Medical Safety Project at the University of Massachusetts is exploring using a process programming language to define medical processes, a requirements elicitation framework for specifying important medical properties, and finite-state verification...

Corresponding Author: Fares Anwar Centre of Software Technology and Management, Faculty of Information Science and Technology, University Kebangsaan Malaysia, Selangor, Malaysia [email protected] Abstract: Requirements elicitation is the most critical phase in software requirements engineering. The process is resource intensive, as it concerns with a lot of dedicated stakeholders gathering ...

Despite the importance of capturing a precise and complete set of requirements in the requirements engineering stage, there are few tools that adequately support requirements analysis in the process of capturing quality related requirements (non-functional requirements). This paper presents ElicitO, a requirements elicitation tool aimed at empowering requirements analysts with a knowledge repos...

Being able to reduce the gap between Requirements Engineering and Software Engineering is crucial to foster the developments of better Informations Systems that more precisely adresses the organizational needs of the stakeholders. One of the key factor toward this objective is adopting methodologies in which the the conceptual level of Requirements Engineering techniques is raised, so that form...

Context. Requirements changes are unavoidable in any software project. Requirements change over time as software projects progress, and involved stakeholders (mainly customers) and developers gain better understanding of the final product. Additionally, time and budget constraints prevent implementing all candidate requirements and force project management to select a subset of requirements tha...