• DocumentCode
    1549895
  • Title

    The top risk of requirements engineering

  • Author

    Lawrence, Brian ; Wiegers, Karl ; Ebert, Christof

  • Author_Institution
    Coyote Valley Software, Silicon Valley, CA, USA
  • Volume
    18
  • Issue
    6
  • fYear
    2001
  • Firstpage
    62
  • Lastpage
    63
  • Abstract
    The worst thing that can happen in requirements engineering is that your set of requirements, however expressed, doesn´t accurately represent your users´ needs and consequently leads your team down the wrong development path. The whole point of requirements engineering is to steer your development toward producing the right software. If you don´t get the requirements right, how well you execute the rest of the project doesn´t matter because it will fail. The article looks at how we can be led astray
  • Keywords
    systems analysis; customer representation; functional requirements; requirements engineering; Computer crashes; Costs; Heart; Inspection; Reliability engineering; Robustness; Scalability; Security; Software quality; Technological innovation;
  • fLanguage
    English
  • Journal_Title
    Software, IEEE
  • Publisher
    ieee
  • ISSN
    0740-7459
  • Type

    jour

  • DOI
    10.1109/52.965804
  • Filename
    965804