Definición de problemas #RHoK

1,560 views
1,470 views

Published on

En esta presentación se hace un análisis de la metodología de formulación de problemas del Random Hacks of Kindness y de los principales problemas formulados para este importante evento.

Published in: Education, Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
1,560
On SlideShare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
9
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Definición de problemas #RHoK

  1. 1. RHOK.org <br />Formulación Problemas<br />
  2. 2. 46 problemas definidos<br />http://wiki.rhok.org/Category:Problem_Definitions<br />
  3. 3. 23 para el RHoK 2.0<br />
  4. 4. Definiciones de los problemas<br />http://wiki.rhok.org/Category:Problem_Definitions_RHoK2.0<br />
  5. 5. Definiciones<br />Los problemas pueden ser adiciones, nuevos enfoques a proyectos existentes, o la arquitectura general de un nuevo problema. Ambas aproximaciones son válidas.<br />http://wiki.rhok.org/Category:Problem_Definitions_RHoK2.0<br />
  6. 6. Definiciones: Lo ideal es (pero no siempre) <br />Plantear problemas locales, y es necesario disponer de las personas que posean los detalles del problema a solucionar, en el proceso de formulación<br />http://wiki.rhok.org/Category:Problem_Definitions_RHoK2.0<br />
  7. 7. Definiciones: Lo ideal es (pero no siempre) <br />Verificar los problemas planteados antes de formular uno nuevo. Teniendo en cuenta que los problemas pueden ser o no globales.<br />http://wiki.rhok.org/Category:Problem_Definitions_RHoK2.0<br />
  8. 8. Definiciones<br />Sólo porque alguien ya ha trabajado, o esté trabajando actualmente en un problema, no significa que no se puede crear una nueva variante, o iniciar una nueva solución<br />http://wiki.rhok.org/Category:Problem_Definitions_RHoK2.0<br />
  9. 9. Definiciones<br />Toda colaboración es bienvenida<br />http://wiki.rhok.org/Category:Problem_Definitions_RHoK2.0<br />
  10. 10. Definiciones<br />Pueden presentarse soluciones que resuelvan otro tipo de problemas.<br />http://wiki.rhok.org/Category:Problem_Definitions_RHoK2.0<br />
  11. 11. Definiciones<br />Se debe pensar en el usuario final, antes, durante y despues de diagnóstica un problema y creada la solución.<br />http://wiki.rhok.org/Category:Problem_Definitions_RHoK2.0<br />
  12. 12. Definiciones<br />Buscar en los viejos problemas es un lugar interesante para comenzar, pensando en actualizarlos y hacerlos más pertinentes.<br />http://wiki.rhok.org/Category:Problem_Definitions_RHoK2.0<br />
  13. 13. Definiciones<br />Los problemas y la soluciones transcienden un solo evento.<br />http://wiki.rhok.org/Category:Problem_Definitions_RHoK2.0<br />
  14. 14. Formulación de los problemas<br />http://wiki.rhok.org/Category:Problem_Definitions_RHoK2.0<br />http://wiki.rhok.org/Problem_Definition_Template<br />
  15. 15. Nombre del Problema<br />Lo primero que debe hacer es comprobar si ya existe esa definición del problema<br />http://wiki.rhok.org/Problem_Definition_Template<br />
  16. 16. Nombre del Problema<br />Escribir el nombre de la nueva página (nombre corto del problema) en el cuadro de búsqueda, si el problema no existe, se procede a crear página.<br />http://wiki.rhok.org/Problem_Definition_Template<br />
  17. 17. Propietario<br />Es el doliente del problema (individuo, institución), el afectado, el que demanda la solución.<br />http://wiki.rhok.org/Problem_Definition_Template<br />
  18. 18. Propuesto por:<br />Individuo y/o colectivo que formula el problema.<br />http://wiki.rhok.org/Problem_Definition_Template<br />
  19. 19. Propuesto por:<br />Datos de contacto: nombre, teléfono, skype<br />http://wiki.rhok.org/Problem_Definition_Template<br />
  20. 20. Resumen<br />Un breve reseña del problema incluyendo los detalles relevantes.<br />http://wiki.rhok.org/Problem_Definition_Template<br />
  21. 21. Resumen: Ejemplo<br />Sobrevivientes atrapados bajo escombros de un edificio tienen la necesidad de enviar señales de ayuda desde sus teléfonos móviles a través de #bluetooth. Deben existir receptores #bluetooth en las paredes de los edificios e integrado a conexiones externas. Con disponibilidad de energía através de un transductor que aproveche la energía del sismo.<br />http://wiki.rhok.org/Problem_Definition_Template<br />
  22. 22. Resumen: Nota<br />Se debe precisar si se quiere aportar a un problema existente o innovar en el enfoque diferente de lectura del problema y/o de la solución.<br />http://wiki.rhok.org/Problem_Definition_Template<br />
  23. 23. Historias de usuario/Casos de Uso/Escenarios<br />Son párrafos precisos, que describen cómo alguien podría utilizar una solución (hardware, software, personas, ideas) para resolver el problema.<br />http://wiki.rhok.org/Problem_Definition_Template<br />
  24. 24. Historias de usuario/Casos de Uso/Escenarios<br />Alternativamente esbozar el escenario de una persona frente al problema, y ofrecer algunas opciones y pensamientos de cómo la tecnología podría ayudarlos.<br />http://wiki.rhok.org/Problem_Definition_Template<br />
  25. 25. Definición del problema<br />Formulación, que sintetiza los elementos clave del problema, su ubicación en el espacio y en el tiempo.<br />http://wiki.rhok.org/Problem_Definition_Template<br />
  26. 26. Definición del problema: ejemplo<br />Ana está en casa cuando ocurre un terremoto. La mayor parte de el edificio se derrumba y ella se ha quedado atascado en el interior, lesionada, pero bien Ella tiene un teléfono móvil con ella, está aterrorizada, y trata de llamar a la policía, y luego sus amigos en busca de ayuda, pero no hay recepción. Finalmente su batería se agota y ella está preocupada de que no puede hacer ninguna llamada más.<br />http://wiki.rhok.org/Problem_Definition_Template<br />
  27. 27. Historias de usuario<br />Texto descriptivo con la historia de usuario que generaliza el problema.<br />http://wiki.rhok.org/Problem_Definition_Template<br />
  28. 28. Historias de usuario: ejemplo<br />Conexión bluetooth con los receptores en las paredes:<br />En el terremoto los sensores en las paredes captan el sismo y proceden activar un receptor Bluetooth que funciona con una batería.  Ana vía bluetooth (teléfono móvil) realiza una conexión automática (ella lo establecido de antemano) a la antena integrada en el receptor el cual le da potencia a la señal para alcanzar una torre y su llamada pueda ser procesada.<br />http://wiki.rhok.org/Problem_Definition_Template<br />
  29. 29. Casos de uso<br />Análisis del detalle de los diferentes casos en que el usuario interactúa dentro de la problemática en la implementación de las posibles soluciones.<br />http://wiki.rhok.org/Problem_Definition_Template<br />
  30. 30. Casos de uso: ejemplo<br />Setup conexión teléfono-receptor (bluetooth)<br />La solución debe brindar la funcionalidad de personalizar la conexión, automática, manual, para conectarse con los receptores de las paredes, y conmutar la llamada de emergencia por este canal.<br />http://wiki.rhok.org/Problem_Definition_Template<br />
  31. 31. Consideraciones importantes, limitaciones<br />Qué se necesita saber, que limitaciones existen para resolver el problema y/o implementar soluciones.<br />http://wiki.rhok.org/Problem_Definition_Template<br />
  32. 32. Consideraciones importantes, limitaciones<br />Ejemplo:<br />Energía AC. Debe tener un costo de menos de $0.001/unidad.<br />http://wiki.rhok.org/Problem_Definition_Template<br />
  33. 33. Similar projects and Resources<br />Enlaces a otros proyectos (que tratan similares problemas), investigaciones, iniciativas-proyectos existentes, estándares, etc. <br />http://wiki.rhok.org/Problem_Definition_Template<br />
  34. 34. Similar projects and Resources<br />Ejemplo:<br /><ul><li>Investigaciones sobre antenas y arquitectura celulares.
  35. 35. Estándares bluetooth y W3C
  36. 36. Análisis de costos por unidad de energía</li></ul>http://wiki.rhok.org/Problem_Definition_Template<br />
  37. 37. Análisis de Problemas FormuladosRHoK2.0<br />http://wiki.rhok.org/Category:Problem_Definitions_RHoK2.0<br />
  38. 38. AutomaticSiteTranslation<br />Enable quick and dirty translation support for arbitrary websites with minimal changes/dependencies on the site templating system.<br />
  39. 39. ConnectivityMapper<br />Create the inverse of the AT&T Wireless DeadZone app: A smart phone app that automatically uploads (GPS, wireless signal strength) and maps the resulting areas of connectivity<br />
  40. 40. Crisis & Recovery Mapping and Analysis Toolkit<br />CRMA Toolkit, Ver video: http://www.youtube.com/watch?v=1gsaU5bKDlE<br />
  41. 41. DATA_CHAT<br />Tweak the Tweet has shown some of the potential for exchanging structured information over a public network like Twitter, using the existing practice of #hashtag markup to add crisis-related message annotations, and recommending new conventional use to encode some data types near certain tags.<br />
  42. 42. Digital proof of property ownership<br />Survivors sometimes return to their property after a disaster and find someone else living there who claims to be the legal owner. There may be no way to proof land ownership since there either is no official title to the land, or the paper title and even the digital record the local administration got destroyed or lost during the event.<br />
  43. 43. EarthquakeWarning<br />Ver diagrama: http://xkcd.com/723/<br />
  44. 44. Risk In A Box<br />Risk and impact modelling are required by governments around the world to reduce loss of life and financial loss caused by disasters. These analyses in general are static documents/maps built in silos and forgotten on shelves. What is needed is a dynamic way to combine the disparate datasets about hazard levels and exposure, calculate impacts and effectively communicate the results on-line.<br />
  45. 45. GIS Data cleaning algorithms for Humanitarian Crowd-Sourcing data capturing<br />With the United Nations Logistics Cluster Geoportal we try to establish a public crowd-sourcing portal for emergency GIS data. Freelancer and NGO partners can participate to collect data for the cooperate logistic infrastructure and transportation database of the humanitarian community<br />http://geoportal.logcluster.org/useradmin/auth<br />
  46. 46. HumanitarianLogisticsPlanningMap<br />The aim is to provide humanitarian agencies with the ability to quickly design a conceptual logistics operation planning map based on up-to-date logistics data made publicly available by the WFP Global Logistics Cluster Support Cell (GLCSC) GeoPortal.<br />
  47. 47. IAmNotOk<br />An easy to use Android app that will allow a user to send out an emergency broadcast message across multiple mediums to indicate they are not OK and need help.<br />
  48. 48. IncidentCommander<br />Incident Commanders, whether managing an international humanitarian crisis or a local volunteer response to a fire or medical emergency, need to understand where critical resources and points-of-interest are located e.g. Responders, Equipment, Locations, Security, Supplies, etc... The application will track Responders in real-time; give them route information to their target destinations; enable them to request urgent assistance should they be threatened; alert them to danger areas through virtual "fencing"; enable basic data collection via voice, web or SMS communications.<br />
  49. 49. Listing and Certification of Local Resources and Service Providers<br />An information system to facilitate the identification of existing local capacity, capacity building and strengthening needs and existing and potential local service providers which can be part of and engaged in assistance initiatives, allowing local talent to be acknowledged, strengthened, certified and used by assistance organizations, beyond the assistance intervention process.<br />
  50. 50. PersonFinder<br />Person Finder is a searchable public database of missing persons. It was created by Google volunteers in response to the Haiti earthquake in January 2010. It was used again for the Chile earthquake, the Yushu earthquake, and the Pakistan floods, and now runs at http://person-finder.appspot.com/<br />
  51. 51. Population Centers In Disaster<br />We need a tool that would allow us to extract from Wikipedia into a Google Doc - the population centers for a defined area - such as City, District, Country. This would improve our speed of response on emerging events.<br />
  52. 52. DevLinks- A Social Network for NGOs<br />DevLinks will be a social network tool that will achieve the following functions: <br />Facilitate NGO-NGO communication in the developing world. <br />Create a platform through which donors/volunteers around the world can contribute to organizations based on a variety of criteria (geographical proximity, personal interests, etc.)<br />Develop larger NGO-smaller non-profit communication (e.g.: Unicef to local developing world non-profit)<br />
  53. 53. SurveyTablet<br />Upcoming low-cost tablets could revolutionize the process of on-the-ground assessments and other types of in-the-field data collection. Create an easy-to-use, “have to try hard to break it” data collection app for a tablet.<br />
  54. 54. Tweak the Tweet - user testing<br />Tweak the Tweet was a (2nd place) winning hack from RHOK#0. The idea is that users of the Twitter platform can add special hashtags to their tweets that enable them to be automatically processed/filtered/categorized/mapped by simple computer programs.The "problem" today is user testing for the Tweak the Tweet format/syntax. We want to simplify it, make it easier to adopt and use during a disaster.<br />
  55. 55. UshahidiTaggingPlugin<br />The problem that we want to solve is to be able to harmonize the work of different teams of people working on the same message in the back end of the Ushahidi platform.<br />
  56. 56. UshahidiTicketingPlugin<br />We need a ticketing systems that basically assign a code (number or letters plus numbers) to each information incoming into the Ushahidi platform.<br />
  57. 57. Vulnerability and Mapping field survey tool rework<br />http://groups.google.com/group/wfp-vam-field-survey-tool?pli=1<br />The video below features George Muammar of the WFP Vulnerability Analysis and Mapping Unit. He describes rapid data collection in an Emergency Food Security Assessment in Goma, N. Kivu, Democratic Republic of Congo.  <br />http://mobileactive.org/mobile-data-early-warning<br />
  58. 58. WhoIsOk<br />After a disaster, I want one page that shows a list of my contacts and who and who has not tweeted nor posted to facebook or buzz since the disaster.<br />
  59. 59. Formulación Problemas<br />rhok.org (-#rhok2.0)<br />http://wiki.rhok.org/Category:Problem_Definitions<br />
  60. 60. Access to Landslide Prediction Software for Risk Reduction<br />Develop a web-interface for inputting field data to an existing landslide prediction model, and allow the user to download the model outputs for visualization, interpretation and identification of landslide risk reduction measures. <br />
  61. 61. Browser AlertsProblemDefinition<br />Show emergencyalerts (hurricane, tsunami, tornado, warnings, etc) in browsers. Constrainto IP geolocations in warningarea. Startwith a desktop plugin, migrateto a native browser feature, meldwith CAP standard, deploy as a mobileapplication. Enableforwarding of messagetofriends/contacts.<br />http://en.wikipedia.org/wiki/Common_Alerting_Protocol<br />
  62. 62. BushfireConnect<br />We know when bushfires happen, people want fast access to trustworthy information. Bushfire Connect aggregates information from multiple sources: official and social, about events and incidents such as community meetings, fires, and road closures, in a way that empowers anyone to contribute local knowledge and make informed decisions.<br />
  63. 63. CERTS Community Emergency Response Teams (CERT) http://www.cert-la.com/index.shtml<br />CERT Team are local emergency response teams based on volunteers that take 8-10 week courses. They get mobilized as a last resort, when all government-owned response teams are maxed out and overwhelmed. Famous ones are e.g. the LA CERT, the Arlington County CERT here in the area, and others. CERTs have limited recourses and no standard equipment, so providing tools for them to register and organize their users beyond list-servs, assign responsibilities, keep track of skill-sets, general community management etc<br />
  64. 64. Coordinated Response/Diaspora<br />Develop a web tool where members of a diaspora community, governments, and NGOs can “meet up” after a natural disaster and coordinate long-term response efforts. Such a tool would allow for a more grassroots response to disaster relief and will allow individuals who have a stake in the affected communities to leverage and multiply their resources.<br />
  65. 65. Credibility of the Human Sensor<br />Create an app that allows citizen-captured information to be uploaded and shared via a mobile platform (iPhone, Andorid, other mobile OS). The information should be SMS/photos/video clips (automatically and manually geo-referenced) and uploaded to a website, and which, in turn, displays these SMS/photos/vids and allows them to be filtered by type, location, severity, etc. This technology should allow community crowdsourcing and expert reviewers to determine the trustworthiness of information. Such a tool will be used as situational awareness for coordinators of response teams. Solution should support<br />
  66. 66. Crisis Corps<br />During times of crisis, needs arise for crowdsourcing tasks to assist with efforts in the field. These efforts include contributing to maps, identifying resources, Currently, driving people to these crowdsourcing tasks to complete them efficiently can be a challenge.<br />
  67. 67. CrisisWiki / CrisisCommons Project<br />http://crisiscommons.org/<br />
  68. 68. Framework for risk analysis using data from Geoserver Problem Definition<br />Geoserver provides a spatial infrastructure that forms the basis for such a platform. What is needed is to be able to extract vector and raster data from the server into Python, perform some computations reflecting the desired impact analysis and create a color coded map according to the result.<br />
  69. 69. HaitiAMPsProblemDefinition<br />It is difficult, if not impossible, to know just how many new amputees there are in Haiti at the present time. Post earthquake estimates from credible sources vary wildly and change weekly, initial estimates of four thousand now complete with more alarming estimates into tens of thousands. The purpose of the Haiti Amps project is to promote and support optimal recovery from loss of limbs.<br />
  70. 70. WhatisHelpStays?<br />HelpStays provides the emergency services, e.g. the red cross, UN, doctors without borders etc. access to a database of private accommodation available to their volunteers.<br />http://www.slideshare.net/bexpaget/rhok-10-sydney-helpstays-project<br />
  71. 71. Humanitarian Data Portal ProblemDefinition<br />The humanitarian community has a portal (UNOCHA's Relief Web) available to them. ReliefWeb is a very comprehensive repository of maps, graphics and analysis of current and past crises, but it is very difficult to access in a low bandwidth environment.<br />
  72. 72. I NeedHelp<br />Build an app for iPhone, Android and other mobile OSes that enables users to send emergency appeals for help—including actionable data like geolocation and medical information—across multiple mediums. For instance, the app sends out an email, Tweet, Facebook alert, Buzz, etc. and pings a list of contacts every 5 minutes until user shuts the alerting system down. <br />
  73. 73. ImOk<br />I'm OK! helps you report your status to friends and family after a disaster.<br />After a disaster, everybody wants to call their friends at the same time, congesting the cell network. The I'm OK! system lets you send one SMS to a server that then gets forwarded to a list of your friends and family via email or other media like social network messages. Using SMS means you're more likely to get through, and you're saving bandwidth for emergency responders.<br />http://imokapp.appspot.com/<br />
  74. 74. InfoSharing<br />Prototyping Aggregated Situational Awareness Applications<br />There is a need to have better information sharing among NGOs in a crisis. Create prototype applications which show how an individual NGO could get improved management of their resources while at the same time, providing better situational awareness to the rest of the NGOs operating in the same sector.<br />
  75. 75. Mobile Data Collection device for disaster risk assessment and response<br />http://code.google.com/p/opendatakit/<br />Develop a tool (mobile and web-based) for mobile data collection via cellular phones that is easy to use, deploy and customize data collection requirements. The tool would serve to allow for both improved efficiency in centrally-coordinated data collection as well as crowd-based collection efforts. It would serve to help improve disaster risk reduction activities and other humanitarian activities. <br />
  76. 76. Near-Real Time UAV Imagery Processing<br />There is a strong need for near real-time, geo-referenced imagery and geospatial information in the aftermath of natural disasters and humanitarian crises. One means of collection is to use Unmanned Aerial Systems (UAS). In recent years, the development of next generation UAV platforms has become a vibrant research field, particularly mini- and micro-UAVs.<br />http://wiki.rhok.org/Near_Real-Time_UAV_technical_notes<br />
  77. 77. Open Data<br />Open data is essentially open access to public sector information to facilitate knowledge sharing, find patterns across organizations (e.g. Hans Rosling in his famous TED-talks) and empower the community to help you make sense of this data in new and interesting ways a la mashups.<br />
  78. 78. SMShelp<br />Hundreds of millions of people in the poorest regions of the world have access to simple mobile phones. Even where no land lines have been installed, there are no hospitals or decent schools, often people still have access to a mobile phone.<br />The question is, can we tap into the fact that this SMS capability exists to assist millions of people? SMSHLP aims to do this.<br />http://wiki.rhok.org/SMSToDoList<br />
  79. 79. TaskTurking<br />A design and architecture document and as much code as possible outlining the detailed scenarios, functionality, workflow, schema, API and even UX for a web site and service that tracks and facilitates job tasking to support job “turking” for systems like OpenStreetmap and also incident follow-up for syste like Ushahidi. It should also consider the pro/cons of this system vsCrowdflower.<br />
  80. 80. The money tracker/ where did my money go<br />The money tracker/ where did my money go: Smart way to make donations and track those donations – You can track where donations are going- like you track your mail. In this way you can leverage transparency — and it becomes a social change tool. As text messages are sent when supplies are arriving at shelters- connect it to ensure money arrives at right place- as well as meeting the right needs (i.e. we need cash not cans). <br />http://www.slideshare.net/heatherleson/the-money-tracker<br />
  81. 81. WeHaveWeNeed.org<br />WeHaveWeNeed.org was a donation management system created in support of the Haiti Crisis. Initially this was developed as a stand-alone system where people could post their “Haves” and others could post their “Needs”. While this is a workable approach, it has become clear that there are other donation management systems which WeHaveWeNeed.org should be interacting with.<br />
  82. 82. http://knowledgefactory.tv<br />http://twitter.com/kfactory<br />http://twitter.com/KFactory/nuestras-cuentas-twitter/members<br />http://redsalvavidas.org<br />http://twitter.com/redsalvavidas<br />http://www.facebook.com/pages/redsalvavidas/341294540523<br />

×