1 / 41

Open Source Migration for Software Developer's Assistant to Drupal CMS

This project aims to migrate the Software Developer's Assistant (SDA) to an open-source Content Management System (CMS), specifically Drupal, to address SDA's limitations. The existing SDA lacks organization boundaries, has an inflexible modular architecture, and faces challenges in upgrades and clean URL support. The candidate solution of using PHP, MySQL, and Apache is proposed for the migration to Drupal due to its flexible modular architecture, organization boundary support, and strong community backing. The project includes transitioning SDA functionalities to Drupal's user interface, logic presentation, and communication mechanisms. Lessons learned include leveraging teamwork and tools like Google Wave. The study concluded with positive feasibility results and recommends Drupal for the successful migration.

eeric
Download Presentation

Open Source Migration for Software Developer's Assistant to Drupal CMS

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. A prototype for migrating the Software Developer’s Assistant (SDA) to open source Content Management System (CMS) Instructor: • Kwok-Bun Yue Mentor: • AbbasiDhilawala Team # 1: • AdityaMacherla • Arun Gupta Mahankali • Shruti Damle • Truyen Van Le • VishakhaKadam University of Houston Clear Lake

  2. Content • Project Goal • Background • SDA Limitations • Candidate Solutions • Why Drupal? • System Architecture • Implementation • Lessons Learned • Conclusion • Questions University of Houston Clear Lake

  3. Project Goal A prototype for migrating the Software Developer’s Assistant to open source Content Management System University of Houston Clear Lake

  4. Background • Who developed SDA? University of Houston Clear Lake

  5. Background • Who developed SDA? • What is SDA? University of Houston Clear Lake

  6. Background • Who developed SDA? • Who are using SDA? • What is SDA? University of Houston Clear Lake

  7. SDA Limitations • No organization boundaries University of Houston Clear Lake

  8. SDA Limitations • No organization boundaries • Inflexible modular architecture Module 1 Module 2 Module 3 Module 4 Module 5 Module 6 Module 7 Module 8 Module 9 University of Houston Clear Lake

  9. SDA Limitations • No organization boundaries • Inflexible modular architecture • Difficult to upgrade University of Houston Clear Lake

  10. SDA Limitations • No organization boundaries • No clean URL • Inflexible modular architecture • Difficult to upgrade https://terra2.tietronix.com/SDA/c/portal/layout?p_l_id=269.1&p_p_id=1004&p_p_ University of Houston Clear Lake

  11. Candidate Solutions JAVA MySQL Apache University of Houston Clear Lake

  12. Candidate Solutions PHP MySQL Apache University of Houston Clear Lake

  13. Candidate Solutions PHP MySQL Apache University of Houston Clear Lake

  14. Why Drupal? University of Houston Clear Lake

  15. Why Drupal? • Flexible modular architecture New Module University of Houston Clear Lake

  16. Why Drupal? • Flexible modular architecture • Organization boundary support University of Houston Clear Lake

  17. Why Drupal? • Flexible modular architecture • Organization boundary support • Strong community support University of Houston Clear Lake

  18. Why Drupal? • Flexible modular architecture • Organization boundary support • Strong community support • Symmetry in organization University of Houston Clear Lake

  19. Current System Architecture University of Houston Clear Lake

  20. New System Architecture THIS PROJECT EXISTING SYSTEM Presentation layer SDA Core University of Houston Clear Lake

  21. New System Architecture Drupal • User Interface • Logic to present data • PHP/HTML/JS/CSS Presentation layer SDA Core University of Houston Clear Lake

  22. New System Architecture Communication mechanism to interact with SDA Core Presentation layer SDA Core University of Houston Clear Lake

  23. Implementation • Life Cycle • My Worklist University of Houston Clear Lake

  24. Life Cycle • Display graphical view of project’s processes and activities University of Houston Clear Lake

  25. Life Cycle • Display graphical view of project’s processes and activities • Link to the lower-level processes University of Houston Clear Lake

  26. Life Cycle • Display graphical view of project’s processes and activities • Link to the lower-level processes • Display breadcrumb University of Houston Clear Lake

  27. Life Cycle • Display graphical view of project’s processes and activities • Link to the lower-level processes • Display breadcrumb • Display Legend University of Houston Clear Lake

  28. Life Cycle • Get project data from SDA core Life Cycle Presentation layer SDA Core University of Houston Clear Lake

  29. Life Cycle • Life Cycle Demo University of Houston Clear Lake

  30. My Worklist • Display the work assigned for the user for that project in a tree format University of Houston Clear Lake 30

  31. My Worklist • Get work items assigned to user from SDA core My Worklist Presentation layer SDA Core University of Houston Clear Lake 31

  32. My Worklist • My Worklist Demo University of Houston Clear Lake

  33. Lessons Learned • Brainstorming University of Houston Clear Lake

  34. Lessons Learned • Brainstorming • Team Work University of Houston Clear Lake

  35. Lessons Learned • Brainstorming • Team Work • Google wave University of Houston Clear Lake

  36. Conclusion • Positive results of feasibility study University of Houston Clear Lake

  37. Conclusion • Positive results of feasibility study • Completed two modules University of Houston Clear Lake

  38. Conclusion • Positive results of feasibility study • Completed two modules • Highly recommend Drupal for migration University of Houston Clear Lake

  39. Questions? University of Houston Clear Lake

  40. References • [1] Drupal http://drupal.org/ [2] Drupal http://en.wikipedia.org/wiki/Drupal [3] Joomla http://en.wikipedia.org/wiki/Joomla [4] Joomla http://www.joomla.org/ [5] Joomla CMS and Its Advantages http://cms.sys-con.com/node/1029542 [6] Liferay http://en.wikipedia.org/wiki/Liferay [7] Liferay http://www.liferay.com/ [8] PHP/Java Bridge http://php-java-bridge.sourceforge.net/pjb/ [9] Software Developer’s Assistant (SDA) https://terra2.tietronix.com/SDA/html/common/data/Help/index.htm [10] XMLRPC http://ws.apache.org/xmlrpc/ University of Houston Clear Lake

  41. For further queries contact truyen.le@tietronix.com University of Houston Clear Lake

More Related