Project 1. Java Enabled Diagram Technology (2000-2003)

Participants: Natasha Kositsyna, Mark Austin. Support: NSF, Northrop Grumman, GE Research and Development. Motivation -- Lessons Learned from Training Classes at Company XYZ (in 1999-2000) Systems engineering training activities should mirror those of the practising systems engineer. This is hard!!! Systems engineering is a team activity -- training needs to support multiple viewpoints, levels of experience, and backgrounds. Systems engineering processes make use of many different entity types (e.g., primary and derived requirements; traceability links; various models of system behavior and system structure), sometimes connected in complicated ways. Training materials are linear -- but systems concepts are best organized into a variety of architectures. See the adjacent figure. Too many pages! Too many links! Readers feel overwhelmed. They jump around material and gloss over content rather than learning it. Students need to see how new systems engineering concepts can be applied to applications they are familiar with. (i.e., if you're at a company that makes trains, you need a case study on trains). Challenge We need to find ways of using web technology to enhance quality of learning. Otherwise, whole exercise is a waste of time.

Section 9-1: April, 2003.