1. Spring 2007 1 CS-EE 481 Lillevik 481s07-l1 University of Portland School of Engineering Senior Design Lecture 1 Fall re-cap Spring pre-view Debugging

2. Spring 2007 2 CS-EE 481 Lillevik 481s07-l1 University of Portland School of Engineering Our overall goal University Professional Practice, Graduate School Senior design facilitates the transition Today

3. Spring 2007 3 CS-EE 481 Lillevik 481s07-l1 University of Portland School of Engineering Fall semester re-cap Formed design team and defined project Established a methodology Developed specification (FS doc) Created a plan (Plan doc) Designed the project (DR milestone) It was a busy semester, many accomplishments

4. Spring 2007 4 CS-EE 481 Lillevik 481s07-l1 University of Portland School of Engineering Fall 2006 grades Distribution (CS/EE) A = 6/9A- = 0/1 B+ = 1/3B =0/1B- = 0/0 C+ = 0/0C = 0/2 Class averages CS = 3.58 students EE = 3.518 students

5. Spring 2007 5 CS-EE 481 Lillevik 481s07-l1 University of Portland School of Engineering Evaluation messages Design components Technical Process Spring contribution may need to shift

6. Spring 2007 6 CS-EE 481 Lillevik 481s07-l1 University of Portland School of Engineering Spring semester pre-view Lots of implementation and debugging Little formal lecture time (use class time for team meetings) Two documents (TOP, Final Report) Selection of “Outstanding Project” Founders Day: April 17 Commencement: May 6

7. Spring 2007 7 CS-EE 481 Lillevik 481s07-l1 University of Portland School of Engineering Spring deliverables DateDeliverable Jan. 30, Feb. 1January Program Review Feb. 9Theory of Operations 0.9 Feb. 23Theory of Operations 1.0 and Approval Meeting Feb. 27, Mar. 1February Program Review Mar. 27, 29March Program Review Apr. 13Prototype Release and Approval Meeting Apr. 17Founders Day Celebration Apr. 18Final Report 0.9 Apr. 25Post Mortem with Junior Class Apr. 27Final Report 1.0 and Approval Meeting Very busy !! 2 months !!

8. Spring 2007 8 CS-EE 481 Lillevik 481s07-l1 University of Portland School of Engineering January 2007 CS-EE 480 University of Portland Pgm rev Weekly MonTueWedThuFri 45 89101112 1516171819 2223242526 2930 31 1 2 123 Xmas Ends Weekly Semester Begins

9. Spring 2007 9 CS-EE 481 Lillevik 481s07-l1 University of Portland School of Engineering February 2007 CS-EE 481 University of Portland Pgm rev Weekly TOP 0.9 Weekly TOP 1.0 Approv mtg Weekly MonTueWedThuFri 12 56789 1213141516 1920212223 26272812 TOP 0.95 to IR

10. Spring 2007 10 CS-EE 481 Lillevik 481s07-l1 University of Portland School of Engineering March 2007 CS-EE 481 University of Portland Pgm rev Weekly PR info list Weekly MonTueWedThuFri 56789 1213141516 1920212223 2627282930 Spring Break Starts Spring Break Ends Comp Exam

11. Spring 2007 11 CS-EE 481 Lillevik 481s07-l1 University of Portland School of Engineering April 2007 CS-EE 481 University of Portland Founders Day Final rpt 0.9 Weekly Proto rel Approv mtg Weekly, optional Weekly Final rpt 1.0 Approv mtg MonTueWedThuFri 56 910111213 1617181920 2324252627 301234 234 PR info to IR FD Rehearsal Final rpt 0.95 to IR Peer reviews Finals Start Post Mortem with Jr’s Easter Monday Finals End Senior luncheon Weekly

12. Spring 2007 12 CS-EE 481 Lillevik 481s07-l1 University of Portland School of Engineering Comprehensive exam Purpose: curricula assessment and development Format: multiple choice Date: March 6 at 9-11 or 10-12 Coordinators: Dr. Lillevik, Dr. Lu Policy: must pass (60%) or senior design grade dropped by one letter Senior luncheon: top 2 scores recognized

