1. 10 Aug 2010 ECE/BENG-492 SENIOR ADVANCED DESIGN PROJECT Meeting #6

2. ECE-492 Meeting#6 Q1: Any questions about Design Document, its format and delivery? Q2: Teams – show your state diagrams

3. Design Review The goals are: –To present your Level-2 design –To highlight all trouble areas and issues –To demonstrate your ongoing early prototyping effort –To receive valuable feedback from faculty –To revise your design before Design Document submission Design Review will last longer than your proposal presentation and discussion. So, allocate 1 hour for the review –Presentation should take about 20 min –Remaining 40 min should be allocated to discussion You need to submit Design Review presentation slides to CC

4. Design Review Slides Cover page Short review of identification of need and requirements definition Design architecture (Level-0 and Level-1) Preliminary detail design (Level-2) Preliminary models used in your design (state diagrams, data flow diagrams, etc.) List of prototyping activities and progress discussion Problems/surprises you encountered

5. Design Document The focus is on detail design –Emphasize the top-down design –Get to the bottom – circuit-level, algorithm-level, etc. You don’t have much time to do the entire design – so hurry up Technical part and administrative part –Administrative issues depend on technical designs –Again, you must have technical issues resolved before addressing administrative issues –Don’t neglect the administrative part ! Look back at your proposal You must report your early prototyping activity

6. Design Document Format Cover page Short introduction (Problem Stement) Requirements specification System design/architecture - system decomposition Detail design –All levels of your design down to circuit schematics, state diagrams, and/or algorithm flowcharts – even if you are not sure about the design –Detail description of components and interfaces –Include flow diagrams with identification of subroutines and main parameters for simulation projects

7. Prototyping progress report –List components acquired –What was built/experimented with/tested –What knowledge learned Testing plan –What kind of experiments (and explain why such experiments)? –Determine evaluation criteria (how do you measure success?) List and description of tasks –Description of each task/subtask provides an explanation of activities conducted within this task/subtask –Decompose tasks into subtasks –Allocate responsibilities to each task

8. Schedule and milestones –Cover the next semester time (+ summer/winter break if you plan to work) –Be realistic –Make a significant push at the beginning of the next semester Exploit the first weeks of relatively light class schedule Remember, most projects are delayed –Include demos – mention functionalities to be presented by a sequence of demos/experiments –See sample schedule on the web page

9. For the Next Meeting Read textbook –Chapter 7 (Testing) and –Chapter 10 (Project Management) Next meeting: –Testing; Scheduling