The requirements elicitation phase is often regarded as the most critical stage of the entire software engineering effort with strong evidence suggesting that increasing the effectiveness of requirements analysts and reducing requirements elicitation errors may be the key to improve project outcomes and deliver high quality software. This paper presents a requirements elicitation approach and a...

Requirements elicitation is widely regarded as the most challenging activity within the scope of requirements engineering. The activity concerns the understanding of problems that a system should address, which later leads to the identification of system requirements. As an abstract process, its effectiveness is greatly influenced by the credibility and suitability of the stakeholders involved....

1. INTRODUCTION Software developers are constantly under pressure to deliver code on time and on budget. As a result, many projects focus on delivering functionalities at the expense of meeting non-functional requirements such as reliability, security, maintainability, portability, accuracy, among others. As software complexity grows and clients demand higher and higher quality software, non-fu...

0950-5849/$ see front matter 2012 Elsevier B.V. A http://dx.doi.org/10.1016/j.infsof.2012.07.011 ⇑ Corresponding author. E-mail addresses: [email protected] (S.T. Ac te.uam.es (J.W. Castro), [email protected] (N. Juristo). Context: To develop usable software we need to understand the users that will interact with the system. Personas is a HCI technique that gathers information about users in...

The guidelines for Requirements Management have been documented many times formally but the actual problems faced by the software industry are quite different. Through research it is found that most of the software projects fail before they are completed or if they do reach completion their quality is not up to the mark. The aim of this Research study is to identify the loopholes in the require...

Requirements changes are sometimes pointed out as being one of the causes for project failure. Our solution to cope with this problem is to plan and manage requirements changes strategically. This paper introduces the PRINCE model that consists of 3+1 types of requirements elicitation processes based on the time of the maturation of the requirements elicitation activity. To explain the model, w...

In this paper, we discuss an approach to system requirements engineering, which is based on using models of the responsibilities assigned to agents in a multi-agency system of systems. The responsibility models serve as a basis for identifying the stakeholders that should be considered in establishing the requirements and provide a basis for a structured approach, described here, for informatio...

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

Goal Oriented Requirements Elicitation Process (GOREP) is used to identify the requirements of software using AND/OR graph. Requirements elicitation plays an important role for the identification of software's functional and non-functional requirements. The objective of this paper is twofold; firstly, we classify different requirements elicitation techniques on the basis of different crite...

The requirements elicitation phase of software development projects is characterised by the intensity and importance of communication activities. Requirements elicitation is a traditional exploratory phase in which context is analysed and an abstraction is performed as a consequence. However, exploratory processes are characterised by a deep interaction with environmental factors. In this paper...