Category Archives: Uncategorized

Challenges with re-working a class into a modified problem-based learning class

We are currently working on detailed class preparation for a hands-on version of statics in which we attempt to explicitly teach the process of problem abstraction. That is, we start with physical objects and develop tractable engineering mechanics problems. Only then will we introduce theory and analysis techniques. The physical objects will be small-scale analog models of everyday objects that our students come into contact with, such as bridges, roof trusses in big-box stores, their own body, or a crane. The students will build and experiment with the models under different loading. While I am excited to teach this class in the fall of 2024, the class preparation is not easy. So, I wanted to write about some of the challenges we are facing. The main challenges are buy-in, object identification, object incorporation, and timing. 

First, a little background. The class will be taught every Tuesday and Thursday for 75 minutes each day with between 40 and 44 students. There will be a total of 27 classes over the semester. Assuming a few tests and a review day, that leaves 23 class periods to work on all the material in the syllabus. My section will be one of 6 sections and my student’s will need to learn the same material as everyone else. The class will have students majoring in civil, environmental, industrial, biosystems, and biomedical engineering. 

Buy-in

While the research team has bought into the project at an intellectual level, we are all still connected to the traditional lecture approach (motivation, theory, example, example, more theory …) to organizing an engineering class period. We all, to varying degrees, still want to put the theory first. For example, if we want to talk about 2D equilibrium at a point, then surely we need to explain that force is a vector before we can get started. The problem with this approach is that mental step is part of the abstraction process. Putting the theory first immediately limits student’s thinking. Our goal is to have them discover that force is a vector by interacting with the everyday objects they see around them. Further, the more complex the problem, the greater the temptation to put the theory first. 

Identifying objects

The main challenges with object identification are number, location, diversity, complexity, and scale. Our current thinking is that we will have time to analyze two objects per class period. That means we need to identify around 45 everyday objects that we can analyze and that allows students to learn all the material needed in the class. To create an additional challenge, we plan to publish all our class materials online so we would prefer to use objects that we have taken photos of ourselves to avoid any copyright infringement issues. This means that the objects need to be local to Clemson, South Carolina, or other locations the research team travels to. While there are a lot of objects to find, it can be a challenge to find a broad enough range to cover all the topics in the class. To overcome both the volume and location challenge we ran a survey in a dynamics class prompting students to suggest objects they might like to analyze. We used dynamics as all the students would have completed statics. Students were asked to upload a photo of an object and then pose a question about it that could be answered using the knowledge and skills they learned in statics. While this provided several ideas for objects, the related questions were often too vague for direct use. We will be using a similar approach during the trial classes but with more detail on expectations. 

Diversity and complexity are also a major challenge. While we currently have over 100 objects that we have collected photos of, we will likely need more to complete the entire course. Our diversity goal is to find a broad set of objects that are relevant to all the different majors represented in our classroom. For example, we want to include biomechanics problems for the biomedical engineers, workstation objects for the industrial engineers, and maybe an irrigation system for the biosystems engineers. In addition, we need to find objects with an appropriate range of complexity. For example, when we discuss trusses, we can’t only analyze big-box store roof trusses. At the same time, analyzing the forces in a three-dimensional crane truss is likely too complex for a first class in statics.

Finally, we want our students to understand the real-world scale of these objects. That is, we want them to have a feel for the actual loads that might be applied to an object, and to have a physical context for different weights and forces. These insights could get lost in the process of working with small-scale models. To address this problem, we are developing a graphical scale dictionary. The dictionary contains photographs of familiar objects, such as a gallon of milk or a minivan, and their approximate size and weight. We currently have objects ranging in weight from 0.5 lbs. to 80,000 lbs.

Incorporating objects

Having identified a particular object for a particular topic, we then have to incorporate it into the lesson plan. This requires several steps. The simplest step is to develop a physical model that students can play with. We have been doing that with Knex systems, Erector sets, weights, pulleys, cables, and spring balances. We are also building some wooden 3-sided 2-foot cubes for mounting the models on (see figure 1.) We expect to have students work in teams of four so we will need 10-11 of everything. As we build the models, we need to make sure that they are manipulable so that students can explore their behavior and not simply look at them. Figure 2 shows an example of a physical object (leg extension machine) and the analog model we could use in class to understand how the system behaves. 

Figure 1. Image of the three sided cube to be used for building analog models for class.
Figure 2. From left to right: image of a leg extension machine, the machine being used, and an analog model with two different loadings on the leg with resulting change in angle.

The greater challenge is working out how to introduce the objects and guide a conversation with the students about how to analyze the object. We do not want to ask questions like, “What is the reaction at the pin support?” as that is too specific and bypasses much of the abstraction process. Instead, we may want to ask, “What keeps it from falling over?” When students are experimenting with an object, it will be important to focus their observations on certain questions such as, “What happens to the tension in the cable when you change its angle?” However, this is a delicate balance. We want students to explore on their own terms but we also want to guide them toward questions that allow the instructor to introduce the theory that they need to solve the problem. This is an ongoing struggle, and we will likely not get it right before the first time teaching the class. 

