Martyn Hill

Most well established large organizations suffer from some level of "Web sprawl." It organically grows for the same reasons as a disparate systems environment: Mergers and acquisitions Legacy architecture now deprecated Tactical solutions circumventing architectural goals Disparate IT skill sets Lack of architecture steering COTS package purchases provide heterogeneous platforms and functional overlaps No centralized IT, i.e., different IT organizations across business units The list could continue. By the same token the enterprise architecture team is tasked with reigning in Web sprawl and stemming its propagation. Fighting Web sprawl within a large organization is an uphill battle. Experiencing this on a daily basis has shown me that there are some things you can do to help alleviate the issues. It is popular (and rightly so) to have a target unified portal frame... (more)

Service Taxonomy and Service Ontologies Deliver Success to Enterprise SOA

A lot has been written on the approach to service-oriented architecture (SOA) migration. Although they are referred to by many names, there is the strategic approach, which is of high quality and so is also costly and initially less responsive because of the analysis involved up front. Then there is the organic growth approach, in which services are developed on an as-needed basis within the context of projects, which is responsive, but leads to redundancy and the lack of vision leads to unmanageability later. Finally, there is the hybrid approach, which attempts to take the best... (more)