Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Usability in Emergency Response Applications

1,636 views

Published on

Slides to go with my 2009 ESRI South West Users Group (SWUG) talk on creating a highly usable web application for emergency response users. Video of this talk can be viewed at http://vimeo.com/7557517

Published in: Technology
  • Be the first to comment

Usability in Emergency Response Applications

  1. 1. Usability and Operational Efficiency in Emergency Response Applications: A Case Study<br />
  2. 2. GIS-enabled emergency applications, while increasingly critical to planning and managing response to incidents on the ground, must avoid the pitfalls of providing full-featured GIS packages to management and response personnel. Because these personnel are not typically trained GIS analysts or power users, significant operational efficiencies can be gained through the deployment of focused applications that match the mental model of response personnel when coordinating the response to an incident. DTSAgile has implemented a system for the Mid American Regional Council using the ESRI ArcGIS Server JavaScript and REST APIs that removes much of the perceived GIS complexity for emergency managers. The application instead relies on a focused, highly performant application supporting a finite number of workflows for the most common operational tasks or scenarios. This presentation will focus on approaches to building focused, workflow enabled emergency management applications with ESRI technologies. A case study involving a recently completed emergency response application will be used to illustrate design and implementation patterns, UI paradigms, key useability and operational efficiency features, data and functional considerations, and security options for applications serving the emergency response / emergency management markets<br />
  3. 3. SWUG 2009<br />Usability Ideas for<br />Emergency Response<br />Applications<br />http://www.flickr.com/photos/soldiersmediacenter/3059082014<br />
  4. 4. http://www.flickr.co/m/photos/zooboing/3711224527<br />
  5. 5. http://www.flickr.com/photos/malcolmtredinnick/317603723<br />
  6. 6.
  7. 7. http://www.flickr.com/photos/poolie/2430954000<br />
  8. 8. http://www.flickr.co/m/photos/killbox/387652272/<br />
  9. 9. http://www.flickr.co/m/photos/syslfrog/172945973<br />
  10. 10. http://www.flickr.com/photos/gretyl/54301880<br />
  11. 11. http://www.flickr.com/photos/chascar/476475563/<br />
  12. 12. http://commons.wikipedia.org<br />
  13. 13. http://www.flickr.com/photos/scissorhands33/3371981988<br />
  14. 14. Emergency Response<br />workflow application<br />multi-service “mash-up”<br />ESRI JS API + Dojo<br />ArcGIS Server 9.3 REST<br />
  15. 15. SWUG 2009<br />Real-Time<br />Weather<br />http://www.flickr.com/photos/92833011@N00/824037794<br />
  16. 16. SWUG 2009<br />Incident<br />Boundaries<br />http://www.flickr.com/photos/martiniko/2354406802<br />
  17. 17. SWUG 2009<br />Human<br />Impacts<br />http://www.flickr.com/photos/pedrosimoes7/393217457<br />
  18. 18. SWUG 2009<br />Material<br />Impacts<br />http://www.flickr.com/photos/kenneth_hynek/3844780152<br />
  19. 19. SWUG 2009<br />The<br />Tour<br />
  20. 20.
  21. 21. IIS<br />JS Starter Kit<br />Get Config<br />Config.json<br />
  22. 22. SWUG 2009<br />Identity<br />Matters<br />
  23. 23. JS Framework<br />ASP.NET MVC<br />Get Config<br />Config<br />SQL Server<br />
  24. 24. Workflows<br />
  25. 25. 1<br />SWUG 2009<br />Weather<br />Warnings<br />
  26. 26.
  27. 27.
  28. 28. What if…<br />
  29. 29.
  30. 30.
  31. 31.
  32. 32.
  33. 33.
  34. 34.
  35. 35. 3<br />2<br />SWUG 2009<br />Real-Time<br />Modeling<br />
  36. 36.
  37. 37.
  38. 38.
  39. 39.
  40. 40. Action<br />
  41. 41. Zoom to spatial results<br />layer created<br />tabular results<br />
  42. 42.
  43. 43.
  44. 44.
  45. 45. 3<br />SWUG 2009<br />Ad-Hoc<br />Incidents<br />
  46. 46.
  47. 47.
  48. 48.
  49. 49.
  50. 50.
  51. 51.
  52. 52.
  53. 53. SWUG 2009<br />Usability<br />Features<br />
  54. 54. simplicity.<br />
  55. 55. consistency<br />
  56. 56. SWUG 2009<br />smart<br />features<br />Do Stuff!<br />
  57. 57. SWUG 2009<br />quick<br />plume<br />
  58. 58. SWUG 2009<br />one-click<br />reports<br />
  59. 59. SWUG 2009<br />flexible<br />configuration<br />
  60. 60. User Managment<br />
  61. 61. SWUG 2009<br />user<br />manager<br />
  62. 62.
  63. 63.
  64. 64. SWUG 2009<br />catalog<br />manager<br />
  65. 65. Incident Layers<br />Standard Layers<br />Local or Remote AGS<br />Tiled or Dynamic<br />Bitmap or Geometry*<br />Public or Secured<br />
  66. 66. Data Type controls the icon<br />Name<br />Short Description<br />Long Description<br />In pop-up window<br />
  67. 67.
  68. 68.
  69. 69.
  70. 70.
  71. 71.
  72. 72.
  73. 73.
  74. 74.
  75. 75.
  76. 76. SWUG 2009<br />challenges<br />
  77. 77. SWUG 2009<br />secured<br />services<br />
  78. 78. Request<br />Response<br />
  79. 79. Credentials<br />Token<br />Request + Token<br />Response<br />
  80. 80. Couldn't someone sniff <br />the credentials or <br />the token and subvert <br />the whole thing?<br />
  81. 81. Credentials<br />Token<br />Request + Token<br />Response<br />
  82. 82. Credentials<br />AGS<br />Token<br />Request<br />PROXY<br />Response<br />Request + Token<br />Response<br />Credentials<br />
  83. 83. SWUG 2009<br />Fun and games<br />https://<br />SSL + proxies<br />
  84. 84. Credentials<br />AGS<br />Token<br />Request<br />PROXY<br />Response<br />Request + Token<br />Response<br />Credentials<br />
  85. 85. Source Server<br />Request<br />E<br />D<br />PROXY<br />Response<br />E<br />D<br />
  86. 86. KC AGS<br />KC AGS<br />KC AGS<br />ArcGIS Online<br />Request<br />E<br />D<br />Source Server<br />PROXY<br />Response<br />E<br />D<br />
  87. 87. 90<br />%<br />increase<br />
  88. 88. SWUG 2009<br />random<br />errors<br />
  89. 89. Remote<br />AGS<br />Request<br />E<br />D<br />Source Server<br />PROXY<br />Response<br />E<br />D<br />
  90. 90. Remote<br />AGS<br />Request<br />E<br />D<br />Source Server<br />PROXY<br />Response<br />E<br />D<br />
  91. 91. Remote<br />AGS<br />Service<br />Harvesting<br />
  92. 92. HTTP 404: Resource Not Found<br />
  93. 93. hell<br />SWUG 2009<br />browser<br />
  94. 94.
  95. 95.
  96. 96.
  97. 97. Browsers<br />
  98. 98. dbouwman@dtsagile.com<br />
  99. 99.
  100. 100. http://www.flickr.com/photos/uberzombie/330972741<br />
  101. 101.
  102. 102. configurable<br />secure<br />usable<br />

×