404 lecture powerpointdesign

11

The Engineering Design The Engineering Design ProcessProcess

Creative processCreative process

Problem solving – the big Problem solving – the big picturepicture

No single "correct" solutionNo single "correct" solution

Technical aspects only small Technical aspects only small partpart

22

Elements of Design the Elements of Design the ProcessProcess

Problem IdentificationProblem Identification Research PhaseResearch Phase Requirements SpecificationRequirements Specification Concept GenerationConcept Generation Design PhaseDesign Phase Prototyping PhasePrototyping Phase System IntegrationSystem Integration Maintenance PhaseMaintenance Phase

33

Cost of Design ChangesCost of Design Changes

Costs increase exponentially as Costs increase exponentially as the project lifetime increasesthe project lifetime increases

44

Problem Identification and Problem Identification and Requirements Requirements SpecificationSpecification

55

Needs IdentificationNeeds Identification

What is the Problem?What is the Problem?

1.1. Collect informationCollect information

2.2. Interpret informationInterpret information

3.3. Organize needs hierarchyOrganize needs hierarchy

4.4. Determine relative importance of Determine relative importance of needsneeds

5.5. Review outcomes and processReview outcomes and process

66

Example Needs HierarchyExample Needs Hierarchy

77

Problem StatementProblem Statement

Example 2.1Example 2.1

NeedNeed: Drivers have difficulty seeing : Drivers have difficulty seeing obstructions in all directionsobstructions in all directions

ObjectiveObjective: design system to avoid : design system to avoid accidentsaccidents

88

Requirements SpecificationRequirements Specification

Identifies requirements design Identifies requirements design must satisfy for successmust satisfy for success

1.1. Marketing requirementsMarketing requirements Customer needsCustomer needs

2.2. Engineering requirementsEngineering requirements Applies to technical aspectsApplies to technical aspects Performance requirementsPerformance requirements

99

Properties of Engineering Properties of Engineering RequirementsRequirements

1.1. Abstract – what, not howAbstract – what, not how

2.2. Unambiguous – unique and specificUnambiguous – unique and specific Unlike marketing requirementsUnlike marketing requirements

3.3. Traceable – satisfy need?Traceable – satisfy need?

4.4. Verifiable – test/measureVerifiable – test/measure

1010

Example Engineering Example Engineering RequirementsRequirements

Performance and FunctionalityPerformance and Functionality1.1. Will identify skin lesions with a 90% accuracyWill identify skin lesions with a 90% accuracy2.2. Should be able to measure within 1mmShould be able to measure within 1mm

Reliability Reliability 1.1. Operational 99.9% of the timeOperational 99.9% of the time2.2. MTBF of 10 yearsMTBF of 10 years

EnergyEnergy1.1. Average power consumption of 2 wattsAverage power consumption of 2 watts2.2. Peak current draw of 1 ampPeak current draw of 1 amp

1111

Properties of Requirements Properties of Requirements SpecificationSpecification

1.1. Normalized (orthogonal) setNormalized (orthogonal) set2.2. Complete setComplete set3.3. ConsistentConsistent4.4. BoundedBounded5.5. Granular – system vs. componentGranular – system vs. component6.6. ModifiableModifiable

From IEEE Std. 1233-1998From IEEE Std. 1233-1998

1212

ConstraintsConstraints

EconomicEconomic EnvironmentalEnvironmental Ethical and LegalEthical and Legal Health and SafetyHealth and Safety ManufacturabilityManufacturability Political and Social – FDA, language?Political and Social – FDA, language? SustainabilitySustainability

1313

StandardsStandards

Examples – RS-232, TCP/IP, USBExamples – RS-232, TCP/IP, USB TypesTypes

SafetySafety TestingTesting ReliabilityReliability CommunicationsCommunications DocumentationDocumentation Programming LanguagesProgramming Languages

1414

Concept Generation and Concept Generation and EvaluationEvaluation

Explore many solutionsExplore many solutions BrainstormBrainstorm

Select the best solutionSelect the best solution Based on needs and constraintsBased on needs and constraints

CreativityCreativity Development of new ideasDevelopment of new ideas

