Engineering design process

Slide 1 Design Process Overview (Material developed by Project Lead the Way) What is Design? The word “design” is often used as a generic term that refers to anything that was made by a conscious huma.aaaaaaaaaaaaaaaaaaaaaaaaaaaaa

Trang 1

Textbook: Design for ECE Engineers, Ford

 No single "correct" solution

 Technical aspects only small part

Trang 2

Elements of Design the

Trang 3

Text book: Design for ECE engineers Ford

Cost of Design Changes

 Costs increase exponentially as the project lifetime increases

Trang 4

Problem Identification and Requirements

Specification

Trang 5

3 Organize needs hierarchy

4 Determine relative importance of

needs

5 Review outcomes and process

Trang 6

Example Needs Hierarchy

Trang 7

Problem Statement

 Example 2.1

 Need: Drivers have difficulty seeing

obstructions in all directions

 Objective: design system to avoid

accidents

Trang 8

Requirements Specification

 Identifies requirements design

must satisfy for success

Trang 9

Properties of Engineering

Requirements

1 Abstract – what, not how

2 Unambiguous – unique and specific

 Unlike marketing requirements

3 Traceable – satisfy need?

4 Verifiable – test/measure

Trang 10

Example Engineering

Requirements

 Performance and Functionality

1 Will identify skin lesions with a 90% accuracy

2 Should be able to measure within 1mm

Trang 11

Properties of Requirements Specification

1 Normalized (orthogonal) set

Trang 12

 Economic

 Environmental

 Ethical and Legal

 Health and Safety

 Manufacturability

 Political and Social – FDA, language?

 Sustainability

Trang 13

Trang 14

Concept Generation and

Evaluation

 Explore many solutions

 Brainstorm

 Select the best solution

 Based on needs and constraints

Trang 15

Creativity

Trang 16

• Engineering cultural bias

• Understand tools

Trang 17

Trang 18

Concept Generation

 Substitute – new elements

 Combine – existing elements

 Adapt – different operation

 Modify – size, shape, function

 Put to other use – other app domains

 Eliminate – parts or whole

 Rearrange or reverse – work better

Trang 19

Concept Table

Trang 20

Concept Evaluation

Trang 21

Trang 22

Design Considerations

2) RELIABILITY

 measured by MTBF, failure rate = 1/MTBF

 mechanical parts fail first

 design redundancy into system

 simple system/fewer parts = more reliable

Trang 23

Trang 24

Design Methodologies:

Top-Down

only at the lowest level

linear in practice

commitments are made at high levels

in the design process

Trang 25

design are explored and redesigned, if

necessary, first

Trang 26

Design Methodologies

ITERATIVE REFINEMENT:

general design is completed

more specific

until the complete detail design in done

Trang 27

BOTTOM‑UP DESIGN:

where you are going So, often this

feedback from the bottom

Trang 28

"EXPLORER" METHOD:

 Typically used for new design ideas or

research It is useful in initial design and specification stages, and is often used

when in "unfamiliar territory":

telephone, domain expert's office, etc.

be.

Trang 29

 No more than two control buttons

 Implement Run, Stop and Reset

 Output a 16-bit binary number for seconds

Trang 30

Top-Down Design: Level 0

Trang 31

Top-down Design: Level 1

Trang 32

(cont’)

Trang 33

, Textbook: Design for ECE Engineers,

(cont’)

Trang 34

Design Group (Team)

Trang 35

 Develop decision making guidelines

1 Decision by authority (leader)

2 Expert Member

3 Average member opinion

4 Majority

5 Consensus

Trang 36

 Teams that spend time together tend

to be successful teams

 Respect each other

1 Listen actively

2 Consider your response to others

3 Constructively criticize ideas, not people

4 Respect those not present

5 Communicate your ideas effectively

6 Manage conflict constructively

Trang 37

 Hold effective meetings

Trang 38

Project Management

 Work breakdown structure

 Hierarchical breakdown of tasks

and deliverables need to complete project

 Activity

1 Task – action to accomplish job

2 Deliverable – e.g circuit or report

Trang 39

Trang 41

Schedule – Gantt Chart

Trang 42

Project Management

 Guidelines

 Project plan after design plan complete

 Double time estimates and add 10%

 Assign a lot of integration and test time

 Remember lead times for parts ordering

 Assign tasks based on skills and interests

 Track progress versus plan

 Plans change

Trang 43

Trang 44

Project Proposal

• One goal is to sell idea, be

persuasive

should show:

Trang 45

Project Proposal

Format

• Second goal is to inform

section number, group number

more detailed the better Will help with the scheduling and task assignment

senior project.

development

Trang 46

Oral Presentations

Trang 47

 Eye contact with entire audience

 Avoid too much information

 Meet time constraints

 Look and act professionally

 Use visuals effectively

Trang 48

Oral Presentations

 Slides

Trang 49

Presentations

engineering team (5-10 min for a team of 2) Due to the

limited class time you will be cutoff if you exceed the upper limit.

 Professionalism ‑ appearance, manner, visual aids

 Clarity ‑ Can we understand what your design is about?

 Organization ‑ Is your talk well‑organized? Does it follow a

logical progression? Is it presented in a top-down manner?

 Completeness ‑ Are all the parts there? Did you provide a good introduction? Clear, positive conclusions and/or summary? etc

 Communication ‑ Did you maintain eye contact with the entire audience? Did they understand you ? etc

 Time Limits ‑ Did you stay within the specified time limits?

 Questions ‑ Were you successful at fielding questions after you presentation? Are you knowledgeable on the subject matter ?

Tiêu đề	Engineering Design Process
Trường học	University of Engineering and Technology
Chuyên ngành	Engineering Design
Thể loại	Textbook

Định dạng
Số trang	50
Dung lượng	1,75 MB