DMS 2.0 JDEVELOPER PLAN Vision Statement TO MIGRATE OUR ...

translatoryazooInternet και Εφαρμογές Web

12 Νοε 2013 (πριν από 3 χρόνια και 10 μήνες)

87 εμφανίσεις

DMS 2.0

JDEVELOPER

PLAN

Vision Statement

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.

Migration Objectives


Use industry standard technologies.


Leverage existing staff’s knowledge base.


Mix mentoring and training into Development.


Retain the Oracle DBMS.


Modernize the user interface.

Technology Decision


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.


Which Technology Realm?


Which Development Tool?


Which Technology Stack?


Which Persistence Layer?


Which additional Frameworks to help migration?

Which Technology Realm?


Decision: Java EE


Industry Standard.


Oracle is focusing on it.


Available anywhere, any time.

Which Development Tool?


Decision: Jdeveloper11g


Template Driven


Reason:


Contains Oracle Application Development
Framework(ADF).


Optimized for Oracle Databases.


Standard Oracle Development Tool.


Relatively familiar environment for Forms Developer.

Which Technology Stack?


Decision: Oracle ADF frameworks


Reasons:


Strong support in Jdeveloper.


Declarative programming


More familiar to PL/SQL and Forms developers.


Oracle supports them


Vendor support vs. community support.


Oracle is using them for Fusion Apps.

Which Persistence Layer?


Decision: ADF BC


Reasons:


ADF BC is better suited for Oracle DB than EJB.


Easier than EJB and TopLink for traditional Oracle
Developers.


Simple to develop


less Java code.


Highly
-
evolved.

Which View/Controller Layers?


Decision: 11g ADF Faces/JSF


Reasons:


Oracle is using in Fusion Apps.


Excellent support in Jdeveloper.


ADF Faces.


Oracle supported.

Which Add’l Frameworks?


OraFormsFaces


Toolkit to embed Forms in a Web Application to co
-
exist with Java apps.


JHeadstart


Extension for Template


based automation of ADF
development.

The Team


Leverage existing Staff PL/SQL knowledge.


Building infrastructure for a Template based
approach is key.


All Staff has a minimum of 7+ years in Oracle
Development.


Adopting Jdeveloper and ADF would be a more
natural transition for Form Developers.

Market Summary


Main benefit is having Oracle and community to
support your investment into Java.


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.


Plus future is secure with Fusion Apps being on
same Technology Stack.

Opportunities


Migrating the DMS system in 3+ years to Java.


Transitioning the Staff to Java in 2 years.


Establish New Development Methodology.


Bring Web 2.0 technology into DMS 2.0


Enhanced the User Web experience with
Dashboards.


Look into Mobile Technology for DMS 2.0.

Business Concept


Migrate into a Rich Internet Application with
current DMS functionality.


Explore Web 2.0 capabilities into future DMS
2.0 system.


Provide faster updates and enhancements thru
Web deployment.


Integrate new services and existing process
into DMS for a more homogenous system.

Resource Requirements


List requirements for the following resources:


4 Developers, 1 Java Developer, 1 Architect, 1 DBA,
and 1 Unix Admin.


Jdeveloper, Subversion, TOAD, Testing Tool, etc.


Provide Training, books, and Java Mentoring.


Migration Tools to speed up conversion of system.


Consulting Services for resource shortage.

Risks and Rewards


Risks is 3 years after an aggressive schedule.


We will manage it by evaluating Migration
paths, Skills of Staff, and Project Modules
complexities.


Choosing Oracle Jdeveloper and ADF will
provide the support and Technology to
succeed now and in the future.


We should be left with a maintainable and
current supported system by staying with
Oracle Technology.