really\nlong name" #99FF99 '/ Alice->Bob: Authentication Request Bob->Alice: Authentication Response Bob->L: Log transaction @enduml Возможно изменить порядок следования участников с помощью ключевого слова order Alice: Authentication Failure group My own label Alice -> Log : Log attack start loop 1000 times Alice -> Bob: DNS Attack end Alice -> Log : Log attack end end else Another type of failure Bob -> Alice: Authentication Failure group My own label [My own label 2] Alice -> Log : Log attack start loop 1000 times Alice -> Bob: DNS Attack end Alice -> Log : Log attack end end @enduml [Ref. QA-2503] 1.13 Примечания в

really\nlong name" #99FF99 '/ Alice->Bob: Authentication Request Bob->Alice: Authentication Response Bob->L: Log transaction @enduml Возможно изменить порядок следования участников с помощью ключевого слова order Alice: Authentication Failure group My own label Alice -> Log : Log attack start loop 1000 times Alice -> Bob: DNS Attack end Alice -> Log : Log attack end end else Another type of failure Bob -> Alice: Authentication Failure group My own label [My own label 2] Alice -> Log : Log attack start loop 1000 times Alice -> Bob: DNS Attack end Alice -> Log : Log attack end end @enduml [Ref. QA-2503] 1.13 Примечания в

declared. To have a dotted arrow, you use --> It is also possible to use <- and <--. That does not change the drawing, but may improve readability. Note that this is only true for sequence diagrams, rules will be the (default) order of display. Using these other keywords to declare participants will change the shape of the participant representation: • actor • boundary • control • entity • database participant 1 SEQUENCE DIAGRAM @enduml Rename a participant using the as keyword. You can also change the background color of actor or participant. @startuml actor Bob #red ' The only difference between

declared. To have a dotted arrow, you use --> It is also possible to use <- and <--. That does not change the drawing, but may improve readability. Note that this is only true for sequence diagrams, rules will be the (default) order of display. Using these other keywords to declare participants will change the shape of the participant represen- tation: • actor • boundary • control • entity • database collections Foo -> Foo7: To queue @enduml Rename a participant using the as keyword. You can also change the background color of actor or participant. @startuml actor Bob #red ' The only difference between

declared. To have a dotted arrow, you use --> It is also possible to use <- and <--. That does not change the drawing, but may improve readability. Note that this is only true for sequence diagrams, rules will be the (default) order of display. Using these other keywords to declare participants will change the shape of the participant represen- tation: • actor • boundary • control • entity • database collections Foo -> Foo7: To queue @enduml Rename a participant using the as keyword. You can also change the background color of actor or participant. @startuml actor Bob #red ' The only difference between

declared. To have a dotted arrow, you use --> It is also possible to use <- and <--. That does not change the drawing, but may improve readability. Note that this is only true for sequence diagrams, rules will be the (default) order of display. Using these other keywords to declare participants will change the shape of the participant represen- tation: • actor • boundary • control • entity • database collections Foo -> Foo7: To queue @enduml Rename a participant using the as keyword. You can also change the background color of actor or participant. @startuml actor Bob #red ' The only difference between

really\nlong name" #99FF99 '/ Alice->Bob: Authentication Request Bob->Alice: Authentication Response Bob->L: Log transaction @enduml Возможно изменить порядок следования участников с помощью ключевого слова order Alice: Authentication Failure group My own label Alice -> Log : Log attack start loop 1000 times Alice -> Bob: DNS Attack end Alice -> Log : Log attack end end else Another type of failure Bob -> Alice: Authentication Failure group My own label [My own label 2] Alice -> Log : Log attack start loop 1000 times Alice -> Bob: DNS Attack end Alice -> Log : Log attack end end @enduml [Ref. QA-2503] 1.13 Примечания в

really\nlong name" #99FF99 '/ Alice->Bob: Authentication Request Bob->Alice: Authentication Response Bob->L: Log transaction @enduml Использовав ключевое поле order (порядок) можно настроить порядок печати participant Alice: Authentication Failure group My own label Alice -> Log : Log attack start loop 1000 times Alice -> Bob: DNS Attack end Alice -> Log : Log attack end end else Another type of failure Bob -> Alice: Authentication Failure group My own label [My own label 2] Alice -> Log : Log attack start loop 1000 times Alice -> Bob: DNS Attack end Alice -> Log : Log attack end end @enduml [Ref. QA-2503] 1.13 Примечания в

really\nlong name" #99FF99 '/ Alice->Bob: Authentication Request Bob->Alice: Authentication Response Bob->L: Log transaction @enduml order 키워드를이용하여, 참여자의출력순서를지정할수있다. @startuml participant Last order 30 participant Alice: Authentication Failure group My own label Alice -> Log : Log attack start loop 1000 times Alice -> Bob: DNS Attack end Alice -> Log : Log attack end end else Another type of failure Bob -> Alice: Authentication Failure group My own label [My own label 2] Alice -> Log : Log attack start loop 1000 times Alice -> Bob: DNS Attack end Alice -> Log : Log attack end end @enduml [Ref. QA-2503] 1.13 메시지에노트추가하기

really\nlong name" #99FF99 '/ Alice->Bob: Authentication Request Bob->Alice: Authentication Response Bob->L: Log transaction @enduml You can use the orderkeyword to custom the print order of participant. @startuml Alice: Authentication Failure group My own label Alice -> Log : Log attack start loop 1000 times Alice -> Bob: DNS Attack end Alice -> Log : Log attack end end else Another type of failure Bob -> Alice: Authentication Failure group My own label [My own label 2] Alice -> Log : Log attack start loop 1000 times Alice -> Bob: DNS Attack end Alice -> Log : Log attack end end @enduml [Ref. QA-2503] 1.13 Notas en mensajes