1. Spring 2007 1 CS-EE 481 Lillevik 481s07-l2 University of Portland School of Engineering Senior Design Lecture 2 Technical staff Prototype phase: DEP, TOP

2. Spring 2007 2 CS-EE 481 Lillevik 481s07-l2 University of Portland School of Engineering SOE technical staff Electrical –Sandy Ressel –Egr. 208, x7862, ressel@up.edu –Parts and assembly Mechanical –Rick Severs –Egr. 1009, x7383, severs@up.edu –Materials and fabrication

3. Spring 2007 3 CS-EE 481 Lillevik 481s07-l2 University of Portland School of Engineering Next few 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

4. Spring 2007 4 CS-EE 481 Lillevik 481s07-l2 University of Portland School of Engineering Jan. program review Demonstrate if possible Use correct milestone table –Original: date and contents does not change –Previous: include Nov. information –Present: update/highlight with Jan. information Be prepared to explain changes in features, schedule, or budget

5. Spring 2007 5 CS-EE 481 Lillevik 481s07-l2 University of Portland School of Engineering Correct November NumberDescriptionOriginal 10/30/05 Previous 10/30/05 Present 11/20/05 1Product Plan 1.011/20/06 2Graphic Site Design11/30/06 3Design Release Approval12/08/06 4Database Setup Complete1/25/07 5TOPS 1.01/26/07 6Account Creation Complete2/8/07 7Search/Buying Complete3/1/07 8 Account Management Complete 3/1/07 9Site-Wide CSS3/22/07 10Book Listings Complete3/22/07 11Alpha Release Complete3/22/07 12Prototype Release4/5/07 13Prototype Release Approval4/13/07 14Founder’s Day4/17/07 15Final Report 1.04/30/07 Column stays the same October data Any changes go in this column

6. Spring 2007 6 CS-EE 481 Lillevik 481s07-l2 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

7. Spring 2007 7 CS-EE 481 Lillevik 481s07-l2 University of Portland School of Engineering Prototype phase Define Design Prototype Evaluation Production Milestones/ Approvals Prototype Release Documents Debug & Evaluation Plan Theory of Operations

8. Spring 2007 8 CS-EE 481 Lillevik 481s07-l2 University of Portland School of Engineering Prototype phase overview Purpose –Create the initial (alpha) version of the product –Integrate the pieces (big step) Documents –Debug & Evaluation Plan (testing methodology) –Theory of Operations (technical description) Milestone: Prototype Release

9. Spring 2007 9 CS-EE 481 Lillevik 481s07-l2 University of Portland School of Engineering Debug & evaluation plan Purpose –Defines who is doing what and when –Prove that design works and how well (robust) We do not prepare a DEP –Reduce documentation requirements, increase development time –Suggest your team prepare an informal DEP

10. Spring 2007 10 CS-EE 481 Lillevik 481s07-l2 University of Portland School of Engineering What would a DEP include?

11. Spring 2007 11 CS-EE 481 Lillevik 481s07-l2 University of Portland School of Engineering Theory of operations What: technical description of how the design works Scope: focus on the internal workings We prepare a TOP: fundamental document, technical writing an important skill Your TOP’s: if you can describe it, you can’t debug it

12. Spring 2007 12 CS-EE 481 Lillevik 481s07-l2 University of Portland School of Engineering How is a TOP’s used? Egr- what they’re doing Mktg- advertising Mfg- understand the technologies Service- help explain to customers Sales- understand their market Sr. Mgmt- waste basket liner Finance- another liner From CS-EE 480, Fall 2006

13. Spring 2007 13 CS-EE 481 Lillevik 481s07-l2 University of Portland School of Engineering How is a TOP’s used? Egr- debug Mktg- customer mtgs Mfg- plant layout, testing Service- maintenance guide, training Sales- customer mtg Sr. Mgmt- sales Finance- None Instructor’s response

14. Spring 2007 14 CS-EE 481 Lillevik 481s07-l2 University of Portland School of Engineering Organization Summary Introduction Background Architecture Design Overview Conclusions Appendices NOTE: Remember to use present tense because you are describing something that is done

15. Spring 2007 15 CS-EE 481 Lillevik 481s07-l2 University of Portland School of Engineering Summary Contains key messages of document Standalone For the busy executive Often easier to write this section last

16. Spring 2007 16 CS-EE 481 Lillevik 481s07-l2 University of Portland School of Engineering Introduction Purpose Intended reader Significance Scope: what’s in, what’s out Outline remainder of document

17. Spring 2007 17 CS-EE 481 Lillevik 481s07-l2 University of Portland School of Engineering Background Set the scene or constraints for the design Review the key product features Use excerpts from Functional Specifications

18. Spring 2007 18 CS-EE 481 Lillevik 481s07-l2 University of Portland School of Engineering Architecture Foundation of design Architectural block diagram (high-level view) Explain major components –What are they? –How do they interact? Use collateral from Design Review meeting

19. Spring 2007 19 CS-EE 481 Lillevik 481s07-l2 University of Portland School of Engineering Design Overview Bulk of document System block diagram Tops-down description Explain implementation –Separate into major sections –Describe how each section works Use collateral from Design Review meeting

20. Spring 2007 20 CS-EE 481 Lillevik 481s07-l2 University of Portland School of Engineering Conclusions Recap key points No new information Do not repeat summary, complement it Recommendations for future work

21. Spring 2007 21 CS-EE 481 Lillevik 481s07-l2 University of Portland School of Engineering Appendices Use only if needed Place detailed or lengthy information here

22. Spring 2007 22 CS-EE 481 Lillevik 481s07-l2 University of Portland School of Engineering

23. Spring 2007 23 CS-EE 481 Lillevik 481s07-l2 University of Portland School of Engineering What would a DEP include? Define design units Describe unit testing: setup, procedures, expected results Describe integration process –Order units are combined –Setup, procedures, expected results System testing: setup, procedures, expected results