InnovationInnovation Bringing creative ideas to realityBringing creative ideas to reality

1515

CreativityCreativity

1616

Barriers to CreativityBarriers to Creativity

Perceptual blocksPerceptual blocks• Limiting problem spaceLimiting problem space

Emotional blocksEmotional blocks• Fear of failure – “fail early and Fear of failure – “fail early and

often”often” Environmental blocksEnvironmental blocks

• Engineering cultural biasEngineering cultural bias Intellectual and expressive blocksIntellectual and expressive blocks

• Understand toolsUnderstand tools

1717

Strategies to Enhance Strategies to Enhance CreativityCreativity

Lateral thinkingLateral thinking

QuestionQuestion

PracticePractice

Suspend judgmentSuspend judgment

Allow timeAllow time

Think like a beginnerThink like a beginner

1818

Concept GenerationConcept Generation

Substitute – new elementsSubstitute – new elements Combine – existing elementsCombine – existing elements Adapt – different operationAdapt – different operation Modify – size, shape, functionModify – size, shape, function Put to other use – other app domainsPut to other use – other app domains Eliminate – parts or wholeEliminate – parts or whole Rearrange or reverse – work betterRearrange or reverse – work better

1919

Concept TableConcept Table

2020

Concept EvaluationConcept Evaluation

2121

Design ConsiderationsDesign Considerations

1)1) WORST CASE DESIGNWORST CASE DESIGN

Component variationComponent variation

Environmental conditionsEnvironmental conditions

Use computer simulationsUse computer simulations

2222


2) RELIABILITY 2) RELIABILITY measured by MTBF, failure rate = 1/MTBFmeasured by MTBF, failure rate = 1/MTBF

mechanical parts fail firstmechanical parts fail first design redundancy into systemdesign redundancy into system simple system/fewer parts = more reliablesimple system/fewer parts = more reliable

2323


3) SAFETY3) SAFETYidentify failure modesidentify failure modesprovide protectionprovide protection

4) TEST4) TESTdesign for ease of testdesign for ease of test

5) 5) PRODUCTION/MANUFACTURINGPRODUCTION/MANUFACTURINGconsider ease of assemblyconsider ease of assembly

2424

Design Methodologies: Design Methodologies: Top-DownTop-Down

Also called “functional Also called “functional decompostion“decompostion“

implementation details considered implementation details considered only at the lowest levelonly at the lowest level

top‑down design, is not so clean and top‑down design, is not so clean and linear in practicelinear in practice

Often implementation‑level Often implementation‑level commitments are made at high levels commitments are made at high levels in the design processin the design process

2525

Design MethodologiesDesign Methodologies

CASE‑BASED:CASE‑BASED: Research a specific, similar design case Research a specific, similar design case

study study Model your process on thatModel your process on that

INCREMENTAL REDESIGN:INCREMENTAL REDESIGN:

Find an existing design and "unravel" the Find an existing design and "unravel" the design from the bottom updesign from the bottom up

Modify as requiredModify as required Detailed and least global aspects of the Detailed and least global aspects of the

design are explored and redesigned, if design are explored and redesigned, if necessary, firstnecessary, first

2626


ITERATIVE REFINEMENT: ITERATIVE REFINEMENT: An iterative top‑down approach An iterative top‑down approach First a rough, approximate and First a rough, approximate and

general design is completed general design is completed Then we do it finer, more exact Then we do it finer, more exact

and more specificand more specific This process continues iteratively This process continues iteratively

until the complete detail design in until the complete detail design in donedone

2727


BOTTOM‑UP DESIGN:BOTTOM‑UP DESIGN: Opposite of top‑downOpposite of top‑down Start at the bottom with detail design Start at the bottom with detail design To do this, you must have some idea of To do this, you must have some idea of

where you are going. So, often this where you are going. So, often this becomes...becomes...

HYBRID DESIGN: HYBRID DESIGN: Combines aspects of both top‑down and Combines aspects of both top‑down and

bottom‑upbottom‑up More practical design approach then pure More practical design approach then pure

