BluePrint: Sahana First Response

Current Status

​Fit-Gap analysis spreadsheet

Available features:

Missing features:

1. built on the Emergency Data Exchange Language (EDXL) Common Alerting Protocol (CAP) version 1.2 [1]
2. manage templates, manage messages
   
3. manage CAP Profiles (multiple languages, identifier format, etc) in ../cap/000_config file
4. receive CAP feeds [2] to serve as an aggregator and a pubhub
5. approve or reject a CAP message prior to dissemination
6. delivery options: HTTP, RSS/Atom, SMS, Email, FTP (dynamic labels)
7. visualize CAP feeds on a map ("common operating picture")
8. Use GIS-based risk assessment techniques to develop predefined (hazard, event, and severity specific) CAP alert area templates\1. delivery options: HTTP, RSS/Atom, SMS, Email, Voice-text (audio)
9. subscription management (who, what, when, and where) serve as a subhub
10. Feed in to Google Alerthub [3] and ​IFRC Universal Hazard App
11. support multiple language CAP message publication
12. digitally sign the messages
13. Mobile application to server as a publisher and a subscriber
14. Pictographs for Alerting
15. Event 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>