CyberGIS engages multidisciplinary communities through a participatory approach to evolving CyberGIS software requirements. We adopt the Open Process Framework (http://www.opfro.org/) that articulates multiple perspectives about engineering requirements as a way of organizing the requirements for CyberGIS software integration:
Both face-to-face and online approaches are part of the participatory community endeavor. Social media (e.g. eLearningLearning (eLearningLearning 2011)), participation platform (e.g. HUBZero: http://hubzero.org/), and participatory GIS technology for structured participation will be combined and configured to support CyberGIS community-based artifact sharing in support of requirements engineering. Having evaluated the vast array of Unified Modeling Language (UML) artifacts as well as several others, Nyerges and Wu (Nyerges et al. 2006, Wu 2007), identified at least six types of artifacts needed to develop participatory GIS: use case narratives (business and application requirements), class diagrams (system and components requirements), activity function diagrams (systems requirements), architecture diagrams (systems and components requirements), mock-ups (application requirements), and prototypes (components and application requirements) which align with the four engineering requirements categories. Those six artifacts are what people need to develop a shared understanding of the content, structure, process, and context of system development and implementation models. The CyberGIS community effort will evolve through end-to-end artifact development starting with at least those six types of artifacts.
The following steps describe the participatory process as it evolves and provide the CyberGIS community access to the artifacts that have been completed.
January 11-30, 2011
Researchers from the field of Emergency Management and CyberGIS project members and international collaborators completed an online requirements survey.
Survey Results [.xls]
February 1-14, 2011
The survey results were synthesized and presented in a live workshop in Washington, DC. Participants shared lightning talks to give voice to their unique perspectives.
February 15-March 31, 2011
A selection of use cases by participants are listed below, categorized by the type of use case.
Emergency Management Business Use Cases
System Use Cases
April 1-May 15, 2011
The use cases will be structured to describe the application requirements.
A draft document is ready, and is currently being evolved into an application/integration requirements synthesis.
Draft Use Case Synthesis [.docx]
May 16-June 30, 2011
July 1 - July 15, 2011
July 16 - July 13, 2011
August 1, 2011
The results of the requirements survey and use cases will be combined to describe the application requirements.