Abstract
Software engineering is what is being done everywhere in the world where people (“software engineers”) develop, or modify, software. Good software engineering is not too common.
Researchers in the field of software engineering often fail to address the problems software engineers actually have. They have lost contact to the practitioners, while many practitioners never expected to benefit from research, and never tried to. Therefore, many well-known problems are still waiting for solutions, as the results of a Dagstuhl-Seminar in 1999 indicate.
The situation of software engineers has not changed significantly since 1990, except for their equipment, and there is no reason to believe that there will be far more changes in the next decade. In order to improve the general level of software engineering, more emphasis should be put on education, and on close co-operation of software engineers and researchers.
This is a preview of subscription content, log in via an institution to check access.
Access this chapter
Tax calculation will be finalised at checkout
Purchases are for personal use only
Preview
Unable to display preview. Download preview PDF.
References
Aspray, W., R. Keil-Slawik, D. Parnas (eds.) (1996): The History of Software Engineering. Dagstuhl-Report 153 on the Dagstuhl-Seminar 9635, August 1996.
Bauer, F.L. (1993): Software Engineering-wie es begann. Informatik-Spektrum 16, 259f.
Beck, L.L., T.E. Perkins (1983): A Survey of Software Engineering Practice: tools, methods, and results. IEEE Transactions on Software Engineering, SE-9, 5, 541–561.
Brooks, F.P., Jr. (1987): No silver bullet-essence and accidents of software engineering. IEEE COMPUTER 20, 4, 10–19.
Denert, E., D. Hoffman, J. Ludewig, D. Parnas (1999): SE Research and Education: Seeking a new Agenda. Seminar-Report 230, Dagstuhl, February 1999. The report is available from http://www.dagstuhl.de/DATA/Seminars/99/#99071
Ludewig, J., R. Reiβing (1998): Teaching what they need instead of teaching what we like — the new software engineering curriculum at the University of Stuttgart. Information and Software Technology 40 (4), 239–244. The paper (and more recent ones in German) is available from http://www.informatik.uni-stuttgart.de/ifi/se/publications
Parnas, D.L. (1972): On the criteria to be used in decomposing systems into modules. Communications of the ACM, 15, 1053–1058.
Parnas, D.L. (1976): On the design and development of program families. IEEE Transactions on Software Engineering, SE-2 (1), 1–9.
Royce, W.W. (1970): Managing the development of large software systems. IEEE WESCON, August 1970, pp.1–9. reprinted in Proc. of the 9th ICSE (IEEE), pp.328-338.
Zelkowitz, M.V., R.T. Yeh, R.G. Hamlet, J.D. Gannon, V.R. Basili (1984): Software Engineering Practices in the US and Japan. IEEE COMPUTER, 1984, June, 57–66.
Author information
Authors and Affiliations
Editor information
Editors and Affiliations
Rights and permissions
Copyright information
© 2001 Springer-Verlag Berlin Heidelberg
About this chapter
Cite this chapter
Ludewig, J. (2001). Software Engineering in the Years 2000 Minus and Plus Ten. In: Wilhelm, R. (eds) Informatics. Lecture Notes in Computer Science, vol 2000. Springer, Berlin, Heidelberg. https://doi.org/10.1007/3-540-44577-3_7
Download citation
DOI: https://doi.org/10.1007/3-540-44577-3_7
Published:
Publisher Name: Springer, Berlin, Heidelberg
Print ISBN: 978-3-540-41635-7
Online ISBN: 978-3-540-44577-7
eBook Packages: Springer Book Archive