® Forging new generations of engineers. Introduction to Design Briefs.

Slides:



Advertisements
Similar presentations
By: Stefano Hernandez Joseph Gonzalez and Simon Valdez.
Advertisements

 Team Norms  Norm#1- Treat the members of the team with the upmost respect and how you want to be treated.  Norm#2- Team members need to be notified.
The Design Process Engineering Graphics Dr. Stephen Crown.
Design Brief. design brief One way to define the problem is through the use of a design brief. This concise document (no more than one page) identifies.
Software Requirements
Software Engineering General Project Management Software Requirements
Soft. Eng. II, Spr. 2002Dr Driss Kettani, from I. Sommerville1 CSC-3325: Chapter 1 (cont ’d) Title : Client requirements (Review) Mandatory reading: I.
Engineering Fundamentals and Problem Solving, 6e
Session 7 Page 11 ECE361 Engineering Practice Brainstorming, Trades, Evaluation, and Conceptual Capture.
Design Brief. design brief One way to define the problem is through the use of a design brief. This concise document (no more than one page) identifies.
Copyright ©2014 Pearson Education, Inc. Chapter 3 Requirements and Business Rules Chapter3.1.
Science Fair Project Type your project title here Your name Your teacher’s name Your school.
Dyer Junior High School
Year 7 Independent Learning Task 1
1 Software Process Lecture Outline Nature of software projects Engineering approaches Software process A process step Characteristics of a good.
Team Symmetric By: Samantha Manjarrez, Allen Yang, Dylan Salopek.
CS 350 – Software Design An Introduction to Design Patterns – Chapter 5 A proposition behind design patterns is that quality of software systems can be.
Science Fair Project Type your project title here Your name Your teacher’s name Your school.
Introduction to Design Briefs. Design Brief design brief The engineer will often return to the design brief throughout the design process in order to.
An Introduction to Software Engineering. Communication Systems.
Team Horizontal.  Engineering Notebook daily entries  Day 1 entry dates: 4/15, 4/21, 4/25, 4/27, 4/29, 5/3, 5/5, 5/9  Day 2 entry dates: 4/18, 4/19,
Documentation. Your documentation must fit the needs of your audience. It’s always better to say one thing that is useful, as opposed to many things that.
Experiment Type your project title here Your name.
QUESTION Your name Your teacher’s name Your school.
Lab Safety Cartoon Physical Science Objective –To understand all the lab safety guidelines and explain why they are important. Students will create a poster.
Unit F Supervised Experience in Agriculture/Horticulture.
The Design Process.
Software Engineering REQUIREMENT ENGINEERING. Software Engineering Phases.
Requirement Engineering
SCIENCE FAIR PROJECT Project title Your name | Your teacher’s name | Your school.
Team Offset Locker By: Isaac Arellano Dylan Conter Dylan Conter Marco Pando 8 Slides.
What is technology?. Technology is not… Only things that move Only computers Only things that use electricity.
Type your project title here | Your name | Your teacher’s name | Your school Science Fair Project.
By: Ean Smith Parker Murphy Wyatt Jurney.  Virtual Design Checklist Project Due Date: May 11th (Day 1) or May 10th (Day 2) 1. Engineering Notebook daily.
Lesson One Expository Essay
Design Brief Introduction © 2011 Project Lead The Way, Inc.
EMS Materials Expectations October 2017
Materials (detailed list) Quantity (be specific)
Materials (detailed list) Quantity (be specific)
Materials (detailed list) Quantity (be specific)
Engineering Design Process
Design Notebook Guidelines
Design Brief Gateway To Technology®
Materials (detailed list) Quantity (be specific)
Your name | Teacher’s name | School
Mechanical Project Challenge
Design Brief Design Brief Gateway To Technology®
Design Brief Design Brief Gateway To Technology®
Design Brief Design Brief Gateway To Technology®
Introduction to Design Briefs
Materials (detailed list) Quantity (be specific)
Materials (detailed list) Quantity (be specific)
Writing a Design Brief © 2012 Project Lead The Way, Inc.
Writing a Design Brief Introduction to Engineering Design
Your name | Teacher’s name | School
Materials (detailed list) Quantity (be specific)
Materials (detailed list) Quantity (be specific)
Design Brief Introduction © 2011 Project Lead The Way, Inc.
Design Brief Introduction © 2011 Project Lead The Way, Inc.
Design Brief Introduction © 2011 Project Lead The Way, Inc.
Design Brief Design Brief Gateway To Technology®
2 Engineering Design.
Design Brief Introduction © 2011 Project Lead The Way, Inc.
Design Brief Introduction © 2011 Project Lead The Way, Inc.
Introduction to Design Briefs
Materials (detailed list) Quantity (be specific)
Type your project title here Your name Your teacher’s name Your school
Your name | Teacher’s name | School
Your name | Teacher’s name | School
Presentation transcript:

