Atlas Module Project Timeline

Owned by Victor Chircu
Last updated: May 22, 2011 by Ben WolfeVersion comment
2 min read

1. Initial Proposed Timeline

April 25 – May 23

  • Familiarise with the OpenMRS system.

  • Elaborate a detailed architectural plan, while getting feedback from the mentor and other developers from the OpenMRS community.  

May 24 – June 6

  • Design the JSP Pages

June 6 – June 13

  • Make a first version of the Javascript code, that will interact with the web service (or a mock-up of it, if not available)

By mid-term evaluation, I should have the general structure of the web pages and a working Proof of Concept.
June 13 – June 27

  • Start working on the jQuery plug-in, by defining it’s structure.

June 27 – July 1

  • Continue the work on the plug-in, making it fully functional.

July  11 – July 18

  • Make sure that the plug-in uses Progressive Enhancement, so users that have blocked Javascript code can still have a nice looking interface.

July 18 – July 25

  • Design Test Cases.

  • Implement Unit Tests, where possible, using one of the available JS Unit Test Frameworks.

July 25 – August 22

  • Test, make further improvements.

  • Buffer Zone

After discussing with Burke, I’ve revised the Project Timeline.

2. Project Timeline

April 25 – May 23

  • Familiarise with the OpenMRS system.

  • Elaborate a detailed architectural plan, while getting feedback from the mentor and other developers from the OpenMRS community.  

May 24 – June 13

  • Design a JSP Page that collects the implementation name and geo location (by selecting it’s location on a map) and sends it to OpenMRS through an HTTP Post

  • Prepare for the first presentation (on the 9th of June)

June 13  -- July 1

  • Add the option for the user to select it’s geolocation by entering an address in a textbox (autocomplete would be a nice feature)

July  1 – July 18

  • Add the other JSP Pages that will allow the user to select what other implementation info  (contact details, photo, etc) and what statistics to send to the server, and post this data to the server

July 18 – July 25

  • Save the input values in the current implementation Global Properties table.

July 25 – August 1

  • Implement a job that sends the statistics to OpenMRS periodically.

July 1 – August 22

  • Define Unit Tests.

  • Test, make further improvements.

  • Buffer Zone