Professional Documents
Culture Documents
Welcome!
What is design
The process
Example of one design process
What you’re in for
- Goals
- Schedule
- Grading
- Logbook
- Exam
What is design?
What is design?
• Painting
• Brooklyn Bridge
• 4-Pines Brewery
What is a GOOD design?
Good Designs - Functional
Good Designs - Attractive
Good Designs - Simple
Good Designs – Cost effective
Good design? Not until its tested!
Simple
Elegant
Functional
Freezing O-rings
Wind shear
Catastrophic failure
The Fix
The Point—
5. HONEST REPORTING
• Research
• Conceptualisation
• Feasibility / Requirements scoping
• Conceptual design
• Detailed Design
• Prototype
• Test
• Refinement
• Tooling, Production, Manufacture…
Other Related Methods
Testing Wargaming
Low complexity
Modular Design
Highly structured
Difficult to change
Design Methodologies – “Spiral”
Emergent Design
Extends Waterfall
User focused
Small teams
Rapid development
Role focused
Organised “scrums”
Scrum
Product
Master
Owner
Team
For Example…
For Example – “Request for Proposal”
“Design a bottle that can allow easy consumption of liquids in zero gravity”
Integration information
1-g
0-g
For Example – Conceptual Design
For Example – Detailed design
3D CAD (Solidworks)
Simulation testing
https://www.solidworks.com/sw/resources/solidworks-tutorials.htm
Grading
LATE = 0
A professional reference
Capture your development process
A legal document, part of intellectual property
Engineers, scientists
Part of your assessment!
Logbook – The Good
The Standard:
1. Hard bound book. No binders
2. Only in ink
3. Keep it organised: Date/titles and
sequential
4. Label everything
5. Clean enough to be duplicated
When to use?
Meetings, brainstorms, sketchings, diagrams, plots, test results, random thoughts…
Searches, epihpanies, calculations, and ANYTHING related to your project
Logbook – The Bad
Common mistakes:
1. Information missing
2. No date
3. Missing context: Reasons and
conclusions
4. Using White-out
5. Blank pages, torn out pages
6. Missing labels
The Exam
The Project
Project