Mechanical Analysis and Design

ME 2104 Plan for today

Lecture 4
Design Process
Requirements Customer requirements
» Objectives tree method
Team meeting
Prof Ahmed Kovacevic Project assignment
School of Engineering and Mathematical Sciences » Tennis ball server
Room C130, Phone: 8780, E-Mail: a.kovacevic@city.ac.uk
www.staff.city.ac.uk/~ra600/intro.htm

Ahmed Kovacevic, City University London Ahmed Kovacevic, City University London

The Engineering Design Process

Engineering Design Process 2nd
Phase 1 - Vision Edition, Chapter 4

Phase 2 - Concept » Expand requirements from the needs

statement
Phase 3 » Prioritize requirements according to
importance
Phase 4 - Design
» Organize requirements into an objective
tree
Product
Phase 5

Ahmed Kovacevic, City University London Ahmed Kovacevic, City University London

Phase 1: Clarify Problem

Without Design, there is no product!

1. Clarify Objectives – The Objectives tree
method With a poor design, no matter how good the manufacturing
- Prepare list of objectives
- Order the list
methods are, or quality control, etc, the end product will still be a
- Draw the objectives tree bad idea and no one will buy
2. Establish user requirements Most people will buy something based on the design followed by
3. Identify constraints the quality
4. Establish functions
- Create ‘black box’ model of the product
What about cost?
- Break down overall function in sub-functions
- Connect sub-function chains together
- Define the system boundaries (Constrains)

Ahmed Kovacevic, City University London Ahmed Kovacevic, City University London
Most end-users do not know/care about the details or technical Everyone has a different opinion / desire on how a product
features of a product. should be designed…
They look only at the design … both the functionality of the Customers of a product are NOT just the end-users.
product and the way it looks. Who do you think are customers of an airplane?
Think about how people choose to buy a kettle or even a mobile Customers include the people that manufacture, maintain, sell,
phone. dissassemble… etc.

Ahmed Kovacevic, City University London Ahmed Kovacevic, City University London

Accounts

Ahmed Kovacevic, City University London Ahmed Kovacevic, City University London

Requirements are a ‘wish list’ that the product needs to do.

This is usually given by the customers or sponsors or even as a
list of requirements in the designer’s mind
They are not usually technical
E.g. for a coffee cup … ‘something that will hold coffee’ etc..

Ahmed Kovacevic, City University London Excerpt – See book for full table Ahmed Kovacevic, City University London
 Ahmed Kovacevic, City University London Ahmed Kovacevic, City University London

Ahmed Kovacevic, City University London Ahmed Kovacevic, City University London

The Objectives Tree Method The Objectives Tree Method (1)

The objectives tree method is an approach to
transform vague design statements into more Three step procedure:
specific customer requirements 1. Prepare a list of design objectives
Make vague statements more specific by 2. Order the list into sets of higher-level and
asking: lower-level objectives
– What is meant by that statement? 3. Draw a tree of objectives, showing
Other useful questions to ask when expanding hierarchical relationships and
and clarifying design objectives: interconnections
– Why? How? What?

Ahmed Kovacevic, City University London Ahmed Kovacevic, City University London
Objectives Tree Method Objectives Tree Method

Step 1: Listing the Objectives Step 2: Ordering the List

This can be done by: Group the statements into related topics
» Talking with (interviewing) customer using an affinity diagram
» Thoroughly reading any written design Design
Objective
statements and requirements
Take vague statements and make them
clearer by asking “what is meant by this
statement”

Ahmed Kovacevic, City University London Ahmed Kovacevic, City University London

Objectives Tree Method Objectives Tree Method

Affinity Diagram Step 3: Draw the Tree

Copy design objectives to post-it® notes The Objectives Tree diagram looks like an
Place one on a board “upside-down” tree
Compare next objective card to the first » The overall objective of the tree is at the top
» If different, begin a new column » Underneath it, branches
» If similar intent, place under the first column break the objective
into more detailed
Repeat for all design objective cards objectives
Result: Objectives sorted by similar statement » Can have many
» Within each column there may be levels of objectives levels and
» Lower-level objectives answer the question “How?” interconnections
» Higher-level objectives answer the question “Why?”
Ahmed Kovacevic, City University London Ahmed Kovacevic, City University London

Objectives Tree Method

Step 3: Draw the Tree (1) Example: Bumble Ball
The objectives
tree diagram
may alternatively
be drawn on its
side
Example: Car As a team, generate a list of objectives for the
door bumble ball toy
Complete the affinity method for ordering the
objectives in class
Draw an objectives tree for the bumble ball
Ahmed Kovacevic, City University London Ahmed Kovacevic, City University London
 Deliverables for Week 4 Team meeting
» Notebook
» Work agreement
» Team roles
» WBS
» Calendar
» Gantt Chart
» Meeting minutes from last week
» Objectives tree

Ahmed Kovacevic, City University London Ahmed Kovacevic, City University London

Project assignment Testing

Ahmed Kovacevic, City University London Ahmed Kovacevic, City University London

What to do Deliverables
Teams will provide weekly memo reports documenting their progress
» Group notebook and Personal logbooks
Teams will have three design reviews, and the final presentations on
dates specified in the Timetable.
» Project review 1 – Vision (Report and PPT Presentation)
» Project review 2 – Concepts (Report and PPT presentation)
» Project review 3 – Detailed design (Report and PPT presentation)
» Final report – ‘Dragons den’
(Prototype, Report – Marketing, business, technical, PPT presentation,
poster and user manual)

Ahmed Kovacevic, City University London Ahmed Kovacevic, City University London
Project assignment

Ahmed Kovacevic, City University London