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

Fall 2006

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

CS-EE 480

Senior DesignLecture 3

Corporate organization

Product development cycle

Definition phase

Fall 2006


CS-EE 480

What’s confusing you?

• Industry rep

• Advisors

• Parts

• 314A

• Budget

• Guidelines, restrictions

Fall 2006


CS-EE 480

Pre-approval template

Due: Friday

Sept. 8

Fall 2006


CS-EE 480

Corporate organization

BOD/Officers

Engineering Marketing Manufacturing Sales Finance

Silicon

Hardware

Software

Mechanical

Test

Materials

Production

Technical

Product

North America

Worldwide

Support

Corporate objective: to make money ($$$)

Fall 2006


CS-EE 480

Responsibilities ??

• BOD/Officers: bottom line

• Engineering: designing

• Marketing– Technical: how it works– Product: long term view

Fall 2006


CS-EE 480

Responsibilities ??, continued.

• Manufacturing– Test: quality of product– Materials: get parts cheap– Production: efficency

• Sales– North America: NA region– Worldwide: ww region

Fall 2006


CS-EE 480


• Finance: bottom line, investors, funding

• Service: customer satisfaction

Fall 2006


CS-EE 480

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?

Fall 2006


CS-EE 480

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

Fall 2006


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


CS-EE 480

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

Fall 2006


CS-EE 480

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

Fall 2006


CS-EE 480

What is a milestone?

• Something you can measure

• Marks a state or phase

• Major point in time

• Identifies sequence

Fall 2006


CS-EE 480

Overlapping PDC cycles

Staffing

Time

Product 1 Product 2 Product 3

Area under the curve is constant: headcount

H/C

Fall 2006


CS-EE 480

Product dimensions

Budget

Schedule

Features

Usually, one dimension is fixedWhich one?

Fall 2006


CS-EE 480

Why do we document?

Fall 2006


CS-EE 480

Definition phase

Define Design Prototype Evaluation Production

Milestones/

Approvals

Product

Approval

DocumentsFunctional

Specifications

Fall 2006


CS-EE 480

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)

Fall 2006


CS-EE 480

How are specifications used?

• BOD/Officers:

• Engineering:

• Manufacturing:

• Marketing:

• Support:

• Sales:

• Finance:

Fall 2006


CS-EE 480

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)

Fall 2006


CS-EE 480

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

Fall 2006


CS-EE 480

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

Fall 2006


CS-EE 480

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, …)

Fall 2006


CS-EE 480

Fall 2006


CS-EE 480

Responsibilities ??

• BOD/Officers: profitability

• Engineering: design the product

• Marketing– Technical: customer information/training– Product: product line planning (road map)

Fall 2006


CS-EE 480


• Manufacturing– Test: verifies product works– Materials: assures parts supply line– Production: builds

• Sales– North America: local region– Worldwide: distant region

Fall 2006


CS-EE 480


• Finance: planning, auditing

• Service: happy customers

Fall 2006


CS-EE 480

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

Fall 2006


CS-EE 480

What is a milestone?

• Well defined and quantifiable action that marks progress

Fall 2006


CS-EE 480

Why do we document?

• Communication

Fall 2006


CS-EE 480

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

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

Documents

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