Version 9 (modified by 11 years ago) ( diff ) | ,
---|
BluePrint: <Name of the solution>
Table of Contents
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
Emergency personnel and people in or near a crisis zone. Statistics reporting and missing persons agencies will be able to more easily report on people using the app. This should simplify some aspects of rescue operations and news propagation of crises to affected peoples in modern areas.
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>.>
User Story 1: Search and rescue teams want to see if there are any people they might have missed in an area. They want some way for people who have working mobile phones to be able to contact them and let them know where they are. This would make their job much easier and quicker.\
User Story 2: Something something families and disasters
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>