[Left] [Up] [Right] Web-based Systems Engineering Training [Left] [Up] [Right]

Lessons Learned from Company XYZ

What did we observe and learn from our training classes at XYZ?

  1. Systems engineering is a team activity -- training needs to support multiple viewpoints, levels of experience, and backgrounds.

  2. 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.

  3. Training materials are linear -- but systems concepts are best organized into a variety of architectures. See the adjacent figure.

  4. Too many pages! Too many links! Readers feel overwhelmed. They jump around material and gloss over content rather than learning it.

  5. 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

  1. Need to find ways of using web technology to enhance quality of learning. Otherwise, whole exercise is a waste of time.

  2. How to work with XYZ's businesses to create business-specific case studies?

[Web Training : Fig 4 ]

Figure : Architecture of Training Material Contents


Section 3-3: November, 2001. [Left] [Up] [Right]