Requirements engineering: social and technical issues
Requirements engineering: social and technical issues
Creating products customers demand
Communications of the ACM
The capability maturity model: guidelines for improving the software process
The capability maturity model: guidelines for improving the software process
A systematic survey of CMM experience and results
Proceedings of the 18th international conference on Software engineering
Software improvements in an international company
ICSE '93 Proceedings of the 15th international conference on Software Engineering
Mastering the requirements process
Mastering the requirements process
Requirements engineering: a roadmap
Proceedings of the Conference on The Future of Software Engineering
Software developer perceptions about software project failure: a case study
Journal of Systems and Software - Special issue on software engineering education and training for the next millennium
Validating the ISO/IEC 15504 Measure of Software Requirements Analysis Process Capability
IEEE Transactions on Software Engineering
Requirements Engineering: A Good Practice Guide
Requirements Engineering: A Good Practice Guide
Experiences in the Application of Software Process Improvement in SMES
Software Quality Control
Software Process Improvement at Hughes Aircraft
IEEE Software
Introducing Measurable Quality Requirements: A Case Study
RE '99 Proceedings of the 4th IEEE International Symposium on Requirements Engineering
Introducing Requirements Engineering: How to Make a Cultural Change Happen in Practice
RE '02 Proceedings of the 10th Anniversary IEEE Joint International Conference on Requirements Engineering
Successful Process Implementation
IEEE Software
Requirements Engineering and Downstream Software Development: Findings from a Case Study
Empirical Software Engineering
RE '05 Proceedings of the 13th IEEE International Conference on Requirements Engineering
Research Directions in Requirements Engineering
FOSE '07 2007 Future of Software Engineering
Architecting-problems rooted in requirements
Information and Software Technology
Software architecting without requirements knowledge and experience: What are the repercussions?
Journal of Systems and Software
Modelling Web-Based Systems Requirements Using WRM
WISE '08 Proceedings of the 2008 international workshops on Web Information Systems Engineering
Advances in Engineering Software
Continuous SCRUM: agile management of SAAS products
Proceedings of the 4th India Software Engineering Conference
Information and Software Technology
Empirical analysis of the impact of requirements engineering on software quality
REFSQ'12 Proceedings of the 18th international conference on Requirements Engineering: foundation for software quality
Proceedings of the 17th International Conference on Evaluation and Assessment in Software Engineering
Transforming and tracing reused requirements models to home automation models
Information and Software Technology
Requirements traceability across organizational boundaries: a survey and taxonomy
REFSQ'13 Proceedings of the 19th international conference on Requirements Engineering: Foundation for Software Quality
REFSQ'13 Proceedings of the 19th international conference on Requirements Engineering: Foundation for Software Quality
Hi-index | 0.00 |
Requirements engineering is an important component of effective software engineering, yet more research is needed to demonstrate the benefits to development organizations. While the existing literature suggests that effective requirements engineering can lead to improved productivity, quality, and risk management, there is little evidence to support this. We present empirical evidence showing how requirements engineering practice relates to these claims. This evidence was collected over the course of a 30-month case study of a large software development project undergoing requirements process improvement. Our findings add to the scarce evidence on RE payoffs and, more importantly, represent an in-depth explanation of the role of requirements engineering processes in contributing to these benefits. In particular, the results of our case study show that an effective requirements process at the beginning of the project had positive outcomes throughout the project lifecycle, improving the efficacy of other project processes, ultimately leading to improvements in project negotiation, project planning, and managing feature creep, testing, defects, rework, and product quality. Finally, we consider the role collaboration had in producing the effects we observed and the implications of this work to both research and practice.