{"id":2852,"global_id":"projects.mae.uci.edu?id=2852","global_id_lineage":["projects.mae.uci.edu?id=2852"],"author":"1","status":"publish","date":"2016-09-05 21:59:43","date_utc":"2016-09-06 04:59:43","modified":"2016-11-30 09:37:26","modified_utc":"2016-11-30 17:37:26","url":"http:\/\/projects.mae.uci.edu\/event\/fall-design-review\/","rest_url":"http:\/\/projects.mae.uci.edu\/wp-json\/tribe\/events\/v1\/events\/2852","title":"Fall Design Review","description":"
The Fall Design Review is scheduled for Friday, December 2 from 12:00-3:00pm. It is a great opportunity to showcase and receive feedback for your projects from industry professionals, alumni, students, and faculty. The poster display will be in the Engineering Gateway Plaza and will allow for direct interaction with our reviewers for detailed questions and advice. <\/p>\n<\/div>
Frequently Asked Questions (FAQs)<\/strong><\/p>\n<\/div> <\/td>\n Also, please review the Fall Design Review Poster Presentation Guidelines (click here<\/a>).<\/div><\/div><\/div>\n\n
\n Project Definition<\/strong><\/td>\n Exemplary 4<\/strong><\/td>\n Proficient 3<\/strong><\/td>\n Apprentice 2<\/strong><\/td>\n Novice 1<\/strong><\/td>\n<\/tr>\n \n 1. Background<\/td>\n Detailed background, previous work, prerequisites, and motivation were highlighted to show project significance.<\/td>\n Project background, previous work, and motivation were discussed.<\/td>\n Incomplete discussion of the background and motivation.<\/td>\n Background and motivation were not discussed.<\/td>\n<\/tr>\n \n 2. Goal and Objectives<\/td>\n Well-defined goal. In-depth objectives are aligned to achieve goal.<\/td>\n Defined goal with objectives to support it.<\/p>\n Weak goal with incomplete objectives.<\/td>\n Inconsistent goal and objectives.<\/td>\n<\/tr>\n \n Project Management<\/strong><\/td>\n <\/td>\n <\/td>\n <\/td>\n <\/td>\n<\/tr>\n \n 3. Organization<\/td>\n Functional responsibilities of all project members are aligned to a work breakdown structure.<\/td>\n Functional responsibilities of each member are clear.<\/td>\n Functional responsibilities of some members are not clear.<\/td>\n No functional responsibilities were identified.<\/td>\n<\/tr>\n \n 4. Timeline<\/td>\n Detailed timeline consistent with work breakdown structure showing, milestones, deadlines, and deliverables.<\/td>\n Timeline shown with milestones, deadlines, and deliverables.<\/td>\n Timeline is too general or unclear.<\/td>\n No timeline presented.<\/td>\n<\/tr>\n \n 5. Progress<\/td>\n Excellent progress. Task management is clearly shown. Team members are actively working on tasks and delivering results to ensure project success.<\/td>\n Good progress. Evidence of task management albeit with less structure.<\/td>\n Some progress. The team can benefit from task management.<\/td>\n Little progress shown.<\/td>\n<\/tr>\n \n Technical Approach<\/strong><\/td>\n <\/td>\n <\/td>\n <\/td>\n <\/td>\n<\/tr>\n \n 6. Design Requirements<\/td>\n Clear and concrete evidence of ability to understand the design requirements, understand the limitations, analyze different alternatives, and provide a feasible design.<\/td>\n Technical approach shows that the design requirements were understood.<\/td>\n Mismatch between design requirements and technical approach.<\/td>\n Did not understand the design requirements.<\/td>\n<\/tr>\n \n 7. The Bigger Picture<\/td>\n In-depth discussion of the business, competitive, economic, environmental, social, scientific, and\/or academic impact and significance.<\/td>\n Identified the connection between the project and a greater significance.<\/td>\n Connection of the project to a greater significance is weak.<\/td>\n Unable to connect project to a greater significance.<\/td>\n<\/tr>\n \n Realistic Constraints<\/strong><\/td>\n \u00a0<\/strong><\/td>\n \u00a0<\/strong><\/td>\n \u00a0<\/strong><\/td>\n \u00a0<\/strong><\/td>\n<\/tr>\n \n 8. Budget<\/td>\n Detailed budget that is well thought out.<\/td>\n Budget presented and is complete.<\/td>\n Budget presented but is questionable.<\/td>\n No budget presented.<\/td>\n<\/tr>\n \n 9. Feasibility<\/td>\n Objective(s), scope, and approach are feasible and can be completed in agreed time frame.<\/td>\n Objective(s), scope, and approach seem feasible, but may take longer than originally projected.<\/td>\n Objective(s), scope, and approach need to be reworked.<\/td>\n Objective(s), scope, and approach are not feasible.<\/td>\n<\/tr>\n \n Presentation<\/strong><\/td>\n <\/td>\n <\/td>\n <\/td>\n <\/td>\n<\/tr>\n \n 10. Visual Communication<\/td>\n Excellent, relevant, compelling visual aids depicting the project and\/or the elements of the project.<\/td>\n Clear visual aids depicting the project and\/or the elements of the project.<\/td>\n The visual aids are unclear.<\/td>\n The visual aids were not useful.<\/td>\n<\/tr>\n \n 11. Delivery<\/td>\n Clear, polished, confident.<\/td>\n Understandable and comfortable.<\/td>\n Understandable yet tentative.<\/td>\n Delivery detracts.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div><\/div><\/div>