lec03 - Lecture 3 Historical/Technical Analyses of...

Info iconThis preview shows pages 1–2. Sign up to view the full content.

View Full Document Right Arrow Icon
Lecture 3 Historical/Technical Analyses of Engineering Systems 3 different approaches to thinking about the topics of this course are things you want to ask as you read the assignments: Who’s the author? What’s his primary function? What is he writing against? Vincenti: “Design Knowledge”: what does he mean by this? - In part, he means taking specific scientific knowledge and applying it successfully - Knowledge “that” vs. knowing “how”; understanding the natural science vs. understanding the engineering process that applies the science - Normal vs. radical design Engineering Epistemology: what does this mean? - “epistemology” = theory of knowledge - what counts as knowledge in engineering? It may change at any time. For example: o “CDIO,” course 16’s motto: “conceive, design, implement, operate.” o Creation of ESD at MIT; recognition that systems-level knowledge is important. o Practical experience: in the context of Apollo, there was almost no practical experience – there had been Mercury, but not much else. Whenever we do have prior experience to draw upon, that’s great, but we must make sure not to just draw rote from the handbook; innovative ideas are also important. o
Background image of page 1

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Image of page 2
This is the end of the preview. Sign up to access the rest of the document.

This note was uploaded on 11/08/2011 for the course AERO 16.872 taught by Professor Danielhastings during the Fall '03 term at MIT.

Page1 / 3

lec03 - Lecture 3 Historical/Technical Analyses of...

This preview shows document pages 1 - 2. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online