Requirements To Design In This Iteration popo

Requirements To Design In This Iteration 10% of the requirements were investigated in inception, and Deeper investigation was started in this first iteration of elaboration. popo

Requirements To Design In This Iteration During object design, a logical solution based on the object-oriented technique is developed. This can be done by the creation of interaction diagrams which illustrate how objects collaborate to fulfill the requirements. popo

Requirements To Design In This Iteration Then class diagrams can be drawn. Which illustrate the definition of the software classes(and interfaces) that are to be implemented in software. popo

Interaction Diagram Notation The UML includes interaction diagrams to illustrate how objects interact via messages. popo

Interaction Diagram Notation Sequence and Collaboration Diagrams Both are used to express similar message interactions: They are Collaboration diagrams Sequence diagrams popo

Interaction Diagram Notation Sequence and Collaboration Diagrams Collaboration diagrams illustrate object interactions in a graph or network Here objects can be placed anywhere on the diagram popo

Interaction Diagram Notation Sequence and Collaboration Diagrams Example popo

Interaction Diagram Notation Sequence and Collaboration Diagrams Sequence diagrams Clearly illustrate the sequence of messages. popo

Interaction Diagram Notation Sequence and Collaboration Diagrams   Sequence Collaboration Strengths Clearly Shows Sequences or Time Ordering of Message Simple Notation Economically Flexible to add new object Better to illustrate complex branching, iterations, and branching Weakness Force to extend to the right when adding new objects Take horizontal Space Difficult to see sequence of message More Complex Notations Difference popo

Interaction Diagram Notation Sequence and Collaboration Diagrams Example Collaboration Diagram: makePayment in POS popo

Interaction Diagram Notation Sequence and Collaboration Diagrams The above collaboration diagram read as follows: 1. The message makePayment is sent to an instance of a Register. The sender is not identified. 2. The Register instance sends the makePayment message to a Sale instance. 3. The Sale instance creates an instance of a Payment. popo

Interaction Diagram Notation Sequence and Collaboration Diagrams Example Sequence Diagram: makePayment popo

Interaction Diagram Notation Classes and Instances For any kind of UML element (class, actor, ...), an instance uses the same graphic symbol but diff is . Instance :- underlined popo

Interaction Diagram Notation Basic Collaboration Diagram Notation A link is a connection path between two objects It indicates some form of navigation and visibility between the objects is possible. More formally, a link is an instance of an association. popo

Interaction Diagram Notation Basic Collaboration Diagram Notation A link For example, there is a link--or path of navigation, from a Register to a Sale, along which messages may flow, such as the makePayment message. Multiple messages, and messages both ways, can flow along the same single link. popo

Interaction Diagram Notation Basic Collaboration Diagram Notation Messages Each message between objects is represented with a message expression Small arrow indicating the direction of the message. popo

Interaction Diagram Notation Basic Collaboration Diagram Notation Messages Many messages may flow along a link. A sequence number is added to show the sequential order of messages in the current thread of control. popo

Interaction Diagram Notation Basic Collaboration Diagram Notation Messages to “self” or “this” A message can be sent from an object to itself This is illustrated by a link to itself, with messages flowing along the link. popo

Interaction Diagram Notation Basic Collaboration Diagram Notation Creation of Instances Any message can be create by UML to use a message named create. like so: «create». The create message may include parameters, indicating the passing of initial values. This indicates, for example, a constructor call with parameters in Java. popo

Interaction Diagram Notation Basic Collaboration Diagram Notation Creation of Instances UML property {new} may optionally be added to the instance box to highlight the creation popo

Interaction Diagram Notation Basic Collaboration Diagram Notation Message Number Sequencing The order of messages is illustrated with sequence numbers The numbering scheme is: 1. The first message is not numbered. Thus,msg1() is unnumbered. 2. The order and nesting of subsequent messages is shown with a legal numbering scheme in which nested messages have a number appended to them. Nesting is denoted by prepending the incoming message number to the out going message number. popo

Interaction Diagram Notation Basic Sequence Diagram Notation Links sequence diagrams do not show links. Messages Each message between objects is represented with a message expression on an arrowed line between the objects The time ordering is organized from top to bottom. popo

Interaction Diagram Notation Basic Sequence Diagram Notation Messages to “self” or “this” A message can be illustrated as being sent from an object to itself by using a nested activation box popo