For example, I want to display on the chart:
>System A obtains data from System B
>System B can call certain functions from System A
p>
I want to know about component diagrams and sequence diagrams.
What do you think?
The following figure shows this idea.
Use the interface between the components through the interface and Channel dependencies are a common (and highly recommended) practice. This allows for clearer specifications and better designs (of course, if possible).
Sequence diagrams can be further used to specify specific uses Scenarios are also worth recommending. Therefore, the components of structure, static dependencies and dynamic behavior sequences.
Which UML diagram is most suitable for showing our IT system and other external IT The dependencies between the systems?
For example, I want to display on the chart:
>System A obtains data from System B
>System B can call certain functions from System A
p>
I want to know about component diagrams and sequence diagrams.
What do you think?
Components definitelly and dependencies. Dependencies do not point to the direction of data flow, but come from components that “know” other components (from which something is called, Create objects, etc.).
The following figure shows the idea.
It is common to use interfaces and channel dependencies between components through interfaces (and highly recommended) Practice. This allows clearer specifications and better designs (of course, if possible).
Sequence diagrams can be further used to specify specific usage scenarios and are also recommended. Therefore, structure, static Dependency and dynamic behavior sequence components.