How to model SOA/Event relations/dependency between Apps

Post Reply
[email protected]
Posts: 4
Joined: 03 Aug 2012, 08:01

Hi, I was wandering how it is possible to model SOA service or business event interaction ( interoperability/integration ) between application and view
dependency report (used for instance for impact analysis on changing application interface, etc ).
Thanks in advance
Bye
Fabrizio
User avatar
jonathan.carter
Posts: 1087
Joined: 04 Feb 2009, 15:44

Hi Fabrizio

It is certainly possible to model SOA systems. From what you describe, it sounds like you have SOA solutions e.g. using Web Services, WSDL etc., that exchange information as part of an integrated service oriented application architecture.

The Application Service class in the Application layer can be used to define the services that we have (or plan to have) in our application architecture.
However, the semantics of this class is such that these are what we call "pure design" and are more abstract than the instances that we use to capture the actual SOA implementations that we have built or bought. We use Application Providers to model those - and we may have more than one implementation (Provider) of a particular Application Service.

Through the Functions on Application Services and Application Providers we can capture the operations that we expect a service to publish and what the Provider actually provides, respectively. Comparing the Providers to the Services can give us details on how well an Application Provider provides a particular Application Service.

Each of these Functions (Application Functions and Application Function Implementations) can model the Information that is input and output.

We can also model the interaction between our SOA implementations (Application Providers) by defining the Static Application Architecture of an Application Provider or at the Function-level, the Dynamic Application Architecture. The static model is slightly coarser-grained but meets most needs for understanding the dependencies that exist between Application Providers - including the Information that is passed between them (captured on the arcs of the graphical model).

Hopefully, this gives you a starting point but if you have any further questions, please post back. The SOA paradigm is worth some further discussion and explanation!

Jonathan
Essential Project Team
Post Reply