30
Introduction to Design I Presented by: Dr. Carla Zoltowski Returning Students Should be in ARMS 1109 EPICS Spring 2014 Lecture: Introduction to Design I

Introduction to Design I - Purdue University

  • Upload
    others

  • View
    1

  • Download
    0

Embed Size (px)

Citation preview

1

Introduction to Design I Presented by:

Dr. Carla Zoltowski

Returning Students Should be in ARMS 1109

EPICS – Spring 2014

Lecture: Introduction to Design I

General Info

Weekly email

“Intro lecture series” = 5 lectures

o This is 2nd

Lecture slides posted online

Questions/concerns?

2

Learning Objectives

At the end of this class period, you will be able to:

1. Explain how design engages different kinds of thinking and

why it is challenging

2. Have an overall understanding of design processes

3. Identify where your project is in the design process

4. Describe differences between design and project

management

Lecture: Introduction to Design I Presented By: Dr. Carla Zoltowski

Human-Centered Design

Human-Centered Design as a Process

Human-Centered Design as a Mindset

http://www.mos.org/eie/engineering_design.php

http://ocw.mit.edu/courses/civil-and-environmental-engineering/1-012-

introduction-to-civil-engineering-design-spring-2002/projects/design_process/

EPICS Design Process

People &

Prototypes

EPICS website -> Current Students -> Design Process.pdf

Project Identification Phase

Project Identification Phase: Goal is to identify a specific, compelling need to be

addressed

Co

mm

on

tas

ks

Conduct needs assessment (if need not already defined)

Identify stakeholders (customer, users, person maintaining project, etc.)

Define basic stakeholder requirements (objectives or goals of projects and

constraints)

Determine time constraints of the project

Gate 1: Continue if have identified appropriate EPICS project that meets a

compelling need

Specification Development Phase

Specification Development Phase: Goal is to understand “what” is needed by

understanding the context, stakeholders, requirements of the project, and why

current solutions don’t meet need, and to develop measurable criteria in which

design concepts can be evaluated.

Understand and describe context (current situation and environment)

Create stakeholder profiles

Create mock-ups and simple prototypes: quick, low-cost, multiple cycles

incorporating feedback

Develop a task analysis and define how users will interact with project (user

scenarios)

Compare to benchmark products (prior art)

Develop customer specifications and evaluation criteria; get project partner

approval

Gate 2: Continue if project partner and advisor agree that have identified the

“right” need, and if no existing commercial products meet design specifications.

Conceptual Design Phase

Conceptual Design Phase: Goal is to expand the design space to include as many

solutions as possible. Evaluate different approaches and selecting “best” one to

move forward. Exploring “how”.

Conduct Functional Decomposition

Brainstorm several possible solutions

Create prototypes of multiple concepts, get feedback from users, refine

specifications

Evaluate feasibility of potential solutions (proof-of-concept prototypes); select

one to move forward

Gate 3: Continue if project partner and advisor agree that solution space has

been appropriately explored and the best solution has been chosen.

Detailed Design Phase

Detailed Design Phase: Goal is to design working prototype which meets

functional specifications.

Co

mm

on

tas

ks

Design/analysis/evaluation of project, sub-modules and/or components

(freeze interfaces)

Complete DFMEA analysis of project

Prototyping of project, sub-modules and/or components

Field test prototype/usability testing

Gate 4: Continue if can demonstrate feasibility of solution (is there a working

prototype?). Project Partner and advisor approval required.

Delivery Phase

Delivery Phase Tasks: Goal is to refine detailed design so as to produce a product

that is ready to be delivered! In addition, the goal is to develop user manuals and

training materials.

Common tasks: Complete user manuals/training material

Complete usability and reliability testing

Complete delivery review

Gate 5: Continue if Project Partner, Advisor and EPICS Admin agree that project

is ready for delivery!

Service/Maintenance Phase

Service/Maintenance Phase Tasks

Common tasks: Evaluate performance of fielded project

Determine what resources are necessary to support and maintain

the project

Gate 6: Project Partner and Advisor approve continued fielding of project. If not,

retire or redesign.

Retirement or Redesign Phase

Retirement or Redesign

Why is design difficult?

Engages different types of thinking

o Design is one of the most cognitively complex forms of “problem solving”

Requires designers to manage so many ideas and aspects

Addresses different types of problems

o Ill-defined

o Complex (number of requirements and constraints)

Human-centered Design: Basic Principles

Early focus on users

Designing for and with users

Empirical measurement and evaluation

Iteration