top‑downtop‑down Start with a top‑down approach, but have Start with a top‑down approach, but have

feedback from the bottomfeedback from the bottom

2828


"EXPLORER" METHOD: "EXPLORER" METHOD: Typically used for new design ideas or Typically used for new design ideas or

research. It is useful in initial design and research. It is useful in initial design and specification stages, and is often used specification stages, and is often used when in "unfamiliar territory":when in "unfamiliar territory":

1)1) Move in some direction; e.g. toward the library, Move in some direction; e.g. toward the library, telephone, domain expert's office, etc.telephone, domain expert's office, etc.

2)2) Look at what you find there.Look at what you find there.3)3) Record what you find in your notebook.Record what you find in your notebook.4)4) Analyze findings in terms of where you want to Analyze findings in terms of where you want to

be.be.5)5) Use results of analysis to choose next direction.Use results of analysis to choose next direction.6)6) Back to 1) and continue exploringBack to 1) and continue exploring

2929

Top-Down Application: Top-Down Application: Digital DesignDigital Design

SIMPLE DIGITAL STOPWATCHSIMPLE DIGITAL STOPWATCH

Engineering requirementsEngineering requirements No more than two control buttonsNo more than two control buttons Implement Run, Stop and ResetImplement Run, Stop and Reset Output a 16-bit binary number for Output a 16-bit binary number for

secondsseconds

3030

Top-Down Design: Level 0Top-Down Design: Level 0

3131

Top-down Design: Level 1Top-down Design: Level 1

3232

Top-down Design: Level 1 Top-down Design: Level 1 (cont’)(cont’)

3333

Top-down Design: Level 1 Top-down Design: Level 1 (cont’)(cont’)

3434

Design Group (Team)Design Group (Team)

Engineering projects require diverse Engineering projects require diverse skillsskills

This creates a need for group (team) This creates a need for group (team) workwork

Select members based on skillsSelect members based on skills1.1. TechnicalTechnical

2.2. Problem-solvingProblem-solving

3.3. InterpersonalInterpersonal

3535


Develop decision making guidelinesDevelop decision making guidelines

1.1. Decision by authority (leader)Decision by authority (leader)

2.2. Expert MemberExpert Member

3.3. Average member opinionAverage member opinion

4.4. MajorityMajority

5.5. ConsensusConsensus

3636


Teams that spend time together tend Teams that spend time together tend to be successful teamsto be successful teams

Respect each otherRespect each other

1.1. Listen activelyListen actively2.2. Consider your response to othersConsider your response to others3.3. Constructively criticize ideas, not peopleConstructively criticize ideas, not people4.4. Respect those not presentRespect those not present5.5. Communicate your ideas effectivelyCommunicate your ideas effectively6.6. Manage conflict constructivelyManage conflict constructively

3737


Hold effective meetingsHold effective meetings

1.1. Have an agendaHave an agenda

2.2. Show up preparedShow up prepared

3.3. Pay attentionPay attention

4.4. Schedule time and place of next meetingSchedule time and place of next meeting

5.5. SummarizeSummarize

Assign tasks and responsibilitiesAssign tasks and responsibilities

3838

Project ManagementProject Management

Work breakdown structureWork breakdown structure Hierarchical breakdown of tasks Hierarchical breakdown of tasks

and deliverables need to complete and deliverables need to complete projectproject

ActivityActivity1.1. Task – action to accomplish jobTask – action to accomplish job

2.2. Deliverable – e.g. circuit or reportDeliverable – e.g. circuit or report

3939


Define for each activityDefine for each activity1.1. Work to be doneWork to be done

2.2. TimeframeTimeframe

3.3. Resources neededResources needed

4.4. Responsible person(s)Responsible person(s)

5.5. Previous dependent activitiesPrevious dependent activities

6.6. Checkpoints/deliverables for Checkpoints/deliverables for monitoring progressmonitoring progress

4040

4141

Schedule – Gantt ChartSchedule – Gantt Chart

4242


