Conceptual Design.

Slides:



Advertisements
Similar presentations
Prototyping Teaching materials to accompany: Product Design and Development Chapter 12 Karl T. Ulrich and Steven D.Eppinger 2nd Edition, Irwin McGraw-Hill,
Advertisements

Technology readiness levels in a nutshell
The WINSS School Improvement Planning Tool: An Overview.
Quick Recap. Quick Recap The Project Plan Plan Your Work, then Work Your Plan.
Winter 2015 ECEn 490 Lecture 10 Prototyping 1 Prototyping and Design Standards.
Case-study: PCS handheld unit Prototyping for design exploration.
© conchango Agile Architecture Microsoft Architect Insight Conference Howard van Rooijen
The basics of quantifying qualitative scenarios By Gerald Harris Author, The Art of Quantum Planning.
GAI Proprietary Information
1 Human-Centered Design I Presented by: Craig Titus EPICS High Workshop – Summer 2010 Lecture: Human-Centered Design Presented By: Craig Titus.
CS CS 5150 Software Engineering Lecture 5 by Stephen Purpura Matching Process to Risk.
Copyright 2002 Prentice-Hall, Inc. Chapter 1 The Systems Development Environment 1.1 Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer.
Teaching materials to accompany:
Designing a Product Product design is usually a problem that requires a creative Design and/or manufacturing solution.
Team Members: Brian Barnes Jason Featherman Matt DeWitt Chris Blanchard.
1 Introduction to System Engineering G. Nacouzi ME 155B.
Chapter 5: Project Scope Management
1 SPIRIT Silicon Prairie Initiative on Robotics in Information Technology Engineering Design Tools.
Program Management Satisfy requirements of all individual projects with minimal resources Human resource is the most expensive Leadership Methods of documenting.
1 Focusing on the FCAT/FCAT 2.0 Test-Taking Strategies Grades 3-5 Nancy E. Brito, Department of Assessment , PX47521.
Teaching materials to accompany:
Barry Murash MBBit Nortel 2007
Copyright 2001 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Chapter 1 The Systems.
 Copyright © 2010 Pearson Education, Inc. Publishing as Prentice Hall Chapter 7 Quality and Innovation in Product and Process Design.
