|
 |
|
|
|
Amarco case study: A Banking Management System
The external architecture puts boundaries around the system. So we can see the outside systems, how they are connected and what services are exchanged.
The internal architecture shows the components. The service points seen from the exterior are now mapped on internal objects.
We can display only the connections relative to an object. It is clear what service points (interfaces) are to be respected if we proceed to a replacement.
To improve system visibility, and to stress peculiar aspects, we can show only a selected category of service points. In this diagram we present only the administration links between component objects.
The management system may be represented also by taking into account the various information technologies that are present in its structure. The service points are scattered on various technology -oriented infrastructures. Thus we can see the various exchanges that take place between technology environments. A more detailed view may show the effective communication links, with service points like TCP/IP, X25, SNA etc.
Component object - external architecture If we take into account a component object, we can first present it as an external architecture.
Component object - internal architecture The internal architecture shows the objects that constitute its structure. Somewhere there is a datawarehouse...
Behavior - an execution scenario We can map an execution scenario on the internal structure of the system. In this diagram we choose to underline two phases that seemed important for the presentation of the system before a high-ranking manager.
On this same structure we can map another execution scenario:
|
 |
|
||||||||||||||||||
|
|||||||||||||||||||||
Overview
