uml sequence diagram - modelling generic behaviour that is applied to operations -


i have sequence diagram client makes initial call set session. after initial call, every subsequent operation (e.g. call x, call y, call z) called on server checked see if session exists. there way describe behaviour generically without having show each , every call? guess 1 option add note, there may better way?

session sequence diagram

since sequence diagram show particular execution (client , server should :client , :server in diagram) difficult introduce factorization. use interactionuse reuse sequence fragment in case not since have 1 message ("check session").

don't forget diagrams views of systems , particularly sequence diagrams view of particular transaction. don't have show in diagram. need not show "check session" messages in diagram , use 1 show server checks session, maybe state diagram.


Comments

Popular posts from this blog

How to logout from a login page in asp.net -

Stack level too deep error after upgrade to rails 3.2 and ruby 1.9.3 -