[39] Jackson, M. (1995). Software Requirements and Specifications: A
Lexicon of Practice, Principles and Prejudices. Addison Wesley.
[40] Jackson, M. & Zave, P. (1993). Domain Descriptions. 1st
International Symposium on Requirements Engineering (RE'93), San
Diego, USA, 4-6 January 1993, pp. 56-64.
[41] Jarke, M. & Kurki-Suonio, R. (1998). Guest Editorial - Special issue
on Scenario Management. IEEE Transactions on Software
Engineering, 24(12).
[42] Johnson, P. (1992). Human-Computer Interaction: psychology, task
analysis and software engineering. McGraw-Hill.
[43] Karlsson, J. & Ryan, K. (1997). Prioritizing Requirements Using a
Cost-Value Approach. IEEE Software: 67-74.
[44] Kovitz, B. L. (1999). Practical Software Requirements: A Manual of
Contents & Style. Manning.
[45] Kuhn, T. S. (1962). The Structure of Scientific Revolutions. Urbana:
University of Chicago Press.
[46] Lehman, M. M. (1980). Programs, Life Cycles, and Laws of
Software Evolution. Proceedings of the IEEE, 68(9): 1060-1076.
[47] Loucopoulos, P. & Kavakli, E. (1995). Enterprise Modelling and the
Teleological Approach to Requirements Engineering. International
Journal of Intelligent and Cooperative Information Systems, 4(1):
45-79.
[48] Loucopoulos, P. & Potts, C. (Ed.). (1996). Requirements Engineering
Journal. Springer Verlag.
[49] Lutz, R., Helmer, G., Moseman, M., Statezni, D. & Tockey, S.
(1998). Safety Analysis of Requirements for a Product Family. 3rd
IEEE International Conference on Requirements Engineering (ICRE
'98), Colorado Springs, USA, 6-10 April 1998, pp. 24-31.
[50] Maibaum, T. S. E. (2000). Mathematical Foundations of Software
Engineering: A Roadmap. In this volume.
[51] Maiden, N. (1998). CREWS-SAVRE: Scenarios for Acquiring and
Validating Requirements. Automated Software Engineering, 5(4):
419-446.
[52] Maiden, N. & Rugg, G. (1996). ACRE: Selecting Methods For
Requirements Acquisition. Software Engineering Journal, 11(3):
183-192.
[53] Maiden, N. A. M. & Ncube, C. (1998). Acquiring Requirements for
Commercial Off-The-Shelf Package Selection. IEEE Software, 15(2):
46-56.
[54] Maiden, N. A. M. & Sutcliffe, A. G. (1992). Exploiting Reusable
Specifications Through Analogy. Communications of the ACM,
34(5): 55-64.
[55] Modugno, F., Leveson, N. G., Reese, J. D., Partridge, K. & Sandys,
S. D. (1997). Integrating Safety Analysis of Requirements
Specifications. 3rd IEEE International Symposium on Requirements
Engineering (RE'97), Annapolis, USA, 6-10 January 1997, pp. 148-
159.
[56] Nakajo, T. & Kume, H. (1991). A Case History Analysis of Software
Error Cause-Effect Relationships. Transactions on Software
Engineering, 17(8): 830-838.
[57] Norman, D. A. (1993). Cognition in the Head and in the World: An
Introduction to the Special Issue on Situated Action. Cognitive
Science, 17(1): 1-6.
[58] Nuseibeh, B. (1997). Ariane 5: Who Dunnit? IEEE Software, 14(3):
15-16.
[59] Nuseibeh, B., Kramer, J. & Finkelstein, A. C. W. (1994). A
Framework for Expressing the Relationships Between Multiple
Views in Requirements Specification. IEEE Transactions on
Software Engineering, 20(10): 760-773.
[60] Parnas, D. (2000). When to formalise. Personal Communication
(Email), 17 February 2000.
[61] Popper, K. R. (1963). Conjectures and Refutations: The Growth of
Scientific Knowledge. New York: Basic Books.
[62] Posner, M. I. (Ed.). (1993). Foundations of Cognitive Science. MIT
Press.
[63] Potts, C. (1997). Requirements Models in Context. 3rd International
Symposium on Requirements Engineering (RE'97), Annapolis, USA,
6-10 January 1997, pp. 102-104.
[64] Potts, C., Takahashi, K. & Anton, A. (1993). Inquiry-based
requirements Analysis. IEEE Software, 11(2): 21-32.
[65] Quality Systems and Software (1999). DOORS
<http://www.qss.co.uk/>
[66] Rational Corporation (1999). Requisite Pro
<http://www.rational.com>
[67] Reubenstein, H. B. & Waters, R. C. (1991). The Requirements
Apprentice: Automated Assistance for Requirements Acquisition.
IEEE Transactions on Software Engineering, 17(3): 226-240.
[68] Robertson, S. & Robertson, J. (1994). The Complete Systems
Analysis: The Workbook, The Textbook, the Answers. Dorset House.
[69] Robertson, S. & Robertson, J. (1999). Mastering the Requirements
Process. Addison-Wesley.
[70] Robinson, W. N. & Volkov, S. (1998). Supporting the Negotiation
Life-Cycle. Communications of the ACM, 41(5): 95-102.
[71] Saaltink, M. (1997). The Z/EVES System. 19th International
Conference on the Z Formal Method (ZUM), Reading, UK, April
1997, LNCS 1212, pp. 72-88.
[72] Schneider, G. & Winters, J. (1998). Applying Use Cases: a practical
guide. Addison-Wesley.
[73] Sharp, H., Finkelstein, A. & Galal, G. (1999). Stakeholder
Identification in the Requirements Engineering Process. Workshop
on Requirements Engineering Processes (REP'99) - DEXA'99,
Florence, Italy, 1-3 September 1999, pp. 387-391.
[74] Shaw, M. (1990). Prospects for an Engineering Discipline of
Software. IEEE Software, 7(6): 15-24.
[75] Shaw, M. & Gaines, B. (1996). Requirements Acquisition. Software
Engineering Journal, 11(3): 149-165.
[76] Stevens, R., Brook, P., Jackson, K. & Arnold, S. (1998). Systems
Engineering: Coping with Complexity. Prentice Hall Europe.
[77] Structured Software Systems Ltd (1999). CRADLE
<http://www.threesl.com/>
[78] Thayer, R. & Dorfman, M. (Ed.). (1997). Software Requirements
Engineering (2nd Edition). IEEE Computer Society Press.
[79] van Lamsweerde, A., Darimont, R. & Letier, E. (1998). Managing
conflicts in goal-driven requirements engineering. IEEE
Transactions on Software Engineering, 24(11): 908-926.
[80] Viller, S. & Sommerville, I. (1999). Social Analysis in the
Requirements Engineering Process: from ethnography to method. 4th
International Symposium on Requirements Engineering (RE'99),
Limerick, Ireland, 7-11th June 1999.
[81] Wieringa, R. J. (1996). Requirements Engineering: Frameworks for
Understanding. Wiley.
[82] Yu, E. (1997). Towards Modelling and Reasoning Support for Early-
Phase Requirements Engineering. 3rd IEEE International
Symposium on Requirements Engineering (RE'97), Annapolis, USA,
6-10 January 1997, pp. 226-235.
[83] Zave, P. (1997). Classification of Research Efforts in Requirements
Engineering. ACM Computing Surveys, 29(4): 315-321.
[84] Zave, P. & Jackson, M. (1997). Four dark corners of requirements
engineering. ACM Transactions on Software Engineering and
Methodology, 6(1): 1-30.