Marcos Esterman, Associate Professor Industrial and Systems Engineering Department Rochester Institute of Technology Multidisciplinary.

Slides:



Advertisements
Similar presentations
St. Louis Public Schools Human Resources Support for District Improvement Initiatives (Note: The bullets beneath each initiative indicate actions taken.
Advertisements

Senior Capstone Design Project Learning. What is Project Learning? What is…? How to Make…?
Test Automation Success: Choosing the Right People & Process
Copyright 2010, The World Bank Group. All Rights Reserved. Statistical Project Monitoring Section B 1.
R. I. T Mechanical Engineering Engineering Design Brief Case Study: What is the Engineering Design Process and Why is it Critical? Rochester Institute.
EDGE™ Needs Assessment prepared by Prof. Marcos Esterman (ISE) Copyright © 2005 Rochester Institute of Technology All rights reserved.
ACTIVELY ENGAGING THE STAKEHOLDER IN DEFINING REQUIREMENTS FOR THE BUSINESS, THE STAKEHOLDER, SOLUTION OR TRANSITION Requirements Elicitation.
Systems Analysis and Design 9th Edition
IT Strategic Planning Project – Hamilton Campus FY2005.
EDGE™ Project Status Update P09141 – Thermal Heater Control System Anthony Berwin (Mechanical Engineer)
Ken YoussefiMAE dept. 1 Customer Needs Ken YoussefiMAE dept. 2 Understanding and Identifying Customer Needs Considering the customers’ desires is essential.
A Student Guide to Object- Orientated Development Chapter 2 Requirements for the Wheels case study system.
Internal Auditing and Outsourcing
1. 2  Team Members:  Dan Fenton (CE) – Team Lead  Ryan Muckel (ME)  Christopher Freeman (ME)  Derek Zielinski (EE)  Eric Welch (EE)  Kennedy Kong.
Marcos Esterman, Associate Professor Industrial and Systems Engineering Department Rochester Institute of Technology Multidisciplinary.
Objective Trees and Customer Needs Statements
Identifying Customer Needs
SoberIT Software Business and Engineering Institute HELSINKI UNIVERSITY OF TECHNOLOGY 1 Requirements Engineering T Software Development Project.
S/W Project Management
Project Life Cycle Lecture - 18.
Identifying Customer Needs
1 Rev: 02/12/2007 MSE-415: B. Hawrylo MSE-415: Product Design Lecture #3 Chapter 4 Identifying Customer Needs.
Identifying Customer Needs
Teaching materials to accompany:
CIS 321—IS Analysis & Design Chapter 4: Analysis— Investigating System Requirements.
Demystifying the Business Analysis Body of Knowledge Central Iowa IIBA Chapter December 7, 2005.
Requirements Engineering
1 King Fahd University of Petroleum & Minerals Department of Construction Engineering & Management CEM 515: Project Quality Management Case study of 8-phases.
CSCD 487/587 Human Computer Interface Winter 2013 Lecture 3 HCI and Interactive Design.
Basic of Project and Project Management Presentation.
1 4 Systems Analysis and Design in a Changing World, 2 nd Edition, Satzinger, Jackson, & Burd Chapter 4 Beginning the Analysis: Investigating System Requirements.
Week 2 Seminar: Project Scope Management
SacProNet An Overview of Project Management Techniques.
Needs Analysis. Needs analysis is concerned with establishing the true needs of the customer (VOC- voice of customer). This can be obtained from: –reports.
Lecture 7: Requirements Engineering
Marcos Esterman, Associate Professor Industrial and Systems Engineering Department Rochester Institute of Technology Multidisciplinary.
Systems Analysis and Design 8 th Edition Chapter 2 Analyzing the Business Case.
Requirements Reference: Chapters 5, 6, & 8. CMSC 345, Fall Objectives To introduce the concepts of user and system requirements To explain functional.
PRIMARY MARKET RESEARCH Rehabilitation Engineering Research Center on Technology Transfer Training Module #4.
Marcos Esterman, Associate Professor Industrial and Systems Engineering Department Rochester Institute of Technology Multidisciplinary.
Project Selection And Needs Identification
Where We Are Now 14–2. Where We Are Now 14–2 Major Tasks of Project Closure Evaluate if the project delivered the expected benefits to all stakeholders.
SPX Data Acquisition PROBLEM DEFINITION REVIEW John Dong David Haller Adam Johnson Thomas Klaben Luke Kranz.
Marcos Esterman, Associate Professor Industrial and Systems Engineering Department Rochester Institute of Technology Multidisciplinary.
Systems Development Life Cycle
By Germaine Cheung Hong Kong Computer Institute
R. I. T Mechanical Engineering Design Project Management Voice of the Customer: Interviews and Observations Rochester Institute of Technology Mechanical.
Requirements Engineering Processes. Syllabus l Definition of Requirement engineering process (REP) l Phases of Requirements Engineering Process: Requirements.
Evaluating Requirements
Requirement Engineering
Identifying Customer Needs
Requirements in the product life cycle Chapter 7.
Marcos Esterman, Associate Professor Industrial and Systems Engineering Department Rochester Institute of Technology Multidisciplinary.
Industrial and Manufacturing Engineering JACLYN VANGILDER LAURA PAZ VINCENT ISOPI.
44222: Information Systems Development
Chapter 4: Identifying Customer Needs Product Design and Development Fourth Edition by Karl T. Ulrich and Steven D. Eppinger.
EDGE™ Final Project Plan Presentation P09001 – RFID Reader & Active Tag Philip Davenport (Industrial and Systems Engineering)
Product Design Process Customer Needs Assessment EDSGN100 Introduction to Engineering Design Junfeng Ma (With Acknowledgement to Prof. Sven G. Bilén, Prof.
1 Requirements Determination (Analysis) Lecture 3 Courtesy to Dr.Subhasish Dasgupta.
Project Scope Management Pantelis Ipsilandis- Dimitrios Tselios.
Final Presentations – Decision/Leadership Orientation
PowerPoint to accompany:
Right Move, Right Place, Right Time
PRODUCT PLANNING.
MINGGU KE 9: PROSES DESAIN PRODUK BARU
Multidisciplinary Senior Design I
Copyright © 2005 Rochester Institute of Technology
Introduction to Requirements Management
Lecture # 7 System Requirements
P18325: Automated Breast Pump Cleaning System (Team ABC’s)
Presentation transcript:

Marcos Esterman, Associate Professor Industrial and Systems Engineering Department Rochester Institute of Technology Multidisciplinary Senior Design I Problem Definition: Module 3

NEEDS ELICITATION

Desired Needs List NeedPriority Have a modern look and feel 3 Is Light weight 3 Is Small 3 Is Easy to Use 9 Has Long-Lasting Portable Power 9 Low Cost Functional Prototype 3 Low UMC for Final Design 9 Alert user of the following data: XXX 9 Measure Oxygen Levels 3 Measure CO 2 Levels 3 Transfer Data Wirelessly 9 Assist Human to Breathe 9 Integrates into CPR Process 9 Does not interfere with the following life-saving measures: XXX 9 Improves air quality delivered to patient 9 Is safe 9 Is reliable 9 Needs to use principles in patents #5,211,170 and # 5,398,676 9 Needs to be consistent with FDA 510K Approval 9

Goals of Needs Identification Provide basis for PD decisions Elicit needs that may not be so obvious Provide basis for specifications Ensure critical needs are elicited Develop a common understanding of the needs Archiving of needs Ulrich,K.T. and S. Eppinger, Product Design and Development, Third Edition,

Steps in Identifying Customer Needs Gather the raw data Interpret the raw data Organize the needs Establish relative importance of needs Sanity Check! Ulrich,K.T. and S. Eppinger, Product Design and Development, Third Edition,

Identify the Stakeholders 6

Unresponsive person By-standers First Responders FDA Hospitals Home Users Insurance Companies Ambulance Service Doctors/Ultimate Care- takers Inventors RIT MSD MSD Team Investors? 7

Methods for Gathering Raw Data Brainstorming  Method best suited for your projects Interviews  1-on-1  Dialog Directly w/Company personnel Focus Groups  8-12 People (Typically Paid)  Moderator  Company personnel observe group Observing the Product in Use  Direct Observation (Contextual Inquiry)  Virtual Observation Benchmarking Use Cases  Task Oriented  Simulate and document the steps to accomplish the task Ulrich,K.T. and S. Eppinger, Product Design and Development, Third Edition,

Raw Needs Data Used for P13026 PRP Interviews of  Inventors  EMTs RIT Student External Benchmarking  Other PEVs  PTO

Eliciting Customer Needs Prepare an interview guide Elicit dialog on a particular task or problem  Have them walk through a specific instance Don’t ask them to generalize! Better yet, have them show you Go with the flow Use visual stimuli and props Avoid leading questions  Avoid yes/no questions  Be prepared for latent needs Focus on the customer pain  What’s the underlying problem that needs to be solved Document, Document, Document 10

What a team should know after the customer interview What is (are)…  project about? the problem? the opportunity? deliverables? constraints? Why…  are we doing this? motivation? Higher level goals (profit, productivity, etc.)? commercialization? When…  key milestones? time constraints? is client available and not available? (& how) interact with the client? Who is (are)…  Is client? Stakeholders? Approves? Funds? Uses? How…  Be careful here, how’s are not needs, but you should understand client’s preconceived notions about the solution

Developing Needs Statements: Guidelines for Interpreting the Data Understand the value proposition  Your product is solving some problems What are they? What value do you allow your customer to deliver? Stay close to the customer language What, not how Specificity equal to the raw data Positive, not negative Product Attribute Avoid “must” & “should” Ulrich,K.T. and S. Eppinger, Product Design and Development, Third Edition,

Team’s Cut at Needs NeedPriority Design Similarity3 Maintain Portability3 Include Audio Feedback3 Optimize Battery Life3 Replaceable Batteries3 Minimize Expense3 Display Relevant Data3 Measure Oxygen Levels2 Measure CO 2 Levels2 Transfer Data Wirelessly1 3 – Must Have; 2 – Nice to Have ; 1 – Preference Only

Establish Relative Importance of Needs: Development Team Consensus RatingWeight Very Important9 Important3 Somewhat Important1 14

Sanity Check Did you miss any key stakeholders? Are there any areas that you need to follow- up on or get more information? What do we know now that we didn’t before? Surprises? 15