Results 221 to 230 of about 9,893 (264)
Some of the next articles are maybe not open access.

Situation-Oriented Requirements Elicitation

2016 IEEE 40th Annual Computer Software and Applications Conference (COMPSAC), 2016
In this paper we present a new human-centered requirements elicitation methodology that effectively considers end-user's desire, behavioral and environmental contexts. We follow a methodology that uses a computationally rich definition of situation as a 3-tuple where d denotes human desire, A denotes the action vector, and E denotes the environment ...
Nimanthi L. Atukorala   +2 more
openaire   +1 more source

A Unified Model of Requirements Elicitation

Journal of Management Information Systems, 2004
Effective requirements elicitation is essential to the success of software development projects. Many papers have been written that promulgate specific elicitation methods. A few model elicitation in general. However, none have yet modeled elicitation in a way that makes clear the critical role played by situational knowledge.
Ann M. Hickey, Alan M. Davis
openaire   +1 more source

Supporting Requirements Elicitation Practices

2013
In this paper, we examine the practices in requirements elicitation activities from the perspective of a developer of software projects. By doing so, we want to contribute to a better understanding of how the main activities between stakeholders can be supported by IT, particularly social software.
Mohd Ilias M. Shuhud   +2 more
openaire   +1 more source

Elicitation and Specification of Safety Requirements

Third International Conference on Systems (icons 2008), 2008
In this paper we demonstrate how to derive software requirements from system safety analysis in such a way that they could be easily captured in a software specification. We propose an integral approach for incorporating results of fault tree analysis (FTA) and failure mode and effect analysis (FMEA) into the requirements specification. In our approach
openaire   +1 more source

Anticipating Requirements Changes-Using Futurology in Requirements Elicitation

International Journal of Information System Modeling and Design, 2012
It is well known that requirements changes in a later phase of software developments is a major source of software defects and costs. Thus, the need of techniques to control or reduce the amount of changes during software development projects. The authors advocate the use of foresight methods as a valuable input to requirements elicitation, with the ...
Pimentel, João Henrique   +3 more
openaire   +3 more sources

Eliciting coordination policies from requirements

Proceedings of the 2003 ACM symposium on Applied computing - SAC '03, 2003
Software coordination models and languages describe how agents, resources and processes work together to implement a software system. One of their limitations is that they are used late in the software development and they are not integrated in a typical software development process.What we claim, with our research, is that if coordination becomes ...
MUCCINI, HENRY, F. MANCINELLI
openaire   +2 more sources

Ambiguity Cues in Requirements Elicitation Interviews

2016 IEEE 24th International Requirements Engineering Conference (RE), 2016
Customer-analyst interviews are considered among the most effective means to perform requirements elicitation. However, during these interviews, ambiguity can hamper commu- nication between customer and requirements analyst. Ambiguity is particularly dangerous in those cases in which the analyst misunderstands some linguistic expression of the customer,
Ferrari A, Spoletini P, Gnesi S
openaire   +2 more sources

Usability requirements elicitation

Proceedings of the 13th International Conference on Interacción Persona-Ordenador - INTERACCION '12, 2012
Usability is a key factor to create a quality product. However, there are few proposals to deal with usability requirements from the early steps of the software development process. This paper presents a mapping study to compare existing usability requirement methods and to identify strong points for each one.
Yeshica Isela Ormeño   +2 more
openaire   +1 more source

e-Government Requirement Elicitation

2003
The quality and productivity of e-Government is measured by its successful usage for country development. The e-Government requirement is one of the most important features, which must be elicited from related stakeholders. The e-Government crisis normally comes from the shortage or unqualified IT Man, Machine, Money, Methodology, and Management (5M ...
openaire   +1 more source

Requirements Elicitation with Use Cases

2003
Nowadays, the complexity of the software systems that needs to be produced is staggering. Developing such systems requires that the development team first understands the problem, i.e., they have a global picture of what is required to be built, before they can make a sensible judgment on an architecture for the solution.
openaire   +1 more source

Home - About - Disclaimer - Privacy