Design Reviews.1 KGCOE Multidisciplinary Sr. Design Borkholder 2006 R I T Design Reviews Objectives of the Design Review Participants for a successful.

Slides:



Advertisements
Similar presentations
Strategy and Project Management in the Academic Setting What best practices from industry can be applied within the academic setting?
Advertisements

PROJECT TITLE Project Leader: Team: Executive Project Sponsor (As Required): Date: Month/Day/Year 110/17/2014 V1.
PROJECT TITLE Project Leader: Team: Executive Project Sponsor (As Required): Date: Month/Day/Year 110/17/2014 V1.
Designing and Developing Decision Support Systems Chapter 4.
1 SW Project Management (Planning & Tracking) Dr. Atef Z Ghalwash Faculty of Computers & Information Helwan University.
Software Modeling SWE5441 Lecture 3 Eng. Mohammed Timraz
Composite Filament Winding Machine: P09226 Shijo George Christofer Brayton Alex Sandy Tiago Santos Daniel Weimann Project Manager Electrical Engineer Chief.
[Title of meeting] [Name of sponsor] [Date] For guidance on working with PowerPoint and reformatting slides, click on Help, then Microsoft PowerPoint Help,
Project Kick-off 14-Jan-09.
MSD-I Project Review Modular Motion Tracking Sensors 1.
Project Reviews.1 KGCOE Multidisciplinary Sr. Design Borkholder 2006 R I T MSD I Project Review Objectives of the Project Review Proposed Review Structure.
Presentation By: Chris Wade, P Eng. Finally … a best practice for selecting an engineering firm.
EDGE™ Concept Level Project Plan P08210/11 – Ruggedization of a Data Recorder for a Forklift Truck Shadle Stewart ME Rick Chadwick ME.
EDGE™ A P D C Copyright © 2004 Dr. Edward Hensel P.E. and P.H. Stiebitz. All rights reserved. Technical Data Package & Team Notebook …what is it anyway?
Business Area Analysis Focus: Domain View (selected business area) Goals: –Isolate functions and procedures that allow the area to meet its goals –Define.
Design Reviews.1 KGCOE Multidisciplinary Sr. Design Borkholder 2007 R I T Design Reviews Objectives of the Design Review Participants for a successful.
Ground Scouts P09207 Project Manager: Stewart Wadsworth Faculty Guide: Dr. Sahin Starting: Ending:
Systems Engineering Management
Project Status Update P09457 – Process Improvement Project Eric MacCormack (IE) Colin Roy (IE)
EDGE™ Final Project Plan P09701 – Corning Tropel LightGage™ Metrology System Matthew Bradley (ME) Images Courtesy of Corning Tropel.
Process, Communication, and Certification Padma Venkata
Team Sponsor Defines team ’ s work boundary. Appoints team leader. Receives and reviews team reports. Reviews and critiques team recommendations. Visits.
Your High-Level Overview of the Components Provided by ESP Solutions Group Disaster Prevention and Recovery.
Planning. SDLC Planning Analysis Design Implementation.
Remedy, a BMC Software company Storyboarding the User Interface: Blueprint for an Application Shanaz Kanga | Michele Sarko Sr. UI Design Engineer | Manager,
Project Name Steering Committee Meeting Project Manager: Project Manager Name Program Manager: Program Manager Name Project Sponsor: Project Sponsor Name.
Process Engineer’s Role in Project Management Dr Abdullah Malik.
LSU 07/07/2004Communication1 Communication & Documentation Project Management Unit – Lecture 8.
Team Launch Introduction. Real projects are large and complex, and most software is created by teams Merely throwing people together does not result in.
Introduction to RUP Spring Sharif Univ. of Tech.2 Outlines What is RUP? RUP Phases –Inception –Elaboration –Construction –Transition.
Technological Design STS-118 Lunar Plant Growth Chamber Challenge © 2013 International Technology and Engineering Educators Association STEM  Center for.
Business Systems Development SDLC and introduction to the Microsoft Solutions Framework Team and Process Models.
Chapter 5: Requirement Engineering Process Omar Meqdadi SE 2730 Lecture 5 Department of Computer Science and Software Engineering University of Wisconsin-Platteville.
Project Tracking. Questions... Why should we track a project that is underway? What aspects of a project need tracking?
EARTO – working group on quality issues – 2 nd session Anneli Karttunen, Quality Manager VTT Technical Research Centre of Finland This presentation.
ITEC 275 Computer Networks – Switching, Routing, and WANs Week 12 Chapter 14 Robert D’Andrea Some slides provide by Priscilla Oppenheimer and used with.
CSZ QUANTUM LEAP – Vic Falls Peter Doona Finance Director BAT Zimbabwe.
Software Engineering Management Lecture 1 The Software Process.
Automatic Shift Controls for ATV Sponsored by: Joel Notaro Polaris Industries Advised by : Professor George Slack Project Family: Modular, Scalable, Open.
1 Project Management Introduction. 2 Chap 1 What is the impact? 1994: 16% of IT projects completed “On-Time” 2004 : 29% of IT projects “On- Time” 53%
Product Documentation Chapter 5. Required Medical Device Documentation  Business proposal  Product specification  Design specification  Software.
Efficient Meetings Cassandra Groen BSCE ‘09 MSCE ‘11 Research Engineer II Industrial Engineering South Dakota School of Mines and Technology Thursday,
Detailed Design & Component Selection. Detailed Design Phase Portion of the engineering design process where the engineering team can completely describe.
Systems Analysis and Design in a Changing World, Fourth Edition
 Project management is the organization and management of resources (i.e. people, information, tools and machines, materials, time, capital and energy)
