BHJS
Contents
- 1 List of group members
- 2 Project Suggestions
- 3 Application Structure
- 4 Summary of Requirements
- 5 Time Schedule
- 6 How you are dividing tasks within the group
- 7 Screenshots and screen flows
- 8 Documented learning during project
- 9 Suggested improvements to APIs etc
- 10 Link to repository
- 11 Download link to sample web app or Android app
List of group members
- Bård Winther (baardew) baardew@ifi.uio.no
- Henrik Tufte Lien (henriktl) tuftelien@gmail.com
- Jonas Sandnes (jonsandn) jonsandn@ifi.uio.no
- swati sharma (swatis) swatis@ifi.uio.no
Project Suggestions
This section is just a bunch of notes that should be further developed or organized better.
Application Structure
For the remainder of this document "backend" would refer to application controller and other javascript that is not used directly with presentation. Likewise, "fronend" denote everything connected to or is GUI elements.
File layout
Organization of program structure using MVVM:
Technologies:
Javascript, AngularJS, HTML and CSS. JSON for rest communication.
TDD is a must: Protractor or alternatively QUnit [UNRESOLVED]
Attempt to solve the problem with a generic implementation that parses any json object and displays it on screen.
GUI Layout:
The GUI laytout describes the three different methods of viewing the content. Each view is switchable in the same main page.
Api index (listing the resources)
resource view (list of objects)
object view (info about a specific object)
Questions:
Could not find the API for data model fields (https://www.dhis2.org/doc/snapshot/en/user/html/apes04.html)?
Summary of Requirements
List is in prioritized order
- Display every possible path obtained by click-through of API (in other words, every link should be "followable")
- User friendly, which implies: no need for direct keyboard input, all information readily avaiable (no hidden content) and simple to retrace steps
- The program should deal with errors and misuse correctly and elegantly (in other words, not crash if someone does something un-expected)
Time Schedule
These milestones are guidelines only, except for 3rd December.
- 1. nov : design layout finished
- 8. nov : static html layout presentable
- 29. nov : main work done
- 3. dec : hard deadline
How you are dividing tasks within the group
baardew: backend controller and configuration + additional frontend where required
henriktl: ?
jonsandn: ?
swatis: ?
Screenshots and screen flows
Documented learning during project
Suggested improvements to APIs etc
Link to repository
gitolite@git.uio.no:inf5750/baardew/dhis_bhjs