Dms 2.0 Plan Proposal

1,269 views

Published on

Presentation for Migration to Java.

Published in: Technology, Business
  • Be the first to comment

Dms 2.0 Plan Proposal

  1. 1. DMS 2.0 JDEVELOPER PLAN
  2. 2. Vision Statement <ul><li>TO MIGRATE OUR DMS SYSTEM FROM ORACLE FORMS TO JAVA EE. ALSO, TO BUILD THE SKILLS IN-HOUSE TO MAINTAIN AND BUILD NEW SYSTEM AFTER THE MIGRATION IS COMPLETED. </li></ul>
  3. 3. Migration Objectives <ul><li>Use industry standard technologies. </li></ul><ul><li>Leverage existing staff’s knowledge base. </li></ul><ul><li>Mix mentoring and training into Development. </li></ul><ul><li>Retain the Oracle DBMS. </li></ul><ul><li>Modernize the user interface. </li></ul>
  4. 4. Technology Decision <ul><li>As an Oracle shop, we naturally gravitated toward an Oracle product. We were especially impressed by the amount of support that Oracle has provided to the Oracle Forms and PL/SQL expert who is transitioning to this new world. </li></ul><ul><li>Which Technology Realm? </li></ul><ul><li>Which Development Tool? </li></ul><ul><li>Which Technology Stack? </li></ul><ul><li>Which Persistence Layer? </li></ul><ul><li>Which additional Frameworks to help migration? </li></ul>
  5. 5. Which Technology Realm? <ul><li>Decision: Java EE </li></ul><ul><li>Industry Standard. </li></ul><ul><li>Oracle is focusing on it. </li></ul><ul><li>Available anywhere, any time. </li></ul>
  6. 6. Which Development Tool? <ul><li>Decision: Jdeveloper11g </li></ul><ul><li>Template Driven </li></ul><ul><li>Reason: </li></ul><ul><ul><ul><li>Contains Oracle Application Development Framework(ADF). </li></ul></ul></ul><ul><ul><ul><li>Optimized for Oracle Databases. </li></ul></ul></ul><ul><ul><ul><li>Standard Oracle Development Tool. </li></ul></ul></ul><ul><ul><ul><li>Relatively familiar environment for Forms Developer. </li></ul></ul></ul>
  7. 7. Which Technology Stack? <ul><li>Decision: Oracle ADF frameworks </li></ul><ul><li>Reasons: </li></ul><ul><ul><ul><li>Strong support in Jdeveloper. </li></ul></ul></ul><ul><ul><ul><li>Declarative programming </li></ul></ul></ul><ul><ul><ul><ul><li>More familiar to PL/SQL and Forms developers. </li></ul></ul></ul></ul><ul><ul><ul><li>Oracle supports them </li></ul></ul></ul><ul><ul><ul><ul><li>Vendor support vs. community support. </li></ul></ul></ul></ul><ul><ul><ul><li>Oracle is using them for Fusion Apps. </li></ul></ul></ul>
  8. 8. Which Persistence Layer? <ul><li>Decision: ADF BC </li></ul><ul><li>Reasons: </li></ul><ul><ul><ul><li>ADF BC is better suited for Oracle DB than EJB. </li></ul></ul></ul><ul><ul><ul><li>Easier than EJB and TopLink for traditional Oracle Developers. </li></ul></ul></ul><ul><ul><ul><li>Simple to develop – less Java code. </li></ul></ul></ul><ul><ul><ul><li>Highly-evolved. </li></ul></ul></ul>
  9. 9. Which View/Controller Layers? <ul><li>Decision: 11g ADF Faces/JSF </li></ul><ul><li>Reasons: </li></ul><ul><ul><li>Oracle is using in Fusion Apps. </li></ul></ul><ul><ul><li>Excellent support in Jdeveloper. </li></ul></ul><ul><ul><li>ADF Faces. </li></ul></ul><ul><ul><li>Oracle supported. </li></ul></ul>
  10. 10. Which Add’l Frameworks? <ul><li>OraFormsFaces </li></ul><ul><ul><li>Toolkit to embed Forms in a Web Application to co-exist with Java apps. </li></ul></ul><ul><li>JHeadstart </li></ul><ul><ul><li>Extension for Template – based automation of ADF development. </li></ul></ul>
  11. 11. The Team <ul><li>Leverage existing Staff PL/SQL knowledge. </li></ul><ul><li>Building infrastructure for a Template based approach is key. </li></ul><ul><li>All Staff has a minimum of 7+ years in Oracle Development. </li></ul><ul><li>Adopting Jdeveloper and ADF would be a more natural transition for Form Developers. </li></ul>
  12. 12. Market Summary <ul><li>Main benefit is having Oracle and community to support your investment into Java. </li></ul><ul><li>The migration will allow us to open the door to a Rich Internet Application experience and not be locked into a close Framework as Oracle Forms has been in the past. </li></ul><ul><li>Plus future is secure with Fusion Apps being on same Technology Stack. </li></ul>
  13. 13. Opportunities <ul><li>Migrating the DMS system in 3+ years to Java. </li></ul><ul><li>Transitioning the Staff to Java in 2 years. </li></ul><ul><li>Establish New Development Methodology. </li></ul><ul><li>Bring Web 2.0 technology into DMS 2.0 </li></ul><ul><li>Enhanced the User Web experience with Dashboards. </li></ul><ul><li>Look into Mobile Technology for DMS 2.0. </li></ul>
  14. 14. Business Concept <ul><li>Migrate into a Rich Internet Application with current DMS functionality. </li></ul><ul><li>Explore Web 2.0 capabilities into future DMS 2.0 system. </li></ul><ul><li>Provide faster updates and enhancements thru Web deployment. </li></ul><ul><li>Integrate new services and existing process into DMS for a more homogenous system. </li></ul>
  15. 15. Resource Requirements <ul><li>List requirements for the following resources: </li></ul><ul><ul><li>4 Developers, 1 Java Developer, 1 Architect, 1 DBA, and 1 Unix Admin. </li></ul></ul><ul><ul><li>Jdeveloper, Subversion, TOAD, Testing Tool, etc. </li></ul></ul><ul><ul><li>Provide Training, books, and Java Mentoring. </li></ul></ul><ul><ul><li>Migration Tools to speed up conversion of system. </li></ul></ul><ul><ul><li>Consulting Services for resource shortage. </li></ul></ul>
  16. 16. Risks and Rewards <ul><li>Risks is 3 years after an aggressive schedule. </li></ul><ul><li>We will manage it by evaluating Migration paths, Skills of Staff, and Project Modules complexities. </li></ul><ul><li>Choosing Oracle Jdeveloper and ADF will provide the support and Technology to succeed now and in the future. </li></ul><ul><li>We should be left with a maintainable and current supported system by staying with Oracle Technology. </li></ul>

×