ACM Home Page
Please provide us with feedback. Feedback
Requirements engineering in the year 00: a research perspective
Full text PdfPdf (206 KB)
Source International Conference on Software Engineering archive
Proceedings of the 22nd international conference on Software engineering table of contents
Limerick, Ireland
Pages: 5 - 19  
Year of Publication: 2000
ISBN:1-58113-206-9
Author
Axel van Lamsweerde  Département d'Ingénierie Informatique, Université catholique de Louvain, B-1348 Louvain-la-Neuve (Belgium)
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): 81,   Downloads (12 Months): 551,   Citation Count: 45
Additional Information:

abstract   references   cited by   index terms   collaborative colleagues  

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

ABSTRACT

Requirements engineering (RE) is concerned with the identification of the goals to be achieved by the envisioned system, the operationalization of such goals into services and constraints, and the assignment of responsibilities for the resulting requirements to agents such as humans, devices, and software. The processes involved in RE include domain analysis, elicitation, specification, assessment, negotiation, documentation, and evolution. Getting high-quality requirements is difficult and critical. Recent surveys have confirmed the growing recognition of RE as an area of utmost importance in software engineering research and practice.The paper presents a brief history of the main concepts and techniques developed to date to support the RE task, with a special focus on modeling as a common denominator to all RE processes. The initial description of a complex safety-critical system is used to illustrate a number of current research trends in RE-specific areas such as goal-oriented requirements elaboration, conflict management, and the handling of abnormal agent behaviors. Opportunities for goal-based architecture derivation are also discussed together with research directions to let the field move towards more disciplined habits.


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.

 
Abr80
J.R. Abrial, "The Specification Language Z: Syntax and Semantics" . Programming Research Group, Oxford Univ., 1980.
 
Amo94
Bal82
 
BAR99
Bay Area Rapid Transit District, Advance Automated Train Control System, Case Study Description. Sandia National Labs, http://www.hcecs.sandia.gov/bart.htm.
 
Beh99
 
Bel76
 
Ben93
 
Ber91
 
Boe81
Boe95
 
Bra85
 
Bro84
M. Brodie, J. Mylopoulos, and J. Schmidt (eds.), On Conceptual Modeling: Perspectives from Artificial Intelligence, Databases, and Programming Languages. Springer-Verlag, 1984.
 
Bro87
 
Bub80
J. Bubenko, "Information Modeling in the Context of System Development", Proc. IFIP Congress '80, North Holland, 1980, 395-411.
 
But98
R.W. Butler, S.P. Miller, J.N. Potts and V.A. Carreno, "A Formal Methods Approach to the Analysis of Mode Confusion", Proceedings DASC'98 - 17th Digital Avionics Systems Conference, Seattle, November 1998. See also http:// shemesh.larc.nasa.gov/fm/fm-now-mode-confusion.html.
 
Cha98
Che76
 
Cla99
 
Dar91
 
Dar93
Dar96
 
Dem78
 
Dub93
Dwy99
 
Eas94
 
ESI96
European Software Institute, "European User Survey Analysis", Report USV_EUR 2.1, ESPITI Project, January 1996.
 
Fau92
Fea87
 
Fea97
 
Fea98
 
Fic92
 
Fin87
A. Finkelstein and C. Potts, "Building Formal Specifications Using Structured Common Sense", Proc. IWSSD-4 - 4th International Workshop on Software Specification and Design (Monterey, Ca.), IEEE, April 1987, 108-113.
 
Gam95
 
Gar97
 
Gog93
J. Goguen and C. Linde, "Techniques for Requirements Elicitation", Proc. RE'93 - First IEEE Symposium on Requirements Engineering, San Diego, 1993, 152-164.
 
Gog94
 
Got95
 
Gre82
 
Gre86
 
Har87
 
Har90
Har96
 
Heim96
Heit96
 
Hei98a
 
Hei98b
 
Hen80
K.L. Heninger, "Specifying Software Requirements for Complex Systems: New Techniques and their Application", IEEE Transactions on Software Engineering Vol. 6 No. 1, January 1980, 2-13.
 
