Design Reviews.1KGCOE Multidisciplinary Sr. Design Borkholder 2007R•I•TDesign Reviews•Objectives of the Design Review•Participants for a successful Design Review•Logistics–Materials for review–Optimized review structure (time)–Running the review–Actions /Issues /Decisions–Documentation•Weeks 5-9 MSD I reviews (distributed to accomplish goals)•TemplatesDesign Reviews.2KGCOE Multidisciplinary Sr. Design Borkholder 2007R•I•TDesign Review Objectives•Design reviews take significant time… why do them?•Key Objectives:–Technical review of system and /or sub-systems to confirm meet Functionality, Robustness, Engineering Specifications and Customer Needs–Cross-disciplinary review to ensure optimized systemsolution–Documentation to comply with Product Development Process and support Design History File•Result:–Catch mistakes at the design stage–Save money on debug, iterations, expedite fees–Product meets specifications and customer needs–Teamcoherence on design and a betterproductDesign Reviews.3KGCOE Multidisciplinary Sr. Design Borkholder 2007R•I•TParticipants for a Successful Review•Who should be included in design reviews and does it depend on the stage of development?•Disciplines to consider:–Electrical Engineering–Mechanical Engineering–Software /Computer Engineering–Manufacturing–Marketing (represents Customer)–Regulatory /Quality–Project management–Other departments (e.g. molecular biologists)•Alwaysinvite all representatives. Requireattendance based on stage of development and topic of review. Teamownsthis!Design Reviews.4KGCOE Multidisciplinary Sr. Design Borkholder 2007R•I•TLogistics –Running a Successful Review•Materials –distribute beforethe review–Relevant Specifications–Detailed design drawings, schematics, simulations, flow charts, test plans, etc.–Known issues, discrepancies with specifications, conflicts with other disciplines–Agenda with timeline by discipline•Structure –review by discipline and subsystem•Running the Review -may be held on different dates–Start on time and stay on schedule (project or engineering manager)–Nota formal Presentation Round table approach–Focus on improving the design (no personal attacks)–Individual (notdesign engineer) responsible for documentation–Cover everything! If run out of time… schedule more time!Design Reviews.5KGCOE Multidisciplinary Sr. Design Borkholder 2007R•I•TLogistics –Running a Successful Review•Actions /Issues /Decisions fully documented–Action items for changes, items to check, functionality changes, etc.–Issues for specification and discipline conflicts that need to be escalated, or longer term changes not implemented this Rev. –Decisions about design approach, specification changes, trade-offs, etc.•Documentation–Meeting minutes including attendance, reference to materials covered, reference to actions /issues /decisions list (if not integrated)–Need documented closure on all actions before completingthe next design step–Add to Design History File (including copies of materials reviewed)Design Reviews.6KGCOE Multidisciplinary Sr. Design Borkholder 2007R•I•TConcept Design Review (Weeks 5-7)•Concept review /update•System level architecture•Identification of high risk areas of design with focus on technology•Modeling /simulations /breadboard results demonstratingrisk mitigationfor high risk areas of design•Guide-specific requirementsDesign Reviews.7KGCOE Multidisciplinary Sr. Design Borkholder 2007R•I•TConcept Design Review(Weeks 5-7)•Participants–All appropriateteam members–Guide plus Faculty /Staff consultants (team responsibility to invite)–Team members from related projects within track–Students with relevant technical expertise–Balance group size with required participation•Materials–Hardcopy of agenda, all drawings, schematics, specs, modeling and simulation results, etc.–All materials on laptop–Physical prototypes if available–All materials distributed priorto the meetingDesign Reviews.8KGCOE Multidisciplinary Sr. Design Borkholder 2007R•I•TConcept Design Review (Weeks 5-7)•Review Structure /Execution–1-2 hours (good planning to optimize resource time commitment)–Can break into multiple reviews distributed over days /weeks–Clearly stated goals and objectives with list of materials to be reviewed–Be prepared to articulate risks and mitigations based on proof of concept prototype activities (linked to specifications)–Highly technical review be quantitative!!–Project manager (or other designate) runs review•Documentation–Meeting notes required with Actions /Issues /Decisions (use template)–Project manager (or other designate) responsible–All materials and notes to Design History File•Schedule another review if required!!Design Reviews.9KGCOE Multidisciplinary Sr. Design Borkholder 2007R•I•TDetailed Design Review (Weeks 8-9)•Participants: Same as previous review•Materials: Same as previous review plus BOM•Review Structure /Execution–2+ hours (good planning to optimize resource time commitment)–Likely need multiplereviews to cover all subsystems distribute–Clearly stated goals and objectives with list of materials to be reviewed–Highly technical, quantitative review of all aspectsof design–Be prepared to articulate detailed analysis of designs–Review of specifications (line-by-line) to ensure design adequacy–Review of BOM against budget and schedule–Project manager (or other designate) runs review•Documentation: Same as previous reviewDesign Reviews.10KGCOE Multidisciplinary Sr. Design Borkholder 2007R•I•TTemplates•Agenda template•Meeting notes template•Both available in Word format on EDGE Resources Current Downloads Microsoft Word Files