Practical No 8
Practical No 8
Experiment No 8
Draw class diagram, Sequence diagram, Collaboration diagram, State Transition diagram
for the assigned project.
I Practical Significance
Class diagram describes the attributes and operations of a class and also the constraints imposed on
the system. Sequence diagrams describe how and in what order the objects in a system function.
Collaboration diagrams are used to describe the structural organization of the objects taking part in
the interaction. In state transition diagram we represent that what actions are leads to change the
state of the object.
Prepare class diagram, Sequence diagram, Collaboration diagram, State Transition diagram of
project.
V Practical Skills
Deeper understanding of System modeling: class diagram, Sequence diagram, Collaboration diagram,
State Transition diagram.
Behavioral diagrams basically capture the dynamic aspect of a system. Dynamic aspect can be
further described as the changing/moving parts of a system.
Sequence diagram
Collaboration diagram
Activity diagram
VIII Procedure
IX Precautions
X Description
Class diagrams describe the static structure of a system or how it is structured rather than how it
behaves.
These diagrams contain the following element with their symbol.
1) Class– It represents entity with common characteristics or features. These features can include
attributes, operations and associations.
The symbol used to denote class is rectangle with three compartments.
First contains the name of the class, second contains the attributes of the class and third contains the
operations of that class.
Notation:
2) Association – It represents relationships that relate to two or more other classes where the
relationships have common characteristics.
The symbol used to denote association is solid line.
Notation:
5) Generalization: It is a relationship between a class (superclass) and its derived classes (subclasses).
Notation:
6) Qualified association: It uses the special attribute qualifier which reduces the effective multiplicity of
an association.
Notation:
1) Object: Class roles describe the way an object will behave in context. Use the UML object
symbol to illustrate class roles, but don't list object attributes.
2) Activation or Execution Occurrence: Activation boxes represent the time an object needs to
complete a task. When an object is busy executing a process or waiting for a reply message, use
a thin gray rectangle placed vertically on its lifeline.
3) Messages: Messages are arrows that represent communication between objects. Use half -
arrowed lines to represent asynchronous messages. Asynchronous messages are sent f rom an
object that will not wait for a response from the receiver before continuing its tasks.
4) Lifelines: Lifelines are vertical dashed lines that indicate the object's presence over time.
5) Destroying Objects: Objects can be terminated early using an arrow labeled "<< destroy >>"
that points to an X. This object is removed from memory. When that object's lifeline ends, you
can place an X at the end of its lifeline to denote a destruction occurrence.
6) Loops: A repetition or loop within a sequence diagram is depicted as a rectangle. Place the
condition for exiting the loop at the bottom left corner in square brackets [ ].
A collaboration Diagram is an interaction diagram which emphasizes the structural organization of the
objects that send and receive messages.
Link to self is used to link the bjects that fulfill more than one role.
Constraint is an extension mechanism that enables you to refine the semantics of a UML model
element.
during its life time and Statechart diagrams are used for this purpose. When these states and
events are identified, they are used to model it and these models are used during the
implementation of the system.
Notations :
State defines current condition of an event or activity. State diagram is of ten used to describe
state changes triggered by events.
Transition takes operation from one state to another and represents the response to a
particular event. A single transition comes out of each state or activity, connecting it to the next
state or activity.
Constraint is an extension mechanism that enables you to refine the semantics of a UML model
element.
Ans: