= !BluePrint: Sahana First Response =
[[TOC]]


== Current Status == 

[https://docs.google.com/spreadsheets/d/1N9xUqZQhignq7QM_7CtrV4zv86sq4lMdJj81IQuch3Y/edit?usp=sharing Fit-Gap analysis spreadsheet]
==== Available features: ====

==== Missing features: ==== 
1. Common Operating Picture with a Crisis Map
1. manage event type specific templates and messages
1. receive SITREP and RM feeds '''[2]''' to serve as an aggregator and a pubhub
1. approve or reject dispatch, incident reports, situational-reports, request-resources
1. delivery options: HTTP, RSS/Atom, SMS, Email, FTP (dynamic labels)
1. built on the Emergency Data Exchange Language (EDXL) SITREP and RM standards
1. subscription management (who, what, when, and where) serve as a subhub
1. Exchange data with other EDXL compliant systems
1. support multiple language SITREP/RM message publication
1. digitally sign the messages
1. Mobile application to server as a publisher and a subscriber
1. Pictographs for reporting incidents and situational=reports
1. Incident specific SOP check list

== Introduction ==
<Briefly describe the solution?>
<What problem is this solution solving?>
<How will this solution add value to Sahana?>
<Name any similar existing solutions>

== Stakeholders ==
<Who will be the users of the solution?>
<Who else will be affected by this solution? eg. Developers, Users of Existing Functionality that may be changed?>
<How will stakeholders be affected?>
Tip: Engage these stakeholders in the development of your !BluePrint.

== User Stories ==
<http://en.wikipedia.org/wiki/User_story>
<A good User Story should answer the following questions:>
<* Who the user is>
<* What they want the solution to do for them?>
<* Why they want it to do that? (goal)>
<eg. A <type of user> wants the solution to <do something for them> so that <can achieve a goal>.>

== Requirements ==
<Group requirements in subsections, e.g.,, etc.>
<http://en.wikipedia.org/wiki/Requirements_analysis requirements>
<Identify different types of requirements:>
=== Functional ===
=== Non-functional ===
http://en.wikipedia.org/wiki/Non-functional_requirements
=== Interoperability ===
=== Standards ===
=== System Constraints ===

== Design ==
<Where relevant include alternative design options>
=== Data Model ===
(e.g. EER or class diagrams)
=== Workflows ===
<Diagrams or Pseudocode> 
=== Site Map ===
<for User Interface solutions>
=== Wireframes ===
<for User Interface solutions>
=== Technologies ===

== Current Implementation ==
<Leave open for a list of existing implementation of this solution in Sahana Eden:>
<*a brief description of the implementation (date/time, name, design options chosen)>
<*a link to the code>
<*list of deployments of the implementation>
<*links to case studies>
<*short analysis of achievements/problems>

== Planned Implementation ==
<List of goals for your implementations which you (include your name/github repo/IRC handle) are currently working on>

== Future Extensions ==
<List of features which could be included, but are outside of the scope of this extension>

== Outstanding Questions ==
<Questions about the features or design that haven't been (and need to be) answered>

== References ==
<Links to external resources>