Architecture dependencies and interface modelling

[wzietek]

Hello, this is my first post on this forum.

I've tried to find simmilar topic, but without success, if anyone feels like this post duplicates any existing discussion, please provide me a link.

Challenge I am facing:

I'd like to model IT architecture composed of several interfacing systems systems.
Integration of those systems varies from webservices to dblinks.

I'd like to model this architecture and be able to validate it - for example if I change the scope of data passed via interface or type of those data I'd like to validate model and see information, that this model is nolonger valid.

So, basically, I'd like to track changes in architecture and it's impact on other systems.

Do You know how to do that, and what kind of diagram I should use ?


Regads

[qwerty]

Of course there are many different approaches. One would be to use a SOA profile. This will give a 360 degrees view but its difficult to understand and manage. A more simple approach is to create physical nodes for each machine and connect these as you see them. Now you can create components and deploy these on the nodes. The components receive interface which can be refined and connected to other components. You will find examples for that in the EA example (AFAIR) delivered with the standard package.

q.