Often during the requirements engineering (RE) process, the value of a requirement is assessed, e.g., in requirement prioritisation, release planning, and trade-off analysis. In order to support these activities, this research evaluates Goal Oriented Requirements Engineering (GORE) methods for the description of a requirement’s value. Specifically, we investigate the goal-to-goal contribution r...

This paper is concerned with software requirements evolution in industrial settings. The discussion provides new insights in requirements engineering. This paper highlights the problem of empirically understanding and modelling requirements evolution.

Many applications that are developed do not completely fulfil the requirements of their stakeholders. This can be a result of inadequate requirements elicitation and poorly defined requirements. Many solutions, including model-driven inspired ones, have been proposed to improve the elicitation of the requirements, though many of them are not yet widely used in practice as they require training ...

[Context and Motivation] The word “creativity” is used widely in business and academia, but its meaning may differ greatly depending on context. This may cause confusion in the minds of requirements engineers who have to determine which kinds of creativity are relevant to their project and which creativity tools to use. [Question/Problem] The main goal of this work is to understand why and how ...

e-Health is a rising research area in the intersection of public health and business sectors which refers to health and information services that are delivered or improved by using the Internet and other related information and communication technologies. Various aspects of e-Health are discussed in the literature; however, there is a research gap in the areas of system requirements engineering...

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...