|
|
|||||||||||||||||||||||||||||||||
|
|
|||||||||||||||||||||||||||||||||
|
|
I was teaching a Strength of Materials class and the textbook I was using provided a software package that was not user friendly: it wasn't very interactive, it didn't address all the parameters in a problem, and the program often halted because it had errors in it. So I looked around and a colleague of mine recommended MDSolids®--some faculty had been using it for the past couple of years, and fortunately the software was loaded on our machines in the PC labs.
The University of Dayton is a private Catholic university that enrolls 10,000 students, and 1,200 of those are in the College of Engineering. Both the administration and the faculty here are very encouraging and the culture is very positive in terms of technology use.
If there isn't an appropriate software program available for a specific course, then I ask the students to write simple spreadsheet templates, programming different equations or different concepts so they can then implement these "What if?" scenarios.
In all my courses, in addition to integrating the learning technology, I have the students do a major project. For Strength of Materials, I assigned a semester-long project in which they were to investigate as a group a major collapse or a previous disaster, such as the space shuttle or a bridge collapse, and look at it from different perspectives: why the structure failed, what were the shortcomings, and were there any unethical practices involved? That's how you learn, from the previous failures. It was a semester-long project, and they had to draft a report and make an oral presentation. One of the comments the students made about this project was that they wished we had done the project early on in the semester, so they could study harder! They found out that just making a small error could cause a big disaster. They realized they have to study harder and be much more conscientious of the work they do.
The students worked in groups of four or five; one person would be the group leader, responsible for getting everybody together and communicating directly with me. I would e-mail them memos and guide them through the project. We would meet occasionally, once a week or so, to discuss their progress and they would make a dry-run presentation to me and then they would prepare either a PowerPoint® or some sort of slide presentation to the class of what they had learned in the project. They had to make sure the presentation related to the things they had learned in the course and link the course to the real world situation.
The other course in which I've used learning technology is Statics, for which I had to use another software (see below). In Statics, I asked them to design a bridge, to build the bridge, to prepare a technical report of their work, and then make an oral presentation. My colleagues said, "There's no way you can even get through half of this," but I pulled it off and the students just loved it. These kinds of things put the course in perspective and relate it to real-life situations.
The topics covered by the routines include: beams, trusses, columns, flexure, statically indeterminate structures, and Mohr's circle analysis, including stress and strain transformations, and more. The software groups the routines into modules very much like textbook chapters, and the modules are very conducive to interactive. The software is available for downloading from the Web, and now it's also offered in place of the previous software with the latest edition of that textbook I mentioned: Mechanics of Materials, 2nd Edition, by Roy R. Craig, Jr. (Wiley).
Visual Mechanics: For the Statics course I taught, MDSolids® didn't apply, so I used Visual Mechanics, which is a CD-ROM that can be ordered to accompany Engineering Mechanics Statics, 8th edition, by R.C. Hibbler (Prentice Hall, 1998). This software was not as versatile as MDSolids® it offered a group of example problems that already existed in the textbook. But I also assigned "What if?" scenarios for this course--what if you change the parameters within those example problems, what would be the end result? I would assign those problems occasionally, and I would ask them to write a couple of paragraphs discussing what they had learned from changing those parameters.
I would recommend to faculty that they try it out--there's nothing to lose. Try it with a couple of different problems and get feedback form the students to find out how it's panning out. Normally, I don't wait until the end of the semester to get feedback or evaluations. I will give an evaluation within two to three weeks of the beginning of the semester, to see how things are progressing. Then I know where I stand.
I've strongly recommended MDSolids® to several of my colleagues. I told them that we benefited quite a bit from this software, and that I would even be glad to sit down and show them how it is working and how it operates. Some have come round when they see how the students' attitudes have changed. Still, several have been hesitant in using it. They think they don't have enough time within a course, that they'll be lucky to cover the essential materials. I respond by saying that when I see the students get excited about something, when they see the benefits, when they sit down and interact with the software, then I think it is not a waste of time.
If you have any questions, you can contact me at: mzoghi@engr.udayton.edu
|
||||||||||||||||||||||||||||
Search || Who We Are || Site Map || Meet the CL-1 Team || WebMaster || Copyright || Download
College Level One (CL-1) Home || Collaborative Learning || FLAG || Learning Through Technology || NISE