What’s New in EPICS

This is for students returning to EPICS New EPICS Students should be in PHYS 114.

Carla Zoltowski, Ph.D.

What’s New in EPICS

This is for students returning to EPICS New EPICS Students should be in ARMS B061.

Carla Zoltowski, Ph.D.

Schedule Changes Final Design Reviews Fall = Week 13/14 Spring = Week 14

Team Culture survey = Week 14.5

Fall Course Deliverables/Assignments Deliverable(s) Due Date

Team/ Individual

Assignment Lab Safety Awareness form (all students) and Model Release form (for new students only) Week 2 (8/26 – 8/30) Individual

Semester Plan Week 3 (9/3 – 9/6) Team

Individual Evaluation Rubric Week 4 (9/9 – 9/13) Individual

Team Website Week 5 (9/16 – 9/20) Team Design Documentation (posted for reviewers with one page overview) Week 6 (9/23 – 9/27) Team

Design Review Presentation Week 7 (9/30 – 10/4) Team

Individual Evaluation Rubric

Week 8 (10/9 – 10/15) Individual Individual Documentation

Peer Evaluation

Project Evaluation Rubric Week 8 (10/9 – 10/15) Team

Individual Evaluation Rubric Week 12 (11/6 – 11/12)- Optional Individual

Design Documentation (posted for reviewers with one page overview) Week 12/13 (11/11 – 11/15) Team

If delivering, Delivery Checklist Week 13/14 (4/8 – 4/19) Team

Design Review Presentation Week 13/14 (11/18 – 11/22) Team

Team Culture Survey Week 14.5 (11/25 – 11/26) Individual

Individual Evaluation Rubric

Week 15 (12/2 – 12/6) Individual

Individual Documentation

Peer Evaluation

Purdue Course Evaluations

Final Reflection

Project Evaluation Rubric Week 15 (12/2 – 12/6) Team

Lab and lecture attendance Weeks 1 - 15 Individual

Current Website Weeks 5 and 14 Team

Milestones Schedule Provides Objectives and Strategies for

the Assignments Making sure you are meeting the

objectives of the activities versus just completing the assignment. E.g. Transition Checklist Can use as a guide, but simply going

through to check off each box is not the point!

Reminder…In the Semester Plan…. Be as detailed as possible when

developing Semester Plan Include tasks associated with design process

and Milestone objectives Include activities to better understand project

partner/user, and to get feedback Think about critical path and lead time for

different activities

Lectures/Skill Sessions: A number of skill sessions for semester

will be posted in next week Recommend PLAN what lectures/skill

sessions you will be participating in Again: Leadership Special topic tracks Will receive extra credit for outside work

(e.g., Four sessions + outside work = 8 credits) Expected that you participate in ALL

sessions

Lectures: Special note for 5:30 Only 4:30 lectures held regularly The 5:30 Lecture will only meet for the

first week. Rest of lectures will be completed online Watch Video:

https://engineering.purdue.edu/EPICS/Resources/Lectures Submit attendance in myEPICS by date

listed on Lecture Schedule (usually 2 weeks)

Lectures: Special note for 5:30 For new students: only in PHYS 114 for

the first 5 lectures Lecture schedule is posted on web Advisor can approve events that count (fill

out “Advisor Approved Activity” form to count – within two weeks!)

Special Meetings Senior Design = Required meeting Tuesday, August 27th 5:30 – 6:30 pm ARMS 1098C

Team Leader Meeting (Recommended) Monday, August 26th 5:30 – 6:30 pm ARMS 1098C Pizza provided

Providing more detail/resources: Working on more detailed descriptions

of the following: Accomplishments Process Critical/Reflective Thinking Teamwork/Leadership Communication

Grading Summary

Reflective/Critical Thinking format What did I learn? How did I learn it? Why does this learning matter? What will could I or others do in light of

this learning Can be applied to personal/professional, disciplinary, and civic learning. From: Ash, Clayton, and Moses (2009). Learning through Critical Reflection: A Tutorial for Service-Learning Students. Raleigh, NC.

Budgeting/Financial Can still spend up to $200 without budget Service-learning grants available:

http://www.purdue.edu/servicelearning/Students/funding.html Last year, these grants provided almost $16,000

toward project expenses

Shout out to CED and CSI – each team received several grants

