What is important when deciding to include a software requirement in a project or release?

@article{Wohlin2005WhatII,
  title={What is important when deciding to include a software requirement in a project or release?},
  author={Claes Wohlin and Ayb{\"u}ke Aurum},
  journal={2005 International Symposium on Empirical Software Engineering, 2005.},
  year={2005},
  pages={10 pp.-}
}
The requirements on software systems are so many that not all requirements may be included in the next development project or the next release. This means that it is necessary to select a set of requirements to implement in the forthcoming project, and hence to postpone the implementation of other requirements to a later point in time. In this selection process different criteria are used. In many cases, the criteria are not officially stated, but rather implicitly used by the decision-makers… CONTINUE READING
Highly Cited
This paper has 57 citations. REVIEW CITATIONS

From This Paper

Figures, tables, and topics from this paper.
33 Citations
18 References
Similar Papers

Citations

Publications citing this paper.
Showing 1-10 of 33 extracted citations

58 Citations

051015'08'11'14'17
Citations per Year
Semantic Scholar estimates that this publication has 58 citations based on the available data.

See our FAQ for additional information.

References

Publications referenced by this paper.
Showing 1-10 of 18 references

Valuebased software engineering: A case study

  • Boehm, Huang, B. W. 2003 Boehm, Huang L.G
  • IEEE Computer Society,
  • 2003

Applying decision-making models in requirements engineering

  • Aurum, Wohlin, A. 2002 Aurum, C. Wohlin
  • Proceedings of Requirements Engineering for…
  • 2002

Similar Papers

Loading similar papers…