Scenarios and goals are effective techniques for requirements definition. Goals are objectives that a system has to meet. They are elaborated into a structure that decomposes decla...
Literature tends to discuss software (and system) requirements quality control, which includes validation and verification, as a heterogeneous process using a great variety of rel...
Assumptions are frequently made during requirements analysis of a system about the trustworthiness of its various components (including human components). These trust assumptions, ...
Charles B. Haley, Robin C. Laney, Jonathan D. Moff...
Pre-requirements specification tracing concerns the identification and maintenance of relationships between requirements and the knowledge and information used by analysts to info...
In the last decade, software product management has received much practical attention, though research in this area is still scattered. In this paper, we present a reference frame...
Inge van de Weerd, Sjaak Brinkkemper, Richard Nieu...
The challenges to requirements from linguistic factors are well-known. This work concerns an approach to communicating requirements with greater fidelity among stakeholders throug...
Use-cases often capture the expected behaviors of a system and its components. During requirements analysis, it is important to understand and model the relationship among differe...
A technique is presented for obtaining a specification from a requirement through a series of incremental steps. The starting point is a Problem Frame description involving a requ...
This paper describes an experience in requirements engineering for an open source E-Learning tool selection. The process meets the challenges of software selection such as the int...
Terminological interference occurs in requirements engineering when stakeholders vary in the concepts they use to understand a problem domain, and the terms they use to describe t...