Current and Future Research Directions in Requirements Engineering

Cheng, Betty H. C.; Atlee, Joanne M.

doi:10.1007/978-3-540-92966-6_2

Cited by 40 publications

(18 citation statements)

References 131 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…The objective of the requirements elicitation technique is to determine what problem needs to be solved, therefore, the elicitation techniques focuses the requirements engineer on the problem domain, rather than on possible solution of those problems. Based on the literature survey [1,2,4,5,6,7,8,9,13,14 ], we divide the requirements elicitation techniques into 4 types: (i) traditional techniques i.e., based on data gathering, (ii) group elicitation techniques i.e., based on groups or workshop, (iii) cognitive techniques i.e., related to the mental process, and (iv) contextual techniques i.e., based on observation of workplace of the customer. Hickey and Davis [7] suggests that models and ethnography techniques are the recommended techniques used by most of the analyst during requirements elicitation.…”

Section: Requirements Elicitationmentioning

confidence: 99%

An Insight into Requirements Engineering Processes

Sadiq

Jain

2012

Lecture Notes of the Institute for Computer Sciences, Social Informatics and Telecommunications Engineering

View full text Add to dashboard Cite

Abstract. Requirements Engineering (RE) determines the requirements of software according to the needs of customers. Requirements engineering process includes requirements elicitation, requirements modeling, requirements analysis, requirements verification & validation, and requirements management. Among these sub-processes, requirements elicitation plays an important role in extracting the needs of stakeholders, since it is the first requirements engineering sub-process and has cascading effect. It means errors occurring during requirements elicitation will affect the remaining RE processes. Improper understanding of requirements engineering processes may lead to failure of software projects. This article presents an insight into requirements engineering processes.

show abstract

Section: Requirements Elicitationmentioning

confidence: 99%

An Insight into Requirements Engineering Processes

Sadiq

Jain

2012

Lecture Notes of the Institute for Computer Sciences, Social Informatics and Telecommunications Engineering

View full text Add to dashboard Cite

show abstract

“…Much of RE research has focused on developing notations, techniques, and evaluation methodologies for requirements elicitation, modeling, analysis, validation, verification, and management [39]. Requirements identification, one of the major objectives of the RE process, involves determining the organizational or customer needs that must be addressed by the delivered artifact [72,114,175].…”

Section: Requirements Identification In Rementioning

confidence: 99%

Stakeholders' social interaction in requirements engineering of open source software

Bhowmik

2014

2014 IEEE 22nd International Requirements Engineering Conference (RE)

View full text Add to dashboard Cite

In this work, we use the phrase "stakeholders' social interaction" to indicate interaction among stakeholders regarding the software system that takes place through some communication means, such as posting comments and artifacts over the issue tracking system.We investigate the influence of stakeholders' social interaction in different RE activities, in particular, requirements identification, creativity in RE, and requirements implementation of OSS systems. This research enables us to gain valuable insights to generate guidelines for enhancing software engineering practice in relevant areas.

show abstract

“…In particular, the success of a software system depends on how well it fits the needs of its users and its environment. Therefore, software requirements comprise these needs, and Requirements Engineering (RE) is the process by which the requirements are determined [1]. If the requirements are not right, the execution of the entire project during development will be faulty.…”

Section: Introductionmentioning

confidence: 99%

“…This initiates a process that needs to be followed in order to ensure quality improvement. The authors in [1] observed that RE is about defining precisely the problem that the software is to solve (i.e., defining what the software is to do). In reality, [12] observed that budget and schedule constraints limit the number of requirements that can be worked on for a software system and is thus necessary to select the most valuable requirements for implementation.…”

Section: Introductionmentioning

confidence: 99%

A Proposed Process Model for Requirements Engineering using Delphi Techniques for Prioritisation

Gambo¹,

Soriyan²,

Ikono³

2014

IJITCS

View full text Add to dashboard Cite

Abstract-Requirements engineering (RE) addresses the first software development step and lays the foundation for a successful system. Consequently, ability to identify problems and suggestions for improvements in the RE process opens up significant potential for increasing the success of software projects. Since RE process is naturally collaborative in nature, the intensiveness from both knowledge and human perspectives opens up the problem of decision making on requirements that can be facilitated by requirements prioritisation. In this regard, the paper opined the need for requirements prioritization techniques that will help the developers to obtain consensus among stakeholders using a suitable technique. In particular, the paper proposed a RE process model using Delphi technique. The Delphi technique was suggested in this paper to facilitate and enhance the process of requirements prioritisation in a multilevel prioritisation dimension. Therefore, the proposed model on implementation will contribute to the formulation of an interactive framework for requirements prioritisation to produce a requirement ordering which complies with the existing priorities.

show abstract

Current and Future Research Directions in Requirements Engineering

Cited by 40 publications

References 131 publications

An Insight into Requirements Engineering Processes

An Insight into Requirements Engineering Processes

Stakeholders' social interaction in requirements engineering of open source software

A Proposed Process Model for Requirements Engineering using Delphi Techniques for Prioritisation

Contact Info

Product

Resources

About