Class timing

Each class period will be 75 minutes long and will include time for a mental break toward the middle of that period. We have many goals for this class period including having student groups report out their results from homework problems, working through abstraction and analysis of objects, presentation of theory, introduction of the next set of homework problems, and an exit activity.

Our current plan is to have the student groups do three homework problems before each class. They will then report out their solutions to the other students at the start of the class period. We will do this in a range of ways including having them all write out their solution to one of the problems on a board and then have them explain it to another group, have them present at the front of the classroom, or some other variation.

Next, we will work on the objects of the day. This will include showing a range of objects that relate to the topic of the day and then focusing on one for modeling. We will then guide a discussion of what we might want to know about the object and what they can apply that they already know. This could include experimenting with the small-scale analog models of the object. The conversation will be guided toward a particular set of problems with flexibility to allow students to propose their own problems. Then, and only then, will we introduce any theory. This will be kept to an absolute minimum to enable the students to solve the problem at hand. The students will then solve a problem related to the object. We hope to work through two objects per class.

Finally, we will introduce the homework problems due at the start of the next class and conduct some sort of exit activity such as a muddiest point question or having them sketch a free body diagram for one of the homework problems.

The timing challenge is that we want to provide students with the opportunity to explore during the discussion of objects and while experimenting with the analog models. However, we also must get through the technical content of the syllabus. This will require a lot of flexibility from one class to the next and experimenting with timing over the course of the semester. We will be tracking the timing in each class, with the help of graduate student assistants, so that we can reorganize the material for future semesters.

Abstracting mechanics problems is a problem in itself.

Statics is a foundational class in civil and mechanical engineering. Students learn about forces, moments, and static equilibrium. They learn skills, such as drawing free body diagrams, that they will continue to use throughout their coursework. However, statics classes often have high failure rates and, unfortunately, is sometimes seen by students (and used by faculty) as a weed out class.  

Statics is also one of the first classes in which students learn how to model physical systems from the world around them. The problems move from theoretical to practical, or at least that is the goal. However, a quick perusal of the most popular statics textbooks tells a slightly different story. Textbooks tend to introduce theory first, before they even get to a problem. Students learn about forces, vectors, vector multiplication, components, and notation and then are presented with abstracted problems. This is not to say that the problems are not practical or that they are not “real world problems.” Rather, I mean that the problems have already been simplified (reduced to a 2-dimensional drawing) and fully defined (lots of clearly defined parameter values). Therefore, students do not need to make a direct connection between the physical problem and the engineering mechanics problem that they end up solving.[1]

The net effect of this is that students sometimes leave engineering because they struggle in one of the first classes where they get to apply engineering problem solving skills to real world practical problems.


Project goals

Our research team, with the support of an NSF RIEF grant seek to change the way we teach statics to include the missing first step of taking a real-world problem and abstracting it to a tractable engineering mechanics problem. We will start with small-scale physical models of actual engineered structures and guide students through the process of abstracting the physical model into an engineering mechanics problem. Only then will we introduce the mathematical tools needed to solve the problem. By explicitly teaching students how to abstract the physical world, we hypothesize that (1) students will develop greater confidence in their ability to solve statice problems (increased self-efficacy) and (2) will have a stronger connection between the class material and their future career as professional engineers. In turn, this will increase their enthusiasm to learn the material (future oriented motivation.)

Example abstraction problem

Figure 1. Image of multiple traffic lights suspended from a cable.

To illustrate this point, we might have a class in which students are asked how strong the cables need to be to support a local traffic light. We will then lead a discussion about what the question means and what more we need to know. Some questions students might have could include:

  1. What do we mean by “how strong”?
  2. How heavy is a typical traffic light?
  3. How many traffic lights are on the cable?
  4. How long is the cable?
  5. How is the cable held in place?

After this point students will start to engage with a physical model on their desks. The model will be designed to capture the key features of the traffic light problem (a weight supported by a cable). The model will be designed so that students can experiment with different weights and different locations for the model light. We will use the model to help students understand that forces have both magnitude and direction and that both need to be accounted for when solving for the forces in the cable. Finally, we will have students develop a model (free body diagram) of the problem, solve it, and then compare their results with their measured values of the tension.

Future plans

The research team will be developing this course over the next 8 months and, in parallel, will develop and deploy surveys and interviews to assess if this new approach increases student’s self-efficacy and future-oriented motivation. We will continue to post updates on this project every few months.

[1] In defense of textbooks, I do not mean to suggest that textbooks do a bad job. Authors and publishers are constantly improving with more focus on problem solving skills, detailed worked examples, providing students with formative self-assessment opportunities, and an array of online tools that support learning. I just point out that, the very nature of textbooks, is that they are abstract.