Changes between Initial Version and Version 1 of BluePrint/CrisisMap


Ignore:
Timestamp:
02/10/14 03:34:32 (11 years ago)
Author:
Michael Howden
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • BluePrint/CrisisMap

    v1 v1  
     1= !BluePrint: Crisis Mapping =
     2[[TOC]]
     3
     4== Introduction ==
     5Sahana Eden can be used as a Crisis Mapping Platform to allow incidents and other information to be mapped during a crisis. Most of the building blocks for Crisis Mapping are already in place in Sahana Eden, and the goal of this project would be to bring these pieces together in a usable solution. This will allow Crisis Mapping to be integrated into other Sahana Eden solutions. The focus of this project is building an easy to use solution.
     6
     7This project will involve developing a custom [DeveloperGuidelines/Templates Template]: {{{Crisis_Map}}
     8
     9Michael Howden from the Sahana Community is able to help mentor this project. If you have any questions, please contact the [https://groups.google.com/group/sahana-eden Sahana Eden Mailing List]
     10
     11== Stakeholders ==
     12TBC
     13<Who will be the users of the solution?>
     14<Who else will be affected by this solution? eg. Developers, Users of Existing Functionality that may be changed?>
     15<How will stakeholders be affected?>
     16Tip: Engage these stakeholders in the development of your !BluePrint.
     17
     18== User Stories ==
     19TBC
     20* A person in the community wants to be able to report the impact of a disaster to get assistance
     21* An emergency manager wants to be able to view the needs across the community
     22
     23== Requirements ==
     24TBC
     25=== Phase I ===
     26* Custom homepage & menu
     27* Form to upload incidents to the map (using {{{irs_rireport}}} )
     28* Map showing incidents
     29* Ability to select different icons (See: DeveloperGuidelines/GIS)
     30
     31=== Phase II ===
     32* Import feeds from different social media platforms (See: DeveloperGuidelines/Messaging)
     33* Configure feeds to import
     34* Create incidents from clicking on map points
     35
     36=== Phase III ===
     37* Allow "voting" to prioritize
     38* Control voting by different permissions
     39* Allow requests & tasks to be generated and linked from incidents
     40
     41== Design ==
     42TBC - But having some wireframes for the solution would be useful
     43<Where relevant include alternative design options>
     44=== Data Model ===
     45(e.g. EER or class diagrams)
     46=== Workflows ===
     47<Diagrams or Pseudocode>
     48=== Site Map ===
     49<for User Interface solutions>
     50=== Wireframes ===
     51<for User Interface solutions>
     52=== Technologies ===
     53
     54== Current Implementation ==
     55TBC
     56<Leave open for a list of existing implementation of this solution in Sahana Eden:>
     57<*a brief description of the implementation (date/time, name, design options chosen)>
     58<*a link to the code>
     59<*list of deployments of the implementation>
     60<*links to case studies>
     61<*short analysis of achievements/problems>
     62
     63== Planned Implementation ==
     64TBC
     65<List of goals for your implementations which you (include your name/github repo/IRC handle) are currently working on>
     66
     67== Future Extensions ==
     68<List of features which could be included, but are outside of the scope of this extension>
     69
     70== Outstanding Questions ==
     71<Questions about the features or design that haven't been (and need to be) answered>
     72
     73== References ==
     74* Other Crisis Mapping Software:
     75 * [www.ushahidi.com Ushahidi]
     76* Similar Functionality is described here: BluePrint/SocialMedia
     77
     78----
     79BluePrint