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
Within this website:
External resources:
  • DOOR (for registering your stay at Dagstuhl)
  • DOSA (for proposing future Dagstuhl Seminars or Dagstuhl Perspectives Workshops)
Within this website:
External resources:
Within this website:
External resources:
  • the dblp Computer Science Bibliography

Dagstuhl Seminar 99071

Software Engineering Research and Education: Seeking a new Agenda

( Feb 14 – Feb 19, 1999 )

(Click in the middle of the image to enlarge)

Please use the following short url to reference this page:

  • D. Hoffman (Victoria)
  • D. Parnas (McMaster)
  • E. Denert (sd&m, München)
  • J. Ludewig (Stuttgart)

The Dagstuhl Foundation gratefully acknowledges the donation from



In any engineering discipline, establishing the core body of knowledge is an essential step. In the software engineering community, the lack of agreement regarding this knowledge is a handicap. Educators and researchers are left without clear answers to the questions:

  • What do we already know?
  • What should we teach?
  • What are the most important open problems?

And, last but not least:

  • Where are the limits of our field?

The result is that we are not focussing on the most important problems and there is much wasted effort in education, research, and development.

The goal of this seminar is to make concrete progress towards establishing the core body of knowledge for software engineering. We will structure this knowledge as observations about the solutions to a set of tasks that every practicing software engineer should be able to perform.

The seminar will focus on problems which are clearly technical. We will, however, spend some time for defining the limits towards adjoining problems, like software project management, software quality assurance, and the design of the computer system configuration, including the separation of hardware and software.

Each participant is required to contribute a position paper well before the seminar. This paper should focus on one task (from a given list) and state whether the task is: "Standard operating procedure (SOP)", "Solved", "Partially solved", "Unsolved", or "Not relevant".

The position paper must briefly justify the claim. If the claim is "SOP" or "solved", then an approach must be named and successful applications cited. If the claim is "unsolved", then the open problems must be described.

The Dagstuhl Seminar will be run as a "writer's workshop". The submitted position papers are viewed as drafts to be improved by discussion at the seminar. Most of the workshop sessions will be spent on discussing and improving the position papers. New drafts are expected daily. Our goal is a Dagstuhl seminar where we produce concrete useful results, in this case a collection of well-written position papers that together constitute a new kind of agenda for software engineering research and education.

  • D. Hoffman (Victoria)
  • D. Parnas (McMaster)
  • E. Denert (sd&m, München)
  • J. Ludewig (Stuttgart)