Service Oriented Enterprise

Friday, July 16, 2004

Composite Application: Def #1  

Phil at Loosely Coupled was kind enough to send me a definition of "composite application":
Hereís Loosely Coupledís definition:
An application built by combining multiple services. A composite application consists of functionality drawn from several different sources within a service oriented architecture (SOA). The components may be individual web services, selected functions from within other applications, or entire systems whose outputs have been packaged as web services (often legacy systems).
Itís a favourite term of Gartnerís Massimo Pessini, the man who also gave us ĎESBí
I had great conversations on this topic recently with some really smart people. Unfortunately we were all rather drunk and I don't remember what we concluded - although I think it had something to do with molecules. Ok, this in only partially true. We basically agreed that the definitions of composite apps was still too loose (SOI, SODA, integration at the glass, how many of the NFR's need to be addressed by services, how much of the app needs to be SO enabled, etc.) Bottom line is that we need to move to a 'definition by constraints' view.

posted by jeff | 1:28 PM

ToDo: Create Agility Index  

On my list of things to do is to create an agility index (and a fragility index). Before I go too far down the road I thought I'd post to see if anyone already has a favorite agility/fragility index in use. Lemme know.
Oh yea... so it isn't about being service oriented. Service networks must be evaluated from an 'ility' perspective. I'll start with agility.

posted by jeff | 1:21 PM

Monday, July 12, 2004

Nice paper  

Google led me to this nice paper by ACM Fellow, Carlo Ghezzi:

posted by jeff | 6:48 PM