Distances between requirements engineering and later software development activities: a systematic map

Authors:
Elizabeth Bjarnason
Affiliations:
Department of Computer Science, Lund University, Lund, Sweden
Venue:
REFSQ'13 Proceedings of the 19th international conference on Requirements Engineering: Foundation for Software Quality
Year:
2013

Citing 29
Cited 0

A field study of the software design process for large systems

Communications of the ACM
Estimating Software Project Effort Using Analogies

IEEE Transactions on Software Engineering
Robust estimations of fault content with capture-recapture and detection profile estimators

Journal of Systems and Software - Special issue on Evaluation and assessment in software engineering
On the inevitable intertwining of specification and implementation

Communications of the ACM
Defining and Applying Measures of Distance Between Specifications

IEEE Transactions on Software Engineering
Weaving Together Requirements and Architectures

Computer
Using a Groupware Space for Distributed Requirements Engineering

WETICE '98 Proceedings of the 7th Workshop on Enabling Technologies: Infrastructure for Collaborative Enterprises
An Empirical Study of Requirements Engineering in Distributed Software Projects: Is Distance Negotiation More Effective?

APSEC '01 Proceedings of the Eighth Asia-Pacific on Software Engineering Conference
Requirements engineering paper classification and evaluation criteria: a proposal and a discussion

Requirements Engineering
Understanding the Product Life Cycle: Four Key Requirements Engineering Techniques

IEEE Software
Automated impact analysis of UML models

Journal of Systems and Software
The adjusted analogy-based software effort estimation based on similarity distances

Journal of Systems and Software
Lessons from applying the systematic literature review process within the software engineering domain

Journal of Systems and Software
A fuzzy clustering methodology for linguistic opinions in group decision making

Applied Soft Computing
An Empirical Study of the Complex Relationships between Requirements Engineering Processes and Other Processes that Lead to Payoffs in Productivity, Quality, and Risk Management

IEEE Transactions on Software Engineering
An Empirical Investigation on Text-Based Communication in Distributed Requirements Workshops

ICGSE '07 Proceedings of the International Conference on Global Software Engineering
The impact of cultural differences in offshore outsourcing--Case study results from German---Indian application development projects

Information Systems Frontiers
Does distance still matter?

Software Process: Improvement and Practice - Global Software Development: Where Are We Headed?
Linking Requirements and Testing in Practice

RE '08 Proceedings of the 2008 16th IEEE International Requirements Engineering Conference
Software project similarity measurement based on fuzzy C-means

ICSP'08 Proceedings of the Software process, 2008 international conference on Making globally distributed software development a success story
Detection of consistent patterns from process enactment data

ICSP'08 Proceedings of the Software process, 2008 international conference on Making globally distributed software development a success story
Comparison of Requirements Hand-off, Analysis, and Negotiation: Case Study

RE '10 Proceedings of the 2010 18th IEEE International Requirements Engineering Conference
Instant Messenger in Offshore Outsourced Software Development Projects: Experiences from a Case Study

HICSS '11 Proceedings of the 2011 44th Hawaii International Conference on System Sciences
Explaining variations in client extra costs between software projects offshored to india

MIS Quarterly
Analysing requirements in a case study of pairing

Proceedings of the 1st Workshop on Agile Requirements Engineering
Requirements are slipping through the gaps -- A case study on causes & effects of communication gaps in large-scale software development

RE '11 Proceedings of the 2011 IEEE 19th International Requirements Engineering Conference
How interaction between roles shapes the communication structure in requirements-driven collaboration

RE '11 Proceedings of the 2011 IEEE 19th International Requirements Engineering Conference
Systematic mapping studies in software engineering

EASE'08 Proceedings of the 12th international conference on Evaluation and Assessment in Software Engineering
Multiple stages grey target decision making method with incomplete weight based on multi-granularity linguistic label

Information Sciences: an International Journal

Quantified Score

Hi-index	0.00

Visualization

Abstract

[Context and Motivation] The main role of requirements engineering (RE) is to guide development projects towards implementing products that will appeal to customers. To effectively achieve this RE needs to be coordinated with and clearly communicated to the later software development activities. [Question/Problem] Communication gaps between RE and other development activities reduce coordination and alignment, and can lead to project delays and failure to meet customer needs. [Principle ideas/results] The main hypothesis is that coordination is enhanced by proximity to RE roles and artefacts, and that distances to later activities increase the effort needed to align requirements with other development work. Thirteen RE-related distances have been identified through a systematic map of existing research. [Contribution] Reported distances are mapped according to research type, RE activity and later software development activities. The results provide an overview of RE distances and can be used a basis for defining a theoretical framework.