Fall 2006 1 CS-EE 480 Lillevik 480f06-l5 University of Portland School of Engineering Senior Design...

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

Transcript of Fall 2006 1 CS-EE 480 Lillevik 480f06-l5 University of Portland School of Engineering Senior Design...

Fall 2006

Lillevik 480f06-l5 1University of Portland School of Engineering

CS-EE 480

Senior DesignLecture 5

Prototype phase

Evaluation phase

Production phase

Fall 2006

Lillevik 480f06-l5 2University of Portland School of Engineering

CS-EE 480

Product development cycle

Define Design Prototype Evaluation Production

Milestones/

Approvals

Product

Approval

Design

Release

Prototype

Release

Beta

Release

Product

Release

DocumentsFunctional

Specifications

Project

Plan

Debug &

Evaluation

Plan

Theory of

Operations

Qualification

Report

Not in class

Manufacturing

Report

EOL

Final Report

Fall 2006

Lillevik 480f06-l5 3University of Portland School of Engineering

CS-EE 480

Any questions?

• Definition phase– Functional Specifications document– Product Approval milestone

• Design phase– Project Plan document– Design Release milestone

Fall 2006

Lillevik 480f06-l5 4University of Portland School of Engineering

CS-EE 480

Prototype phase

Define Design Prototype Evaluation Production

Milestones/

Approvals

Prototype

Release

Documents

Debug &

Evaluation

Plan

Theory of

Operations

Fall 2006

Lillevik 480f06-l5 5University of Portland School of Engineering

CS-EE 480

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 2006

Lillevik 480f06-l5 6University of Portland School of Engineering

CS-EE 480

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 2006

Lillevik 480f06-l5 7University of Portland School of Engineering

CS-EE 480

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 2006

Lillevik 480f06-l5 8University of Portland School of Engineering

CS-EE 480

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 2006

Lillevik 480f06-l5 9University of Portland School of Engineering

CS-EE 480

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 2006

Lillevik 480f06-l5 10University of Portland School of Engineering

CS-EE 480

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 2006

Lillevik 480f06-l5 11University of Portland School of Engineering

CS-EE 480

Evaluation Phase

Define Design Prototype Evaluation Production

Milestones/

Approvals

Beta

Release

DocumentsQualification

Report

Fall 2006

Lillevik 480f06-l5 12University of Portland School of Engineering

CS-EE 480

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 2006

Lillevik 480f06-l5 13University of Portland School of Engineering

CS-EE 480

Why an evaluation phase?

• Get rid of bugs

• Make sure it works

• Quality, defects

Fall 2006

Lillevik 480f06-l5 14University of Portland School of Engineering

CS-EE 480

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 2006

Lillevik 480f06-l5 15University of Portland School of Engineering

CS-EE 480

Example bug tracking application

Fall 2006

Lillevik 480f06-l5 16University of Portland School of Engineering

CS-EE 480

Pentium evaluation

• Number of engineers?

• Time frame?

• Number of bugs tracked?

Fall 2006

Lillevik 480f06-l5 17University of Portland School of Engineering

CS-EE 480

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 2006

Lillevik 480f06-l5 18University of Portland School of Engineering

CS-EE 480

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 2006

Lillevik 480f06-l5 19University of Portland School of Engineering

CS-EE 480

Beta Release

• Purpose– Begin widespread prototype deployment– Start manufacturing ramp-up

• Process– Checklists work well– Include peer & expert reviewers

Fall 2006

Lillevik 480f06-l5 20University of Portland School of Engineering

CS-EE 480

Production (Ramp-Up) Phase

Define Design Prototype Evaluation Production

Milestones/

Approvals

Product

Release

DocumentsManufacturing

Report

Fall 2006

Lillevik 480f06-l5 21University of Portland School of Engineering

CS-EE 480

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 2006

Lillevik 480f06-l5 22University of Portland School of Engineering

CS-EE 480

How is a mfg report used?

• Egr-

• Mktg-

• Mfg-

• Service-

• Sales-

• Sr. Mgmt-

• Finance-

Fall 2006

Lillevik 480f06-l5 23University of Portland School of Engineering

CS-EE 480

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 2006

Lillevik 480f06-l5 24University of Portland School of Engineering

CS-EE 480

Fall 2006

Lillevik 480f06-l5 25University of Portland School of Engineering

CS-EE 480

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 2006

Lillevik 480f06-l5 26University of Portland School of Engineering

CS-EE 480

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 2006

Lillevik 480f06-l5 27University of Portland School of Engineering

CS-EE 480

Pentium evaluation

• Number of engineers?300 - 400

• Time frame? 9 months

• Number of bugs tracked? 300 - 500

Fall 2006

Lillevik 480f06-l5 28University of Portland School of Engineering

CS-EE 480

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 2006

Lillevik 480f06-l5 29University of Portland School of Engineering

CS-EE 480

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