You are here:
(27 Nov 2007,
Requirements engineering is the interface between customers and developers on a software project. Requirements should make explicit the ideas of the customer about the prospective system.
A. van Lamsweerde,
"Goal-Oriented Requirements Engineering: A Guided Tour"
. Invited minitutorial, Proc. RE'01 - International Joint Conference on Requirements Engineering, Toronto, IEEE, August 2001, pp.249-263.
Lemai Nguyen Jocelyn Armarego Paul Swatman.
Understanding Requirements Engineering: a Challenge for Practice and Education
. Deakin University, School of Management Information Systems, Working Paper 2002/10
B. Regnell, K. Kimbler, and A. Wesslen,
"Improving the Use Case Driven Approach to Requirements Engineering"
, Proc. RE'95 - 2nd Int. Symp. on Requirements Engineering, York, IEEE, 1995, 40-47.
B. Regnell and A. Davidsson.
"From Requirements to Design with Use Cases -- Experiences from Industrial Pilot Projects"
, Proceedings of the Third International Workshop on Requirements Engineering: Foundations of Software Quality (REFSQ'97), pp. 205--222, Editors: Dubois, Opdahl, and Pohl, Presses Universitaires de Namur, 1997.
iew wiki text
ore topic actions
Topic revision: r3 - 27 Nov 2007,
Copyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding UUCS?