Tools to help with HCD

Tools for Interviews and Observations

o Sharepoint->Shared Documents-> Project Partner meeting planning document

IDEO website: Human-Centered Design Toolkit (http://www.ideo.com/work/human-centered-design-toolkit/)

Stanford d-school website: http://dschool.stanford.edu/use-our-

methods/

Seeking and Selecting

Divergence Convergence Expand possibilities Narrow Focus

Name the

problem

Lecture: Introduction to Design I Presented By: Dr. Carla Zoltowski

Iterative within Process

D.Mindsets

http://dschool.stanford.edu/wp-

content/uploads/2011/03/BootcampBootleg2010v2SLIM.pdf

D.Mindsets

http://dschool.stanford.edu/wp-

content/uploads/2011/03/BootcampBootleg2010v2SLIM.pdf

D.Mindsets

http://dschool.stanford.edu/wp-

content/uploads/2011/03/BootcampBootleg2010v2SLIM.pdf

Big Ideas of Design Human-centered

o Who are you involving and how are you involving them?

o From whose perspective are you designing from?

Iterative Process

o Cycles of divergent-convergent thinking

o Different goals throughout process phases

Decision-making

o Balancing a great deal of information

o Tools to help manage

o Based on theoretical and empirical data

Importance of prototyping

o To communicate ideas and facilitate feedback

o Demonstrate feasibility

How do you know how much time you can and should spend in each phase?

Why Project Mgmt

At this point in the semester, you are developing semester plans and individual goals

Success (team and individual) depends on managing the plan

Project management is one of the key skills that cuts across disciplines and valuable to all professionals

o Used “all the time” by alumni

Project Mgmt Tools

Within the Design Document, the Semester Plan and Timeline (and at the end, Transition report) are TOOLS

Use the tools to:

o Plan the semester

o Track progress

o Manage scope

o Document changes

o Document successes

o Leave lessons learned

Gantt Chart

Project Tasks 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16

Bring new team members up to speed on MagRacer (all)

Solve FET prolem in demo track (Brad/Julie)

Concept of MagRacer2 cabinet (Syed/Erin)

Meet with IS people/ visit IS (all)

Finalize track/coil assembly (Syed/Julie)

AutoCAD drawings of MagRacer2 cabinet (Erin/Brad)

Finalize display concept (Julie)

Deliver working test track (Syed/Julie)

Week 4 Demo (all)

Milestone: Submit MR2 drawings to WP (Erin/Brad)

Complete PCB layout (Syed/Julie)

Milestone: Submit PCB layout for fabrication (Syed/Julie)

Final order of all circuit material (Syed/Julie)

Construct coils (Julie/Syed)

Construct track mounting hardware (Erin/Brad)

Construction of visual display (Julie)

Week 8 Progress Report (Brad)

Exected delivery of MG2 cabinet from WP (4wk) (WP - Erin)

Expected delivery of PCBs (3wk) (Syed)

Spring Break (all)

Final assembly of MagRacer2 (all)

Week 11 Design Review (all)

Milestone: Delivery of completed MagRacer2 (all)

Troubleshoot MagRacer2 (Syed/Julie)

Prep documentation for MagRacer2 (Brad/Erin)

Week 16 End of Semester reports due (Brad)

MagRacer 2.0 Timeline (weeks)

Do you see a tension between design process and project management?

o Has motivated the creation of the “Project Manager” role

Ingredients of successful schedules*

Be optimistic in vision and sceptical in the schedule.

Invest in good design practice to avoid unexpected challenges.

Plan for checkpoints with project partners and advisors.

Continue to refine schedule as more information is known.

Address unknowns as early in the process as possible.

*Based on Making Things Happen by Scott Berkun

Week 2 Homework

Due: Monday, February 3rd (Week 4) in notebook; bring to lecture

1. Read “EPICS Design Process” document if you haven’t already

2. Consider your project as related to the design process : a. Where in the design process (what phase) is your project and how do you

know?

b. What are your project goals for the semester? What design tasks are planned to meet those goals?

c. How well do your project goals and tasks align with the phase of the design process?

d. When was/is your project promised? How does your current semester plan align with the overall project timeline?

3. What are ways you can incorporate one or more of the “Mindsets” within your design approach?

4. How do you plan to keep stakeholders at the center of the design?

Attendance Form

o Fill in name and 10-digit PU ID

o “T” for Question 1

o Sign

o It takes approximately two weeks from the date of the lecture to update myEPICS with your attendance.

Hand individually to TA or me