View Tomoaki Sawada's profile on LinkedIn Share
Locations of visitors to this page
Irving Wladawsky-Berger of IBM describes why business architecutre is important in order for SOA to become widely accepted. Worth reading to grasp high level view why it is so important.

SOA, Services and Business Architecture

At the end of May, I will be participating in an IBM sponsored conference - Impact 2007.  The conference will focus on Service Oriented Architectures (SOA), " ...  a business-centric IT architectural approach that supports integrating your business as linked, repeatable business tasks, or services."  SOA is being embraced by an increasing number of companies because it helps them build a more flexible IT foundation that can respond quickly to rapidly changing business conditions and user requirements.

There are many ways to view SOA, but to me its most compelling features are the introduction of standard, modular, interchangeable components to the world of software.  This enables developers to build composite applications by drawing upon pre-defined components from multiple sources within and beyond the enterprise.

The introduction of standard, interchangeable parts was one of the critical innovations that helped bring about the Industrial Revolution a couple of centuries ago and ushered in the concept of mass production in many different kinds of industries.  Modern engineering practices - especially those used for developing complex systems or objects like airplanes, bridges and microprocessors, - are built around the concept of standard, modular components.  Such components are a pre-requisite for sophisticated tools like those used in Computer-Aided Design (CAD) and Supply Chain Management

continue reading