Geo-1

Members

Ying Li
Henrik Nårstad
Marcel Eggum
Henrik Vest Simonsen

Summary of requirements

(Application requirements and user stories)

(Who is the application intended for?)

- A user should be able to register single event entries with information about the context and location.
- These entries need not be related to other, existing entitites from the DHIS2 system. But act as single objects in the system. 

- All entries should be presented on a dynamic map. With the ability to filter entries by categories. 

- Location information about an entry should be based on GPS based latitude and longditude coordrinates. 

- It is wishful to bind multimedia elements to an entry. As an example, it would be preferable to attach one or more images to a single entry point. 

- The application should be available as an DHIS2 Web-Application and an Android based mobile Application

Form saving some log entries about patient admission and discharge associated with geographical location.
- Single event data entries: events are not linked neither to each other nor to other objects registered is the system (for example patient object)
- The location might be either current location or selected manually ( pointed on a map?)
- Show entries on map ( maybe with filtering option: identify desease outbreak)
- Can get entry details when clicking on a needdle
- Solution available as android app and web app

Task Management

Our project tasks and user-stories are created and maintained in Trello. A task manager and Kanbean board. 

The Board can be is publicly available, and can be viewed @ Geo-Location Trello

Time Schedule

Milestone 1 :

Wiki is created. Team members have successfully set up DHIS2.
HTML, CSS and JS workshops are completed

Milestone 2: 

Application requirements and user stories are written down. 
Low fidelity prototypes are drawn. 

Sprints

(Week by week plan)

Prototypes, Design

(Low fidelity user interface sketches)

Diagrams

(UML based class or interaction diagrams)