1. Fall 2006 1 CS-EE 480 Lillevik 480f06-l3 University of Portland School of Engineering Senior Design Lecture 3 Corporate organization Product development cycle Definition phase

2. Fall 2006 2 CS-EE 480 Lillevik 480f06-l3 University of Portland School of Engineering What’s confusing you? Industry rep Advisors Parts 314A Budget Guidelines, restrictions

3. Fall 2006 3 CS-EE 480 Lillevik 480f06-l3 University of Portland School of Engineering Pre-approval template Due: Friday Sept. 8

4. Fall 2006 4 CS-EE 480 Lillevik 480f06-l3 University of Portland School of Engineering Corporate organization BOD/Officers Engineering Silicon Hardware Software Mechanical Marketing Technical Product Manufacturing Test Materials Production Sales North America Worldwide FinanceSupport Corporate objective: to make money ($$$)

5. Fall 2006 5 CS-EE 480 Lillevik 480f06-l3 University of Portland School of Engineering Responsibilities ?? BOD/Officers: bottom line Engineering: designing Marketing –Technical: how it works –Product: long term view

6. Fall 2006 6 CS-EE 480 Lillevik 480f06-l3 University of Portland School of Engineering Responsibilities ??, continued. Manufacturing –Test: quality of product –Materials: get parts cheap –Production: efficency Sales –North America: NA region –Worldwide: ww region

7. Fall 2006 7 CS-EE 480 Lillevik 480f06-l3 University of Portland School of Engineering Responsibilities ??, continued. Finance: bottom line, investors, funding Service: customer satisfaction

8. Fall 2006 8 CS-EE 480 Lillevik 480f06-l3 University of Portland School of Engineering Who’s king of the hill? Engineering: they design it Marketing/sales: they sell it Manufacturing: they make it But who is the top dog?

9. Fall 2006 9 CS-EE 480 Lillevik 480f06-l3 University of Portland School of Engineering The development issue Development environment –Teams, some to 300 - 500 engineers –Multidisciplinary, multi-site, major $$$ –Long time frame, some to 5 years or more Problem: communications Solution –Process –Language

10. Fall 2006 10 CS-EE 480 Lillevik 480f06-l3 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

11. Fall 2006 11 CS-EE 480 Lillevik 480f06-l3 University of Portland School of Engineering PDC diagram Illustrates process vs. time Funnel shape: team’s understanding (focus) increases over time Five distinct phases –Transitions actually iterative –Each phase Documented Specific entry/exit milestones & criteria

12. Fall 2006 12 CS-EE 480 Lillevik 480f06-l3 University of Portland School of Engineering SW vs. HW difficulty? SW More abstract Exceptions Different Not ideal Forward, backward HW Natural phenomena Not ideal Forward, backward Physical devices Harder to debug, fix

13. Fall 2006 13 CS-EE 480 Lillevik 480f06-l3 University of Portland School of Engineering What is a milestone? Something you can measure Marks a state or phase Major point in time Identifies sequence

14. Fall 2006 14 CS-EE 480 Lillevik 480f06-l3 University of Portland School of Engineering Overlapping PDC cycles Staffing Time Product 1Product 2Product 3 Area under the curve is constant: headcount H/C

15. Fall 2006 15 CS-EE 480 Lillevik 480f06-l3 University of Portland School of Engineering Product dimensions Budget Schedule Features Usually, one dimension is fixed Which one?

16. Fall 2006 16 CS-EE 480 Lillevik 480f06-l3 University of Portland School of Engineering Why do we document?

17. Fall 2006 17 CS-EE 480 Lillevik 480f06-l3 University of Portland School of Engineering Definition phase Define Design Prototype Evaluation Production Milestones/ Approvals Product Approval Documents Functional Specifications

18. Fall 2006 18 CS-EE 480 Lillevik 480f06-l3 University of Portland School of Engineering Definition phase overview Purpose –Starts product development –Estimate return on investment (ROI) Document –Functional Specifications –Describes what the product is Milestone –Product Approval (corporate OK)

19. Fall 2006 19 CS-EE 480 Lillevik 480f06-l3 University of Portland School of Engineering How are specifications used? BOD/Officers: Engineering: Manufacturing: Marketing: Support: Sales: Finance:

20. Fall 2006 20 CS-EE 480 Lillevik 480f06-l3 University of Portland School of Engineering Functional specifications Typical issues –Feature creep: adding capabilities once design started, avoid “like the plague” –Poorly defined, incomplete, or incompatible features Recommendation: be as specific as possible, as soon as possible (often very difficult)

21. Fall 2006 21 CS-EE 480 Lillevik 480f06-l3 University of Portland School of Engineering Product approval Purpose –Freeze (change control) product features –Resources (staffing, funds) applied to product Process –Hold an approval meeting: team, advisor, industry rep –Review (page-by-page) the Functional Specifications

22. Fall 2006 22 CS-EE 480 Lillevik 480f06-l3 University of Portland School of Engineering Document revision Rev. 0.9 Rev. 0.95 Rev. 1.0 Rev. 1.x Team submits to advisor for review Team modifies document per advisor, sends Rev. 0.95 to industry rep Team modifies document per approval meeting, change control in effect Team modifies document per CCB approval

23. Fall 2006 23 CS-EE 480 Lillevik 480f06-l3 University of Portland School of Engineering Change control Once a document is at Rev. 1.0 it is subject to change control Motivation: avoid feature creep, communicate changes Process –Request submitted to Change Control Board –Approvals require document changes and new revision number (1.1, 1.2, …)

24. Fall 2006 24 CS-EE 480 Lillevik 480f06-l3 University of Portland School of Engineering

25. Fall 2006 25 CS-EE 480 Lillevik 480f06-l3 University of Portland School of Engineering Responsibilities ?? BOD/Officers: profitability Engineering: design the product Marketing –Technical: customer information/training –Product: product line planning (road map)

26. Fall 2006 26 CS-EE 480 Lillevik 480f06-l3 University of Portland School of Engineering Responsibilities ??, continued. Manufacturing –Test: verifies product works –Materials: assures parts supply line –Production: builds Sales –North America: local region –Worldwide: distant region

27. Fall 2006 27 CS-EE 480 Lillevik 480f06-l3 University of Portland School of Engineering Responsibilities ??, continued. Finance: planning, auditing Service: happy customers

28. Fall 2006 28 CS-EE 480 Lillevik 480f06-l3 University of Portland School of Engineering SW vs. HW difficulty? No difference in degree of difficulty All technologies are equally challenging There is a natural implementation progression Silicon  Hardware  Software  Manufacturing

29. Fall 2006 29 CS-EE 480 Lillevik 480f06-l3 University of Portland School of Engineering What is a milestone? Well defined and quantifiable action that marks progress

30. Fall 2006 30 CS-EE 480 Lillevik 480f06-l3 University of Portland School of Engineering Why do we document? Communication

31. Fall 2006 31 CS-EE 480 Lillevik 480f06-l3 University of Portland School of Engineering How are specifications used? BOD/Officers: profit Engineers: know what to design Mfg: special equipment, processes tuning, data Marketing: advanced sales, long cycles Service: spares, contracts, training Finance: forecast revenue/profit Sales: collateral, trade shows