® Forging new generations of engineers

Introduction to Design Briefs

At the conclusion of this lesson, you will be able to… explain what a design brief is and why it is used in the design process. identify the different parts of a design brief. differentiate between a problem statement and a design statement.

Many variations of the design process exist, and almost all of them require a problem to be defined after it has been recognized. Step #2: Defining the Problem Identify the Problem Step #1 Step #2 Define the Problem Design Process

design brief One way to define the problem is through the use of a design brief. This concise document (no more than one page) identifies the client, clearly states his/her problem or need, details the degree to which the engineer will carry out the solution, and lists the rules and limits within which the engineer must perform. Design Brief

design briefThe design brief serves as an agreement between the client and the engineer. design briefThe engineer will often return to the design brief throughout the design process in order to gage the progress and validity of the creative work. Design Brief

The Client

client The client is usually a person, company, organization, or target consumer group whose problem or need requires the talents of an engineer/designer to develop a physical solution (electrical, mechanical, structural, software, etc).

The Designer

designer The designer is the creative problem- solver. Engineers are only one type of designer. They perform engineering design… the application of math, science and engineering principles to the creation and development of systems components and processes.

Problem Statement

The problem statement clearly and concisely identifies the problem. A problem statement must never imply or state a solution. The solution is not the problem.

Example of a good problem statement: Problem Statement My school locker is a mess. I can never find a pen, pencil or calculator. My homework is always getting lost; my lunch gets crushed under a sea of books and binders. Because of the clutter, it is hard to close my locker door completely.

Example of a poor problem statement: Problem Statement My locker needs a Lockermate™ so that I can get my locker more organized. In this case, a Lockermate™ is a fictitious brand name of an already- existing solution to the problem. Note:

Design Statement

design statement The design statement challenges the engineer to take action to address the need and to solve the problem. It must specify the degree to which the engineer will carry out the solution. The design statement may also contain an underlying theme or very important constraint.

Design Statement design statement A good design statement should not unintentionally bias the engineer’s creative thought process by using terminology that suggests an already existing solution.

Example of a good design statement: Design Statement Design, model, and test a high school locker organization system that will neatly contain items commonly used and kept in school.

Design Statement Design a Lockermate™ for a high school locker. Example of a poor design statement: Redesigning a Lockermate™ is not the purpose of the activity. The word Lockermate™ may serve to bias the designer, and narrow his/her creativity. Note:

Constraints

Constraints Giving an engineer an unlimited amount of time and money to complete a job is impractical. Limitations must be imposed. Constraints Constraints can be thought of as guidelines that must be followed, or rules that must not be broken.

Example of constraints: Constraints TimeSafety BudgetAesthetics Established Codes Materials & Manuf. Processes Physical Attributes (size, weight, color, etc.)

Constraints Often, new constraints are discovered that were not obvious in the beginning stages of the design process. constraints Because constraints are given in list form, they may be added to as the design process plays itself out.

Deliverables