Automated support for the requirements engineering (RE) process is a recognized research area. However the mainstream practice still relies on word processors and drawing tools rather than the requirements engineering tools (RETs). The aim of this paper is to validate an evaluation framework for RETs. The validation process concerns a RET acquisition process for concrete organizational needs. A...

Requirements determine how an Information System should operate. Requirements Engineering errors become failure reasons of the Information System. In this paper we propose a Web-based focus group method to overcome many problems of the requirements elicitation activity. Collaboration is promoted in discussions involving all stakeholders to achieve consensual decisions. The proposal was evaluate...

Requirements engineering is a key discipline in analysis and design of business software. There are commonly accepted processes available for requirements engineering, but many organizations struggle to implement and follow these processes. A number of methods have therefore been developed to help assess and improve requirements practices. This exploratory study reports from a project at TelSof...

Requirements elicitation consists in collecting information about the requirements and the environment of a systemto-be. It usually involves business analysts who are eliciting information, and stakeholders who are providing information. This paper investigates how the commitment of stakeholders to a RE project influences the results of elicitation. We suggest a way to measure the commitment of...

Increasingly, information systems development occurs in the context of existing systems and established organizational processes. Viewing organizational and system components as cooperating agents offers a way of understanding their inter-relationships and how these relationships would or should be altered as new systems are introduced. In this paper, we show how two agent-oriented frameworks c...

Defining what stakeholders really ask for, which is called a scenario acquisition in this paper, is a very important activity for concept making of a new product and system requirements analysis. We will use the term “stakeholders” to refer to all the people concerned with a product and a system, such as end users, suppliers, and manufacturers of the system. The term “scenario” is defined as a ...

Requirements elicitation is the first of the four steps in software requirements engineering (the others being analysis, specification, and validation). Software engineers use several elicitation techniques. To facilitate teaching these techniques, materials are provided to support an introductory lecture and four lectures on specific techniques: joint application design, brainstorming, intervi...

The approaches for extraction and representation of knowledge from textual user requirements could be summarized in two groups: i) when we have in mind an end model and seek, mine and represent knowledge for it. In short, this approach can be defined as “knowledge driven from a target model”; ii) when we have in mind knowledge in a text, and seek an appropriate model to represent it. The interm...

Negotiation is one promising effort during requirements elicitation process to improve the quality of software requirements. When negotiation is claimed beneficial theoretically, it is important that the deployment of negotiation is examined and the effectiveness of negotiation is evaluated through empirical study. This paper aims at providing an empirical framework design to examine the improv...

Due to the specific challenges that ICT4D projects present, conventional requirements elicitation techniques are often inapplicable or insufficient. We address this shortcoming by introducing structured digital storytelling (SDS) as an alternative elicitation technique especially suited for the ICD4D domain. SDS is supported by our mobile elicitation tool designed around the needs and capabilit...