Portland, Oregon
June 12, 2005
June 12, 2005
June 15, 2005
2153-5965
10
10.598.1 - 10.598.10
10.18260/1-2--15118
https://peer.asee.org/15118
1912
Everyday Problem Solving in Engineering: Lessons for Educators1 David Jonassen, Johannes Strobel, Chwee Beng Lee University of Missouri/Concordia University/Nanyang Technology University
Many engineering programs have integrated problem-based learning (PBL) into their instruction. Quite often, the problems that are solved in PBL programs are not authentic. In order to develop more authentic problems that are required to prepare engineering graduates to solve complex, ill-structured workplace problems, we developed a case library of engineering problems as described by practicing engineers. The qualitative analysis of those stories showed that workplace problems are ill-structured because they are constrained by unpredictable, non-engineering parameters; driven by multiple, often conflicting goals; evaluated using non-engineering success criteria; possessing aggregates of smaller well-structured problems; requiring complex collaborations; and replete with unanticipated problems. The implications for developing problem-based learning environments in engineering are clear: problems must represent more complexity, ambiguity, collaboration, and dynamic conditions.
Of all of the ABET accreditation standards, undergraduate and graduate engineering students as well as practitioners consider the ability to design and conduct experiments and to identify, formulate, and solve engineering problems as being the most important 1. In an effort to meet ABET accreditation standards and to better prepare engineering graduates, engineering education programs have been implementing a variety of forms of problem- based learning (PBL). In fact, several engineering programs around the world (e.g., Aalborg University on Denmark, McMasters University in Canada, Monash University in Australia, Manchester University in England, Glasgow University in Scotland, Eindhoven University in the Netherlands, and Republic Polytechnic in Singapore) deliver the majority of their curricula via PBL. Additionally, PBL modules or courses have been implemented in numerous engineering programs, including biomedical engineering 2, chemical engineering 3, software engineering 4,5, thermal physics 6, design processes 7, aerospace engineering 8, computing 9, microelectronics 10, construction engineering 11, control theory 12. Limited efforts have even examined the use of PBL for engineering workplace training 13.
While PBL represents an important pedagogical innovation in engineering education, the nature of the problems that are solved by students are inconsistent with those that engineers solve in the workplace. Workplace problems are assumed to be complex and ill-structured problems because they have vaguely defined or unclear goals and unstated constraints; possess multiple solutions, solution paths, or no solutions at all; possess multiple criteria for evaluating solutions; where there is uncertainty about which rules and theories are necessary for a solution 14. These problems often require engineers to make judgments and express personal opinions or beliefs about the problem. While engineering education programs are beginning to engage students in more authentic forms of problem solving, as evidenced by
Proceedings of the 2005 American Society for Engineering Education Annual Conference& Exposition Copyright © 2005, American Society for Engineering Education
Strobel, J., & Jonassen, D. (2005, June), Everyday Problem Solving In Engineering: Lessons For Educators Paper presented at 2005 Annual Conference, Portland, Oregon. 10.18260/1-2--15118
ASEE holds the copyright on this document. It may be read by the public free of charge. Authors may archive their work on personal websites or in institutional repositories with the following citation: © 2005 American Society for Engineering Education. Other scholars may excerpt or quote from these materials with the same citation. When excerpting or quoting from Conference Proceedings, authors should, in addition to noting the ASEE copyright, list all the original authors and their institutions and name the host city of the conference. - Last updated April 1, 2015