GE 121 – Engineering Design - 2009 Engineering Design GE121 Introduction to Engineering Design (continued) Lecture 2.

Slides:



Advertisements
Similar presentations
System Development Life Cycle (SDLC)
Advertisements

How to Map a Sales Process That Creates Value for Customers! July 2003.
HCI in the software process Chapter 6
The software process A software process is a set of activities and associated results which lead to the production of a software product. This may involve.
SEP1 - 1 Introduction to Software Engineering Processes SWENET SEP1 Module Developed with support from the National Science Foundation.
Experiential Learning Cycle
A GUIDE TO GETTING YOUR ART OUT THERE Public Art: The Art of Place-making.
ARCH-01: Introduction to the OpenEdge™ Reference Architecture Don Sorcinelli Applied Technology Group.
S.T.A.I.R.. General problem solving strategy that can be applied to a range problems.
Project Plans CSCI102 - Systems ITCS905 - Systems MCS Systems.
1 CS 501 Spring 2003 CS 501: Software Engineering Lecture 2 Software Processes.
Chapter 1 Software Development. Copyright © 2005 Pearson Addison-Wesley. All rights reserved. 1-2 Chapter Objectives Discuss the goals of software development.
CS 501: Software Engineering
1 Software project management (intro) An introduction.
Business Driven Enterprise Architecture Assessment Methodology Josh Arceneaux August 16, 2011.
Course Technology Chapter 3: Project Integration Management.
CAREER DECISION-MAKING APPROACHES
Copyright © 2012 Assessment and Accountability Comprehensive Center & North Central Comprehensive Center at McRel.
Performance Management
Lecture 3: Writing the Project Documentation Part I
Enterprise Architecture
The Project AH Computing. Functional Requirements  What the product must do!  Examples attractive welcome screen all options available as clickable.
Undergraduate Engineering Research Day Poster Design for UnERD 2013.
IE398 - lecture 10 SSM in detail
Copyright Course Technology 1999
Systems Analysis And Design © Systems Analysis And Design © V. Rajaraman MODULE 14 CASE TOOLS Learning Units 14.1 CASE tools and their importance 14.2.
Oral Presentations ELEC Objective and Outline 1. Why is the ability to present orally important? 2. What are the components of an effective oral.
IACT 418/918 Corporate Network Management Week 1 Introduction & Assessment SITACS University of Wollongong Bob Brown 2003.
7 STEPS IN CREATIVE PROBLEM-SOLVING The Process of Design.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 4 Slide 1 Software Processes.
MIS 385/MBA 664 Systems Implementation with DBMS/ Database Management Dave Salisbury ( )
Problem Statement Proposed Solution Key Considerations Laboratory Reports Entire Solution Phase I Solution Conclusion Design Team Jonathan Correia, Sean.
Introduction to Interactive Media The Interactive Media Development Process.
Chapter 1 Object-Oriented Analysis and Design. Disclaimer Slides come from a variety of sources: –Craig Larman-developed slides; author of this classic.
Managing your time and career: A personal point of view Eckart Meiburg Department of Mechanical and Environmental Engineering University of California,
Modern Project Management CHAPTER ONE Student Version McGraw-Hill/Irwin Copyright © 2011 by The McGraw-Hill Companies, Inc. All rights reserved. McGraw-Hill/Irwin.
Chapter 7: A Summary of Tools Focus: This chapter outlines all the customer-driven project management tools and techniques and provides recommendations.
ISM 5316 Week 3 Learning Objectives You should be able to: u Define and list issues and steps in Project Integration u List and describe the components.
© Copyright 2011 John Wiley & Sons, Inc.
Process Walk & SIPOC Define Kaizen Facilitation. Objectives Understand the process as a “system” Describe the concept of an entity and how it relates.
PPA 502 – Program Evaluation Lecture 2c – Process Evaluation.
1 Introduction to Software Engineering Lecture 1.
Software Engineering. Introduction Objective To familiarize students to the fundamental concepts, techniques, processes, methods and tools of Software.
1 Software Development Software Engineering is the study of the techniques and theory that support the development of high-quality software The focus is.
ITEC0700/ NETE0501/ ISEC0502 Research Methodology#2 Suronapee Phoomvuthisarn, Ph.D.
An Introduction to Software Engineering
1 CSE 403 Introduction Reading: Rapid Development Ch3.3 These lecture slides are copyright (C) Marty Stepp, 2007, with significant content taken from slides.
1 CS 501 Spring 2004 CS 501: Software Engineering Lecture 2 Software Processes.
1-1 Software Development Objectives: Discuss the goals of software development Identify various aspects of software quality Examine two development life.
Nutrition 564: Management/ Leadership. What is management? Nutrition 564: Management Working with and through other people to accomplish the objectives.
Introduction: definition of a lesson plan It can be simple as a mental checklist or as a complex as a detailed two-page typed lesson plan.
The Project Plan Plan Your Work, then Work Your Plan
1 The Software Development Process ► Systems analysis ► Systems design ► Implementation ► Testing ► Documentation ► Evaluation ► Maintenance.
Introduction to Management LECTURE 16: Introduction to Management MGT
Implementing a Writer’s Workshop
UTA/ARRI. Enterprise Engineering for The Agile Enterprise Don Liles The University of Texas at Arlington.
Software Production ( ) Lecture 3: Dr. Samer Odeh Hanna (PhD) office: 318.
CSCI 383 Object-Oriented Programming & Design Lecture 7 Martin van Bommel.
Project Management Methodology Project Closing. Project closing stage Must be performed for all projects, successfully completed or shut off by management.
Teaching Study Strategies Using WYNN Peggy Dalton
Yellow Belt Ninja: Quest for the Strategic Guru. This is the framework used for the reflection and goal setting journey of the GE Ninjas and their teams.
Project Management PTM721S
Object-Oriented Software Engineering Using UML, Patterns, and Java,
Basic Management Functions
Welcome W 3.1 Introduction to Engineering Design II (IE 202)
Project Management Process Groups
Introduction to Engineering Design II (IE 202)
Chapter Four Engineering Communication
Chapter Four Engineering Communication
Chapter Four Engineering Communication
Presentation transcript:

