topic : UML DIAGRAMS content : Use Case Diagram Class Diagram Interaction diagram Activity diagram Case Study details : Use Case Diagram :: 1 Dynamic in nature. 2 It is used to model the system/subsystem of the application. 3 Built in early stage of development and developed by analyst 4 Involves interaction between user and system. Class Diagram :: 1 Class diagram is a static diagram. 2 Class diagram used for different aspects of a system. 3 The class diagram describe the attributes and operations of a class. 4 It is also known as structural diagram.

1. UML DIAGRAMS
Presented by
Shweta Raj(48)
Pooja Singh(30)
Rishav Raj(39)
Jyoti Kumari(19)
Ashwani kr. Madhukar(10)

2. Content
 Use Case Diagram
 Class Diagram
 Interaction diagram
 Activity diagram
 Case Study
 References
 Questions 2

3. Use Case Diagram
 Dynamic in nature.
 It is used to model the system/subsystem of the application.
 Built in early stage of development and developed by analyst .
 Involves interaction between user and system.

4. Purpose of Use Case Diagram
 Specify the context of a system.
 Capture the requirement of system.
 Validate a system architecture.

5. Elements of Use Case Diagram and their
Representation
Actor :
 Someone who interacts with system.
 Actor triggers use case.
 Actor can be ranked on:
(i) primary
(ii) secondary
 It is represented by stick person.

6. Elements of Use Case Diagram and their
Representation (cont…)
Use Case:
• A set of sequence of action a system perform.
• A use case
- is always initiated by an actor.
- provides value to an actor.
 It is represented by ellipse.

7. Elements of Use Case Diagram and their
Representation (cont…)
Association :
 Connects an actor and the use case.
 Also known as communication relationship.
 It is represented by a line.
Boundary :
 Indicates the scope of system.
 Represented by rectangular box.

8. Linking Use Case
Association relationships
Generalization relationships
 One element (child) "is based on" another element
(parent)
parent
child

9. Linking Use Case (cont…)
Include relationships
 One use case (base) includes the functionality of another
(inclusion case)
 Supports re-use of functionality
Base included
<<include>>

10. Linking Use Case (cont…)
Extend relationships
 One use case (extension) extends the behaviour of another(base)
Base
Common
use case
<<extends>>

11. Class Diagram
 Class diagram is a static diagram.
 Class diagram used for different aspects of a system.
 The class diagram describe the attributes and operations of a class.
 It is also known as structural diagram.

12. PURPOSE OF CLASS DIAGRAM
 It model the static view of application.
 Showing the collaboration among the elements of the static view.
 Construction of software applications using object oriented language.

13. RELATIONSHIP FOR REPRESENTATION
OF CLASS
1). ASSOCIATION
 Association between two classes by drawing a straight line between the
concerned classes.
association
Class A class B
 Associaton simply states that there is some kind of a
link or a dependency between two classes or more.

14. 2).AGGREGATION
 Aggregation is a special type of association relation where the involved
classes are not only associated to each other but a whole part
relationship exist between them.
 It can be represented by an empty diamond symbol.
 Aggregation is also known as shared association.
 Notation

15. 3).COMPOSITION
 Composition is stricter form of aggregation .
 Here , the parts are existence dependence on whole.
 The lifeline of the whole and the parts are identical.
 Notation

16. CLASS DIAGRAM EXAMPLE

17. Interaction diagram
 Overview
 Purpose
 How to draw interaction diagram
 The sequence diagram
 The collaboration diagram

18. Overview
I. From the name interaction it is clear
II. This interactive behaviour is represented in UML two
types diagram
a. Sequence diagram
b. Collaboration diagram
III. The basic purposes of both the diagram are similar.

19. Purpose
 To capture dynamic behaviour of a system
 To describe the message flow in the system
 To describe structural organization of the objects
 To describe interaction among objects
CUSTOMER
PRODUCT

20. Now we have 2 types of interaction diagram in
UML:
1) Sequence diagram
2) Collaboration diagram

21. Some key points:
 Dashed lines represent the duration for which the object will be live
 Messages sent from a object is represented by dark arrow
 Return message are represented by dotted arrow
 Message are denoted by an arrow or sequence number
 Objects are represented in rectangles
 Conditional statements are denoted by square brackets
 The sources of an arrow indicates the activations which sent the message

22. 1) Sequence diagram
• Sequence diagrams are used to capture the order of messages
flowing from one object to another

23. 2) Collaboration diagram
• The collaboration diagrams are used to describe the structural
organizations of the objects taking part in the interaction

