Software requirements negotiation: some lessons learned
Proceedings of the 20th international conference on Software engineering
Software Process Improvement Problems in Twelve Software Companies: An Empirical Analysis
Empirical Software Engineering
An empirical study of industrial requirements engineering process assessment and improvement
ACM Transactions on Software Engineering and Methodology (TOSEM)
A view of 20th and 21st century software engineering
Proceedings of the 28th international conference on Software engineering
Guidelines for conducting and reporting case study research in software engineering
Empirical Software Engineering
Software & Systems Requirements Engineering: In Practice
Software & Systems Requirements Engineering: In Practice
Requirements engineering as a key to holistic software quality
ISCIS'06 Proceedings of the 21st international conference on Computer and Information Sciences
A meta model for artefact-orientation: fundamentals and lessons learned in requirements engineering
MODELS'10 Proceedings of the 13th international conference on Model driven engineering languages and systems: Part II
Information and Software Technology
| Hi-index | 0.00 |
Requirements Engineering (RE) constitutes a critical discipline within Software Engineering. The quality of requirements is the backbone of project execution since the following phases strongly rely on it. Nowadays, industries are more then ever facing the problem that the RE process is highly volatile because it depends on the customer's capabilities, on the used process models, and on the type of specifications developed. This paper describes a study on the RE process in a specific company in the application domain of business information systems. While existing surveys often analyse the general impact of RE processes on project success, we investigate and discuss different influences that arose in 12 real-life projects and the effects of these influences onto produced RE artefacts. We infer different artefact patterns and probable project execution strategies that cause these patterns. The strategies are performed in order to tackle the different project influences. The identification enables us to get a more detailed understanding of RE in practice for the future elaboration of tailoring approaches that customise RE efforts to volatile project environments.