Results 301 to 310 of about 89,500 (322)
Some of the next articles are maybe not open access.

Eliciting gaps in requirements change

Requirements Engineering, 2004
We consider requirements change due to system evolution which results from contextual forces such as the decision to standardise practices across subsidiaries of a company. Our experience with the financial branch of the French Renault group is that eliciting change requirements poses its own specific problems.
Rolland, Colette   +2 more
openaire   +2 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

User Requirements Elicitation

2019
This chapter identifies why the collection of end user requirements is such a defining and important stage of any serious game development project. It outlines requirements elicitation techniques and discusses their strengths, weaknesses and where they are useful. It will then discuss how to analyse the data that has been obtained.
Steffi Davey, Jonathan Saunders
openaire   +1 more source

Security Requirements Elicitation

2011
Information security is becoming increasingly important and more complex as organizations are increasingly adopting electronic channels for managing and conducting business. However, state-of-the-art systems design methods have ignored several aspects of security that arise from human involvement or due to human factors.
openaire   +1 more source

Requirement engineering elicitation methods

Information Management & Computer Security, 2009
PurposeThe purpose of this paper is to investigate the perceptions of 19 requirement engineering (RE) techniques in Kuwait in term of three criteria “awareness,” “use,” and “perceived value generated over past system development projects.” Also, this paper aims to examine possible relationships between these RE techniques and two information system ...
Kamel Rouibah, Sulaiman Al‐Rafee
openaire   +1 more source

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

Requirements Elicitation Technique Selection

2009
Requirements elicitation has been recognized as a critical stage in system development projects, yet current models prescribing particular elicitation techniques are still limited in their development and application. This research reviews efforts aimed at addressing this issue, and synthesizes a common structure consisting of project contingencies ...
Miguel I. Aguiree-Urreta   +1 more
openaire   +1 more source

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

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

Non-Functional Requirements Elicitation

2004
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.
Luiz Marcio Cysneiros, Eric Yu
openaire   +1 more source

Home - About - Disclaimer - Privacy