« SOA Means Always Focus on the Bigger Picture | Main | Building a SOA...Make Sure to Focus on Service Design as Part of the Overall Architecture »
January 05, 2006When Considering a SOA Define the Business Value Up Front
As technologists, we don’t always want to make business cases for the technology. Indeed, we have a tendency to leverage the most popular technology without regard for how its use will affect the bottom line. Not a good practice if you want IT to have a strategic position within an organization.
From my blog on Monday, we indeed build SOAs because they provide an infrastructure for agility, or the ability to change processes in support of a changing business. They also allow for reuse; the ability to reuse application behaviors from system to system without having to port and retest code.
In order to understand the ROI, you need to define a business case around the notions of reuse and agility before you begin your movement toward an SOA. The anticipated ROI will determine the proper investment, and thus insure that the implementation of a SOA strategy has value within the enterprise, and you’ll have business success along with technological success.
Posted by davel at 07:50 AM in
|
Digg This |
Add to del.icio.us

Dave Linthicum's Podcast Channel
