Download - Oracle ADF Architecture TV - Design - Project Dependencies


Real World ADF Design & Architecture Principles

Project Dependencies

15th Feb 2013 v1.0


Learning Objectives

•  At the end of this module you should be able to:

–  Identify factors that constrain your ADF project in regards to technology decisions, methodologies and architecture

–  Think ahead to identify areas in which your application may grow – Participate actively in this training

Image: imagerymajestic/ FreeDigitalPhotos.net


Program Agenda

•  ADF Project Dependencies •  Introduction to the use case

5 Copyright © 2013, Oracle and/or its affiliates. All rights reserved. 5 Copyright © 2013, Oracle and/or its affiliates. All rights reserved.

What decisions do you think will impact the architecture of your ADF application?

Exercise



ADF Architecture Decisions

•  Team size, skills, capabilities •  One vs multiple applications •  One vs multi-page applications •  Multi-browser tab support •  Level of software reuse •  Sequential vs parallel development •  Application customization •  Requirements based around legacy architectures •  Legacy application modernization •  Integrating mobile

Decisions that may affect your architecture

Image: Ambro / FreeDigitalPhotos.net


The ADF Reuse Challenge

•  Hard for beginners, difficult to design, needs long term outlook •  Reuse for external consumers can become time consuming •  Components may need to be revisited and reworked many times •  Edge cases can create messy & overloaded components


The ADF Reuse Challenge

•  Requires explicit build management: – Build, packaging, distribution, installation, configuration,

deployment, maintenance and upgrade issues •  Creates dependencies on a component and its contract (API) •  Need to maintain dependency graphs


“Extreme reuse” is an obsession – making components ready for reuse that will only be used once is a waste



Sequential ADF Application Development

•  Consecutive develop one application after another •  For the first application

–  Future reuse requires visionaries – Reuse for some modules may never be used

•  For later applications – Potential for reuse across applications will be easier to see –  The opportunities lost – Re-architecting required


Parallel ADF Application Development

•  Develop multiple applications at the same time

•  Reuse across applications requires governance and clear communication

•  Waiting for reusable modules may become a project bottleneck

Image: samuari / FreeDigitalPhotos.net


ADF architecture is software design. This software design has to fit into an overall IT

architecture, which may or may not be SOA.



Cube of Dependencies Team Skills/ Size/ Location

Business / User Requirements

(Multi Channel Access, Customization, Accessi-

bility, Functionality)

Technology Choice

(SOA, SSO, Java EE, EJB, POJO, WS ...)

Budget (Development,

Testing, Production, Maintenance)

Application Size

(Single application module, Application suite, ...)

Overall IT Architecture


Business / User

Requirements

Budget

Team Skill, Size, Location

Application Size

IT Architecture

Cube of Dependencies

15 Copyright © 2013, Oracle and/or its affiliates. All rights reserved. 15 Copyright © 2013, Oracle and/or its affiliates. All rights reserved.

For a quick start. How about looking at what Oracle Fusion Applications does and

just do the same?

Exercise



Conclusion •  Building ADF applications is constraint by dependencies

that often are orthogonal to each other •  Copying Oracle Fusion Applications architecture

only makes sense if you are Oracle Fusion Applications –  Still you can look at Oracle Fusion Applications to pick up some

ideas and pattern

•  Make sure you plan your project so it can grow and leaves you time to build up expertise

•  Consider reuse as a tool not a necessity. Bad reuse can be worse than no reuse


Program Agenda

•  ADF Project Dependencies •  Introduction to the use case

Download - Oracle ADF Architecture TV - Design - Project Dependencies

Top Related