Hic74
 
Hol97
 
Hsi94
Hun98
 
Jac78
 
Jac95
 
Jaco93
 
Jar98
M.Jarke and R. Kurki-Suonio (eds.), Special Issue on Scenario Management, IEEE Trans. on Sofware. Engineering, December 1998.
 
Jon93
 
Ken93
S. Kent, T. Maibaum and W. Quirk, "Formally Specifying Temporal Constraints and Error Recovery", Proc. RE'93 - 1st Intl. IEEE Symp. on Requirements Engineering, Jan. 1993, 208- 215.
 
Koy92
 
Lam98a
 
Lam98b
 
Lam98c
 
Lam2Ka
Lam2Kb
 
LAS93
Report of the Inquiry Into the London Ambulance Service, February 1993. The Communications Directorate, South West Thames Regional Authority, ISBN 0-905133-70-6. See also the London Ambulance System home page, http:// hsn.lond-amb.sthames.nhs.uk/http.dir/service/organisation/fea-turs/ info.html.
 
Let2K
E.Letier and A. van Lamsweerde, "KAOS in Action: the BART System". IFIP WG2.9 meeting, Flims, http:// www.cis.gsu.edu/~wrobinso/ifip2_9/Flims00.
 
Lev94
Lev95
 
Luc95
 
Lut93
R.R. Lutz, "Analyzing Software Requirements Errors in Safety-Critical, Embedded Systems", Proceedings RE'93 - First International Symposium on Requirements Engineering, San Diego, IEEE, 1993, 126-133.
 
Mag95
Mai93
 
Man92
 
Mas97
 
McM93
 
Mey85
B. Meyer, "On Formalism in Specifications", IEEE Software, Vol. 2 No. 1, January 1985, 6-26.
 
Mor95
 
Mun81
E. Munford, "Participative Systems Design: Structure and Method", Systems, Objectives, Solutions, Vol. 1, North-Hol-land, 1981, 5-19.
 
Myl92
 
Myl98
Myl99
 
Nil71
 
Nis89
 
Nix93
B. A. Nixon, "Dealing with Performance Requirements During the Development of Information Systems", Proc. RE'93 - 1st Intl. IEEE Symp. on Requirements Engineering, Jan. 1993, 42-49.
 
Nus94
 
Par95
Per92
 
Pot94
Pot95
 
Pot96
 
Qui68
R. Quillian, Semantic Memory. In Semantic Information Processing, M. Minsky (ed.), MIT Press, 1968, 227-270.
 
Reu91
 
Rie99
Rob89
 
Ros77a
D.T. Ross, "Structured Analysis (SA): A Language for Communicating Ideas", IEEE Transactions on Software Engineering, Vol. 3, No. 1, 1977, 16-34.
 
Ros77b
D.T. Ross and K.E. Schoman, "Structured Analysis for Requirements Definition", IEEE Transactions on Software Engineering, Vol. 3, No. 1, 1977, 6-15.
Rub92
 
Rum91
 
Rum99
 
Sha96
Smi77
 
Sou93
J. Souqui~res and N. Levy, "Description of Specification Developments", Proc. RE'93 - First IEEE Symposium on Requirements Engineering, San Diego, 1993, 216-223.
 
Sta95
The Standish Group, "Software Chaos", http:// www.standishgroup.com/chaos.html.
 
Sut97
 
Tay96
Tho99
 
War85
 
Was79
A. Wasserman, "A Specification Method for Inteactive Information Systems", Proceedings SRS - Specification of Reliable Software. IEEE Catalog No. 79 CH1401-9C, 1979, 68-79.
 
Wei98
 
Yue87
K. Yue, "What Does It Mean to Say that a Specification is Complete?", Proc. IWSSD-4, Fourth International Workshop on Software Specification and Design, Monterey, 1987.
 
YuM94
 
Yu97
Zav93
 
Zav96
Zav97a
Zav97b

CITED BY  45

Collaborative Colleagues:
Axel van Lamsweerde: colleagues