TOP
Search the Dagstuhl Website
Looking for information on the websites of the individual seminars? - Then please:
Not found what you are looking for? - Some of our services have separate websites, each with its own search option. Please check the following list:
Schloss Dagstuhl - LZI - Logo
Schloss Dagstuhl Services
Seminars
Within this website:
External resources:
  • DOOR (for registering your stay at Dagstuhl)
  • DOSA (for proposing future Dagstuhl Seminars or Dagstuhl Perspectives Workshops)
Publishing
Within this website:
External resources:
dblp
Within this website:
External resources:
  • the dblp Computer Science Bibliography


Dagstuhl Seminar 9208

Future Directions in Software Engineering

( Feb 17 – Feb 21, 1992 )

Permalink
Please use the following short url to reference this page: https://www.dagstuhl.de/9208

Organizers
  • N. Habermann
  • W.F. Tichy



Impacts

Motivation

The intent of the workshop was to identify promising directions for future research in Software Engineering. The motivation for the meeting was the shared realization that although the quantity of research in Software Engineering has been increasing, quality has not. Emphasis on software development management and risk control has diverted attention from important technical issues. Fresh ideas and solid, technical results are rare. This situation has a negative impact on Software Engineering as a whole and deprives industry of potential technical benefits.

The first four days of the workshop were spent in intensive discussions. The abstracts of participants' position statements and discussion summaries follow this epitome. During the final session, each participant was given a ten minute timeslot for presenting the areas of Software Engineering where research should be intensified. Participants were specifically asked to consider areas in which they were not involved personally. Below is an extract of these presentations, compiled by the editors. The following topics emerged as crucial for progress:

  1. Software architecture as a foundation;
  2. Mastering evolving systems;
  3. A scientific basis for Software Engineering;
  4. Education based on engineering know-how.

Formal methods, domain specific knowledge, special purpose languages, and reuse were seen as important approaches to software architecture and evolution, but not as ends in themselves. There was also a fair amount of introspection of what constitutes appropriate research methodology in Software Engineering.

Copyright

Participants
  • N. Habermann
  • W.F. Tichy