SAMBRO Mobile Application =
[[TOC]]

== 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>

Step 1. Test the current SAMBRO GUIs for its responsiveness to mobile
handhelds. If necessary suggest some GUI tweaks to harmonize the
desktop version with the mobile screens.

Step 2. Design hazard specific alert authoring and issuing GUIs. For
example, Alerting Authorities, in a local area (Barangay,
Gramaniladari, Thaluk, etc) do not need the full CAP message but a few
attributes like the area and water level. We will target on delivering
3-5 mobile GUIs for Landslide, Flood, Accident,

Step 3. Develop the requirements/design for using the concept of
Pictographs in Alerting and other features such as a wake up function
to sound an Audible Alarm etc. I think we should do the same with the
web GUI such that we can set a siren audio to sound for a specific
warning_priority threshold.

We may have to look for funding outside of the ESCAP project for step 3.

== 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>