Security Management Module

Introduction

"In the last decade, lethal attacks against humanitarian personnel have tripled, reaching over 100 deaths per year." Delivering aid in risky environments: what works? UN OCHA 12 April 2011 At present there does not appear to be any purpose designed software that is easy to use and deploy for the security tracking of volunteers/staff members operating in hostile environments. Building on the Volunteer Module the Security Management Module would enable the humanitarian community "to stay and deliver."

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

Mary a UNDSS Security Officer in a city in a developing country is ordered to concentrate all staff from various Agencies, Funds and Programs at a secure location due to widespread rioting. Peter a staff member with Agency X is reported as not having arrived at the concentration point. Peter looks in the Sahana Eden Security Management Module and is able to find out who the Staff Member's supervisor is. Mary contacts and confirms with the supervisor that the staff member is indeed in country and not on leave. Further Mary finds that the staff member should be at home. Mary prints out a sheet of paper with a photo of the staff member, a GPS reference and photograph of the entrance of her residence and a Google/Openstreetmap or sketch showing the exact location. (In many developing or war damaged cities there are no street/house numbers or road signs.) Mary is able to locate the residence and bring Peter to the concentration site.

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>

---