On p. 90 Petroski says, " Before the fact one must not only define the design "puzzle" but also verify one's "solution" by checking all the possible ways it can fail." If you are designing something new, how do you go about doing this?
Petroski goes on to say, on p. 105, that "success does not prove the hypothesis to be valid". So, even if you are looking at other similar designs, you can't know if they are truly successful or they just haven't failed yet! How do you move forward with a new idea?
Whether you are designing a structure, a new medical device or software, it must be an incredibly daunting task, in many ways. I would love to know more ( and I know my students would as well) how you go about this.
Directions for Book Blogging
Welcome to our summer book blog! Unlike most blogs that have one blogger- everyone gets to blog about the book, To Engineer is Human, and share ideas about K-12 engineering education and the "human side" of engineering. To reply to a post, click on Comments at the bottom of the post. To start a new post, click on New Post at the top right. However, to start a new post you have to have a Google account. If you don't want to register on Google, you can send me the text for your post and a title, and I will post it for you.
Who do we have on the blog? Our book blog consists of 16 high school teachers, 1 middle school teacher, 7 elementary teachers, 4 faculty or engineering students from the University of Maine, 3 MMSA staff, and 2 DOE staff. We have a diverse and well-rounded book group which should lead to some interesting conversations. One thing to remember- the most recent post is always at the top of the blog. If you haven't been on for awhile, scroll down and work backwards.
If you start a new post you also have the option of adding photos or other graphics as well as making a hyperlink. Play around with it a bit to get to know how it works. Try a test post- you can always delete it afterwards. Also, you will notice we will build a collection of links listed on the right. Since only the person (Page) with the Google account can add these, if you have any you would like to share, just send them to me at pagekeeley@gmail.com and I will post them for you. This is the first time we have ever tried this as a blog, so we're all getting our feet wet. Don't hesitate to wade right in!
Who do we have on the blog? Our book blog consists of 16 high school teachers, 1 middle school teacher, 7 elementary teachers, 4 faculty or engineering students from the University of Maine, 3 MMSA staff, and 2 DOE staff. We have a diverse and well-rounded book group which should lead to some interesting conversations. One thing to remember- the most recent post is always at the top of the blog. If you haven't been on for awhile, scroll down and work backwards.
If you start a new post you also have the option of adding photos or other graphics as well as making a hyperlink. Play around with it a bit to get to know how it works. Try a test post- you can always delete it afterwards. Also, you will notice we will build a collection of links listed on the right. Since only the person (Page) with the Google account can add these, if you have any you would like to share, just send them to me at pagekeeley@gmail.com and I will post them for you. This is the first time we have ever tried this as a blog, so we're all getting our feet wet. Don't hesitate to wade right in!
This is a monster of a toughy! Typically, the more important a/or innovative the design, the more important this step is. Often, independent reviewers are brought in. Sometimes, two separate designs are performed and compared. Almost always an engineer will look to other engineers with different backgrounds to brainstorm for flaws. Generally we focus our energy on looking for the problems. Sometimes this comes across as us being negative or pessimistic, but I think most engineers are looking for the potential problems in order to find a solution, and to avoid a failure, not because of negative view on the world. It is foremost a habit or state of mind that needs to be developed through practice. Think about how something will be used, analyze the consequences of that use. Think about how it may be mis-used, analyze again. Think about the more common general issues that lead to failure - heat/cold, moisture/dryness, fatigue, accidental or intentional overload - and see what affects these may have. I have a friend whose job is trying to make some design engineering software crash or spit out wrong answers - he has to think of all the things that an owner of the software might possibly do. In the end, after all the checks and thinking, there is still some risk, and I think all engineers are aware of it, and we push it to the side so that we can carry on. Many professions require this, from athletics to medicine to the military, mining, construction, fishing, etc. One nice parallel can be found in legislators - it is very difficult to foresee how a given law might be mis-used or reinterpreted, but laws must be written.
ReplyDelete