UML sequence diagram

I have a question about sequence diagrams.

When building sequence diagrams,

Is it enough to make one diagram for each user case?

or we need to draw a set of sequence diagrams for each instance of a user case. (represents a sequence of actions performed by a system that gives the observed result of a value to a particular actor of use)

+5
source share
3 answers

, , . 1 ; , . , , , , , , , , .

; , , , .

+8

- , .

"" , . UC, , , , , , . , , , UC Sequence /, , / .

/​​, - , , .

+4

Remember that sequence diagrams represent possible interaction scenarios. Therefore, for each relevant scenario, you must draw a different sequence diagram. The meaning of "relevant" is up to you. This can be only one if you think that for a specific use case there is only one corresponding scenario (perhaps other scenarios are obvious and not worth a specific diagram) or many

+2
source

All Articles