Request for Proposal (RFP)
1 REVIEWS A Standard Form of Quality Assurance. 2 Major Alternatives for QA proof of correctness review code testing.
through Introduction  Particle Imaging Velocimetry (PIV) uses a sheet laser beam to illuminate particles that cross the sheet.  The particles.
10 Aug 2010 ECE/BENG-493 SENIOR ADVANCED DESIGN PROJECT Meeting #2.
The new EC impact assessment: what for? EUROPEAN TRADE UNION CONFEDERATION Sophie Dupressoir.
SOLUTION What kind of plan do we need? How will we know if the work is on track to be done? How quickly can we get this done? How long will this work take.
1 Project Management C13PM Session 2 Project Initiation & Definition Russell Taylor Business Department Staff Workroom
EDGE™ Concept Level Project Plan P08210/11 – Ruggedization of a Data Recorder for a Forklift Truck Shadle Stewart ME Rick Chadwick ME.
Chapter 3 : Designing a Consolidation Strategy MCITP Administrator: Microsoft SQL Server 2005 Database Server Infrastructure Design Study Guide (70-443)
© 2013 Gartner, Inc. and/or its affiliates. All rights reserved. Gartner is a registered trademark of Gartner, Inc. or its affiliates. The Value Review.
Complete Design & Gate Review. Complete Design Detailed Design Review (DDR) 1.“High and medium technical risk” areas –Design Review (Prelim-DDR): standard.
What has been accomplished at the end of MSD 1 & 2?
ITEC 275 Computer Networks – Switching, Routing, and WANs Week 12 Chapter 14 Robert D’Andrea Some slides provide by Priscilla Oppenheimer and used with.
Request for Proposal (RFP) In response to the RFP – the first step is to prepare a proposal 1. Review Customer Requirements and come up with candidate.
IS&T Project Reviews September 9, Project Review Overview Facilitative approach that actively engages a number of key project staff and senior IS&T.
Presenter: Igna Visser Date: Wednesday, 18 March 2015
Office 365 Security Assessment Workshop
Dr. Marcos Esterman Faculty Guide W. Casolara Project Leader
Chapter 10 Software Quality Assurance& Test Plan Software Testing
Eleanor Roosevelt High School
CS 325: Software Engineering
Request for Proposal (RFP)
Guidance notes for Project Manager
Preliminary Detailed Design Review: P18001
Presentation transcript:

Design Reviews.1 KGCOE Multidisciplinary Sr. Design Borkholder 2006 R I T Design 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 6-9 MSD I reviews Templates

Design Reviews.2 KGCOE Multidisciplinary Sr. Design Borkholder 2006 R I T Design 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 system solution –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 –Team coherence on design and a better product

Design Reviews.3 KGCOE Multidisciplinary Sr. Design Borkholder 2006 R I T Participants 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) Always invite all representatives. Require attendance based on stage of development and topic of review.

Design Reviews.4 KGCOE Multidisciplinary Sr. Design Borkholder 2006 R I T Logistics – Running a Successful Review Materials – distribute before the 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 –Start on time and stay on schedule (project or engineering manager) –Not a formal Presentation  Round table approach –Focus on improving the design (no personal attacks) –Individual (not design engineer) responsible for documentation –Cover everything! If run out of time… schedule more time!

Design Reviews.5 KGCOE Multidisciplinary Sr. Design Borkholder 2006 R I T Logistics – 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 completing the next design step –Add to Design History File (including copies of materials reviewed)

Design Reviews.6 KGCOE Multidisciplinary Sr. Design Borkholder 2006 R I T High Risk Feasibility Assessment Review (Weeks 6-7) Participants –All team 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 prior to the meeting

Design Reviews.7 KGCOE Multidisciplinary Sr. Design Borkholder 2006 R I T High Risk Feasibility Assessment Review (Weeks 6-7) Review Structure / Execution –1-2 hours (good planning to optimize resource time commitment) –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.8 KGCOE Multidisciplinary Sr. Design Borkholder 2006 R I T Detailed 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 multiple reviews to cover each subsystem –Clearly stated goals and objectives with list of materials to be reviewed –Highly technical, quantitative review of all aspects of 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 review

Design Reviews.9 KGCOE Multidisciplinary Sr. Design Borkholder 2006 R I T Templates Agenda template Meeting notes template Both available in Word format on EDGE  Resources  Current Downloads  Microsoft Word Files