Academia.edu no longer supports Internet Explorer.
To browse Academia.edu and the wider internet faster and more securely, please take a few seconds to upgrade your browser.
2011 ASEE Annual Conference & Exposition Proceedings
Engineering design involves insightful identification of factors influencing a system and systematic unpacking of specifications/requirements from goals. However, many engineering students are slow to articulate the major problems to be solved and the sub problems associated with achieving the main design goals and constraints. Prior research in design describes students" premature termination of solution finding to select a single idea. Then all other design decisions are constrained by this initial decision [1]. In this paper, we report how first-year engineering (FYE) students attempted to translate given design goals into sub-problems to be solved or questions to be researched. We found that, instead of decomposing the problem through further analysis and sense making, many FYE students tended to "restate" the goal, identify one major function, and then use hands on building as the central creative process. Further, students claimed they used a systematic design process, but observations of their problem solving process and teaming skills indicated a different behavior. Further investigation indicated that many FYE students could identify the superficial features from the problem statement, but they were not able to identify the implicit logical steps or deep structure of the problem. Our current data provided the baseline of how FYE students abstract and interpret information from a design goal to generate a specific problem statement. We are interested in treatments to improve students" ability to recognize critical features of a given context and encourage taking multiple perspectives to identify alternative solutions. We are combining the use of graphical representational tools as organizational tools to support teams collaboration and we encourage opportunities to reflect and refine their design process. This research is relevant to engineering instructors/researchers who want to develop students" ability to deal with complex design challenges and efficiently decompose, analyze and translate the problem statements into meaningful functional specifications, stakeholder requirements and a plan of action.
2011
Engineering design involves insightful identification of factors influencing a system and systematic unpacking of specifications/requirements from goals. However, many engineering students are slow to articulate the major problems to be solved and the sub problems associated with achieving the main design goals and constraints. Prior research in design describes students" premature termination of solution finding to select a single idea. Then all other design decisions are constrained by this initial decision [1]. In this paper, we report how first-year engineering (FYE) students attempted to translate given design goals into sub-problems to be solved or questions to be researched. We found that, instead of decomposing the problem through further analysis and sense making, many FYE students tended to "restate" the goal, identify one major function, and then use hands on building as the central creative process. Further, students claimed they used a systematic design process, but observations of their problem solving process and teaming skills indicated a different behavior. Further investigation indicated that many FYE students could identify the superficial features from the problem statement, but they were not able to identify the implicit logical steps or deep structure of the problem. Our current data provided the baseline of how FYE students abstract and interpret information from a design goal to generate a specific problem statement. We are interested in treatments to improve students" ability to recognize critical features of a given context and encourage taking multiple perspectives to identify alternative solutions. We are combining the use of graphical representational tools as organizational tools to support teams collaboration and we encourage opportunities to reflect and refine their design process. This research is relevant to engineering instructors/researchers who want to develop students" ability to deal with complex design challenges and efficiently decompose, analyze and translate the problem statements into meaningful functional specifications, stakeholder requirements and a plan of action.
The act of evaluating solutions is a common engineering design activity. Over the past eight years we have used verbal protocol analysis to gain insight into engineering students' design processes. This study includes protocols from 32 freshmen and 61 seniors who solved 2 design problems that differed in complexity. In this dataset, 18 of the subjects solved the same problems as both freshmen and seniors. This dataset has allowed us to characterize differences between freshmen and seniors on a global scale as well as an individual scale. Additionally, the inclusion of two problems that vary in complexity allows us to analyze differences in performance and behaviors across problems. One of the important findings that has emerged from an across problem comparison is differences in the amount of time that students spent evaluating their solutions. In particular, (i) students spent more time evaluating their solutions and (ii) a greater number of students evaluated their solutions when solving a more "complex" problem as compared to a less "complex" one. In this paper, we present these results and discuss reasons for these differences. These include differences in the complexity of the two problems and the kinds of processes students employed while designing their solutions. We will also discuss the relationships between time spent evaluating and the number of constraints considered (constraints either given or introduced by the student). We conclude this paper with a summary of implications for engineering education.
2000 Annual Conference Proceedings
Engineering design problems are often ambiguous, ill-structured, and usually have multiple solutions. As a result, a designer's understanding of the problem or possible solutions evolves through a process of iteration. To understand iterative behaviors we need to investigate what information is known by the designer, how that information is acquired and utilized, what kinds of changes to the design problem occurred as a result of these activities, and how these behaviors affect the quality of the final solution and contribute to the efficiency of the design process itself. In our previous work, we developed a cognitive model for capturing both the evolution of these information processing activities and any changes made to the design problem, solution or process. In this paper we present a case study analysis comparing freshmen and senior engineering students. Verbal protocol data and independent measures of the quality of students final design solutions were used to provide illustrative examples of differences in iterative approaches related to experience and performance. An analysis of these behaviors in terms of problem scoping, solution revision, and comprehension monitoring activities will be presented and discussed.
2016
21st century engineering graduates should be proficient in engaging their conceptual thinking and analytical capabilities to proffer solutions to societal problems. Various literatures dwelling on problem-solving skills indicate that fresh engineering undergraduates are not adept at conceptualising solutions to design problems. However, the process of conceptualising solutions to design problems has not been well developed, understood and managed in many engineering curricula. In order to illuminate our understanding in regards to how engineering students conceptualise solutions to design problems at various stages of their educational programme, ten fresh engineering undergraduate and ten engineering postgraduate students were interviewed with a view to exploring: (i) what approaches they employ in identifying design problems? (ii) how they determine the relevance of the identified design problems to the needs of their community? (iii) how they conceptualise design solutions to the...
Journal of Technology Education, 2016
The authors investigated the differences in using problem decomposition and problem recomposition between dyads of engineering experts, engineering seniors, and engineering freshmen. Participants worked in dyads to complete an engineering design challenge within 1 hour. The entire design process was video and audio recorded. After the design session, members participated in a group interview. Video and audio data were transcribed, segmented, and coded to make comparisons. Results show differences between engineering experts, seniors, and freshman in design thinking. Students tend to use depth-first decomposition, and experts tend to use breadth-first decomposition in engineering design. The results also show that students spend less cognitive effort on the problem-definition stage than engineering experts.
Center For the Advancement of Engineering Education, 2007
Because design plays a central role in engineering, it is important for engineering education programs to prepare students with design skills.
International Journal of Designs for Learning, 2021
The research phase preluding a design capstone project is challenging for both students and instructors. In a situation where students are free to work on a topic of their choosing, a preset, generic research design is not suitable. Imposing a rigid framework would endanger the possibility of students truly examining and capturing the complexity of their project problematic. This would also be considered a counterpoint to the learning goal of teaching students how to engage in problematization, a skill highly valued in contemporary design practice. This reality raises the following question: how are instructors supposed to monitor and support students in this process? To address this problem, a teaching assignment called the Newspaper was designed. The Newspaper is an open and flexible framework, based on a digital platform, through which students can organize their research findings and reflections, while ensuring enough flexibility for students to deploy appropriate and relevant research methods. This assignment gives students freedom in terms of their research design, but also has certain constraints to ensure the intelligibility of the research process. This paper presents the Newspaper assignment in detail and discusses its impacts after it is used by three cohorts of industrial design students.
ASEE Annual Conference and Exposition Conference Proceedings, 2007
Because design plays a central role in engineering, it is important for engineering education programs to prepare students with design skills. By describing both novice and expert approaches to engineering design, researchers are contributing to the formulation of more specific design learning outcomes that may be addressed in curriculum design and program planning. One learning area where novices and experts differ is in how broadly they define engineering problems with which they are faced. This paper examines differences between how novices and experts approached the same hypothetical engineering problem. First-year students (n=124) and experienced engineers (n=4) were asked to identify factors they would take into account when designing a retaining wall system for the Mississippi River. Expert data were gathered using verbal protocol analysis, in which subjects were asked to “think aloud” as they addressed the retaining wall problem, and their statements were coded and interpreted. Novice data were gathered using a written protocol in which subjects were asked to simply list the factors on paper. Qualitative data were segmented into distinct ideas, which were then coded using a coding scheme with two dimensions of problem scoping breadth: physical location and frame of reference. We found that novices offered a greater proportion of factors from the natural and social frames of reference, versus technical and logistical frames, which indicated a rather broad approach the problem. We argue that this may reflect the novices’ relative inexperience with engineering concepts. While the four experts’ responses differed in terms of their representations through a “breadth of problem scoping” coding scheme, two of the responses echoed a characteristic top-down, breadth-first approach to design. The difference in protocols presents challenges in comparing expert and novice behavior, and methodological issues of collecting less information from a greater number of subjects versus collecting more information from fewer subjects were addressed. Because asking the experts to think aloud resulted in a rich data set, we employed narrative analysis to further investigate expert responses. The narrative analysis of expert problem scoping behavior suggested a sophisticated approach to situating problems and solutions in context. It highlighted several particular kinds of factors that the four experts in our sample were drawn to – existing engineered solutions, alternative design solutions, costs and benefits, priorities, and history. In addition, the narrative analysis illustrated the relationships between and among an expert’s ideas, and what these relationships imply for the expert designers’ thought processes.
2003
The introduction of engineering design in the first year of the curriculum has become commonplace in order to provide students with early experiences in engineering principles and exposure to realworld applications. Many different approaches to the development and implementation of these courses are used but regardless of the method or specific emphasis, students enrolled in engineering design classes are expected to be problem solvers and to communicate effectively, both verbal and written. We have adapted and integrated a problem-solving and program development methodology originally used in a computer science environment to an introductory engineering design class which helps beginning engineering students develop these important skills. We have also conducted a baseline study in this engineering design course to evaluate this methodology and its impact on students' problem-solving abilities, skills, knowledge, and attitudes in a first-year course on engineering design.
2017 ASEE Annual Conference & Exposition Proceedings
National Center For Engineering and Technology Education, 2011
The objective of this study was to describe the task interpretation of students engaged in a design activity and determine the extent to which students translate their understanding of their design task to their planning and cognitive strategies. Twenty-nine students at one Colorado high school participated in this study. Students worked individually in the Architectural Design class (n=7), and in teams in the Robotics Design class (n=22). To capture students' perceptions of their understanding of the task, planning strategies, and cognitive strategies, the Engineering Design Questionnaire (EDQ) was used. The development of the EDQ was guided by Butler and Cartier's Self-Regulated Learning (SRL) model. Besides the EDQ, a Web-based Engineering Design Notebook was developed to facilitate students reporting planning activities and engineering design strategies. Graphical views are used to present quantitative and qualitative analysis of data collected in this study. In addition, the mean scores of design phases (i.e., SRL dimensions) were compared across SRL features (i.e., task interpretation, planning strategies, and cognitive strategies). From the analysis, the findings suggest that the level of understanding of the task were high in problem definition, conceptual design, and preliminary design. In contrast, students were found to be lacking on those three design process components in the area of planning strategies. Students performed well in cognitive strategies except for problem definition.
2010
This study used Verbal Protocol Analysis (VPA) to investigate the cognitive process of 8 undergraduate engineering students during a hands-on model building design task. The present paper will focus on one aspect that emerged from this research: the paramount importance of correctly interpreting the problem. Although this may seem simplistic, correctly framing or interpreting the problem (which is distinct from identifying the problem) was a crucial and pivotal point for these students. Without it, the developmental process stalled and the design path became more haphazard. Once students were able to correctly interpret the problem, their path to a viable solution progressed much more smoothly and efficiently.
2011 Frontiers in Education Conference (FIE), 2011
This paper presents the results of design cognition studies of two groups of students: high school juniors and seniors who have taken pre-engineering courses and sophomore university students in a mechanical engineering department. Both groups carried out design sessions designing for the same design challenge. Data were collected using the protocol analysis technique through video and audio recordings of design sessions. The students' design cognition was measured by segmenting and coding the transcribed videos using the Function-Behavior-Structure (FBS) ontologically-based design issues and design processes coding scheme that provides a uniform basis for analyzing design protocols. Differences in design cognition were found and tentative explanations provided to account for them.
Journal of Engineering …, 2005
This paper is based on the premises that the purpose of engineering education is to graduate engineers who can design, and that design thinking is complex. The paper begins by briefly reviewing the history and role of design in the engineering curriculum. Several dimensions of design thinking are then detailed, explaining why design is hard to learn and harder still to teach, and outlining the research available on how well design thinking skills are learned. The currently most-favored pedagogical model for teaching design, project-based learning (PBL), is explored next, along with available assessment data on its success. Two contexts for PBL are emphasized: first-year cornerstone courses and globally dispersed PBL courses. Finally, the paper lists some of the open research questions that must be answered to identify the best pedagogical practices of improving design learning, after which it closes by making recommendations for research aimed at enhancing design learning. The capstone course is a U.S. term for design courses typically taken in the senior year. The term cornestone is a recent U.S. coinage for design or project courses taken early (e.g., first year) in the engineering curriculum. It was intended to draw a distinction from and preserve the mataphor of the capstone course. G handle uncertainty; G make decisions; G think as part of a team in a social process; and G think and communicate in the several languages of design.
Research on engineering design is a core area of concern within engineering education and a fundamental understanding of how engineering students approach and undertake design is necessary in order to develop effective design models and pedagogies. Understanding the factors related to design experiences in education and how they affect student practice can help educators as well as designers to leverage these factors as part of the design process. PURPOSE This study investigated the design practices of first-year engineering students' and their experiences with a first-year engineering course design project. The research questions that guided the investigation were: 1. From a student perspective, what design parameters or criteria are most important? 2. How does this perspective impact subsequent student design practice throughout the design process? DESIGN/METHOD The authors employed qualitative multi-case study methods (Miles & Huberman, 1994) in order to the answer the research questions. Participant teams were observed and video recorded during team design meetings in which they researched the background for the design problem, brainstormed and sketched possible solutions, as well as built prototypes and final models of their design solutions as part of a course design project. Analysis focused on explanation building (Yin, 2009) and utilized within-case and cross-case analysis (Miles & Huberman, 1994). RESULTS We found that students focused disproportionally on the functional parameter, i.e. the physical implementation of their solution, and the possible/applicable parameter, i.e. a possible and applicable solution that benefited the user, in comparison to other given parameters such as safety and innovativeness. In addition, we found that individual teams focused on the functional and possible/ applicable parameters in early design phases such as brainstorming/ ideation and sketching. When prompted to discuss these non-salient parameters (from the student perspective) in the final design report, student design teams often used a post-hoc justification to support how the final designs fit the parameters that they did not initially consider. CONCLUSIONS This study suggests is that student design teams become fixated on (and consequently prioritize) certain parameters they interpret as important because they feel these parameters were described more explicitly in terms how they were met and assessed. Students fail to consider other parameters, perceived to be less directly assessable, unless prompted to do so. Failure to consider other parameters in the early design phases subsequently affects their approach in design phases as well. Case studies examining students' study strategies within three Australian Universities illustrate similarities with some student approaches to design.
2007
Professionals in all disciplines are continually engaged in problem solving, design, and research. Because steps in these processes appear similar, many faculty conceptualize a single, universal model for all three processes. However, for students who are just learning these processes, a universal model may not be the best way to build performance skills. This work was undertaken to help novices understand unique characteristics of each process and the circumstances under which each process is most effective and efficient. This paper examines two tools that were created to build this understanding: (i) a matrix analyzing the similarities and differences among the processes and (ii) a graphical presentation highlighting key skills that are hypothesized for each process. Effectiveness of the two tools was evaluated in a freshman design course where teams of five students work on a six-week design mini-project. Data collected included notes by the instructor, observations by peer coaches who observed an activity, and written feedback provided by student teams. In the activity, teams were asked to use the tools to distinguish between problem-solving and design activities that they had performed earlier in the semester. Next, the students were asked to classify a number of simple scenarios. Finally, feedback was solicited about the greatest strengths and areas of improvement for each of the tools as well as insights gained through this class activity. Findings were validated by separate focus groups with design faculty and with students enrolled in a capstone design course. Both students and faculty envisioned the two tools to be a natural extension of project work, prompting new insights about the role of problem solving, design, and research in engineering practice.
2016 ASEE Annual Conference & Exposition Proceedings, 2000
Design is widely recognized as a keystone of engineering practice. Within the context of engineering education, design has been categorized as a type of ill-structured problem solving that is crucial for engineering students to engage with. Improving undergraduate engineering education requires a better understanding of the ways in which students experience ill-structured problems in the form of engineering design. With special attention to the experiences of first-year engineering students, prior exploratory work identified two critical thresholds that distinguished students' ways of experiencing design as less or more comprehensive: accepting ambiguity and recognizing the value of multiple perspectives. The goal of current (work-in-progress) research is to develop and pilot a self-report instrument to assess students' relation to these two thresholds at the completion of an illstructured design project within the context of undergraduate engineering education. The specific research questions addressed in this study are 1) if the piloted self-report instrument can be used to identify discrete constructs, and 2) how these constructs align with prior qualitative research findings. The objective of this study was addressed using a quantitative exploratory research design. Items for the self-report Likert-scaled instrument were designed to distinguish student experience that either accept or reject the presence of ambiguity and the value of multiple perspectives. The instrument was disseminated to a total of 214 first-year engineering students. Exploratory factor analysis was used to identify the constructs that emerge from the self-report data, and these constructs were checked for alignment with the previously identified thresholds. The results of this investigation will be used to help advance progress towards an easily administered instrument able to assist engineering educators with the identification of students in need of intervention or explicit instruction related to critical aspects of learning engineering design. The instrument could also be used to track student growth over time, and, with further development, to provide evidence for ABET student outcomes.
2016 ASEE Annual Conference & Exposition Proceedings
A critical aspect to engineering practice is the ability to design solutions to ill-structured problems. Prior research has shown that such solutions are highly effective when they are evaluated in relation to multiple design concepts. However, prior research has also shown that engineering students tend to fixate on their initial design ideas rather than base their solutions on the integration of many diverse concepts. One recently developed method to overcome the problems of fixation is 77 Design Heuristics. This method for generating design concepts comes in the form of 77 cards, each with a different cognitive prompt for generating a solution (e.g., reduce material, flatten). By using the cards, engineers and engineering students are able to expand their horizons of possible solutions to challenging design problems. Using a first-year engineering course, we integrated the 77 Design Heuristics cards to document how these students develop final concepts in relation to their initial ideas. We analyzed 12 firstyear engineering students, distributed across 3 different design teams. Our findings demonstrate key influences that did foster idea fluency (Theme 1: Influence of 77 Cards on Early Design Concepts) but also ways that students remained attached to particular concepts throughout their design process (Theme 2: Resilient Concepts after Concept Generation).
DS 60: Proceedings of DESIGN 2010, the 11th International Design Conference, Dubrovnik, Croatia, 2010
Loading Preview
Sorry, preview is currently unavailable. You can download the paper by clicking the button above.