Requirements Management - literature survey preparation

OUTLINE
- Introduction
- Definition and Context
- Why RM is Needed
- RM Methods
- RM Metrics
- Conclusion

REFERENCES
[1] R. H. Thayer and M. Dorfman, Eds., Software Requirements Engineering,
2nd ed. Los Alamitos, CA: IEEE Computer Society Press, 1997.

[2] U. Nikula, “Introducing basic systematic requirements engineering practices in small organizations with an easy to adopt method,” p. 207, 2004.

[3] L. Goldin and A. Finkelstein, “Abstraction-based requirements management,” in Proceedings of the 2006 international workshop on Role of
abstraction in software engineering. New York, NY, USA: Association
for Computing Machinery, 2006, pp. 3–10.

[4] B. Nuseibeh and S. Easterbrook, “Requirements engineering: a roadmap,”
in ICSE ’00: Proceedings of the Conference on The Future of Software
Engineering. New York, NY, USA: ACM, 2000, pp. 35–46.

[5] P. Hantos, “A systems engineering view of requirements management
for software-intensive systems,” in ICSE ’99: Proceedings of the 21st
international conference on Software engineering. New York, NY, USA:
ACM, 1999, pp. 620–621.

[6] M. C. Paulik, B. Cutis, M. B. Chrissis, and C. V. Weber, “Capability
maturity model for software, version 1.1,” 1993.

[7] K. Reed, E. Damiani, G. Gianini, and A. Colombo, “Agile management of
uncertain requirements via generalizations: a case study,” in QUTE-SWAP
’04: Proceedings of the 2004 workshop on Quantitative techniques for
software agile process. New York, NY, USA: ACM, 2004, pp. 40–45.