Project Reports:W itt d O lWritten and Oral

Jeffrey DonnellMRDC 3104 894-8568

1

Project Report I

Limited to 3 pages (plus displays)Week of June 27Week of June 27

– Problem Understanding• Spec SheetSpec. Sheet• Function Tree

– Morph Chart / Solution MatricesMorph Chart / Solution Matrices– Other planning tools

2

Project Report II

Limited to 5 pages (plus displays)Week of July 11Week of July 11

– Problem DefinitionSelected System– Selected System

– ConceptsC t E l ti– Concept Evaluation

– Preliminary Results (as available)

3

Final Reports W k f J l 25Week of July 25

Written Reports:Less than 10 pages of textp gAppendices (as needed)Figures may be integrated with textg y g

Oral Reports:Oral Reports:10 minutes (maximum) / 11 slidesOne Speaker

4

One SpeakerClearly labeled figures

Things you don’t reportg y p

• How many meetings you held• Who was in charge of what subsystemg y• Anything about brainstorming• Design disputes within the groupg p g p• The long process of tweaking

5

Things you DO report

• The objective of the system developed by [your] team

• What was constructed • Why the favored design was selected• How it performed

– Did it meet expectations?

• Evaluation / analysis of performance and of design

6

Information to Include in Final Report

• Problem definition• Final DesignFinal Design• Discussion of the design

– Specification Sheet Present these l if th– Function Tree

– Morph Chart– Management & Planning Tools

only if they help you

t fManagement & Planning Tools– House of Quality– Concept alternatives

Concept Evaluation(s)

account for performance or

l i– Concept Evaluation(s)• Performance and Evaluation• (Bill of Materials)

explain your design!

7

( )

Format for Final Report

• Cover sheet• Abstract• Table of Contents• Introduction, with problem statement• Design overviewg• Subsystem descriptions• DiscussionDiscussion

– Planning, concepts, evaluation, results, analysis

• Conclusion

8

Introductions in the final reportp

What functional goal was emphasized?

What challenges had to be addressed?

What solution was developed?

9

Design Introduction:A i fAn overview of a complex system

• What does the assembled system look like?– Cite an overview drawing here

• What objective is it designed to meet?• What are its main components / features?• In what order will those components be described?

10

Component Description:i fThe details of a complex system

• Which subsystem / component is this?– Insert illustration

• What function or goal does it address?• What are its features?• How does it work?

(as needed)( )• What problems does it raise?

Repeat until done!

11

Repeat until done!

Discussion:Justify the system and / or Analyze the resultJustify the system and / or Analyze the result

How was this design selected? / How did it perform?How was this design selected? / How did it perform?

• What Planning Tools were used?(How were they used?)

• What alternatives were developed?(Displa representati e concepts)(Display representative concepts)

• Why was this design selected for competition?(Display evaluation materials)(Display evaluation materials)

• Did the system perform as expected?(Describe and evaluate performance)

12

Performance analysisy

• Describe competition results• Compare the obtained results to predictionsp p• What could you change to improve performance?

Did you use the right evaluation criteria?Did you explore enough concept alternatives? Did you focus on the best way to score points? Were your specifications right?

13

Closing summaryClosing summary

• What design was built for competition?• Why was this design pursued for competition?y g p p• What result was obtained?• What changes would bring a better result?g g

14

Information for Final Presentation

• Introduction: Identify group, goals and competition score.y g p, g p• Final Design: Present system goals / strategy• Overview of Device: Describe assembled systemOve v ew o ev ce: esc be asse b ed syste• Subsystems: Describe the individual tasks• Bill of MaterialsBill of Materials• Actual Performance• Analysis of performance: What worked didn’t work what• Analysis of performance: What worked, didn t work, what

you would change to improve your score. • Closing Summary

15

Closing Summary

An Effective Presentation

• Display an overview of the complete system first• Provide Slide Titles or descriptive captions for all

figures• Provide labels for all system elements

– Labels reflect a consistent level of detail in each d idrawing

– Color is used lightly to distinguish components

effective presentations distinguish and describe system elements

16

The Carnival Project

Carnival Goals were:

• Win at HorseshoesK k d h ilk b l• Knock down the milk bottles

• Collect treats

17

The Carnival Arena

18

Carnival Presentation 1in line drawingsin line drawings

• Assembled, integrated system is shown before subsystems are presentedC l b i h b f i• Complete subsystem is shown before its components are presentedL b l ll tt ti t t t th t d ib d• Labels call attention to structures that are described.

Please Note:1 S d l i h b d f hi1. Scores and analysis have been removed from this

student presentation. 2 Di i t i d f C i l d i

19

2. Dimensions were not required for Carnival drawings

Final Design: A Stationary SystemScissor ArmScissor Arm for Horseshoes Weight Arm

to powerTreat Retriever

to power scissor arm

20

Double Sweeping Arms for Bowling

Sweeping Arms Subsystem Deployed

Pull String

Trigger Mousetrap Sweeping

Arms

Trigger Pin

S

21

Sweep Mousetrap

Scissor Arm Subsystem Deployed Horseshoe Mount

Scissor Arm

Pivot arm Weight

HorseshoeBracket

S t R d

Rod Pull String

22

Support Rod

Catapult Subsystem Deployed

Weight

Launch Tube

Weight

Hook for Treats

Pull String

23

Motorg

System Fully Deployed

24

Judging

• Look like a team

• Demonstrate your system

• Prepare a display board

• Convey enthusiasm

25

Convey enthusiasm

Design Review Presentations(How to Prepare)(How to Prepare)

• Give descriptive titles to your systems and subsystems

• Decide how to demonstrate functions without breaking the device

• Review the strong points—and weaknesses—of your system

26

Design Review Tips(During the Judging)(During the Judging)

• State which points your system is designed to collect

• State what design / performance qualities will make your system advance to the final round

• Show judges what your system does:– Extend drawer slides, Deploy arms, sensors, etc.

27

A typical poster design is presented on the next slide. This is a reasonable starting point g pfor the posters you might prepare for the pre-competition judging. p j g g

28

29

Sample Judge QuestionsSample Judge Questions(General)

• How many points does a team need in order to advance?advance?

Wh t th h t i ti f i i• What are the characteristics of a winning system?

• Which other team is most likely to win? Why?

30

Sample Judge QuestionsSample Judge Questions(Specific)

• What makes your system a winner?

• What does your system do?

• What is unusual about your system?

• What could go wrong for your system?31

• What could go wrong for your system?

System Demonstration• State what points you mean to score• State what points you mean to score

Sh hi h b t hi h i t• Show which subsystems score which points

• Describe operation

• Explain what you’re most pleased with

32• Explain what is most likely to go wrong