Interviews with IS developers suggest that requirements analysis is rarely perceived as a cooperative activity. Instead it is often seen as a process of extracting requirements from passive clients (as terms such as “requirements capture” and “requirements engineering” imply). A more cooperative approach which recognises requirements analysis as a negotiative process between analyst(s) and clie...

Data warehouse is a subject-oriented, integrated, time-variant, and nonvolatile collection of data to provide the strategic information to the decision makers. Most of the data ware house project fails to meet the business requirements and business goals because of the improper requirement engineering phase. Building a data warehouse is a very challenging task. Data warehouse development can us...

[Context and motivation] During requirements engineering the stakeholder view is typically captured by scenarioand goal models focusing on tasks and goals to be achieved with the software. We believe that it is worthwhile to study more general personal values and attitudes of stakeholders and to relate them to software requirements. [Question/problem] The main questions of such an approach are:...

Requirements engineering is concerned with the identification of the goals to be achieved by the envisioned IS/IT system. The processes involved include three interrelated functions: requirements elicitation, specification and validation. This study represents an exposition of requirements elicitation/specification concepts and challenges targeting the Government Sector. Groups of Project Manag...

In recent years the usage of information systems has changed dramatically. Today many information systems are developed for non-organizational users. These wide-area end-users are often socially, as well as geographically very widely dispersed, which makes it for organizations that develop information systems extremely difficult to know who their users are, or what they expect. Previous researc...

Requirements engineering research has for long recognized the leading role of goals as requirement artifacts during the requirements engineering specification processes. Given the large number of artifacts created during the requirements specification and the continuous evolution of these artifacts, reasoning about them remains a challenging task. Moreover, the rising complexity of the target d...

Various security requirements sources need to be incorporated when developing security requirements. A challenge for teams developing security requirements is to identify and structure relevant sources, to satisfy compliancerelated obligations, and to identify and properly address relevant threats, weaknesses and vulnerabilities. In this paper, we present a generic model which can be used for s...

Editor’s Note: The following article is reprinted from the book Software Requirements Engineering, Second Edition, and is provided for readers who want to read a brief tutorial on requirements engineering. The views expressed in this article are the author’s only and do not represent directly or imply any official position or view of the Software Engineering Institute or Carnegie Mellon Univers...