MOM document on UML Diagram 
What is UML diagram? 
UML stands for unified modeling language. 
 Modeling language is where pictographic represent is used. 
There are Nine UML Diagrams that are used 
1. Use case Diagram. 
2. Class diagram 
3. Component diagram 
4. Package diagram 
5. Deployment diagram 
6. Sequential diagram 
7. Activity diagram 
8. Collaboration diagram 
9. State Chart diagram. 
In these BA using Use case and Activity diagrams. 
What is Use case diagram? 
Use case diagrams are usually referred to as behavior diagrams used to describe a set of actions. It gives some 
valuable or observable results to actors of system. 
An Actor is a user or class of person that interacts to the system. 
A Use case represents the actions that are performed by a one or more actor for a particular goal. 
 It is also a high level system diagram. 
Relationships: 
Association: It defines the relation between primary actor and system and it is denoted by →
MOM document on UML Diagram 
Generalization: It defines the relation between generalized class and specific class is called generalization and it 
is denoted as shown below. 
USE CASE DESCRIPTION DOCUMENT 
Every use case description document must have the following: 
Content of the use case description document as follows: 
• Use case name 
• Use case description 
• Actor present 
• Basic flow or (+ve ) work flow 
• Alternate flow 
• Exceptional flow (Ex: wrong user id and password) 
• Precondition (Ex: should be registered) 
• Post condition (Ex: Should access the account) 
• Business rules (Ex: only 5 transactions) 
A use case diagram does not show the detail of the use cases: it only summarizes some of the relationships 
between use cases, actors, and systems. 
Use cases deal only in the functional requirements for a system. 
Other requirements such as business rules, quality of service requirements, and implementation constraints must 
be represented separately.
MOM document on UML Diagram 
Example of Use Case Diagram: 
ATM Transaction 
Customer 
VIP customer 
Actor3 
Login 
Enter Pin no. 
Enter amount 
Geeralization 
Forgot password 
«extends» 
«include» 
Generalizatiopn Generalization 
Withdraw 
Loan 
Transaction 
Mini statement Balance Enquiry 
Logout 
* 
* 
* 
* 
* 
* 
* 
* 
* 
* 
User Generalization 
* 
* 
* 
* 
* 
* 
* 
* 
* 
* 
* 
* 
* 
* 
Check amount 
 The above diagram is shows use case diagram of ATM Transaction. 
Extend:[Optional] 
Use an Extend link to show that one use case may add functionality to another use case under certain 
circumstances. If we forgot password we have another way to get password through forgot password functionality. 
It happen may be. 
Forgot Login 
Password 
<<Extend>>
MOM document on UML Diagram 
Include:[Additional] 
In UML modeling, an include relationship is a relationship in which one use case (the base use case) includes 
the functionality of another use case (the inclusion use case). 
The include relationship supports the reuse of functionality in a use-case model. 
<<Include>> 
Enter 
amount 
Check 
amount 
 For Transaction we use generalization. 
 It shows the relation between tasks and sub tasks. It means in use case diagram for transaction we have 
generalization with Withdraw, Mini statement and Balance enquiry. 
Transaction 
Generalizatiopn «uses» «uses» 
Withdraw Mini statement Balance Enquiry

UML Diagrams

  • 1.
    MOM document onUML Diagram What is UML diagram? UML stands for unified modeling language.  Modeling language is where pictographic represent is used. There are Nine UML Diagrams that are used 1. Use case Diagram. 2. Class diagram 3. Component diagram 4. Package diagram 5. Deployment diagram 6. Sequential diagram 7. Activity diagram 8. Collaboration diagram 9. State Chart diagram. In these BA using Use case and Activity diagrams. What is Use case diagram? Use case diagrams are usually referred to as behavior diagrams used to describe a set of actions. It gives some valuable or observable results to actors of system. An Actor is a user or class of person that interacts to the system. A Use case represents the actions that are performed by a one or more actor for a particular goal.  It is also a high level system diagram. Relationships: Association: It defines the relation between primary actor and system and it is denoted by →
  • 2.
    MOM document onUML Diagram Generalization: It defines the relation between generalized class and specific class is called generalization and it is denoted as shown below. USE CASE DESCRIPTION DOCUMENT Every use case description document must have the following: Content of the use case description document as follows: • Use case name • Use case description • Actor present • Basic flow or (+ve ) work flow • Alternate flow • Exceptional flow (Ex: wrong user id and password) • Precondition (Ex: should be registered) • Post condition (Ex: Should access the account) • Business rules (Ex: only 5 transactions) A use case diagram does not show the detail of the use cases: it only summarizes some of the relationships between use cases, actors, and systems. Use cases deal only in the functional requirements for a system. Other requirements such as business rules, quality of service requirements, and implementation constraints must be represented separately.
  • 3.
    MOM document onUML Diagram Example of Use Case Diagram: ATM Transaction Customer VIP customer Actor3 Login Enter Pin no. Enter amount Geeralization Forgot password «extends» «include» Generalizatiopn Generalization Withdraw Loan Transaction Mini statement Balance Enquiry Logout * * * * * * * * * * User Generalization * * * * * * * * * * * * * * Check amount  The above diagram is shows use case diagram of ATM Transaction. Extend:[Optional] Use an Extend link to show that one use case may add functionality to another use case under certain circumstances. If we forgot password we have another way to get password through forgot password functionality. It happen may be. Forgot Login Password <<Extend>>
  • 4.
    MOM document onUML Diagram Include:[Additional] In UML modeling, an include relationship is a relationship in which one use case (the base use case) includes the functionality of another use case (the inclusion use case). The include relationship supports the reuse of functionality in a use-case model. <<Include>> Enter amount Check amount  For Transaction we use generalization.  It shows the relation between tasks and sub tasks. It means in use case diagram for transaction we have generalization with Withdraw, Mini statement and Balance enquiry. Transaction Generalizatiopn «uses» «uses» Withdraw Mini statement Balance Enquiry