|
 Stuart
has spent 18 years in IT, of which 10 years have been with
CGI (formerly AMS) in a variety of roles encompassing technical
and functional architecture, project management, offering
development and pre-sales (on one occasion all of these at
once). He was a founding member of the AMS Technical Architect
community and is active in the CGI Technology Focus Network.
Functionally his expertise is in telecommunications - mostly
mobile. He has worked on projects for many different European
telcos in pretty much all areas of OSS and BSS. He likes
variety and thrives on it. Over the last few years he has
been something of an evangelist for SOA. Before IT, he tried
very hard to make a living playing music but never quite
made it. Stuart has a son aged 14 who plays rock guitar.
He is a dedicated distance runner and an unrepentant hippy.
|
|
|
| |
 Presentation
Business and Information Architecture
The presentation addresses SOA only from the perspective of a single enterprise,
but many of the themes are equally applicable to a multi-enterprise situation.
The fundamental thesis is that one can only implement a Service Oriented Architecture
by starting from a thorough understanding of the business processes implemented
by an enterprise's IT systems - not necessarily all of them at any one time.
These processes might be documented in an Enterprise Architecture or an Enterprise
Process Model. If not, it's possible to use industry standard models, where
these exist. I use an example based on the TeleManagement Forum's eTOM. This
also touches on the general theme of using available standards in all aspects
of SOA. Moving on, we employ use cases in order to identify more precisely
the functions that each service needs to implement. I talk a little about using
enterprise or standards based information models to take us to the next stage.
Life is, however, not all standards and perfect models,
so the last part of the presentation looks at how we can
use the existing systems in the architecture as a positive
factor rather than just a legacy problem.
 return
to program
|
|
|