Chapter 8: Problem Solving
Shad Valley MUN Introduction to Product Design and Development
1 Portfolio Management – Agile How to plan like a VP Highsmith, Ch 12 CSSE579 Session 6 Part 2 One company’s software product portfolio.
Copyright 2002 Prentice-Hall, Inc. Chapter 1 The Systems Development Environment 1.1 Modern Systems Analysis and Design.
BAB 11 : Prototyping. Dira Ernawati, ST. MT - P3 2 Prototyping An approximation of the product along one or more dimensions of interest –Industrial designers.
Engineering Design By Brian Nettleton This material is based upon work supported by the National Science Foundation under Grant No Any opinions,
1 ISA&D7‏/8‏/ ISA&D7‏/8‏/2013 Systems Development Life Cycle Phases and Activities in the SDLC Variations of the SDLC models.
Lecture 4 Title: The Scope Management Plan
Requirements Engineering CSE-305 Requirements Engineering Process Tasks Lecture-5.
1 CONCEPT GENERATION AND SELECTION SUMMARY Need Required functionality Concept 1 Concept 2 Concept 3 … Concept n QFD Functional Decomposition Morphological.
HCI in Software Process Material from Authors of Human Computer Interaction Alan Dix, et al.
InverstorTech Hadas Mendes. Last Few years ? √ What was missing? - BackWeb Market analysis Product defects (bugs) Higher costs Poor Timing (and positioning.
Engineering Design GE121 The Design Process (continued – Part III)
1 Systems Analysis and Design in a Changing World, Thursday, January 18, 2007.
Ch 4 - Learning Objectives Scope Management You should be able to: n Discuss the relationship between scope and project failure n Describe how strategic.
Insert: Title of Improvement Read Out Date:. 2 Objectives for Today’s Session Share results of improvement effort Demonstrate fact-base, analytical approach.
Software Engineering MCS-2 Lecture # 6
Chapter 14: Using the Scalable Decision Process on Large Projects The process outlined is meant to be scaleable. Individual steps can be removed, changed,
AP-1 5. Project Management. AP-2 Software Failure Software fails at a significant rate What is failure? Not delivering it on time is an estimation failure.
Historical Aspects Origin of software engineering –NATO study group coined the term in 1967 Software crisis –Low quality, schedule delay, and cost overrun.
Spring ’2014 New Product Development
Implementing Parametric CAD in STEP ???? Kenneth E. Wolsey May 16, 2007
The Design Process By Gamal Prather. THE DESIGN PROCESS The design process is an engineering activity that turns a concept into reality. The concept is.
Chapter 12 EIN 6392, Product Design summer 2012
Software Architecture Evaluation Methodologies Presented By: Anthony Register.
Chapter 27 The Engineering Design Process. Learning Objectives Describe the various factors that are changing the design process Discuss the steps in.
Product design challenge Fall the theme  Any product that uses Computer Science to create it  Possible areas:  Safety  Entertainment  Family/relationships.
Project Management Unit 1 Fundamental Concepts. Definition of A Project A temporary endeavor undertaken to create a unique product or service (PMBOK®).
Principles of Software Engineering: Why Study Software Engineering? COSI 120b, Spring 2005.
The WINSS School Improvement Planning Tool: An Overview.
Lecture 2. An Overview of Engineering Design JANUARY 2016 GE105 Introduction to Engineering Design College of Engineering King Saud University.
Software Engineering CE 501 Prepared by : Jay Dave.
1 CONCEPTUAL DESIGN PHASE 1.Specification Development / Planning Phase Determine need, customer and engineering requirements Develop a project plan 2.Conceptual.
Concept Selection and DFMEA Heidi Ploeg Associate Professor Mechanical Engineering and Biomedical Engineering.
Fostering Problem Solving : Singapore Math Success Story By Mark David C. Quitco.
Intro to design1 Intro To Design Systematic Design Process.
Concepts of Engineering Module 2 Test Review. Review Questions Design problems are broken down into sub- problems because smaller problems must be solved.
1 Design and evaluation methods: Objectives n Design life cycle: HF input and neglect n Levels of system design: Going beyond the interface n Sources of.
Ulrich Concept Development Process. Ulrich Definition of Prototype Physical Mock-ups Breadboards Look-and-feel models A prototype is an approximation.
Computer tools for Scheduling
Software Quality Engineering
Chapter 2 The Process of Design.
Introduction to Systems Analysis and Design Stefano Moshi Memorial University College System Analysis & Design BIT
Chapter 12 EIN 6392, Product Design Fall 2009
The Creative Process CREATIVE PROCESS
Presentation transcript:

Conceptual Design

Goal of Conceptual Design Arrive at an agreed-upon design that is ready for detailed design and implementation or fabrication. Design approach agreed upon by the sponsors and the team Presented at the Conceptual Design Review (aka Preliminary Design Review) Reduces risk of investment of time and effort into the wrong approach In industry, often triggers authorization for next round of funding.

Dangers Premature fixation - focus on a solution without considering alternatives Bounded ideation - limitations that the design environment can place on generating ideas Circumscribed thinking - influence that the outside sources can have on design decision making Paralysis by analysis - inability to move forward with concept

Suggested Process Decomposition of system Morphological chart Decision matrix Prototyping

Decomposition of System Divide big problem into smaller problems Known systems have known decompositions New products need new decomposition

Morphological Chart a.k.a. table of options an organization of concepts by function provide a structured approach to concept generation good for individual and group visualization complete concepts are created by choosing a solution for each function

Pictures or references to pictures are better!!!!

How to Fill the Table? Brainstorming Sketching Build on the ideas of others Analogizing

Decision Matrix Combine and improve concepts Is a good concept degraded by one feature? Can a minor change improve one concept while preserving uniqueness of the concept? Are there 2 concepts that can be combined to preserve good qualities and eliminate the bad? Select one or more concepts Reflect on process What are action items going forward?

Prototyping Representation of the solution for analysis of the known and unknown Prototypes are created to help you Learn about the user needs and potential solutions Communicate with managers, customers, team, investors,... Integrate components and systems Milestones in product development

Physical vs Analytical Tangible product Often best for communication If material/process/behavior is built differently may exhibit different results Represent things that are hard to quantify Mathematical representation of the system Often easiest to build and change If material/process/behavior is modeled differently may exhibit different results

Focused vs Comprehensive A specific piece of the whole product Often require multiple for complete prototyping Useful for specific questions The whole product Best for milestones Can be fully tested by users (and team)

Cost of comprehensive prototype Commercial airliner High Software Risk Low Book House Low High Cost of comprehensive prototype

Notes on Prototyping Analytical prototypes are more flexible Physical prototypes help detect unexpected phenomenon Physical prototypes can reduce risk of iteration Most risk when there is high cost of failure, new technology, new application

Notes on Prototypes Use prototypes to reduce uncertainty Have a GOAL for each prototype!!! Avoid guess and check - the hardware swamp