The focus of this one-day workshop on April 18th, 2006 was the experience, current situation, and the future of education and training in software engineering of (more) secure software. The workshop was intended for those in education, government, and industry at all levels doing education or training in secure software engineering and for those who would like to – as well as others interested in the subject or the secure software engineering workforce.

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.

A systematic approach to test data design is presented based on both practical translation of theory and organization of professional lore. The approach is organized around five domains and achieving coverage (exercise) of them by the test data. The domains are processing functions, input, output, interaction among functions, and the code itself. Checklists are used to generate data for processing functions. Separate checklists have been constructed for eight common business data processing functions such as editing, updating, sorting, and reporting. Checklists or specific concrete directions also exist for input, output, interaction, and code coverage. Two global heuristics concerning all test data are also used. A limited discussion on documenting test input data, expected results, and actual results is included.