Requirements BEFORE the Requirements: Understanding the Upstream Impact

Authors:
Christof Ebert
Affiliations:
Alcatel
Venue:
RE '05 Proceedings of the 13th IEEE International Conference on Requirements Engineering
Year:
2005

Citing 0
Cited 4

Understanding the Product Life Cycle: Four Key Requirements Engineering Techniques

IEEE Software
The impact of agile principles on market-driven software product development

Journal of Software Maintenance and Evolution: Research and Practice
A quality performance model for cost-benefit analysis of non-functional requirements applied to the mobile handset domain

REFSQ'07 Proceedings of the 13th international working conference on Requirements engineering: foundation for software quality
Assessing requirements compliance scenarios in system platform subcontracting

PROFES'06 Proceedings of the 7th international conference on Product-Focused Software Process Improvement

Quantified Score

Hi-index	0.00

Visualization

Abstract

Being succesful in product development means to deliver the right products or solutions at the right time for the right markets. While requirements engineering (RE) plays a key role in selecting and managing requirements for a given project, the "up stream" before the project start often remains vague. Typically this upstream process is decoupled from the project-related RE proccesses, which creates lots ofproject deficiencies, such as changes in requirements and ultimately delayed release. We take the position that only by integrating upstream (e.g., roadmap) and downstream (i.e., project) proccesses, projectswill be successful. This field study is supported by data from 246 industry projects over a period of two years. We found that four described the techniques must be used simultaneously in order to see tabgible performance improvement. Each technique is explained by concrete and practical experiences.