Examples for this are "Authentication" or "Authorization". When this level of complexity occurs, consider creating separate sub-scenario Sequence Diagrams, and using it as an object in a particular Sequence Diagram. However, more often than not, the complete end-to-end flow for that scenario may be too complex in order to capture within a single Sequence Diagram. Capturing all the possible "failure" situations that a scenario may encounterĪ Sequence Diagram typically starts with an end user persona performing an action, and then shows all the various components and request/data transfers that are involved in that scenario.Large number of objects / components involved in a particular scenario.There are 2 areas where complexity can result in an overly "crowded" Sequence Diagram, making it costly to maintain. It is okay for a single Sequence Diagram to have many different scenarios if they have some related context that merits them being grouped.Īnother important thing to keep in mind, is that the objects involved in a Sequence Diagram should refer to existing Components from a Component Diagram. have the scenario clearly indicate what the "end" state is, even if it doesn't necessarily end back with the object that initiated the scenario.indicate which object or "actor" initiated that scenario.an abstract sub-scenario (in order to minimize high complexity of a scenario).a system (black box composed of unknown services, data stores or other components).What is an object in this context? It can be: a transfer of any form of data between any objects.What is a message in this context? It can be: ![]() a system specific trigger (time based, condition based) that results in an action to occur.an actual user persona performing an action.Wikipedia defines UML Sequence Diagrams responsible to:ĭepict the objects involved in the scenario and the sequence of messages exchanged between the objects needed to carry out the functionality of the scenario Regarding the how, the section at the bottom will provide tools and plugins to streamline as much as possible when generating Sequence Diagrams through VSCode. This document is intended to provide a baseline understanding for what, why, and how to incorporate Sequence Diagrams as part of an engagement.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |