Version 5 (modified by 9 years ago) ( diff ) | ,
---|
BluePrint: Sahana First Response
Table of Contents
Current Status
Available features:
Missing features:
- Common Operating Picture with a Crisis Map
- manage event type specific templates and messages
- receive SITREP and RM feeds [2] to serve as an aggregator and a pubhub
- approve or reject dispatch, incident reports, situational-reports, request-resources
- delivery options: HTTP, RSS/Atom, SMS, Email, FTP (dynamic labels)
- built on the Emergency Data Exchange Language (EDXL) SITREP and RM standards
- subscription management (who, what, when, and where) serve as a subhub
- Exchange data with other EDXL compliant systems
- support multiple language SITREP/RM message publication
- digitally sign the messages
- Mobile application to server as a publisher and a subscriber
- Pictographs for reporting incidents and situational=reports
- 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>
Attachments (11)
-
use_case_ICS.2.png
(104.1 KB
) - added by 9 years ago.
ICS Use Case
-
use_case_ICS.3.png
(123.7 KB
) - added by 9 years ago.
ICS Use Case
-
use_case_ICS.png
(128.7 KB
) - added by 9 years ago.
ICS Use Case
-
use_case_ICS.4.png
(128.7 KB
) - added by 9 years ago.
ICS Use Case
-
process_flow_incident_management.2.png
(75.2 KB
) - added by 9 years ago.
SAFIRE Process Flow
-
process_flow_incident_management.png
(77.2 KB
) - added by 9 years ago.
SAFIRE Process Flow
-
process_flow_incident_management.3.png
(77.2 KB
) - added by 9 years ago.
SAFIRE Process Flow
-
ER_Diagram_2.png
(21.0 KB
) - added by 7 years ago.
SAFIRE high level ER diagram
-
ER_Diagram_v3.png
(40.5 KB
) - added by 7 years ago.
SAFIRE high level ER diagram
-
ER_Diagram_v5.png
(59.3 KB
) - added by 7 years ago.
SAFIRE high level ER diagram
-
seychells.png
(71.8 KB
) - added by 7 years ago.
seychells
Download all attachments as: .zip