This week, you will read two articles on the application of various methods for developing designs. The first article goes in-depth on the strengths/weaknesses associated with the use of wireframing. The second article focuses particular attention on the challenge of prototyping geographic visualization tools that may not be familiar yet to their intended user audiences.
In both readings, you may encounter terms, theories, etc., that you have not read about before. I encourage you to ask questions, to search for web resources on unfamiliar topics, and to share your findings with your peers.
This article comes from an academic journal that focuses on Cartography and GIScience. The authors discuss their process of developing a GIS based web application to represent changing water levels to help communicate potential landscape change and to assist in environmental management. Particularly relevant for class this week, they walk through the use of wireframing, scenario-based development, and the use of interactive prototypes in the design process. Think about how their design methods match the target goals of the project. Are these design methods used effectively? How are they suited or not suited to the end-goals of the project?
Also, you can also check out the final version of the Lake Level Viewer.
Mediating Geovisualization to Potential Users And Prototyping a Geovisualization Application by David Lloyd, Jason Dykes, and Robert Radburn. (also available via Canvas)
Lloyd & co-authors describe some of the challenges associated with designing geographic visualization tools for users who aren't currently familiar with most geovisualization techniques. They highlight a range of prototyping methods and reflect on their advantages/disadvantages. I would like you to think about which methods you think will work best for designing tools in the work contexts you're most familiar with. Would you modify some of these methods to better suit your needs? Why or why not?