1 / 12

CS 575 Lecture 3 Spring 2012

This lecture explores strategies for improving community resilience and support in post-disaster scenarios, focusing on the importance of needfinding exercises. By analyzing communication gaps and unmet needs in a neighborhood following an earthquake, the session discusses how improved connectivity and resource management can enhance recovery. Key topics include the prioritization of needs like injury care, food provision, and effective communication. The lecture encourages innovative ideation for applications that aid in community recovery efforts, emphasizing realistic constraints and user-centered design principles.

sofia
Télécharger la présentation

CS 575 Lecture 3 Spring 2012

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. CS 575Lecture 3Spring 2012 K.V. Bapa Rao CSULA

  2. Overview • Review Licklider’s papers from lect 2 • View Berners-Lee Web development video • Follow up needfinding exercise

  3. Review of last week’s needfinding exercise • post-earthquake scenario • 5 families on a block • people know their neighbors but not much about anyone else • sporadic phone & internet communication (phone better than internet) • needs • Injury • food • damage to home • missing relatives / pets • Getting help to come to you • Procurement • Barter • Keeping track of balance • Money transfer • different resources • engineering skills • community resources information • money • food • external connectivity • family members outside disaster zone

  4. Summary of Notes • Adding tradeoffs / detail to requirements (when does mom need to know?) • Trade time for [what?] • Change • New info • Have an evolvable plan • If X happens within time Y, we can do Z1, Z2, … • Explore possible steps • Develop more information and expand possibilities • Refine choices: trade how much food? • Prioritize • Meet immediate & pressing needs • Detail plan • Cover self as well as others • Execute? • Evaluate / correct? • Develop more resources • Think of unusual resources (e.g., train station)

  5. Self-Evaluation

  6. Quality of Observations • Self observation & notes • How many others did you observe? • What questions did you have in mind when you observed?

  7. Breakdowns & Opportunities • Where are the pain points? Badness of experience? • Breakdowns • Unmet needs • Wasted time • Innovations & work arounds … • Come up with 3-5

  8. Ideas for user needs • What needs would you meet in an app? • List as many as you can (10? 15?)

  9. Inspirations • See people doing something, have an “aha!” moment • X would be a really great new product / service /app • This is how I would go about making X happen • I watched people doing Y and it made me think of X

  10. Use Cases (develop the ideas) • 1 for each group

  11. For next week (homework) • Develop detailed scenario / storyboard for your app • See Assignment 3 under Klemmer’s Stanford course for a guide

  12. Keep in mind the real-life constraints • State your assumptions • Phones working most of the time with some delay • It takes average of 3 hrs before receiving a response to an internet query

More Related