1 Abstract A typical four-year engineering curriculum is chock-full of courses, concepts, and ideas. However, four years is simply not enough time to explore the vast landscape of engineering knowledge thoroughly. Thus trade-offs are made selecting material within a course as well as selecting courses within a curriculum. One of these trade-offs is depth versus breadth. At the extremes, the specialist is too narrow while the generalist is too shallow. Most curricula locate themselves between these two poles, with general engineering programs leaning somewhat towards breadth. One might think that students who choose general programs would be appreciative of the breadth of the curriculum. However, even here some students object to required courses that are not immediately and obviously applicable to their anticipated career path. How can we convince students that breadth is just as important, if not more so, than depth? As a case study, I describe my approach in an introductory electrical engineering course that is taught to students interested in a variety of engineering disciplines – many of whom are not necessarily interested in electrical engineering per se. Using a variety of pedagogical and curricular techniques, I dispel a number of myths related to the breadth versus depth debate.
[1]
B. Bloom,et al.
Taxonomy of Educational Objectives. Handbook I: Cognitive Domain
,
1966
.
[2]
J. VanAntwerp,et al.
An Optimal Engineering Education: The BSE at a Liberal Arts College
,
2004
.
[3]
Steven H. VanderLeest.
The Built-in Bias of Technology
,
2004
.
[4]
Zoltán Dienes,et al.
Transfer of implicit knowledge across domains? How implicit and how abstract?
,
1997
.
[5]
H. Gardner,et al.
Frames of Mind: The Theory of Multiple Intelligences
,
1983
.
[6]
Byron Newberry,et al.
The Current Status And Uses Of The General (Undesignated) Engineering Program With A Case Study
,
2003
.