LMIS DAZ
Contents
List of group members
- Amanpreet Kaur Powar (amanprep@ifi.uio.no)
- Uzma Sabir (uzmasa@student.matnat.uio.no)
- Zubair Asgar (zubaira@ifi.uio.no)
- Devesh Sharma (deveshs@ifi.uio.no)
Summary of requirements
Click on Logistics Management Information System (LMIS) Light for the project description
Technologies and Framework
- Java android
- SQLite Database
- RESTFul API provided by DHIS2 Messaging module for posting messages.
Tools
- Android SDK
- Android Studio
- Emulator Lollipop x86
Time schedule
Milestone 1: 8th November
- Document features and architecture on Wiki
- This project is a prototype of Logistic Management Information System. A simple android form app will take input related to Medical Logistics and will broadcast the request encapsulating all the parameters entered in the form to either single or multiple user depending on how many users are there in a group or organizational unit.
- Show understanding of DHIS2 web apps
- DHIS2 has quit many web app modules. But there are few which are related to LMIS project. Those are Messaging, Origanizational Units and Users.
- Messaging Framework is responsible for send/receive of inside (between Dhis users) and outside (email) messages. It exposes RESTFUl API in order to use this framework for message delivery.
- The location where data is coming from could be any medical facility i.e Health Centre, Nursing Home etc and these facilities belong to one of the Organizational Unit. One OU can have multiple facilities.
- In DHIS2 user can exist either in isolation or being attached to any User Group or even Organizational Unit. So Messaging module can send a message to either a single user or to any other User Group or Organizational Unit. In case later cases message will be delivered to all users attached to that User Group or Organizational Unit.
Milestone 2: 22th November
- First bare-bone version - static HTML
- Uploadable as DHIS2 web app
Milestone 3: 4th December
- Finished, if applicable also with mobile app.
Final Delivery: 11th December
Tasks division within the group
Screenshots and screen flows
Documented learning during project
Suggested improvements
- Error occurring in Payload in JSON and POST for Organisation Unit
- GUI
Colors Scheme:
The mobile apps must be user friendly and their design must be attractive. The GUI of our application needs improvements such as; from the first page to the last page the design should have some pattern and same color scheme. Dark background colors are always recommended to the mobile apps. To make text visible on dark backgrounds, their color must be light enough to show the contrast.
Buttons Alignment:
The color, button alignment and its design need improvements. The design and color is not looking attractive and alignment is also not managed perfectly. The delete button should be placed in front of each added commodity instead of placing it on the top.
- Functionality:
Delete: There are some areas of improvements found in functionality perspectives. We have a delete functionaltiy of an added commodity. Currently it is working perfectly but must be improve.
Improvement; There should be a way to identify the specific commodity a user wants to delete instead of re writing it into the text boxes.
2. To perform the functionality of delete all the records are fetched from the database and suggestion for improvement for this is as follows.
Improvement: Instead of selecting all the records it must use the id of each commodity to delete.
- Edit: In out context there must be an option for the user to edit the name and quantity of the commodity. In case a user adds a commodity by mistake, or wants to edit the name or quantity, our current app does not provide any facility to handle this problem. So the edit functionality should be added to tackle this problem to facilitate a user who has some wrong entries in a large list of items.
Link to repository
Private Repository(Shared with Mustafa Mahamid - mustafam) https://ds131186@bitbucket.org/lmis_daz/lmis_daz.git
