Fall CS-EE 480 Lillevik 480f06-l5 University of Portland School of Engineering Senior Design Lecture 5 Prototype phase Evaluation phase Production phase

Fall CS-EE 480 Lillevik 480f06-l5 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

Fall CS-EE 480 Lillevik 480f06-l5 University of Portland School of Engineering Any questions? Definition phase –Functional Specifications document –Product Approval milestone Design phase –Project Plan document –Design Release milestone

Fall CS-EE 480 Lillevik 480f06-l5 University of Portland School of Engineering Prototype phase Define Design Prototype Evaluation Production Milestones/ Approvals Prototype Release Documents Debug & Evaluation Plan Theory of Operations

Fall CS-EE 480 Lillevik 480f06-l5 University of Portland School of Engineering Prototype phase overview Purpose –Integrate the pieces (big step) –Create the initial (alpha) version of the product Documents –Debug & Evaluation Plan (testing methodology) –Theory of Operations (technical description) Milestone: Prototype Release

Fall CS-EE 480 Lillevik 480f06-l5 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) Use (true for all plans) –Monitor and track progress, software database application –Identify schedule slips, budget overruns in advance

Fall CS-EE 480 Lillevik 480f06-l5 University of Portland School of Engineering Debug & Evaluation Plan, continued. Issues –Poorly defined tests and minimal coverage –Bugs: repetitive/easy, intermittent/difficult, tracking –High demand for prototypes, little supply Recommendation: plan debug and testing to take at least 2X the time expected

Fall CS-EE 480 Lillevik 480f06-l5 University of Portland School of Engineering Theory of operation What: technical description of how the design works Scope: focus on the internal workings Your TOP’s: if you can describe it, you can’t debug it

Fall CS-EE 480 Lillevik 480f06-l5 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

Fall CS-EE 480 Lillevik 480f06-l5 University of Portland School of Engineering Prototype Release Purpose –Start thorough testing –Begin to deploy product to stakeholders (little value earlier) Process –Hold an approval meeting: team, advisor, industry rep –Demonstrate working prototype (Alpha Release)

Fall CS-EE 480 Lillevik 480f06-l5 University of Portland School of Engineering Evaluation Phase Define Design Prototype Evaluation Production Milestones/ Approvals Beta Release Documents Qualification Report

Fall CS-EE 480 Lillevik 480f06-l5 University of Portland School of Engineering Evaluation phase overview Purpose –Prove that design works and how well (robust) –Finalize design for high-volume production Documents –Qualification Report (data, analysis, conclusions) –Physical evidence Milestone: Beta Release

Fall CS-EE 480 Lillevik 480f06-l5 University of Portland School of Engineering Why an evaluation phase? Get rid of bugs Make sure it works Quality, defects

Fall CS-EE 480 Lillevik 480f06-l5 University of Portland School of Engineering Bug tracking States/dates: open, study, fixed, tested, etc., closed Severity: H, M, L Metrics –Number of bugs, bugs vs. time –Number of high’s, high’s vs. time –High’s open a long time War Room

Fall CS-EE 480 Lillevik 480f06-l5 University of Portland School of Engineering Example bug tracking application

Fall CS-EE 480 Lillevik 480f06-l5 University of Portland School of Engineering Pentium evaluation Number of engineers? Time frame? Number of bugs tracked?

Fall CS-EE 480 Lillevik 480f06-l5 University of Portland School of Engineering Qualification Report Purpose: document qualification What: testing methods, data, analysis Issues –Poorly defined data & methods & conclusions –Impossible to reproduce data –Major document, tons of data, shared with stakeholders

Fall CS-EE 480 Lillevik 480f06-l5 University of Portland School of Engineering How is a Qual Report used? Egr- fix stuff Mktg- hide/document flaws Mfg- tools are working Service- predict problems Sales- ? Sr. Mgmt- who to fire Finance- over budget

Fall CS-EE 480 Lillevik 480f06-l5 University of Portland School of Engineering Beta Release Purpose –Begin widespread prototype deployment –Start manufacturing ramp-up Process –Checklists work well –Include peer & expert reviewers

Fall CS-EE 480 Lillevik 480f06-l5 University of Portland School of Engineering Production (Ramp-Up) Phase Define Design Prototype Evaluation Production Milestones/ Approvals Product Release Documents Manufacturing Report

Fall CS-EE 480 Lillevik 480f06-l5 University of Portland School of Engineering Production phase overview Purpose: ramp the manufacturing line up to full-scale production, take dpm data Documents –Manufacturing Report –Demonstrates manufacturability Milestone: Production Release, PR (first customer ship-FCS)

Fall CS-EE 480 Lillevik 480f06-l5 University of Portland School of Engineering How is a mfg report used? Egr- Mktg- Mfg- Service- Sales- Sr. Mgmt- Finance-

Fall CS-EE 480 Lillevik 480f06-l5 University of Portland School of Engineering Production Release Purpose –Begin high-volume production, bring in revenue ($$) –Post-mortem held to discover learning’s Process: Often requires a risk assessment & judgment call by senior management

Fall CS-EE 480 Lillevik 480f06-l5 University of Portland School of Engineering

Fall CS-EE 480 Lillevik 480f06-l5 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

Fall CS-EE 480 Lillevik 480f06-l5 University of Portland School of Engineering Why an evaluation phase? Make sure it works Discover bugs/fix them Identify weak points for future enhancements Push product to limits (robust) Make sure designed the right thing

Fall CS-EE 480 Lillevik 480f06-l5 University of Portland School of Engineering Pentium evaluation Number of engineers? Time frame?9 months Number of bugs tracked?

Fall CS-EE 480 Lillevik 480f06-l5 University of Portland School of Engineering How is a Qual Report used? Egr- Baseline product performance, submit for certifications (UL, CSA, VDE, software) Mktg- Share with customers for cross-quals Mfg- Validate testing Service- Estimate failure rates (fit’s) Sales- Create promotional literature Sr. Mgmt- IP, legal Finance- None

Fall CS-EE 480 Lillevik 480f06-l5 University of Portland School of Engineering How is a mfg report used? Egr- Adjust design guidelines Mktg- Product planning Mfg- Estimate defects-per-million (dpm) Service- Cost of spares Sales- None Sr. Mgmt- Future plant planning Finance- Validate ROI assumptions, analysis