1. Introduction
Science teaching in United States (US) K-12 schools is undergoing a change. With many states adopting the Next Generation Science Standards (NGSS) [
1], most science teachers need to teach science and engineering practices (SEP) as well as cross-cutting concepts, in addition to disciplinary core ideas and concepts [
1]. This change represents an
innovation, something that is new to science teachers [
2]. Science teachers should incorporate engineering design practices as the NGSS are implemented. Engineering design, however, differs from science inquiry practices [
3]. A working definition of
engineering design practices (EDP) has been described as “(a) defining and delimiting engineering problems; (b) designing solutions to engineering problems; and (c) optimizing the design solution” [
1] (p. A2). EDP differs from SEP in that SEP typically investigates a natural phenomenon, while EDP focuses on designing and building systems [
1]. The two share a teaching goal of hands-on practices to deepen and apply knowledge of scientific principles. In order to design and develop instruction for secondary science preservice teachers to prepare them to teach incorporating the NGSS in their science classrooms, it is important for researchers to describe what perceptions are held toward engineering. In this study, preservice teachers are students seeking teaching certification, and some have obtained previous science, technology, engineering, and mathematics (STEM) degrees. The
innovation in this study is defined as the use of the NGSS, SEP section, which asks teachers to integrate EDP with science when planning, implementing, and assessing student learning. Implementation of the NGSS establishes an external need for instruction regarding teaching engineering [
4]. An innovation may provide a need to design instruction [
5]. Instruction may provide learners logical and compelling reasons to adopt the innovation [
2]. Understanding learners, or
learner analysis, is the first step towards designing instruction to address the innovation [
5]. The participants in this study are the subject of the learner analysis and, for clarity, will be referred to as participants or secondary science preservice teachers rather than learners. The participants in this study are defined as three secondary science preservice teacher cohort groups from 2015–2017 (
n = 43).
Instruction in this study is defined as coursework, including secondary science teaching methods and professional development, that encompasses a variety of learning strategies and learner-centered activities. Secondary science teaching methods are two courses that are considered capstone courses, along with student teaching residency, before gaining teaching certification. The
learner context setting is secondary science methods courses implemented at a research university in the Rocky Mountains of the US.
Figure 1 showcases how this study fits within an instructional design innovation model.
The purpose of this study was to describe how US secondary science preservice teachers, or those about to be certified to teach middle and high school science, at one university, perceive engineering and teaching engineering within an epistemological framework of required domain components pre- and post-instruction (intervention) as well as over three cohort years. An instructional design framework was used to place this study in terms of
learner analysis and
need for instruction [
5]. This study describes perceptions, based on prior knowledge and beliefs that are refined after instruction, that are useful for designing instruction including methods courses and early in-service professional development for teachers.
1.1. Background
Like engineering, instructional design ideally begins with a problem that may be solved. In this case, the problem is how to effectively prepare secondary science preservice teachers to teach EDP. Instructional designers try to solve the problem by developing instruction to fill a gap in knowledge. One of the first steps in designing instruction is to know the audience, in other words, the characteristics of the learners within their context. Learner characteristics may be classified by similarities and differences in participants and whether those similarities and differences are stable or change over time [
5]. Values, beliefs, motivations, and interests are considered to be changing differences among participants, influenced and shaped by experiences [
5]. Perceptions toward engineering and toward teaching engineering may fit best into a changing difference, as perceptions are influenced by experience in life and in coursework. Secondary science preservice teachers craft these perceptions into a
belief about what engineering is and how it is defined. This may be considered an
epistemological belief about a disciplinary field and what knowledge that field encompasses. Their beliefs may exert some influence on how they will teach EDP.
Figure 2 displays the study situated in an instructional design problem and solution.
The EDP domain and teaching engineering may be something secondary science preservice teachers never thought they would need to teach. However, the context of engineering education can be traced back to
Science for All Americans: Project 2061, which explained the importance of a scientifically literate population able to make informed decisions based on familiarity with science and engineering practices [
6]. The NGSS formally combined science with engineering into the SEP [
1]. STEM communities are writing engineering and computer science standards in several states with implementation to follow shortly [
1]. Because of these standards, it is important for preservice science teachers to prepare to incorporate engineering instruction and raise awareness of engineering career opportunities, which can also include computer science instruction.
Research communities have debated whether to incorporate standalone engineering standards for K-12 or to integrate engineering into science standards. Prior to the NGSS, several states included EDP in their science curriculum [
7]. Some researchers proposed a framework for including standalone engineering courses that complemented a firm foundation in math and science [
8], but others proposed a framework in which engineering was integrated into existing STEM courses [
9]. Some have criticized the NGSS as only including EDP in the standards, not providing a complete picture of the engineering domain or focusing on the nature of engineering [
10]. The NGSS do not include engineering disciplinary core ideas in the standards, but rather focus on integrating EDP into SEP. Integrated STEM classes should align with the NGSS, as the SEP portion of the NGSS combines science and engineering as one integrated process [
1]. Although adoption of the NGSS and its integrated curriculum may settle the matter in some states, not all states have adopted the standards, or a variation of the standards [
11]. Researchers have recommended the integration of engineering with other STEM disciplines in teacher training, primarily because teachers “differed widely on what they considered engineering to be” and “how they implemented engineering concepts” [
12] (p. 9). One plan for science teacher preparation is to focus on the integration of engineering within existing STEM classes, especially science and technology, as opposed to planning to teach standalone engineering courses [
13]. This plan allows preservice teachers to gain familiarity with the NGSS science and engineering integration framework as they prepare to begin teaching.
Thus, professional development for in-service teachers is important and needed to teach the NGSS integration skills. Throughout the US, professional development (PD) opportunities at all teaching career levels have been offered to facilitate implementation of the NGSS (i.e., encourage adoption of the innovation) and prepare teachers to teach EDP. Although the purpose of many professional developments is the adoption of an innovation, actual behavior change—changing practices in the classroom—must occur, and this is not always the case [
14]. Professional development (PD) in teaching engineering for in-service teachers often includes instruction on fundamental content knowledge, essential pedagogical principles, and challenges for implementation [
15]. The focus on content may come at the expense of emphasizing process and at the expense of developing strategies for adopting an innovation. Interpersonal skills, pedagogical applications of engineering, and reflective discussion have historically been rare activities in engineering professional development [
15]. In recent years, however, progress has been made towards incorporating these activities [
16,
17,
18]. These activities may be incorporated into secondary science methods courses to help secondary science preservice teachers socially construct their beliefs with peer support before entering their first classroom to teach. A preemptive approach of addressing the innovation earlier, such as in secondary science methods courses, may help adoption by refining perceptions before teachers begin teaching.
1.1.1. Epistemology of Engineering Design Practices
Secondary science preservice teachers’ beliefs about engineering and teaching engineering are part of an overarching epistemological belief about knowledge and knowing about engineering as a discipline and how it relates to other disciplines. Epistemological knowledge of a domain such as engineering may encompass beliefs, perceptions, and ways of knowing to shape understanding [
19]. Domain knowledge consists of declarative, procedural, and conditional knowing [
19]. The researchers of this study asked participants to use procedural knowledge of the engineering domain to determine if a given scenario fits into an engineering domain and to explain their reasoning. Procedural knowledge is an intellectual skill learned in part through the
spread of activation such as reminding the participant of prior knowledge, prior experience, or of acquaintances [
20]. The spread of activation may cause secondary science preservice teachers to relate EDP to a science content domain with which they are more familiar.
Secondary science preservice teachers’ prior experiences and domain knowledge in other content areas may influence their epistemological beliefs and practice regarding EDP. In one study, in-service teachers who began teaching after a career in science attached importance to aspects of science that were valued at their previous careers [
21]. For example, a former lab technician prioritized precision in data collection, analysis, and interpretation during classroom activities. Ways of knowing about a knowledge domain, namely engineering, may relate to one’s domains of expertise, or major content area, but precisely how epistemological knowledge of a familiar domain influences beliefs of a less familiar domain has not been explored in detail [
19]. Data analysis, for example, is one area where prior knowledge in a science domain may affect reasoning [
22]. Content domain knowledge in a science or mathematics discipline influences how a person interprets evidence [
22]. Further research is needed to explore post-baccalaureate preservice teacher perceptions of teaching science and engineering in the classroom [
21]. The authors believe that the participants of this study, because more than half in each cohort year were post-baccalaureates, present a sample that are in keeping with the research recommendations of Antink-Meyer and Brown [
21]. Perceptions regarding data analysis represent another avenue deserving of study.
Knowledge of EDP as a domain is a prerequisite skill needed for lower, novice stages of learning before the expert (mastery) stage [
20]. In this study, demonstration of novice to expert learning may be the recognition of different facets of the EDP domain by reasoning through examples and nonexamples. One characteristic of expert, as opposed to novice, is that knowledge is “the recognition of meaningful patterns of information…organized around core concepts” [
23] (p. 36). Researchers characterize experts as having an “elaborateness of understandings” while novices may use recall to reason through a problem requiring knowledge domain [
23] (p. 41). Instruction during a college course may facilitate progress toward mastery by helping preservice teachers organize their knowledge in meaningful patterns and apply general components of engineering to specific teaching and learning scenarios they will encounter during teaching.
The path to expert knowledge, however, is full of pitfalls. There is a danger that preservice teachers may develop misconceptions about EDP and teaching engineering and bring the misconceptions into the classroom. Four misconceptions held by teachers about engineering were identified in a previous study: (a) research methods in engineering are defined by long-term implications or outcomes, (b) science and engineering is hierarchal, (c) creativity is appropriate only in the design/planning phase, and (d) an engineering process cannot be a research outcome [
24]. Because preservice teachers may not have prior coursework in engineering and may be unfamiliar with engineering, they may already hold or may develop a number of misconceptions about epistemology of engineering, such as the four previously mentioned here. In keeping with identified areas of need in the literature, Jones and Carter [
25] specifically call for research studies that address individuals’ patterns of reasoning that differ across content domains.
1.1.2. Instruments to Measure Perceptions
Advances have been made to address the knowledge gap of epistemological beliefs toward engineering. An instrument, entitled Conceptions of Teaching Engineering, was developed from the Conceptions of Teaching Science task [
26,
27]. Researchers interviewed in-service teachers and identified initial conceptions of the required components of engineering and teaching engineering [
27]. Researchers prepared a list of engineering components to include (a) applications to the real-world; (b) creating or designing a model or product; (c) experimentation and gathering data; (d) conducting background research; (e) revising or optimizing the solution; (f) confronting a challenging, multi-step problem with multiple possible solutions; (g) brainstorming; and (h) communication within the team and to a wider audience [
27]. The study explained in this article extends and builds on that work by determining if the identified engineering components replicate in a different group of participants.
Researchers have completed work exploring beliefs and conceptions that teachers hold about engineering. The Design, Engineering, and Technology (DET) instrument asks about items along many constructs, including (a) perceptions of familiarity, self-efficacy, motivation and desire to teach DET; (b) perceived importance of DET to the curriculum and barriers to teaching; (c) perceptions of a typical engineer; and (d) personal characteristics best suited for engineering [
28]. The DET instrument was administered to elementary preservice teachers pre- and post-short-course on engineering design [
29]. The preservice teachers gained a novice level of procedural knowledge [
30]. The researchers in this study did not use the DET instrument because the constructs did not specifically address perceptions of what EDP is and is not.
Teachers need to effectively communicate to their students what a career in engineering entails, and this requires that they form a comprehensive understanding of the engineering field. In a prior study, an instrument was developed to measure in-service teachers’ beliefs about students’ aptitude for a career in engineering [
31]. Although findings revealed teachers placed importance on attributes such as high GPA and advanced math skills, it was not determined what teachers thought was fundamentally required to classify activities as engineering. The recommendations to address this gap included raising awareness among teachers about what engineering is and what engineers do [
32]. The aforementioned study focused on in-service teachers; and currently preservice teachers’ views are poorly understood.
Other instruments have been developed to approach the problem from different angles. Researchers have asked elementary and middle school students to explain their perceptions of engineering and technology in an instrument containing pictures and images as well as open-ended questions about engineering and technology as defined by the participant [
33,
34]. While a comparison of perceptions from teacher and student perspectives is outside the scope of this study, it further illustrates the gap in the literature about secondary science preservice teachers’ perspectives.
This study examined the domain perceptions that participants held outside of their major focus of study. Examining secondary science preservice teachers’ beliefs about engineering partially addresses a recommendation from other researchers that future research determine “epistemological assumptions and patterns of reasoning [that] may differ for individuals across content domains” [
25] (Future Research, para. 1). On the basis of this recommendation, the authors of this study identified a gap in the literature regarding how prior knowledge, or knowledge applied from other domains, may influence secondary science preservice teachers’ beliefs and future classroom behaviors regarding engineering and teaching engineering. The participants in this study hold or are seeking degrees in science, mathematics, and education and their knowledge has been shaped by various previous knowledge, careers, and experiences.
Using the aforementioned literature gap in
patterns of reasoning, this study begins to address previous researchers’ recommendations by describing secondary science preservice teachers’ perceptions of engineering and teaching engineering, many of whom hold degrees outside of the engineering domain. To probe the
patterns of reasoning, the authors of this study administered a questionnaire to secondary science preservice teachers. The questionnaire items provided a framework for analyzing the participants’ responses and formulating the research questions. The authors of this study administered the questionnaire over a period of three years to examine how perceptions may differ over time in different cohorts. Finally, this study placed perceptions of engineering into a
need for instruction and
learner analysis portion of an overall instructional design context. The questionnaire was administered both pre- and post-methods instruction to gauge if instruction was effective in changing perceptions and is therefore needed. To address Antink-Meyer and Brown’s [
21] and Jones and Carter’s [
25] recommendations, as well as determine if the findings of a previous study would replicate [
27], the following research questions were created and examined:
How do secondary science preservice teachers describe their perceptions of engineering and teaching engineering within an epistemological framework of required domain components?
How do secondary science preservice teachers show changing understanding of engineering and teaching engineering from pre-instruction to post-instruction of secondary science methods course?
How do secondary science preservice teachers’ perceptions of engineering and teaching engineering trend over three cohort years?
3. Results
The number of yes, no, and maybe responses were remarkably consistent over three cohort years.
Figure 4,
Figure 5 and
Figure 6 display the results from the pre-tests and post-tests for each of the three years. Not only did the responses change very little from pre- to post-test, but each year contains roughly the same distribution of responses—yes was answered most frequently, then maybe, then no was answered least frequently. The yes, no, and maybe responses are also consistent with each scenario pre- and post-test over the three cohort years. In other words, no specific scenario saw an appreciable change in yes, no, or maybe responses.
Open-ended reasoning responses were quantified by number of responses using reasoning that fit into one of the components of engineering or one of two emergent themes of reasoning. Overall, creating a product/design/model was the most often-used reasoning (554 total responses). The second most often-used reasoning was challenge/multistep-problem (312 total responses). The third most often-used reasoning was that engineering needed to have application/real-world context (260 total responses). Participants sometimes cited components such as revision process (90 total responses), background research (75 total responses), and brainstorming (42 total responses) as sufficient to be labeled engineering, although often tempered by the wish or constraint that these activities needed to produce something. Participants rarely used the components experimentation (28 total responses) and communication (19 total responses).
The authors created the aggregate trend column in
Table 3 to showcase trends in responses from participants, pre- to post-test, over three cohort years. For example, the number of responses that used
application/real-world context reasoning decreased from pre- to post-test in each year in all three years of the study. If there was no consistent trend from pre- to post-test in every year, no overall trend was reported.
The results showed a shift in reasoning from the pre-test to the post-test for certain reasonings.
Creating a product/design/model increased from pre- to post-test over every cohort year and was also the reasoning with the highest total number of responses overall. Participants tended to cite
application/real-world context,
background research, and
brainstorming as components sufficient to classify the activity as engineering less often after methods course completion. However, these decreases were offset by an increase in participants using the reasoning
creating a product/design/model to solve a problem as a sufficient and necessary component of engineering.
Figure 7,
Figure 8 and
Figure 9 display the pre-test and post-test reasoning by cohort year.
Given the high number of challenge/multistep-problem reasoning, participants seemed to perceive engineering as a multistep process that involves refining a best solution or design from several possibilities or iterations. Participants were satisfied that if the scenario called for a multistep process, especially if that process involved mathematical reasoning or solving equations, then it was engineering. Participants appeared to rationalize that although planning, data collection, and background research were an integral part of EDP, those components alone were not sufficient to call the activity engineering or an example of teaching engineering.
On the other hand, several participants across cohort years indicated that, in several scenarios, data analysis alone was sufficient for the activity to be considered engineering. There was no trend from pre- to post-test and no overall trend by cohort. As many participants described it, “Yes. Students must understand and interpret graphs” or “Yes. Analysis of data”, represented a single necessary and sufficient component in terms of the scenario being classified as engineering. While some participants indicated that this step was one of many steps, others indicated that data analysis alone was considered sufficient to be classified as engineering.
Participants’ reasoning was also examined in relation to the scenario questions, and a similar pattern of response to scenario was found consistently over time. One scenario, “A 4th grade class is doing a project on dinosaurs. A group of students makes a chart that compares the sizes of the five different dinosaurs showing their metric heights and weights” (1Q3) revealed that
challenge/multistep-problem reasoning was used most often pre- to post-test in every cohort year. When participants changed their reasoning in the post-test, typically their responses changed to
creating a product/design/model, which is consistent with the overall increase of use of that reasoning.
Table 4 displays the most often-used reasoning by scenario, pre- to post-test, for each cohort year. The changes from pre- to post-test are highlighted with bar shading.
Overall, when reasoning changed, it changed to creating a product/design/model. However, this happened only in some scenarios; for example, in the debate on the pros and cons of genetically modified food (2Q8). Other scenarios gathered remarkably consistent reasoning, such as students building a compressed air rocket from a kit (2Q5) and students building a scale model of the solar system (1Q5). Participants gave consistent reasoning in scenarios that used words common in engineering, such as scale, model, and rocket.
Several participants in all three cohort years changed their reasoning in two scenarios. The two scenarios were the debate about the pros and cons of genetically modified foods (2Q8) and the math teacher who had students measure dripping water and then create a linear equation of the data (2Q9). For the genetically modified food debate, several participants in all three cohort years used creating a product/solution/model reasoning in the post-test. Reasoning included, “Not problem solving”, and “They are not designing a solution to a need or problem” which is interesting to consider that the participant did not use communication reasoning as offering a solution to a problem. For the data collection and graphing of a dripping faucet, pre-test reasoning was that the scenario was too simplistic, “No, just graphing”, while the reasoning on the post-test used phrases such as “No problem no product”.
Several participants in two of the three years changed their reasoning in three scenarios. The three scenarios included two students working on an assigned slope y-intercept problem for homework from their textbook (2Q1), a student making fudge (2Q2), and a student at home watching a TV documentary about the building of the Hoover Dam in the 1930s (2Q3). While the slope y-intercept problem remained primarily “no”, the reasoning changed from that it had no real-world application to that it did not create a product to solve a problem. The reasoning that it was too simple and did not offer a challenge/multistep-problem was used in both years. For the scenario of a student making fudge, there was an increase in reasoning that the activity could employ EDP to create or improve the product. This was in contrast to the pre-test, in which some participants viewed the activity as “cooking”. Some participants changed their reasoning about the student watching the Hoover Dam documentary scenario, but in both the pre-test and post-test, the reasoning revolved around the activity as the students “not doing anything” or “No problem and no product”.
Emergent Reasoning Themes of Secondary Science Preservice Teachers
A line of reasoning emerged during data analysis as that of the
teacher role. Two reasoning themes that emerged in this study are displayed in
Table 5. Several participants indicated that the teacher needed to emphasize the application to the real-world or guide students’ thinking, for example, “Maybe. If the instructor can relate the rollercoaster design” and “Maybe. How does the teacher encourage their kids to think about the engineering/design process?” and “Maybe. As long as the teacher doesn’t handle everything or make cookie-cutter plans”. Others reasoned that a teacher needed to actively ensure learning, such as, “Maybe. If teaching actually occurs”. Participants used the
teacher role reasoning somewhat often (31 total responses) and most often as a response to one scenario, a class trip to an amusement park (2Q9). Use of the
teacher role theme showed no overall trend over time.
Another emergent theme of reasoning was discipline-specific connections, indicated by stating a particular discipline as reasoning with little further elaboration. As with the teacher role reasoning theme, a connection to other disciplines was not considered a component of engineering but rather a theme of reasoning why a scenario was or was not engineering. Some examples were, “No. Because fudge is more chemistry based than engineering”, or “Yes. Focused in Civil Engineering”, or “physics is taught here”. This reasoning occurred moderately often compared to other responses (72 total responses) in every scenario with no strong correspondence to any scenario in particular. Use of this reasoning decreased from pre-test to post-test for every cohort year. For example, simple rationale such as, “Civil engineering” or “Bioengineering” decreased pre- to post-test and was often replaced by more descriptive reasoning, such as, “Yes. They have to make observations, measure, are creating something” for the scenario of a student making fudge.
Several participants, as rationale for their decision to categorize the activity as not engineering, claimed it “sounds more like chemistry” or “No, Cooking is hardly engineering”. This represents novice understanding, where participants viewed academic disciplines as rigid and well-defined. As mentioned previously, such reasoning was more common in the pre-tests. The participants failed to see applications of other disciplines as pertinent to engineering. Most of the time these missed applications were other STEM disciplines, although one participant indicated that the debate about the pros and cons of genetically modified foods sounded, “more agricultural and social-political”. The domain of mathematics was cited in various scenarios as rationale for considering the scenario engineering, “Maybe. If we discuss math behind this” and as rationale for considering the scenario as not engineering, “No. No math”. Although several participants wrote that mathematics was necessary component of engineering, others indicated that it was part of background research, a skill building component, or that it needed to have multiple, complex steps and/or solutions and not just “plug and chug”.
4. Discussion
This study builds on earlier work by replicating among preservice teachers many of the themes identified by in-service teachers in another study. The in-service teachers gave similar reasoning for required components of engineering or teaching engineering [
27]. In-service teachers described
Application/Real-world context,
creating a product/design/model, and
challenge/multistep-problem most often as necessary components of engineering [
27]. In this study, secondary science preservice teachers described the same three themes most often, although the exact ranking differed, most likely due to the difference in participants between that study (
n = 16) and this one (
n = 43). In light of the consistent results, the authors of this work believe that this study establishes replicability and pragmatic validity of the instrument.
The important themes of reasoning that emerged, namely
teacher role and
discipline-specific, pertain to the novice stage at which participants conceptualized engineering and teaching engineering and how those conceptions changed after instruction. This was most evident in the pre- to post-test change in
discipline-specific reasoning. If science educators ask preservice teachers to integrate SEP into science lessons, then, the preservice teachers need to recognize that science, technology, engineering, and mathematics (STEM) disciplines are not mutually exclusive, and science educators must explicitly deliver this instruction. A model of integrated STEM courses has been proposed, which aligns with the NGSS [
13]. Making explicit connections between disciplines and the integration of EDP into various science and mathematics domains may help move teachers from novice to expert levels [
23,
30]. A focus on the integration of STEM including activities such as lesson plans that encourage secondary science preservice teachers to integrate EDP into SEP may also be helpful.
Moving past a narrowly-defined concept of the boundaries of academic disciplines (or silos) is necessary if secondary science teachers aim to raise awareness of engineering careers in their students. One of the outcomes of an engineering PD for in-service teachers was fostering an awareness of engineering as a possible future career for their students [
32], and this type of explicit instruction is beneficial and necessary. If secondary science teachers plan to instill an understanding of engineering in their student populations, then, they need to recognize that engineering is integrated among many STEM disciplines and moreover, that many STEM disciplines incorporate aspects of the engineering design process into discipline-specific practices. The fact that participants decreased the use of
discipline-specific justifications as sufficient to exclude the scenario from engineering from pre- to post-test shows that participants may have recognized these cognitive contradictions and thought through how to resolve the issues [
30]. Therefore, secondary science teachers could raise awareness of engineering careers in their classrooms by incorporating a more integrated, multidisciplinary, collaborative epistemological perspective of the engineering domain.
Many secondary science preservice teachers have an emerging understanding of the role the teacher should play in learning, particularly EDP. The responses that fit the teacher role theme used third-person rather than first-person. On the basis of textural analysis of the responses, the authors think use of this reasoning indicates an emerging perception of effective teaching in a general sense, not specific to teaching engineering domain. Because no participant indicated actual classroom teaching experience, no one drew a response from previous experience. Participants’ teacher role responses may reflect emerging ideas about the role of the teacher in learning and the impact of student-centered learning. Secondary science preservice teachers’ concepts of how teachers influence learning may need authentic experience to fully crystallize.
A novice level of understanding also became apparent by the number of responses that cited an over-simplified short phrase representing the
creating a product/design/model theme as a component of engineering. This ‘product for a problem’ theme represented the most-often cited reason for categorizing the activity as engineering and was also the only theme that increased from pre-test to post-test in every cohort year. Novice knowledge does not entail the rich, multiple connections with other knowledge domains that is characteristic of expert knowledge [
30]. Moreover, novices are less able to recognize subtle but important patterns and the significance of those patterns [
23,
30]. By applying an oversimplified, easy-to-remember phrase to many scenarios, participants revealed their inexperience with nuances and considerations that each scenario brings to bear. It is noteworthy to add that the science educator might have proliferated this participant response by repeating the phrase during the science methods coursework.
During the secondary science methods course discussion of EDP, providing a definition of engineering, and planning and implementing EDP in SEP, the science educator mentioned that engineering was a solution to a problem, provided a benefit to society, or was a process leading to a product realized by creating or building something. Many secondary science preservice teachers condensed these discussion points down to soundbite-size definitions that varied by cohort year. They tended to repeat the short phrase definition for almost all of the scenarios offered in the post-test. Almost all of the phrases dealt with a product, solution, or model. For example, a few phrases were: “Solving a problem”, “Not creating anything”, “No. No problem, no product”, and “Starts with a problem, ends with a product”. This style of reasoning most likely accounts for the slight drops in other components of engineering, namely
background research,
brainstorming, and
communication, and the increase of defining engineering as
creating a product/design/model. As participants internalized a new definition, in this case classification of the engineering domain, they tended to oversimplify and overgeneralize [
23]. Hence, science educators should take caution and speak explicitly about what belongs in science and engineering practices.
Although the results represent progress in the sense that secondary science preservice teachers refined their epistemological knowledge of the EDP domain, opportunities exist for developing misconceptions. In recognizing that EDP involves creating of a model, product, or solving a problem, participants may have progressed from novice to “competent beginners” [
23] (p. 37). Yet there is a danger for misconceptions to form. As mentioned previously, researchers in a prior study identified four misconceptions about engineering: (a) that research methods are defined by long-term implications or outcomes, (b) that science and engineering is hierarchal, (c) that creativity is appropriate only in the design/planning phase, and (d) that an engineering process cannot be a research outcome [
24]. Any of those misconceptions could arise from early-career teachers simply applying the basic short phrase definition when planning future classroom curriculum.
4.1. Limitations
A limitation to this study is that although the results are compared to the themes generated in an earlier study, the methods of collecting data differed. Researchers in the earlier study collected data by verbal interview, which provided an opportunity to clarify questions, ask for clarification in responses, or ask follow-up questions [
27]. A limitation of the written questionnaire is the inability to follow-up to the participants’ responses. On the other hand, participants were free to expand on their reasoning and in fact, prompted to do so, limited only by how much they chose to write. One advantage of a written questionnaire is the reduction of interviewer bias and greater participant confidentiality. In this study, participants completed the questionnaires individually, and did not discuss their answers with their peers during questionnaire administration, which might have led to more honest answers. Participants were assured confidentiality to perhaps a greater extent than they would in-person interviews due to reaction of the interviewer, nonverbal language, prior acquaintance, etc. Participants were also assured of confidentiality because they generated a four-digit code for the pre- and post-questionnaires. They did not use their names anywhere other than the separate consent form.
This study was also limited by the learner context. Because all of the participants attended the same university and moved through the same secondary teacher education program over three years, the learner context did not appreciably differ by cohort year. While this encouraged reduction of variables, it also limited generalizability and multiple perspectives. Another limitation is that the researchers did not ask how many engineering courses participants had taken. It is not a requirement at the university where the study took place for students pursuing a secondary science education degree to take engineering courses. Other than the sole engineering major, it is unlikely that any of the participants had taken courses in engineering content.
This study used a subjectivist lens to describe individuals’ beliefs and perspectives about a knowledge domain. In light of the modest cohort size (n = 43), no practical significance from year to year, and qualitative methodology the study is not generalizable to a larger population. The overall qualitative research framework using an interpretivist, constructivism theoretical perspective does not lend itself to quantitative analysis of the yes, no, and maybe questionnaire responses [
35]. General trends were described to find practical significance [
35]. Readers might find pragmatic validity to this study by determining if the results apply to other learners in other contexts.
4.2. Recommendations
From an instructional design vantage point, this study indicates a
need for instruction. There is a clear need for this type of instruction if secondary science preservice teachers are providing novice-level reasoning as rationale for their answers to the scenario questions [
5]. For example, several participants began with narrowly defined views of discipline areas, such as civil engineering or biology. Those participants did not view engineering as multidisciplinary endeavor, or, alternatively, that other disciplines could integrate engineering. Although evidence of this reasoning decreased from pre- to post-test, it still indicates novice conceptualizations need to be explored in greater detail in early-career PD or incorporated into redesign of secondary science methods courses.
This study indicates that science educators of secondary science preservice methods courses should begin instruction from a point of novice student understanding. Standard learner analysis parameters in instructional design include prior beliefs, knowledge, and experience [
5]. With baseline information provided by this study, namely that instruction does impact beliefs about the EDP domain, effective instruction may be designed that can assist teachers adopt an innovation of integrating EDP in the classroom. Additionally, instructional efforts should be directed at preventing misconceptions, examining each component of EDP, and integrating EDP into SEP as well as with other STEM disciplines.
Examining each component of EDP should include examining the component of data analysis. Authentic science projects emphasizing how components of EDP fit together may help further participant understanding [
18]. Secondary science preservice teachers’ perception that data analysis alone is sufficient for classification as engineering presents an area for further research. Some researchers have begun to address this issue through expanded lessons focusing on data interpretation as evidence [
22]. There is a need for methods instruction that encourages secondary science preservice teachers to expand their epistemological knowledge about engineering and the role data analysis plays as one necessary, but not entirely sufficient, part of EDP.