24. Activity diagram
 Overview
 Purpose
 Activity diagram-notation
 Example of activity diagram
 Usage of activity diagram

25. Activity diagram
 Activity diagram is an important diagram in UML to describe dynamic
aspects of the system.
 Activity diagram is basically a flow chart to represent the flow from one
activity to another activity.
 Activity is a particular operation of system.
 Activity diagram are mainly used as a flowchart consists of activities
performed by the system.

26. Purpose of activity diagram
 Draw the activity flow of system.
 Describe the sequence from one activity to another.
 Describe the parallel , branched and concurrent flow of system.

27. Activity Diagram-Notations
 Initial Activity: Shows the starting point or first activity of the flow.
Denoted by a solid circle. This is similar to the notation used for Initial
State.
 Activity: Rectangle with rounded edges.
 Decisions: a logic where a decision is to be made is depicted by a
diamond, with options written on either sides of the arrows emerging
from the diamond, within box brackets

28. • Signal: When an activity sends or receives a message, that activity is
called a signal. Two types of Signals
• Input - Message receiving shown by a concave polygon
• Output -Message sending shown by a convex polygon
• Concurrent Activities: Some activities occur simultaneously or in
parallel and are called concurrent activities.
• Final Activity: The end of the Activity diagram is shown
• by a bull's eye symbol.

29. Example of Activity diagram:

30. Usage of activity diagram:
 Modeling work flow by using activities.
 Modeling business requirements.
 High level understanding of the systems functionalities.
 Investigate business requirements at a later stage.

31. Case Study

32. ATM Use Case – Withdraw Cash - Text
Brief Description :
 This use case describes how the Bank Customer uses the ATM to withdraw
money from his/her bank account.
Actors :
 Primary Actor : Bank Customer
 Secondary Actor : Bank
Preconditions :
 There is an active network connection to the Bank.
 The ATM has cash available.

33. ATM Use Case – Withdraw Cash - Text
Basic Flow of Events :
 Bank Customer inserts their Bank Card.
 Use Case: Validate User is performed.
 The ATM displays the different alternatives that are available on this unit. In this case the
Bank Customer always selects “Withdraw Cash”.
 The ATM prompts for an account
 The Bank Customer selects an account.
 The ATM prompts for an amount.
 The Bank Customer enters an amount.
 Card ID, PIN, amount and account is sent to Bank as a transaction. The Bank Consortium
replies with a go/no go reply telling if the transaction is ok.
 Then money is dispensed
 The Bank Card is returned.
 The receipt is printed
 The use case ends successfully

34. ATM Use Case…Alternate Flows
 Invalid User
 If Validate User does not complete successfully, then the use case ends with a failure condition
 Wrong amount
 The entered amount must be multiple of 100.
 The use case resumes at that step and ask the user to renter the amount.
 Amount Exceeds Withdrawal Limit
 Message : The amount entered is above the limit.
 Amount Exceeds Daily Withdrawal Limit
 Message : The amount entered is above the daily limit.

35. ATM Use Case – Alternate Flow (Cont’d)
 Insufficient Cash
 If the ATM runs out of money.
 If the user doesn’t have enough money in his account.
 No Response from Bank
 If in step 8 of the basic there is no response from the Bank in 3 seconds then the reasons may be
 Reasons : Network unavailable.
: System failier.
 Money Not Removed
 Message : Please remove the cash.
 Quit
 If at any point customer selects the Quit option.
 Atm shall print a receipt indicating the transaction was cancelled.
 Atm retuens the card.

36. ATM Use Case - Post Condition, Special
Requirements
Successful Completion
 The user has received their cash and the internal logs have been updated.
Failure Condition
 The logs have been updated accordingly.
Special Requirements
 The ATM shall dispense cash in multiples of Rs. 100
 The maximum individual withdrawal is Rs. 15000 per day
 The ATM shall capture an image of the person logging into the system
 The ATM shall keep a log, including date and time, of all complete and incomplete
transactions with the Bank.

37. customer
Bank
Transactions
View Balance
Change Pin
Withdraw
Deposit
Transfer
Authenticate
user
Cash Dispenser
empty
Money not
removed
<<extends>>
Invalid user
Wrong Amount Withdrawal limit
exceed
Insufficient Funds
UC Diagram – ATM Example

38. Sequence Diagram - ATM Example

39. ATM Example – Activity Diagram

40. References
Books
 Fundamentals of Software Engineering
 by Rajib Mall
Website
 www.tutorialpoint.com
 www.studytonight.com

41. QUESTIONS
? 41