Abstract
Taken literally, the term “requirements engineering” (RE) is a misnomer. A requirement is something that is wanted; engineering, according to Webster’s, is calculated manipulation. If our wants would arise by calculated manipulation, then something would be wrong. Our wants should not be engineered. What should be engineered, are solutions that meet our wants.
Chapter PDF
Similar content being viewed by others
References
Dewey, J.: How We Think: A Restatement of the Relation of Reflective Thinking to the Educative Process. D.C. Heath and Company (1933)
Gause, D., Weinberg, G.: Exploring Requirements: Quality Before Design. Dorset House Publishing, New York (1989)
Cross, N.: Design cognition: results from protocol and other empirical studies of design activity. In: Eastman, C., McCracken, W., Newstetter, W. (eds.) Design Knowing and Learning: Cognition in Design Education, pp. 79–103. Elsevier, Amsterdam (2001)
Wieringa, R.: Requirements Engineering: Frameworks for Understanding. Wiley, Chichester (1996)
Antón, A., Potts, C.: The use of goals to surface requirements for evolving systems. In: International Conference on Software Engineering (ICSE 1998), pp. 157–166. IEEE Computer Society, Los Alamitos (1998)
Dardenne, A., Lamsweerde, A.v., Fickas, S.: Goal-directed requirements acquisition. Science of Computer Programming 20, 3–50 (1993)
Mylopoulos, J., Chung, L., Yu, E.: From object-oriented to goal-oriented requirements analysis. Communications of the ACM 42, 31–37 (1999)
Yu, E.: An organization modelling framework for information systems requirements engineering. In: Proceedings of the Third Workshop on Information Technologies and Systems, WITS 1993 (1993)
Wieringa, R., Heerkens, H.: Requirements engineering as problem analysis: Methodology and guidelines. Technical report, University of Twente (2003)
Lauesen, S.: Software Requirements: Styles and Techniques. Addison-Wesley, Reading (2002)
Beyer, H., Holtzblatt, K.: Contextual Design: Defining Customer-Centered Systems. Morgan Kaufmann, San Francisco (1998)
Bondarouk, T., Sikkel, N.: Implementation of collaborative technologies as a learning process. In: Cano, J. (ed.) Critical Reflections on Information Systems–A Systemic Approach, pp. 227–245. Idea Group Publishing, USA (2003)
IEEE: IEEE Guide to Software Requirements Specifications. In: Software Engineering Standards. IEEE Computer Science Press (1993), IEEE Std 830-1993
Davis, A.M.: Software Requirements: Objects, Functions, States. Prentice-Hall, Englewood Cliffs (1993)
Robertson, S., Robertson, J.: Mastering the Requirements Process. Addison-Wesley, Reading (1999)
Wieringa, R.: A survey of structured and object-oriented software specification methods and techniques. ACM Computing Surveys 30, 459–527 (1998)
Wieringa, R.: Design Methods for Reactive Systems: Yourdon, Statemate and the UML. Morgan Kaufmann, San Francisco (2003)
Author information
Authors and Affiliations
Editor information
Editors and Affiliations
Rights and permissions
Copyright information
© 2004 Springer-Verlag Berlin Heidelberg
About this paper
Cite this paper
Wieringa, R.J. (2004). Requirements Engineering: Problem Analysis and Solution Specification (Extended Abstract). In: Koch, N., Fraternali, P., Wirsing, M. (eds) Web Engineering. ICWE 2004. Lecture Notes in Computer Science, vol 3140. Springer, Berlin, Heidelberg. https://doi.org/10.1007/978-3-540-27834-4_3
Download citation
DOI: https://doi.org/10.1007/978-3-540-27834-4_3
Publisher Name: Springer, Berlin, Heidelberg
Print ISBN: 978-3-540-22511-9
Online ISBN: 978-3-540-27834-4
eBook Packages: Springer Book Archive