1. Engineering Design – Part (1)
By:
Dr. Mouaaz Nahas
Engineering Design and Research
Methods
802602-3
Umm Al-Qura University
Electrical Engineering Department
2. Agenda
What are Design, Development and Product?
Identifying Customer Needs and Target Specifications
Engineering Design (ABET Definition)
Front End Engineering Design
Elements of Engineering Design Process:
– Problem Statement
– Problem Identification / Literature Review
– Problem Definition
– Objectives
– Mission Statement
– ……………………. (continued in the next slides)
Example: Pilgrims Health in Hajj
3. What is Design?
Design refers to those activities involved in:
Creating the styling, look and feel of the
product.
Deciding on the product's mechanical
architecture.
Selecting materials and processes.
Engineering the various components necessary
to make the product work.
4. What is Development?
Development refers jointly to the entire process of:
Identifying a market opportunity (customers’ needs).
Creating a product to appeal to the identified
market (satisfying the customers’ needs).
Testing (for technical specifications to meet the
customers’ needs).
Modifying and refining the product (refining the
technical specifications) until it is ready for
production.
5. What is Product?
A product can be any item from:
A book
A musical composition
Information service
to an engineered product such as:
A computer
A hair dryer
A washing machine
6. Identifying Customer Needs
Team identifies customer needs by gathering
information through:
Interviews with potential purchasers
(customers).
Focus groups (a small group of representative
people who are questioned as part of market
research).
By observing similar products (competitive
products) in use.
7. Identifying Customer Needs –
cont.
The list of needs will include:
Hidden Needs: Customers may not be aware
of these needs or customers simply accept
problems without question.
Explicit Needs: Potential purchasers
(customers) most likely will report these needs.
8. Identifying Customer Needs –
cont.
Team develops the necessary information (Target
Specifications) based on customers’ needs to assess
and compare the following:
Performance
Size
Weight
Life
Other specifications of the product
Customer needs and product specifications are organized into a
hierarchical (ordered) list with a comparative rating value given to each
need and specification.
9. Target Specifications
Engineers are involved in establishing Target
Specifications of the prospective new product or project
based on:
– Customers’ needs
– Review of competitive products (or available projects).
Target Specifications: are basically a list of desired
things limited by known Technical Constraints.
After initial product concepts (or project ideas) have
been generated, the Target Specifications are refined to
justify technical, manufacturing, and economic
constraints.
10. What is Engineering Design?
(ABET Definition)
Engineering Design: is the process of devising a
system, component, or process to meet desired
needs.
It is a decision-making process (often iterative), in
which the basic science and mathematics and
engineering sciences are applied to convert
resources optimally to meet a stated objective.
11. Front End Engineering Design
It is early and basic design, to accurately
discover what resources will be needed.
Or the engineering and design work completed
as part of pre-project planning, done before
more detailed design.
12. Problem Statement
Is a clear concise description of the issue(s)
that need(s) to be addressed by a problem
solving team.
Or basically a statement that illustrates a clear
vision and the overall method that will be used
to solve the problem at hand.
Or a concise description of an issue to be
addressed or a condition to be improved upon.
13. Problem Identification / Literature
Review
Problem Identification: is part of the scientific
method serving as the first step in a systematic
process to identify, evaluate a problem and
explore potential solutions.
Literature Review: is a summary and
explanation of the complete and current state of
knowledge on a limited topic as found in
academic books and journal articles.
It is the first step to successful problem resolution.
14. Problem Identification / Literature
Review – cont.
You will establish the need for your design in this section.
The advisor of your project understands the need, but the real
audience is not yet convinced that you fully understand the
need.
In this section, you will make assertions (statements without
support) about the problems that have triggered (initiated) the
design you are doing.
Do not just make the assertions – rather, back up your
statements with evidence.
That evidence generally will be references from articles or books
that are well recognized and respected. The evidence could also
be surveys or testimonies (the statements or declarations of
witnesses under oath) of users.
15. Problem Identification / Literature
Review – cont.
To accomplish this part, you have to ask the following
questions to the problem statement writer:
Why is it important to solve this problem?
What kinds of solutions to this problem are already
available?
What are the assumptions before solving this problem?
Under what constraints this problem needs to be solved?
What are a few resources to look at for the solution of this
problem?
16. Problem Identification / Literature
Review – cont.
This part of the work may include:
Writing about customer needs by interacting
(asking questions) with the problem statement
writer / doing research.
Providing some statistics showing that the
problem you are working on needs attention (i.e.
it is very important to work on this problem).
After getting the response to all questions, you as a team need to write at
least two paragraphs of literature (internet / journal / book) review.
17. Problem Definition
Is a detailed and operational description of the
difference between the existing situation and the
desired situation.
Here, you set up the problem, to prepare the reader,
without discussing the proposed design solutions.
The reader will know the proposed design solutions
in the sections following Problem Definition Section.
You need to write one paragraph about the project. What are your team
members proposing or planning to do in this project to solve the problem
written in the problem statement.
18. Objectives
Here, you formally state your design proposal.
Normally, the design has two to four definite
objectives. You might consider listing them vertically
as follows:
(1) First design objective
(2) Second design objective
(3) Third design objective
The vertical listing of objectives make it easier to
find them if the reader returns to this section to
review those objectives.
19. Objectives – cont.
If your design objectives are complicated and
depend on variables, then you may place them in
the form of a table.
Here, you would discuss in detail the following:
– What you mean by the different design objectives.
– What you intend to do to achieve those objectives.
– A justification of what you will not do that your audience
might assume.
You might consider writing a paragraph for each objective.
20. Mission Statement
Elements of Missions Statements:
1. Title
2. End-Project/Product/Device/Process Description
3. Benefit Proposition
4. Primary Market
5. Secondary Market
6. Assumptions
7. Constraints
8. Stakeholders / Customers
21. Mission Statement – cont.
This format must be followed in writing the “Mission Statement”.
