1What is a “Concept”?A completely satisfactory solution to the problemHow many do you need?Are some better than others?How can we propose validConcepts?Only if we explain the requirements a “concept” must meetHow can we compare Concepts?Only if we explain & validate the requirements a “concept” must meetRequirements = Engr SpecsLater, how can we prove the design meets requirements?Have Measurable Engr SpecsDo analysis/tests to prove itHow do we define Engr Specs?Target ValuesIf benchmarking and customer dialog continue, does that really mean the wants, metrics, & target values change as we go?Of Course!2Feedback - ContentShow logic & assumptionsExplain “Decisions”Wants = “should” ; constraints = “must”Metrics = ways to measure “wants”Target Values = Engr SpecsIdentify, analyze all subsystemsSummarize why wants, metrics, target values chosenFeedback - FormAlways deliver your best effort Always spell-check, make user-friendly Always read out loud “Sloppy”means unreadable / READ DIRECTIONS for format Nice to have TOC with page numbers Context – what is this report for? Embed important Figs & use Fig. #’s (Flip?) Reflection – what did we learn?Phase 1 – Big PictureIssue – Rept & Presentation produce a small window for judging work done.Process How we got here Where we are now Where we are going How we get therePhase 1 - IntroBackgroundCustomers/wants – updatedBenchmarking Lessons, metrics, range of wild ideasMetrics & Target Values – How?, Why?Phase 1 – Concept SelectionAssumptions! Cantilever conservative for stress Simple supports conservative for deflectionFlow Chart of decisions?Subsystems & InteractionsCritical Metrics, Target ValuesEasy/Tough Choices & CompromisesSafety Factor/Margin SummaryPhase 1 – Audience IssuesCoherence is #1 taskGraphics (shrink sizes) Re-do sketches Intersperse figures in report body Reverse White on Black imagesSchedule – Roll up earlier sub-tasksDrawings – Need Bill of MaterialsBackups – Key to Good
View Full Document
Unlocking...