Difference between revisions of "Modernization Roadmap"

From OpenEMR Project Wiki
(major edit :))
Line 1: Line 1:
=Overview=
==Objective==
:Community is in midst of designing a strategy to modernize both the user interface(front end) and codebase(back end) of OpenEMR. These are basically notes from the ongoing discussions in the forum.
The OpenEMR project codebase and user interface can benefit from modern implementation approaches. The project itself is very large and modernizing it will be accomplished in a very fragmentary way that requires a very organized and enthusiastic approach.
=User interface=
:#Modern styles (first generation).
:#Incorporate bootstrap.
:#Modern styles (second generation).
:#Remove frames (ie. convert to iframe).


=Codebase=
==Roadmap==
:#Begin to normalize directory structure
 
:#*Standard place for static css/js assets (such as jquery), which can be easily migrating when needed in the future.
''(this is intentionally high level)''
:#*Standard place for third party php packages (likely managed/organized via composer), which can be easily migrated when needed in the future.
 
:#Convert codebase to fully use model classes.
* MVC framework with unit tests
:#Integrate an MVC (community is considering Zend at this time).
* Manual test cases
:#Complete the normalization of the directory structure.
* Normalized directory structure
:#Refactor codebase to use most modern version of each asset.
* User interface makeover
 
==Team Space Cats==
 
In order to verify that the codebase refactor is correct as new modules are introduced, high-quality manual test cases need to be built up and maintained moving forward. This is useful for the scope of the modernization project and moving forward as the test suites will enable a group of testers to run through them before releases are shipped. Note that Matthew determined Selenium testing will take a very long time (current frame/pop-up based impl. renders it very difficult… these tests can be added later when a new UI is introduced).
 
All project tracking and information is here: http://open-emr.org/wiki/index.php/Manual_Tests (the Patient Demographics suite is already done… please assign yourself to other suites).
 
'''Team members:'''
* Matthew Vita (lead)
* ???
* ???
 
==Team ChooseAName==
Refactoring the codebase to leverage the MVC design pattern, unit tests, and a more maintainable design is very important.
 
All project tracking and information is here: http://open-emr.org/wiki/index.php/Codebase_Refactor (please assign yourself to individual tasks).
 
'''Team members:'''
* Robert Down (lead)
* ???
* ???
 
==Team PleasePickAName==
Simply put, our EMR needs a modern makeover.
 
All project tracking and information is here: http://www.open-emr.org/wiki/index.php/Active_Projects#UI_Improvement (Robert, please create a project page for this so folks can assign themselves to individual work items).
 
'''Team members:'''
* Robert Down (lead)
* ???
* ???


=Ongoing Forum Discussions=
=Ongoing Forum Discussions=
Line 21: Line 47:
:*[https://sourceforge.net/p/openemr/discussion/202506/thread/d72c360b/ Discussion: Introducing an MVC framework]
:*[https://sourceforge.net/p/openemr/discussion/202506/thread/d72c360b/ Discussion: Introducing an MVC framework]
:*[https://sourceforge.net/p/openemr/discussion/202506/thread/d4ec2b8b/ assets directory]
:*[https://sourceforge.net/p/openemr/discussion/202506/thread/d4ec2b8b/ assets directory]
 
:*[https://sourceforge.net/p/openemr/discussion/202506/thread/5f706dff/ Manual Tests Project Thread]
=Links=
:*[http://www.phptherightway.com/ PHP The Right Way]

Revision as of 20:39, 6 July 2016

Objective

The OpenEMR project codebase and user interface can benefit from modern implementation approaches. The project itself is very large and modernizing it will be accomplished in a very fragmentary way that requires a very organized and enthusiastic approach.

Roadmap

(this is intentionally high level)

  • MVC framework with unit tests
  • Manual test cases
  • Normalized directory structure
  • User interface makeover

Team Space Cats

In order to verify that the codebase refactor is correct as new modules are introduced, high-quality manual test cases need to be built up and maintained moving forward. This is useful for the scope of the modernization project and moving forward as the test suites will enable a group of testers to run through them before releases are shipped. Note that Matthew determined Selenium testing will take a very long time (current frame/pop-up based impl. renders it very difficult… these tests can be added later when a new UI is introduced).

All project tracking and information is here: http://open-emr.org/wiki/index.php/Manual_Tests (the Patient Demographics suite is already done… please assign yourself to other suites).

Team members:

  • Matthew Vita (lead)
  • ???
  • ???

Team ChooseAName

Refactoring the codebase to leverage the MVC design pattern, unit tests, and a more maintainable design is very important.

All project tracking and information is here: http://open-emr.org/wiki/index.php/Codebase_Refactor (please assign yourself to individual tasks).

Team members:

  • Robert Down (lead)
  • ???
  • ???

Team PleasePickAName

Simply put, our EMR needs a modern makeover.

All project tracking and information is here: http://www.open-emr.org/wiki/index.php/Active_Projects#UI_Improvement (Robert, please create a project page for this so folks can assign themselves to individual work items).

Team members:

  • Robert Down (lead)
  • ???
  • ???

Ongoing Forum Discussions

Ongoing forum discussions of the above roadmap can be found here.
Retrieved from "https://www.open-emr.org/wiki/index.php?title=Modernization_Roadmap&oldid=23207"