Financial reports posted on sharepoint NO Personal Reimbursements!!!!!!

Before First Lab Meeting Find old notebooks Review prior semester’s

documentation/transition report Prepare agenda Prepare introduction to projects Identify new projects if needed

Identify/prepare needed training

First Lab Meeting Agenda Team introductions (use name tags) Icebreaker (Wallet Exercise) Introduction to projects

Have one page summary of each project

Team members should be assigned to project teams Have students provide basic info and preferences, then “assign” Identify appropriate training module(s) or skill sessions for individuals Give copies of design documentation/transition report

Team positions should be assigned and updated in myEPICS Team Leader or TA?

Hand out Transition Checklist to new students. Pair new students with returning students (usually within same project team). Check access (myEPICS, sharepoint, Lab)

Discuss/schedule project partner visit or meeting. If before next week, arrange rides to the project partner if meeting, if needed.

Opportunity for Advisor(s) to discuss expectations What else?

Your TA will: Provide information sheet and copies of handouts from

week 1 lecture for any students who did not attend. Collect Model Release and Lab Safety forms if they were not

turned in during 1st lecture.

Facilitate Wallet Exercise if doing Take attendance Identify any lecture and/or lab conflicts and enter lecture

conflicts in myEPICS. Enter team roles into myEPICS or make sure TL does. Make sure webmaster has skills or is aware of skill

session. Help develop or identify training module(s) your team

requires

EPICS Design Process

Design Process Tasks Project Identification Phase: Goal is to identify a specific, compelling need to be addressed

Com

mo

n ta

sks • 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: 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.

Com

mon

task

s • 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: 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”.

Com

mon

ta

sks

• 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: Goal is to design working prototype which meets functional specifications.

Com

mo

n ta

sks • 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: 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 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

Tools to help with HCD 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/ Design Heuristic “Ideation” Cards

From the Wallet Project DP0 Exercise

http://dschool.stanford.edu/use-our-methods/

Characteristics of “beginning designers” Accept “problem” as given – surface level issues Skip research – pose solutions immediately Fixate on first ideas – disconnect from “problem” Make premature design decisions Few or confounded experiments Unfocused way of troubleshooting Unaware or unable to deal with complexities, tradeoffs,

competing issues Design “haphazardly” or in a linear fashion (recipe) Tacit designing with little self-reflection

(Crismond, 2009; slide from Cardella)

Characteristics of “informed designers” Recognize ambiguity and complexities – “explored the

challenge” Do research on the problem, test assumptions Practice idea fluency (problem evolves with design

ideas) Delay decisions until they explore the challenge Use words, sketches, prototypes to explore ideas Conduct valid experimental tests Focus on key problems when troubleshooting Consider benefits and trade-off when making decisions Design in a managed way – strategic and iterative Practice reflective thinking – learn THROUGH design

(Crismond, 2009; slide from Cardella)

Outcome Space of Students’ Experience of Human-Centered Design

Needs,info from

higher levelstakeholders

Design Process and Integration

LacksDesign

LinearDesignProcess

Integratedand

IterativeDesignProcess

VeryIntegrated

DesignProcess,Iterative

EmpathicDesign

Broadercontext,

relationshipEmpathicDesign

Involvesusers Commitment

ContextDesign

inContext

KeepsUsers’Needsin Mind

User isseen as

informationsource

ServiceUser infoInput toLinear

Process

Lacksappreciation

ofusers

Technology-Centered

Technology-Centered

Threshold

Immersive

“Critical”

Reflection: Think-Pair-Share Is human-centered design important?

Why or why not? What category of HCD do I believe I

exhibit? What characteristics of novice designer do

I exhibit? How can I become a more informed designer? What can we do on our teams to keep

stakeholders at the center of the design? How can you have as “immersive”

experience as possible?

Reminder for 5:30 Lecture The 5:30 Lecture will only meet for the

first week. Rest of lectures will be completed

online Watch Video:

https://engineering.purdue.edu/EPICS/Resources/Lectures Submit attendance in myEPICS by date

listed on Lecture Schedule (usually 2 weeks)

Parting Words for today…. If you have friends who want to join

EPICS—it is not too late! See how EPICS counts

Attendance Form Fill in name and 10-digit PU ID “T” for Question 1 It takes approximately two weeks from the

date of the lecture to update myEPICS with your attendance.

Have a great semester!