Skip to Content

I ran a session at TechEd Munich on Tuesday about how to create roadmaps towards Enterprise SOA. I was surprise to find that no one at the session had even heard of the Enterprise SOA Adoption Program….never mind used it….also interesting was that generally no formal methods appeared to be being used by the people who attended the session…..

 

I suggested to the SDN/BPX audience that the first process they should be getting their BPXs to look at was the process of defining the architecture.

 

It was probably just the audience that attended the session as I know that architecture methods are alive and well….but they still appear to be attached to “Enterprise Architects” who are often detached for the “real” world….a gap that needs to be closed….

 

We did agree that any method used (formal or otherwise) should deliver the following;

 

  1. Clearly Drivers / Strategy  to hang priorities on
  2. Linkage / Trace-ability to justify actions even when it gets tough
  3. Shared Target Architecture and Patterns so everyone “points” in the same direction
  4. Guiding Principles / Governance to provide the “legal framework to tell  “right” from “wrong”

 

I am sure with these in place the job of your Average BPX will be better….

To report this post you need to login first.

Be the first to leave a comment

You must be Logged on to comment or reply to a post.

Leave a Reply