ACM Home Page
Please provide us with feedback. Feedback
Requirements engineering: a roadmap
Full text PdfPdf (1.30 MB)
Source International Conference on Software Engineering archive
Proceedings of the Conference on The Future of Software Engineering table of contents
Limerick, Ireland
Pages: 35 - 46  
Year of Publication: 2000
ISBN:1-58113-253-0
Authors
Bashar Nuseibeh  Department of Computing, Imperial College, 180 Queen's Gate, London SW7 2BZ, U.K.
Steve Easterbrook  Department of Computer Science, University of Toronto, 6 King's College Road, Toronto, Ontario M5S 3H5, Canada
Sponsors
IEEE-CS : Computer Society
SIGSOFT: ACM Special Interest Group on Software Engineering
Irish Comp Soc : Irish Computer Society
Publisher
ACM  New York, NY, USA
Bibliometrics
Downloads (6 Weeks): 143,   Downloads (12 Months): 1334,   Citation Count: 51
Additional Information:

references   cited by   index terms   collaborative colleagues   peer to peer  

Tools and Actions: Review this Article  
DOI Bookmark: Use this link to bookmark this Article: http://doi.acm.org/10.1145/336512.336523
What is a DOI?

REFERENCES

Note: OCR errors may be found in this Reference List extracted from the full text article. ACM has opted to expose the complete List rather than only correct and linked references.

 
1
 
2
 
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
 
5
 
6
7
 
8
 
9
 
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
 
14
Chung, L, Nixon, B., Yu, E. & Mylopoulos, J. (2000). Non- Functional Requirements in Software Engineering. Boston: Kluwer Academic Publishers.
 
15
 
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
 
18
 
19
 
20
 
21
22
 
23
 
24
Finkelstein, A. (1993). Requirements Engineering: an overview. 2nd Asia-Pacific Software Engineering Conference (APSEC'93), Tokyo, Japan, 1993.
 
25
 
26
Finkelstein, A. & Sommerville, I. (1996). The Viewpoints FAQ: Editorial - Viewpoints in Requirements Engineering. Software Engineering Journal, 11(1): 2-4.
27
 
28
 
29
 
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. lEE 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
36
 
37
38
 
39
 
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
 
42
Johnson, P. (1992). Human-Computer Interaction: psychology, tusk analysis and software engineering. McGraw-Hill.
 
43
 
44
 
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
50
 
51
 
52
Maiden, N. & Rugg, G. (1996). ACRE: Selecting Methods For Requirements Acquisition. Software Engineering Journal, 11(3): 183-192.
 
53
54
 
55
 
56
 
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
 
59
 
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
 
63
 
64
 
65
Quality Systems and Software (1999). DOORS <http://www.qss.co.uk/>
 
66
Rational Corporation (1999). Requisite Pro <http://www.rational.com>
 
67
 
68
 
69
70
 
71
 
72
 
73
 
74
 
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
 
79
 
80
 
81
 
82
83
84

CITED BY  51
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Collaborative Colleagues:
Bashar Nuseibeh: colleagues
Steve Easterbrook: colleagues

Peer to Peer - Readers of this Article have also read: