Introduction to Engineering Design - PowerPoint PPT Presentation

1 / 17
About This Presentation
Title:

Introduction to Engineering Design

Description:

To demonstrate that you have 'an ability to identify, formulate and solve engineering problems' ... Or bogged down. Or hung up waiting. This Concludes the Presentation ... – PowerPoint PPT presentation

Number of Views:37
Avg rating:3.0/5.0
Slides: 18
Provided by: TimJo3
Category:

less

Transcript and Presenter's Notes

Title: Introduction to Engineering Design


1
Introduction to Engineering Design
  • Tools Tactics of Design
  • Presented by Prof. Tim Johnson
  • Wentworth Institute of Technology
  • Senior Design

2
Why do we take Senior Design?
  • To demonstrate that you have an ability to
    identify, formulate and solve engineering
    problems.
  • To provide a forum for you to learn how to
    function on a multi-disciplinary team.
  • We expect that you will make decisions that have
    consequences, manage a project, communicate with
    team members and others, and collaborate.
  • We take Senior Design to learn by experience and
    study the Design Process.

3
The 4 Step Design Process(the phases described
starting on page 5 in the text)
  • Defining the Problem
  • Formulating Solutions
  • Developing Models and Prototypes
  • Presenting and Implementing

4
Step 1 Defining the Problem
  • Students have now had about 2 or 3 weeks in the
    class.
  • Some student projects have started to come
    together. Some havent.
  • Whats expected at this point?
  • By submitting the proposal, the students will
    have completed the 1st step in the design process.

5
The 1st Step consists of(from Fig.1-4, page 6)
  • Forming the problem statement
  • You have to be solving a particular need
  • Identifying the functional requirements
  • Start your Block Diagram
  • Recognizing constraints and limitations
  • You are undergraduates
  • Defining a Schedule and forming a team
  • Become familiar with MSProject

6
Have you recognized a Need?
  • Anything worth doing will involve a risk of
    failure.
  • If it was easy, itd be solved all ready.
  • If you are not pushing the limits of your
    learning, youre not trying.
  • What is it that youd want to be remembered for?

7
Getting ready for the Preliminary Proposal
  • Define the project in 25 words or less.
  • Give it a catchy name.
  • Begin scoping out what the project needs to make
    it work so you can answer some easy questions.
  • Float this idea with the Professor.
  • You are negotiating what it is that you will be
    working on, the functionality of the design, and
    justification for your team.

8
Steps to the Proposal1. Goal Setting
  • Revamp your preliminary proposal into an
    abstract.
  • Add a history by describing current solutions.
  • Illustrate how they fall short of consumer needs.
  • Point out how your design will satisfy these
    needs.

9
Steps to the Proposal2.Identifying the Objectives
  • The objectives are the functional requirements of
    the design.
  • These are found by defining the inputs and
    outputs to the block diagrams.
  • The initial inputs are the conditions that you
    seek to change. The final outputs is your
    solution. You are doing a Functional Analysis of
    your project.
  • Telling what you expect this project will do (in
    the abstract) when finished helps identify the
    objectives.

10
Steps to the Proposal3. Recognizing Constrains
  • As you visualize the project, there should be
    some constraints or limits on what it is that you
    are able to design.
  • Some constrains are obvious but need to be
    stated.
  • Where needed, use COTS (commercial-off-the-shelf)
    products and add functionality.
  • Aim high.

11
Steps to the Proposal4(a). TEAM Building
  • Tackle the problem
  • The problem is big enough to occupy more than one
    persons time.
  • Evaluate the problem
  • Divide the problem up in time slices
  • Set up concurrent and sequential components
  • Assign the problem
  • Match up the team members skill set to the
    problems difficulty
  • Measure the problem
  • Make your team results driven

12
Steps to the Proposal4(b). Scheduling
  • The project, if it requires a team should have
    various components.
  • Team members can ( should) work independently on
    these components.
  • You become a team when everything fits together
    at the end.
  • You force yourself into the team mode by
    scheduling.

13
Steps to the Proposal4(c). Schedule Components
  • Block Diagram
  • Functional Analysis
  • Schematic Design
  • Model simulation
  • Parts Ordering
  • Prototype Assembly
  • Communicating the Design

14
Steps to the Proposal4(d). Learning Components
  • Web site building
  • Power Point presentations
  • MSProject
  • Other items unique to your project
  • Research
  • Technical skills
  • Public speaking
  • assistance available in various forms at my web
    site

15
Steps to the Proposal4(e). Reading
  • Text references
  • Read Chapter 1 through 3
  • Of special importance are
  • Figure 1.4, page 6
  • Figure 1.7, page 19
  • Figure 3.4, page 63
  • Journal suggestions
  • Figure 3.3, page 58
  • Project Scheduling, page 99ff.
  • Writing Proposals, page 108ff.

16
If you know where you are going
  • You wont get lost
  • Or bogged down
  • Or hung up waiting

17
This Concludes the Presentation
  • You can review this presentation again at the
    professors web site.
  • Before we move to the next subject, are there any
    questions?
Write a Comment
User Comments (0)
About PowerShow.com