13. Spring 2007 13 CS-EE 481 Lillevik 481s07-l1 University of Portland School of Engineering Sr. design award Outstanding Senior Design Project Purpose: recognized top two projects Started in 2003 Senior class selects Names and title engraved on a plaque Teams present in afternoon session on Founders Day

14. Spring 2007 14 CS-EE 481 Lillevik 481s07-l1 University of Portland School of Engineering Product development cycle Define Design Prototype Evaluation Production Milestones/ Approvals Product Approval Design Release Prototype Release Beta Release Product Release Documents Functional Specifications Project Plan Debug & Evaluation Plan Theory of Operations Qualification Report Not in class Manufacturing Report EOL Final Report Today

15. Spring 2007 15 CS-EE 481 Lillevik 481s07-l1 University of Portland School of Engineering Two observations Time is of the essence !! –Don’t procrastinate –Maximize your time Debugging is a major challenge –All projects have anomalies (bugs) –Develop an approach, stick to it

16. Spring 2007 16 CS-EE 481 Lillevik 481s07-l1 University of Portland School of Engineering Fixing a leaky roof Flashing fault Leak in bedroom chimney Where you see the leak is different then the problem

17. Spring 2007 17 CS-EE 481 Lillevik 481s07-l1 University of Portland School of Engineering Debugging Design Error CauseEffect Often, only the effect is observable !! Usually ~6 steps to solve a problem

18. Spring 2007 18 CS-EE 481 Lillevik 481s07-l1 University of Portland School of Engineering Debugging Step 1

19. Spring 2007 19 CS-EE 481 Lillevik 481s07-l1 University of Portland School of Engineering Debugging Step 2

20. Spring 2007 20 CS-EE 481 Lillevik 481s07-l1 University of Portland School of Engineering Debugging Step 3

21. Spring 2007 21 CS-EE 481 Lillevik 481s07-l1 University of Portland School of Engineering Debugging Step 4

22. Spring 2007 22 CS-EE 481 Lillevik 481s07-l1 University of Portland School of Engineering Debugging Step 5

23. Spring 2007 23 CS-EE 481 Lillevik 481s07-l1 University of Portland School of Engineering Debugging Step 6

24. Spring 2007 24 CS-EE 481 Lillevik 481s07-l1 University of Portland School of Engineering Suggestions Keep an open mind, be objective Don’t confuse symptom with cause Avoid “trial and error” debugging Focus on root cause Make sure to test fix

25. Spring 2007 25 CS-EE 481 Lillevik 481s07-l1 University of Portland School of Engineering Debugging in practice Consumes 60% - 80% of project time line Formal process (War Room meetings, several hundred bugs) Bug tracking database (title, symptom, severity, cause, fix, state) Number of bugs determines product release date

26. Spring 2007 26 CS-EE 481 Lillevik 481s07-l1 University of Portland School of Engineering

27. Spring 2007 27 CS-EE 481 Lillevik 481s07-l1 University of Portland School of Engineering Debugging Step 1 Describe the symptom The more detail the better

28. Spring 2007 28 CS-EE 481 Lillevik 481s07-l1 University of Portland School of Engineering Debugging Step 2 Determine if symptom is: 1.Repetitive (easy) 2.Intermittent (hard)

29. Spring 2007 29 CS-EE 481 Lillevik 481s07-l1 University of Portland School of Engineering Debugging Step 3 Isolate cause (very hard) –Break the problem into smaller pieces –Check that each smaller piece works, then put them together

30. Spring 2007 30 CS-EE 481 Lillevik 481s07-l1 University of Portland School of Engineering Debugging Step 4 Propose and implement a fix –If you understand the cause, its often easy to find a fix –Sometimes you want to propose several fixes and later select the “best” one

31. Spring 2007 31 CS-EE 481 Lillevik 481s07-l1 University of Portland School of Engineering Debugging Step 5 Test fix –Functional (does it work?) –Regression (any not working that did before?)

32. Spring 2007 32 CS-EE 481 Lillevik 481s07-l1 University of Portland School of Engineering Debugging Step 6 Document & communicate the change Who needs to know what and when?