Difference between revisions of "Agile Alligators"

From mn/ifi/inf5750
Jump to: navigation, search
(Division of Workload)
Line 43: Line 43:
  
 
=== Division of Workload ===
 
=== Division of Workload ===
* Emil: Low-fidelity prototypes, UX dev,  
+
* Emil: Low-fidelity prototypes, UX dev, displaying previous data values on HTML side of things
* Mwiza:  
+
* Mwiza: Responsible for retrieving previous data values on the javascript side of things
* Nico:
+
* Nico: Setup postgres-database & hibernate connection, responsible for additional usability changes
  
 
== Prototypes ==
 
== Prototypes ==

Revision as of 14:41, 11 December 2015

Link to project description: [1]

Our project will look at the usability of the Tracker Capture app in DHIS2. We will focus on fulfilling the requirements stated by the users, but also look into other possible usability improvements.


Group members

Summary of requirements

  • Visualize the previous data from the database dynamically
  • Further improve usability of the app

Technologies

We foresee developing the existing web application and therefore using the following web technologies: HTML5, CSS, Javascript, Hibernate, PostgreSQL, Spring, Maven, JSON. Although this may be subject to change as the project develops.

Milestones

Milestone 1: 8th November: Finish project planning; Document features and architecture on Wiki

Milestone 2: 22nd (Delayed: 23rd) November: Initial, low-fidelity HTML prototype

Milestone 3: 4th December: Final product

Final delivery: 11th December

Presentation: 17th December

Progress

Meetings

  • Nov. 6th: We decided on a schedule for weekly meetings on tuesdays from 10:15 - 12:00. Communication channels established by exchanging emails and connecting on facebook for IM communication. Initial vision and plan developed.
  • Nov. 10th: Cancelled due to group members being sick.
  • Nov. 17th: Sum up of current progress, and collective work session.
  • Nov. 23rd: Finished the static HTML prototype
  • Nov. 24th: Mapping way forward on Webapp
  • Nov. 25th: CANCELED
  • Dec. 1st:
  • Dec. 3rd:
  • Dec. 4th: Project installation
  • Dec. 8th: Frontend development: JS Exploration
  • Dec. 9th: Frontend development: Implementation and testing
  • Dec. 10th: Frontend development: UX upgrades

Division of Workload

  • Emil: Low-fidelity prototypes, UX dev, displaying previous data values on HTML side of things
  • Mwiza: Responsible for retrieving previous data values on the javascript side of things
  • Nico: Setup postgres-database & hibernate connection, responsible for additional usability changes

Prototypes

Screenshots

Legacy

Documentation of legacy systems from before any effect's are implemented.

Sketches

Changes to The Tracker Capture App

In addition to the main task of this assignment, which was implementing the ability to view data entries for previous events when entering data, we have made some additional changes to the Tracker Capture App that we believe could enchance the user experience.

Changing Event-ordering Within a Stage from Right to Left to Left to Right

In the default Tracker Capture App, when creating a new event in a stage, new events are added to the left of the previous one. We found this confusing, as events within stages would come in reverse chronological order when read from left to right. This contrasts with the order stages are found in a program, and also how we have added the previous values of events to the left of the data-fields. By simply changing the order, we feel the layout for a program with it's stages and events is more intuitive.

Some Changes to the Buttons

<to do>

Learning Outcomes

Suggested improvements to Tracker Capture App

  • Data validation section Stage.programStageDataElements e.g validate, weight and CD4 count values
  • Centralised Naming convention, eg Infant weight and weight


Repo

Static HTML Prototype:

git@github.com:ehatle/AlligatorStaticHTML.git

Final product:

git@github.com:ehatle/AgileAlligators.git

Download link to sample web app