General Engineering Introduction/Presentations/quiz

 {Engineering presentations are important because they + sharpen engineering documentation - help fundraising - figure out what is important - minimize engineering documentation
 * type=""}

{Engineering presentation goals are + planting questions + inviting participation + getting help - explaining details
 * type="[]"}

{Engineering is like art in that + Is evaluated in class through presentations + Is shown to the public + Is juried by customers + Should be able to show off at any time
 * type="[]"}

{Engineers should be able to present at any time because + they are documenting continuously + projects are never "finished" - stuff never works - practice makes perfect
 * type="[]"}

{Valid reasons for not presenting at any time: - not working - not finished + have done nothing since last presentation - haven't documented anything
 * type="[]"}

{During an engineering presentation do the following - snow with details - educate audience with tutorial + start conversations + shrink detail so that those interested will ask questions + plan answers to anticipated questions
 * type="[]"}

{Engineering presentations are best started by - review + problem description - problem/solution pairs - requirements
 * type=""}

{A status update presentation has what objectives? + reassure the client, principal investigator or instructor + renegotiate the problem statement - educate the client - ask client open ended questions
 * type="[]"}

{The purpose of a design review is: + present design details + solicit concerns from other engineers - expose details to the public + prevent death, loss of money, equipment failure
 * type="[]"}

{What is a poster session? - something to academia + a small booth at a tradeshow or a physical poster at college + chance to talk to potential customers and clients - where engineering students plaster hallways with engineering posters
 * type="[]"}