Software engineering processes for building safe and secure software have existed for a long time. However, these processes-particularly for secure software engineering-have not been widely taught within colleges and universities leading to a shortage of graduates skilled in these areas. This panel will discuss the increasing need for colleges and universities to produce graduates that are skilled in building safe and secure software. Panelists will share their experiences teaching courses in these areas and future directions for curricula.

The series of EDSER workshops are a unique forum to discuss and advance the state-of-the-art research and practice in economics driven software engineering. The EDSER-5 will bring together leading researchers and practitioners to provide further understanding how economic and business considerations affect - and should affect - software engineering decisions.

Conducting cost-benefit analyses of architectural attributes such as security has always been difficult, because the benefits are difficult to assess. Specialists usually make security decisions, but program managers are left wondering whether their investment in security is well spent. This paper summarizes the results of using a cost-benefit analysis method called SAEM to compare alternative security designs in a financial and accounting information system. The case study presented in this paper starts with a multi-attribute risk assessment that results in a prioritized list of risks. Security specialists estimate countermeasure benefits and how the organization's risks are reduced. Using SAEM, security design alternatives are compared with the organization's current selection of security technologies to see if a more cost-effective solution is possible. The goal of using SAEM is to help information-system stakeholders decide whether their security investment is consistent with the expected risks.

A goal of the Studio course in the Master of Software Engineering program at Carnegie Mellon University is to bridge the gap between experience and academics. One way to transfer experience to young software engineers is through case studies designed to focus students on specific software engineering problems. This paper discusses my experience with developing a case study to improve students' analytical capabilities and introduce the importance of considering maintenance and implementation issues in software design. The case study, developed as a classroom assignment, proved an effective tool to teach software engineering students that there are more things to consider than performance specifications.