GuidelinesGuidelines Project plan after design plan completeProject plan after design plan complete Double time estimates and add 10%Double time estimates and add 10% Assign a lot of integration and test timeAssign a lot of integration and test time Remember lead times for parts orderingRemember lead times for parts ordering Assign tasks based on skills and interestsAssign tasks based on skills and interests Track progress versus plan Track progress versus plan Plans changePlans change

4343

Project CommunicationProject Communication

Focus on needs of specific Focus on needs of specific audienceaudience

Who?Who? level of knowledgelevel of knowledge their motivation – needstheir motivation – needs

Why?Why? to persuadeto persuade

to informto inform

4444

Project ProposalProject Proposal

• One goal is to sell idea, be One goal is to sell idea, be persuasivepersuasive

In industry the proposal will show:In industry the proposal will show:1.1. Product is useful for someone for somethingProduct is useful for someone for something

2.2. The design will work, it will solve the problemThe design will work, it will solve the problem

3.3. Will meet the specified constraintsWill meet the specified constraints Additionally, in Senior Design, the proposal Additionally, in Senior Design, the proposal

should show:should show:1.1. You are learning something newYou are learning something new

2.2. Sufficiently complexSufficiently complex

3.3. Apply previously learned ECE knowledgeApply previously learned ECE knowledge

4545

Project Proposal Project Proposal FormatFormat• Second goal is to informSecond goal is to inform

1) 1) Title pageTitle page - project title, names, date, 404 lecture - project title, names, date, 404 lecture section number, group number. section number, group number.

2) 2) Table of ContentsTable of Contents, with page numbers., with page numbers.3) 3) IntroductionIntroduction4) 4) Problem AnalysisProblem Analysis5) 5) Requirements SpecificationRequirements Specification6) 6) Preliminary Design.Preliminary Design. Include a block diagram - the Include a block diagram - the

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

7) 7) Preliminary SchedulePreliminary Schedule (see Figure 10.3, Gantt chart) (see Figure 10.3, Gantt chart) 8) 8) ConclusionConclusion – summarize why this will be a great – summarize why this will be a great

senior project.senior project.9) 9) ReferencesReferences – any references used in proposal – any references used in proposal

developmentdevelopment

4646

Oral PresentationsOral Presentations

StructureStructure1.1. Intro: Tell them what you will tell themIntro: Tell them what you will tell them

Introduce group and projectIntroduce group and project Overview and backgroundOverview and background

2.2. Body: Tell themBody: Tell them Use top-down approachUse top-down approach Support main pointsSupport main points

3.3. Conclusion: Tell them what you told themConclusion: Tell them what you told them Summarize and emphasize main pointsSummarize and emphasize main points

4747


TipsTips Prepare – practice, practice, Prepare – practice, practice,

practicepractice Eye contact with entire audienceEye contact with entire audience Avoid too much informationAvoid too much information Meet time constraintsMeet time constraints Look and act professionallyLook and act professionally Use visuals effectivelyUse visuals effectively

4848


SlidesSlides Use a large font, 24 pt or moreUse a large font, 24 pt or more

Avoid more than 4 or 5 bullets per pageAvoid more than 4 or 5 bullets per page

Avoid fancy graphics that add no valueAvoid fancy graphics that add no value

Group slides for major points (top-down)Group slides for major points (top-down)

Avoid reading slidesAvoid reading slides

4949

ECE 404 PresentationsECE 404 Presentations

• Your presentation should be 10 to 15 minutes for a project 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.

• Make sure you read Chapter 12 in the text, Evaluation: 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 ?

5050

ECE 404 PresentationsECE 404 Presentations

Good....................OK…....................Poor 4 3 2 1 0 Introduction ___ ___ ___ ___ ___ Clarity ___ ___ ___ ___ ___ Organization ___ ___ ___ ___ ___ Professionalism ___ ___ ___ ___ ___ Communication ___ ___ ___ ___ ___ Conclusion ___ ___ ___ ___ ___ Time limits ___ ___ ___ ___ ___ Completeness ___ ___ ___ ___ ___ Understanding ___ ___ ___ ___ ___ Questions ___ ___ ___ ___ ___

Oral_Pres_Papers.doc

Evaluation and Grade Sheet

Documents

404 lecture powerpointdesign