SlideServe
Télécharger Obtenir Pro
Menu
Accueil Pro
Préférences
ApparenceLight Aide et commentaires
© SlideServe · v2026

ECE/BENG-493 Senior Advanced Design Project Meeting #2 Overview

lucie avatar
lucie
9 diapositives · 228 Views · Jul 14, 2014

This document outlines the key points from the second meeting of the ECE/BENG-493 Senior Advanced Design Project class held on August 10, 2010. It addresses team progress, potential delays, and group work issues. The importance of maintaining a 50% completion mark to avoid project delays is emphasized. It highlights the schedule of class meetings, in-progress presentations, and final report preparations, along with guidelines for effective presentations and documentation. The goals include informing faculty on project progress and receiving valuable feedback.

ECE/BENG-493 Senior Advanced Design Project Meeting #2 Overview - slide 1
01 / 9ECE/BENG-493 Senior Advanced Design Project Meeting #2 Overview
1 / 17

Télécharger la présentation

ECE/BENG-493 Senior Advanced Design Project Meeting #2 Overview
Une image / un lien ci-dessous est fourni (tel quel) pour télécharger la présentation

Politique de téléchargement : le contenu du site vous est fourni TEL QUEL pour votre information et votre usage personnel ; il ne peut être vendu, concédé sous licence ni partagé sur d’autres sites sans l’accord de son auteur.Le contenu vous est fourni TEL QUEL, pour votre information et votre usage personnel uniquement. Téléchargez la présentation en cliquant sur ce lien. Lors du téléchargement, si vous ne parvenez pas à télécharger une présentation, l’éditeur a peut-être supprimé le fichier de son serveur.Pendant le téléchargement, si vous ne parvenez pas à obtenir une présentation, le fichier a peut-être été supprimé par l’éditeur.

F I N

Plus de contenu associé

Transcription de la présentation

  1. ECE/BENG-493 SENIOR ADVANCED DESIGN PROJECT Meeting #2 10 Aug 2010

  2. ECE-493 Meeting#2 Q1: How many teams are on schedule? Q2: Which teams suffer delays? Q3: Which teams have ‘group work’ issues?

  3. Is Your Work 50% Complete?If not then your project is already delayed – HURRY UP!!! ACTIVITY TIME MILESTONE Week 1  Class meeting #1 Week 2 Week 3 Week 4 Week 5 Week 6  Class meeting #2 Week 7 Week 8 Week 9 Week 10  In-Progress Presentation Week 11 Week 12  Class meeting #3 Week 13 Week 14  Final Report and Oral Presentation Week 15 Project Poster Due • End of prototyping • Full scale implementation • Testing • Final Reporting • Preparation for • final presentation

  4. In-Progress Review • You have to give an In-Progress Presentation • A formal presentation given to your FS and an additional ECE faculty • Hardcopy of presentation slides is your Progress Report #2 • The goals are: • To inform faculty about project progress • To inform faculty about ongoing testing • To highlight all trouble areas and issues • To receive valuable feedback from faculty • Allocate minimum 1 hour for the review • Presentation should take about 30 min • Remaining 30 min should be allocated to discussion

  5. In-Progress Review Slides • Cover page • Short introduction • Level-1 and Level-2 system architecture • Task-by-task discussion of the progress • Summary of achievements in comparison with the original schedule • Demo(s) of system integration effort, implemented modules, etc. • Report from early experimentation • Funds spent and man-hours worked • Problems/surprises you encountered • Action plan for remaining four weeks

  6. Final Report Preparation • Your report is a formal document representing you !!! • Don’t forget about nice printout, cover, etc. • Included drawings must be nice, clean and readable • Include a CD with a hard copy of your report. CD content must include: • MS Word file of your final report • PPT file of your final oral presentation • Any movies from experimentation stages and the final demos • Pictures from work in-progress and final demo • Any marketing materials the ECE Dept. can use to promote your work – you should plan to develop such marketing materials • You have to include all details of your work in the report – therefore it can be a large one • Follow the distribution list

  7. Final Report Format • Cover page • Executive summary (1 page) • Table of Contents • Approach (2-5 pages) • Describe the origin of the project, solution to the problem, alternative designs, and contributions of each of the team members • Technical section (as needed) • Follow top-down design approach • Show system models • Describe each element of the system • Include detail drawings, schematics, pictures, etc.

  8. Experimentation (as needed) • Discuss each experiment properly • Present collected data in the right format • Pictures from the experimentation, etc. • Experiment validation using evaluation criteria (1-2 pages) • Provide a proof you succeeded • Show processed experimental data used to derive your conclusions • Refer to requirements analysis to make final conclusions • Other issues – see point 13 of the course pamphlet (minimum 2 pages) • Very important !

  9. Administrative part (2-4 pages) • Discuss project progress • Did you completed all tasks successfully? • Did you have to change the design, tasks, schedule? What were the changes and why? • Any extra (not-planned) activities you had to carry out? • Funds spent + discussion • Man-hours devoted to the project + discussion • Lessons learned (minimum 1 page) • Additional knowledge and skills learned • Teaming experience • References • Literature references • Web URLs, etc. • Appendix A: Proposal (ECE-492) • Appendix B: Design Document (ECE-492)