Difference between revisions of "MFL"

Revision as of 22:09, 5 December 2017

Group members

Aanund Nordskog (aanundjn@ifi.uio.no)

Nicole Keppler (nicoleke@student.matnat.uio.no)

Saliha Sajid (salihasa@student.matnat.uio.no)

Henrik Halvorsen Hortemo (henrihho@ifi.uio.no)

Product description

MFL is a DHIS2 application for searching, browsing and proposing changes to organisation units, as requested by the Master Facility List assignment.

User stories

Our understanding of the assignment is reflected by the following user stories:

• As a user I want to find specific organization units
  • As a user I want to search for organization units by name
  • As a user I want to filter my search results by unit group membership
  • As a user I want to filter my search results by ancestor relationships
  • As a user I want to filter my search results by which data sets are assigned to the organization units
• As a user I want to see detailed information on a particular organization unit
  • As a user I want to see all attributes of a particular organization unit
  • As a user I want to see the location of a particular organization unit
  • As a user I want to see which organization unit groups a particular organization belongs to
  • As a user I want to see what data sets are assigned to a particular facility
  • As a user I want to see data element and/or indicator values for the particular organisation unit for the current/last year

• As an administrator I want to select what data elements and/or indicators to display

• As a user I want to propose changes to organization units
  • As a user I want to propose changes to organization unit attributes
  • As an administrator I want to review submitted proposals
  • As an administrator I want to mark proposals as resolved/invalid

Mockups

Our UX approach is reflected by the following mockups:

MFL on Moqups.com

Screenshots

The application currently looks like this:

[Browser]

[Detail]

[Admin]

Architecture

MFL will be developed as a Single-Page Application (SPA) using Facebook's React framework. React was chosen for its ubiquitousness as well as for consistency with existing DHIS2 applications. For that reasons, we plan to use the already defined UI components of DHIS (https://github.com/dhis2/d2-ui).

Using React implies, among other things, a component-based UI and uni-directional data-flow. We are considering using Redux to manage the application state.

Timeline for development

Week 44

• Finalize product requirements
• Create mockups
• Setup application foundation (inside DHIS)

Week 45

• Static version of the application:
  • Search view
  • Detailed view
• Document relevant API queries

Week 46

• Static version of the application:
  • Edit view
  • Admin view
• Dynamic version of the application:
  • Search view
  • Detailed view

Week 47

• Dynamic version of the application:
  • Edit view
  • Admin view

Week 48

• Buffer and Testing
• 1.12.2017: End of project

Licensing

Division of labour

We will assign individual user stories from our backlog.

External links

MFL on GitHub

MFL on Moqups.com