|
|
Top-down and bottom-up approaches compared
Gabriel Bechara's Blog |
January 29, 2007 10:55 AM
|
Comments (0)
Top-down and bottom-up approaches compared
Top-down and bottom-up approaches compared
In part 1 of my blog Application architecture using Weblogic Integration on dev2dev
I have introduced 3 approaches those being the bottom-up, top-down and
meet-in-the-middle. The rest of the 3 parts blog focused on application
architecture using Weblogic Integration.
As you may have noticed in Application architecture
using Weblogic Integration - Part 2 I did not mention the approach used in the choices that were made.
The choices could have been done using a top-down or a bottom-up approach. In
the blog From application architecture to enterprise architecture - First
steps I have tried to
take the application a step further to expose some of it's services to be used
thru the enterprise. But in a real context this will depend on the choices done when defining the services interfaces and the business functions they implement: Can and will those
services be reusable holistically
in the organization? How to identify services that can be reused holistically,
how to share them? What is the appropriate approach?
The bottom-up approach may be faster and easier to apply but may
result in services that are not easily reusable holistically in an organization. The top-down approach is harder to apply
and needs more governance and guidance but will result in better reuse thru the
organization. I have submitted an article for review introducing a simplified
top-down approach and the advantages related to it. Hoping it will give some
guidance in this concern.
Comments
Comments are listed in date ascending order (oldest first) | Post Comment
|
|
