In a sequence diagram, we work with the following elements: Comment We will treat this topic in Modeling for System Integration: Figure 3.22 The elements of the sequence diagram Sequence diagrams can be used as the basis for message exchange between the business system and outside parties (Figure 3.22). A sequence diagram illustrates the various scenarios of a business use case. Like the activity diagrams, sequence diagrams can be modeled spanning several use cases, as well as being used to refine business use cases. However, they can be described with supplementary comments. These interactions are clearly laid out in the sequence diagram, whereas the activities of each partner and the conditions under which the interactions take place are omitted in the diagram. The process can be described as a series of interactions. If a customer or business partner uses an offered service, partners communicate with each other. We avoid using unnecessarily many diagram types for the same facts.In our practical work in projects we have observed a much higher acceptance of sequence diagrams because of their simplicity. Sequence diagrams are easier to understand for developers and readers.In the external view, we opt for the representation through sequence diagrams and do without communication diagrams for two reasons: However, the emphasis is different: communication diagrams emphasize the relationships of individual objects and their topology sequence diagrams emphasize the chronological course of exchanged information. Both diagrams visualize the exchange of information. UML provides two types of diagrams for the representation of interactions: the sequence diagram and the communication diagram.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |