Skip to main content

Advertisement

Log in

Requirements Management: A Cinderella Story

  • Viewpoints
  • Published:
Requirements Engineering Aims and scope Submit manuscript

Why do the business requirements and the final software product often have little in common? Why are stakeholders, developers and managers reluctant to embrace a full requirements process? Why does everybody say, ‘We don’t have time for requirements’? Why is the potentially most beneficial part of the development process ignored or short-changed?

 Following are some observations about why the real requirements for the product often go undiscovered. We will address this by focusing on the different concerns of the people involved in requirements.

This is a preview of subscription content, log in via an institution to check access.

Access this article

Subscribe and save

Springer+ Basic
$34.99 /Month
  • Get 10 units per month
  • Download Article/Chapter or eBook
  • 1 Unit = 1 Article or 1 Chapter
  • Cancel anytime
Subscribe now

Buy Now

Price excludes VAT (USA)
Tax calculation will be finalised during checkout.

Instant access to the full article PDF.

Similar content being viewed by others

Author information

Authors and Affiliations

Authors

Rights and permissions

Reprints and permissions

About this article

Cite this article

Robertson, J., Robertson, S. Requirements Management: A Cinderella Story. Requirements Eng 5, 134–136 (2000). https://doi.org/10.1007/PL00010346

Download citation

  • Issue Date:

  • DOI: https://doi.org/10.1007/PL00010346