The sequence diagram has four objects (Customer, Order, SpecialOrder and NormalOrder). The first diagram is a sequence diagram and the second is a collaboration diagram The Sequence Diagram The sequence in which the messages are flowing.įollowing are two interaction diagrams modeling the order management system. Organization of objects in a system taking part in the message flow.įollowing things are to be identified clearly before drawing the interaction diagram The message flow from one object to another and the collaboration diagram describes the The sequence diagram captures the time sequence of We have two types of interaction diagrams in UML. Snapshot of the running system at a particular moment So to capture the dynamic aspect, we need to understand what a dynamic aspect is and how it is visualized. To describe the interaction among objects.Īs we have already discussed, the purpose of interaction diagrams is to capture the dynamic aspect of a system. To describe the structural organization of the objects. To describe the message flow in the system. To capture the dynamic behaviour of a system. Sequence and collaboration diagrams are used to capture the dynamic nature but from a different angle. Hence, the solution is to use different types of models to capture the different aspects of the interaction. Visualizing the interaction is a difficult task. The purpose of interaction diagrams is to visualize the interactive behavior of the system. Sequence diagram emphasizes on time sequence of messages and collaboration diagram emphasizes on the structural organization of the objects that send and receive messages. The basic purpose of both the diagrams are similar. This interactive behavior is represented in UML by two diagrams known as Sequence diagram and Collaboration diagram. This interaction is a part of dynamic behavior of the system. If you have enough time, take a look at the others as well.From the term Interaction, it is clear that the diagram is used to describe some type of interactions among the different elements in the model. I suggest you at least invest time to try out state machine, class, activity, and sequence diagrams, as those are the most popular. Obviously, it takes some experience to decide this. If you don't feel like it'll help you, then simply don't do it. Always remember that you do not model your software in UML for its own sake. Unless your process somehow requires you to use a specific UML diagram, there is no one forcing you to do so. Obviously, the class diagram comes in handy on lower levels of detail, but others, like sequence diagrams, may also make sense if you have complex sequences in your architecture.Īre you developing a distributed system, or something where components have to communicate a lot with each other? Try out the communication diagram. Once you have a set of requirements and actually start thinking about your architecture and later the design, more and more diagrams will start to make sense. Similarly, state machines are already popular on the requirements level as well. I have often seen use-case diagrams as the basis for discussions from which the requirements are then determined. But some do make a lot of sense, in particular use-case diagrams. If you start with SW architecture once someone tells you to do a software for X, then you already missed the most important step there.ĭuring the requirements engineering phase, not all UML diagrams make sense yet. Initially, there should be some collection of requirements. It is all based on what you think is most useful to you/your team.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |