• DocumentCode
    1199185
  • Title

    Point/Counterpoint

  • Author

    Alexander, Lerer ; Beck, Kent

  • Author_Institution
    Three Rivers Institute, OR
  • Volume
    24
  • Issue
    2
  • fYear
    2007
  • Firstpage
    62
  • Lastpage
    65
  • Abstract
    The key to successful systems is building what the stakeholders desire. In a way, this point can hardly be gain.said: nobody wants to build what the stakeholders don´t desire. But as usual, the devil is in the details. this paper contrasts two examples to illustrate what it can mean to build what stakeholders desire. There´s an old saying in software development that the users don´t know what they want until you give them what they asked for. Experienced developers often smile ruefully when they hear this, having been told at least once in their careers that a system they had delivered was totally unacceptable when it was exactly (as far as they could tell) what was requested. There´s more to delivering good software than following orders. The paper describes what positive role developers can play in discovering and exploring requirements
  • Keywords
    formal specification; software development management; systems analysis; DWTTY; requirements engineering; software development; stakeholders requirements; Costs; Discrete wavelet transforms; Engineering profession; Eyes; Lead; Programming; agile methods; requirements engineering; software development;
  • fLanguage
    English
  • Journal_Title
    Software, IEEE
  • Publisher
    ieee
  • ISSN
    0740-7459
  • Type

    jour

  • DOI
    10.1109/MS.2007.50
  • Filename
    4118652