At Level 1 a student should be able to-
– Understand what is relevant data to the project; and what is deemed irrelevant.
Clarify the Task
At this stage should not have formulated any solutions. You’ve have gathered your thoughts in response to the brief and began to formulate what you think the customer wants. You simply want to be checking with the customer that your interpretation of their requirements is correct. This is generally completed at the same time as Understanding the Brief, as you don’t want to be research irrelevant data.
For example, the customer states to four members of a design team; “I’d like a chipboard cupboard that can be assembled at home using wingnuts and without the need for specialist equipment.”
Person A – Has a history of building cupboards from a previous job and understands perfectly.
Person B – Thinks the customer would like to put books in this cupboard and notes that it must have shelves.
Person C – Generally works on aesthetics and thinks a wingnut is what holds an aeroplane’s wing on, but is too shy to ask if he’s correct.
Person D – Has only ever seen chipboard in his kitchen worktop and surmises that it should be made from 38mm deep worktop material.
The meeting disperses and each is sent away to research their relevant area.
Each person is correct from their own perspective. They then begin to gather information; Person C in particular has researched a new design of Titanium alloy rivet that has replaced the need to use nuts to attach wings to aircraft. Obviously this is irrelevant and highlights the requirement of Clarifying the Task. If you’re working alone or with a group it’s important top ensure each part of the customer’s requirements are understood.
There is little better method for this than simply ensuring with each person in the group has fully understood, or if working alone, you’ve clarified the task with the client.
Scope
The Scope of a project defines it boundaries; where it should stop, and states what will be researched. This is particularly important in reducing the possibility of researching irrelevant areas. This states what the project is and what it is not; what it will cover and what it will not cover. This is important, many projects uncover new research areas as they progress, which in unclear may result in wasted time and therefore money. This example is for the design of an aluminium can crusher from Haik and Shahin (2011: 114). It defines what is within the scope and what is outside the scope of the project.
Within the Scope – “Design a device that will crush aluminium cans. The device must be fully automatic (i.e,
customer simply loads machine, it switches on automatically). It should crush the can, eject it and automatically switch off. The following are required;
· The device must have a continuous feeding mechanism.
· Cans should be in good condition without dents.
· Can must be crushed to 1/5th of it’s volume.
· Max dimensions of entire device should be < 450 x 450 x 300 mm.
· Performance based on cans crushed per minute.
· Device must be standalone.
· Should be operable by children aged 8+.
· Final design should retail <£200.”
Haik and Shahin (2011: 110)
All of the above can be considered to be with this scope of the project. However, there are a number of areas could be suggested that are not stated.
Outside of the Scope
Optimum can design to for liquids
Including a function to repair cans before crushing
Function for testing if can is aluminium
Ability to crush other recyclable items
Future developments to make device portable
Automated uplink to central server stating when device is full
A person’s attitude to recycling and methods to increase awareness of recycling
Future developments to create models for international markets.
All of the above scenarios could quite easily slip into the focus of the design and lead a project off track. Before the project gets too far, make clear where boundaries of the project to eliminate time wasted. Scope of Project also features in writing the Product Design Specification.
Mobile Phone analogy
As an example, if the project Title is “How a mobile phone works”. You might reply, “it unlocks with this swipe, then I check my emails with this app. To make phone calls I press this button, dial a number and press the green phone”.
What could ensue, is an entire project that tells me how to use this app, down to the detail of programming in proxy settings for email clients. This would be irrelevant as this simply describes the “use” of a mobile phone, the title was, “how a mobile phone works”.
A mobile phone works by a Li-on battery storing energy and by way of a series of PCBs transmits the power to various chips that feature various semiconductors making binary switches in the circuit which combine to form a signal to the ear-piece when activated such that the user may hear the signal being transmitted via the antennae.
How a mobile phone actually works is very very complicated. Figure1 has a very basic flow diagram.
Be sure to fully clarify the scope of the project and if compiling research, always ask yourself if it’s relevant.
Figure 1 – Basic mobile phone operation (Celtnet.org.uk 2011)
Back to Planning and Clarification
Back to MAE Design Model