The following chapters explore object design. The language used to illustrate the designs is primarily interaction diagrams. Thus, it is advisable to at least skim the examples in this chapter and get familiar with the notation before moving on.<\/p>\n
The UML includes interaction diagrams to illustrate how objects interact via messages. This chapter introduces the notation, while subsequent chapters focus on using them in the context of learning and doing object design for the NextGen POS case study.<\/p>\n
This chapter introduces notation. To create well-designed objects, design principles must also be understood. After acquiring some familiarity with the notation of interaction diagrams, it is important to study the following chapters on these principles and how to apply them while drawing interaction diagrams.<\/p>\n
The term interaction diagram, is a generalization of two more specialized UML diagram types; both can be used to express similar message interactions:<\/p>\n
Throughout the book, both types will be used, to emphasize the flexibility in choice.<\/p>\n
A\u00a0sequence diagram<\/b>\u00a0or\u00a0system sequence diagram<\/b>\u00a0(SSD) shows\u00a0process<\/a>\u00a0interactions arranged in time sequence in the field of\u00a0software engineering<\/a>. It depicts the processes involved and the sequence of messages exchanged between the processes needed to carry out the functionality. Sequence diagrams are typically associated with use case realizations in the\u00a04+1 architectural view model<\/a>\u00a0of the system under development. Sequence diagrams are sometimes called\u00a0event diagrams<\/b>\u00a0or\u00a0event scenarios<\/b>.<\/p>\n For a particular scenario of a\u00a0use case<\/a>, the diagrams show the events that external actors generate, their order, and possible inter-system events. All\u00a0systems<\/a>\u00a0are treated as a\u00a0black box<\/a>; the diagram places emphasis on events that cross the system boundary from actors to systems. A system sequence diagram should be done for the main success scenario of the\u00a0use case<\/a>, and frequent or complex alternative scenarios.<\/p>\n A sequence diagram shows, as parallel vertical lines (lifelines<\/i>), different processes or objects that live simultaneously, and, as horizontal arrows, the messages exchanged between them, in the order in which they occur. This allows the specification of simple runtime scenarios in a graphical manner.<\/p>\n A system sequence diagram should specify and show the following:<\/p>\n A\u00a0communication diagram<\/b>\u00a0in the\u00a0Unified Modeling Language<\/a>\u00a0(UML) 2.0, is a simplified version of the UML 1.x collaboration diagram.<\/sup><\/p>\n UML has four types of interaction diagrams:<\/p>\n A Communication diagram models the interactions between objects or parts in terms of sequenced messages. Communication diagrams represent a combination of information taken from\u00a0Class<\/a>,\u00a0Sequence<\/a>, and\u00a0Use Case Diagrams<\/a>\u00a0describing both the static structure and dynamic behavior of a system.<\/p>\n However, communication diagrams use the free-form arrangement of objects and links as used in Object diagrams. In order to maintain the ordering of messages in such a free-form diagram, messages are labeled with a chronological number and placed near the link the message is sent over. Reading a communication diagram involves starting at message 1.0, and following the messages from object to object.<\/p>\n Communication diagrams show much of the same information as sequence diagrams, but because of how the information is presented, some of it is easier to find in one diagram than the other. Communication diagrams show which elements each one interacts with better, but sequence diagrams show the order in which the interactions take place more clearly.<\/p>\n","protected":false},"excerpt":{"rendered":"Key elements<\/span><\/h5>\n
\n
Communication diagram<\/h4>\n
\n