Requirements engineering: A roadmap

Proceedings of the Conference on the Future of Software Engineering, ICSE 2000

Volumn , Issue , 2000, Pages 35-46

  Nuseibeh, Bashar ^a   Easterbrook, Steve ^b  

^a IMPERIAL COLLEGE LONDON   (United Kingdom)

^b UNIVERSITY OF TORONTO   (Canada)

Author keywords

[No Author keywords available]

Indexed keywords

REQUIREMENTS ENGINEERING;

RESEARCH ISSUES; ROADMAP; SOFTWARE SYSTEMS;

SOFTWARE ENGINEERING;

EID: 85023009798     PISSN: None     EISSN: None     Source Type: Conference Proceeding    
DOI: 10.1145/336512.336523     Document Type: Conference Paper

References (84)

1. Abramsky, S., Gabbay, D. & Maibaum, T. (Ed.). (1992). Handbook of Logic in Computer Science Vol 1: Background: Mathematical Structures. Clarendon Press.
2. Ambriola, V. & Gervasi, V. (1997). Processing Natural Language Requirements. 12th International Conference on Automated Software Engineering, Lake Tahoe, USA, 3-5 November 1997, pp. 36-45.
3. Antoniou, G. (1998). The role of nonmonotonic representations in requirements engineering. International Journal of Software Engineering and Knowledge Engineering, 8(3): 385-399.
4. Bennett, K. H. & Rajllch, V. T. (2000). Software Maintenance and Evolution. In this volume.
5. Blum, B. I. (1996). Beyond Programming: To a New Era of Design. Oxford: Oxford University Press.
6. Boehm, B. (1991). Software Risk Management: Principles and Practices. IEEE Software, 8(1): 32-41.
7. Boehm, B., Bose, P., Horowitz, E. & Lee, M. J. (1995). Requirements Negotiation and Renegotiation Aids: A Theory-W Based Spiral Approach. 17th International Conference on Software Engineering (ICSE-17), Seattle, USA, 23-30 April 1995, pp. 243-254.
8. Boehm, B. W. (1981). Software Engineering Economics. Englewood Cliffs, NJ: Prentice-Hall.
9. Bohner, S.4. & Arnold, R. S. (Ed.). (1996). Software Change Impact Analysis. IEEE Computer Society Press.
10. Brinkkemper, S. & Joosten, S. (1996). Editorial: Method Engineering and Meta-modelling. Information and Software Technology, 38(4): 259.
11. Burg, J. F. M. (1997). Linguistic Instruments in Requirements Engineering. Amsterdam: lOS Press.
12. Carter, R., Martin, J., Mayblin, B. & Munday, M. (1984). Systems, Management and Change: A Graphic Guide. London: Paul Chapman Publishing/Harper and Row.
13. Chung, L. (1993). Dealing with Security Requirements During the Development of Information Systems. 5th International Conference on Advanced Information Systems Engineering (CAiSE'93), Pads, France, 1993, pp. 234-251.
14. Chung, L, Nixon, B., Yu, E. & Mylopoulos, J. (2000). Non-Functional Requirements in Software Engineering. Boston: Kluwer Academic Publishers.
15. Dardenne, A., Lamsweerde, A. v. & Fickas, S. (1993). Goal-Directed Requirements Acquisition. Science of Computer Programming, 20: 3-50.
16. Darke, P. & Shanks, G. (1996). Stakeholder Viewpoints in Requirements Definition: A Framework for Understanding Viewpoint Development Approaches. Requirements Engineering, 1(2): 88-105.
17. Davis, A. (1992). Operational Prototyping: A New Development Approach. Software, 9(5): 70-78.
18. Davis, A. (1993). Software Requirements: Objects, Functions and States. Prentice Hall.
19. del Gobbo, D., Napolitano, M., Callahan, J. & Cukic, B. (1998.). Experience in Developing System Requirements Specification for a Sensor Failure Detection and Identification Scheme. 3rd High-Assurance Systems Engineering Symposium, Washington, DC, USA, 13-14 November 1998.
20. Easterbrook, S. M. (1991). Resolving Conflicts Between Domain Descriptions with Computer-Supported Negotiation. Knowledge Acquisition: An International Journal, 3: 255-289.
21. Easterbrook, S. M. & Nuseibeh, B. A. (1995). Managing Inconsistencies in an Evolving Specification. Second IEEE Symposium on Requirements Engineering, York, UK, March 27-29, pp. 48-55.
22. Estublier, J. (2000). Software Configuration Management: A Roadmap. In this volume.
23. Fickas, S. & Nagarajan, P. (1988). Critiquing Software Specifications: A knowledge based approach. IEEE Software, 5(6).
24. Finkelstein, A. (1993). Requirements Engineering: An overview. 2nd Asia-Pacific Software Engineering Conference (APSEC'93), Tokyo, Japan, 1993.
25. Finkelstein, A., Ryan, M. & Spanoudakis, G. (1996). Software Package Requirements and Procurement. 8th International Workshop on Software Specification and design (IWSSD-9), Schloss Velen, Germany, pp. 141-146.
26. Finkelstein, A. & Sommerville, I. (1996). The Viewpoints FAQ: Editorial-Viewpoints in Requirements Engineering. Software Engineering Journal, 11(1): 2-4.
27. Garlan, D. (2000). Software Architecture: A Roadmap. In this volume.
28. Ghezzi, C. & Nuseibeh, B. (1998). Guest Editorial-Managing Inconsistency in Software Development. Transactions on Software Engineering, 24(11): 906-907.
29. G0guen, J. & Jirotka, M. (Ed.). (1994). Requirements Engineering: Social and Technical lssues. London: Academic Press.
30. Goguen, J. & Linde, C. (1993). Techniques for Requirements Elicitation. 1st IEEE International Symposium on Requirements Engineering (RE'93), San Diego, USA, 4-6th January 1993, pp. 152-164.
31. Gotel, O. & Finkelstein, A. (1994). An Analysis of the Requirements Traceability Problem. 1st International Conference on Requirements Engineering (ICRE'94), Colorado Springs, April 1994, pp. 94-101.
32. Gravell, A. & Henderson, P. (1996). Executing Formal Specifications Need Not Be Harmful. IEE Software Engineering Journal, 11(2): 104-110.
33. Greenspan, S. & Feblowitz, M. (1993). Requirements Engineering Using the SOS Paradigm. 1st International Symposium on Requirements Engineering (RE'93), San Diego, USA, 4-6 January 1993, pp. 260-263.
34. Hauser, J. R. & Clausing, D. (1988). The House of Quality. The Harvard Business Review(3): 63-73.
35. Heitmeyer, C. L., Jeffords, R. D. & Labaw, B. G. (1996). Automated Consistency Checking of Requirements Specifications. IEEE Transactions on Software Engineering and Methodology, 5(3): 231-261.
36. Holtzblatt, K. & Beyer, H. R. (1995). Requirements Gathering: The Human Factor. Communications oftheACM, 38(5): 31-32.
37. Holzmann, G. J. (1997). The Model Checker Spin. Transactions on Software Engineering, 23(5): 279-295.
38. Hunter, A. & Nuseibeh, B. (1998). Managing Inconsistent Specifications: Reasoning, Analysis and Action. ACM Transactions on Software Engineering and Methodology, 7(4): 335-367.
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, tusk 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. Leucopoulos, 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. Pamas, 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. M1T 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 EngineeringDiscipline 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. A CM Computing Surveys, 29(4): 315-321.
84. Zave, P. & Jackson, M. (1997). Four dark comers of requirements engineering. ACM Transactions on Software Engineering and Methodology, 6(1): 1-30.