• DocumentCode
    3619995
  • Title

    Requirements before the requirements: understanding the upstream impacts

  • Author

    Christof Ebert

  • Author_Institution
    Alcatel, Paris, France
  • fYear
    2005
  • fDate
    6/27/1905 12:00:00 AM
  • Firstpage
    117
  • Lastpage
    124
  • Abstract
    Being successful 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 "upstream process" before the project start often remains vague. Typically this upstream process is decoupled from the project related RE processes, which creates lots of project 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) processes, projects are successful. This field study is supported by data from 246 industry projects over a period of two years. We found that four described techniques must be used simultaneously in order to see tangible performance improvement. Each technique is explained by concrete and practical experiences.
  • Keywords
    "Product development","Project management","Engineering management","Delay","Concrete"
  • Publisher
    ieee
  • Conference_Titel
    Requirements Engineering, 2005. Proceedings. 13th IEEE International Conference on
  • Print_ISBN
    0-7695-2425-7
  • Type

    conf

  • DOI
    10.1109/RE.2005.57
  • Filename
    1531033