GE 121 – Engineering Design Engineering Design GE121 Introduction to Engineering Design (continued) Lecture 2

GE 121 – Engineering Design Assumptions Behind the Engineering Design Definition  Design is a thoughtful process that can be understood  There are tools that can help us support decision making / design management  Tools add to and support the creative process  We cannot deduce form (shape, geometry) from function (what artifact is required to do)  Design Specifications help guide us to form, and are a result of a process. Client Objectives  Means  Functions  Metrics

GE 121 – Engineering Design Assumptions Behind the Engineering Design Definition (cont’d)  Fabrication Specifications (set of plans to fabricate object / artifact) enable fabrication independent of designer’s involvement.  Newer design methodologies integrate fabricators/manufacturers into the design process (will be discussed later)  Communication is a key issue in design  Some Design Languages Spoken or written Numbers / Equations Rules Charts or Pictures

GE 121 – Engineering Design More On Design / Engineering Design  Design has been going on for a very, very long time  People have been talking and writing about design for a long time, but not nearly as long as design has been going on  Why design is hard  Suggestions that design is like learning to dance or ride a bike

GE 121 – Engineering Design Evolution of Design Practice / Thinking  Flint knife  Designing and Making inextricably linked  Must have put thought into process  Trial and error  Great Pyramids, Mayan Temples, Great Wall of China  Must have been designed  No ‘Paper Trail’  Modern Design  Fabricator typically NOT the designer  ‘Craft’ typically fabricated by designer

GE 121 – Engineering Design Evolution of Engineering Design  Engineers produce Fabrication Specifications  Separates Designing from Making  Typically blueprints, circuit diagrams, flow charts  May not capture design intent – Hyatt Regency walkway (Kansas City) 114 people died Could not be fabricated as designed (threaded rod not available on required length) Like two people hanging on a rope, versus one person hanging onto another person’s foot

GE 121 – Engineering Design Evolution of Engineering Design (cont’d) Fig. 1.4 p10

GE 121 – Engineering Design Evolution of Engineering Design (cont’d)  New Idea is Concurrent Engineering  Specialists from manufacturing / purchase / support / use / maintenance (essentially product life cycle) all considered/consulted throughout the design process  Communication of design intent is extremely important, right through to fabrication and life cycle

GE 121 – Engineering Design A Systems-Oriented Definition of Design  Herbert Simon, a founding father of design theory – Definition  As an activity, design is intended to produce an artifice in terms of its organization and functioning – its interface between inner and outer environments  Designers are expected to:  Describe the shape and configuration of a device/process/product (organization)  How that device/process/product does what it is intended to do (function)  How the device/process/product (inner environment) works (interfaces) within its operating (outer) environment

GE 121 – Engineering Design Engineering Design Addresses Hard Problems  Design Problems are Ill-Structured  Cannot normally be found by applying mathematical formulas or algorithms in a routine or structured way  Design Problems are Open-Ended  Usually have several acceptable solutions  Problem is generally not finding one exact solution, but having too many solutions from which to choose

GE 121 – Engineering Design Learning Design By Doing  Learning by Doing  Studio aspect like riding a bike, throwing a ball, painting or dancing – watch what I do, then try to do it yourself  Use drills and exercises – that’s what we are trying to do in this course, and other design courses that will follow  Rely on coaching – we will try to help you through the process  Pay attention wherever you can to skilled practitioners – we have Engineers in Residence to help us out

GE 121 – Engineering Design Managing Engineering Design  Good Design doesn’t just happen  Management achieves organizational goals by planning, organizing, leading and controlling  Planning – the process of setting goals and deciding best how to achieve them  Organizing – the process of allocating and arranging human and non-human resources so that plans can be carried out successfully  Leading – ongoing activity of exerting influence and using power to motivate others to work toward reaching organizational goals  Controlling – process of monitoring and regulating the organization’s progress toward achieving goals

GE 121 – Engineering Design Activity  Take a few minutes to get a copy of your Project Proposal ready  We will provide more details in the next section to help you refine it Note: Epsilon Lab (2A23) is reserved for our use during class and lab times.