Experiences and methods from integrating evidence-based software engineering into education

In today's software development organizations, methods and tools are employed that frequently lack sufficient evidence regarding their suitability, limits, qualities, costs, and associated risks. For example, in Communications of the ACM (Communications of the ACM May 2004/Vol. 47, No. 5) Robert L. Glass, taking the standpoint of practitioners, asks for help from research: "Here's a message from software practitioners to software researchers: We (practitioners) need your help. We need some better advice on how and when to use methodologies". Therefore, he demands: - a taxonomy of available methodologies, based upon their strengths and weaknesses; - a taxonomy of the spectrum of problem domains, in terms of what practitioners need; - a mapping of the first taxonomy to the second (or the second to the first). The evidence-based Software Engineering Paradigm promises to solve parts of these issues by providing a framework for goal-oriented research leading to a common body of knowledge and, based on that, comprehensive problemoriented decision support regarding SE technology selection