UML (Unified Modeling Language) diagrams are essential tools for business analysts to understand and communicate system requirements and objectives to stakeholders. There are 7 main UML diagram types, but business analysts most commonly use use case diagrams to map interactions between users and systems, activity diagrams to illustrate business process flows, and sometimes sequence and class diagrams. UML diagrams provide clarity on systems and aid collaboration between teams like business analysts, IT departments, and clients.

1. As a Business Analyst there are some essential tools necessary to perform the job to its fullest.
One of these is the use of Diagrams(using UML) to display objectives to the stakeholders and
end users.
- The Unified Modeling Language(UML) are the graphic noting techniques that are used when
creating Diagrams for software-intensive systems.
- The UML Diagrams were developed in the 1990’s by the Rational software company and the
pioneers of its developments are Grady Booch, Ivar Jacobson and Jim Rumbaugh.
The purpose of UML diagrams in a nutshell:
They are used to specify, visualize, modify, construct and document the different stages within
the project.
The Types of UML Diagrams
There are 7 distinct UML diagrams, which are as follows:
1. Use Case Diagrams
2. Interaction Diagrams
3. Activity Diagrams
4. Class Diagrams
5. Sequence Diagrams
6. Component Diagrams
7. Deployment Diagrams
The Diagrams explained
The importance of UML diagrams can’t be denied. They are the main component used by the
business analyst, as they are required to get requirements validated and assessed. UML

2. Diagrams also play a big role in giving clarity to the project and its objectives.
1.Use Case Diagrams
This shows the interactions that take place between the actors, which can be the users or
external interfaces and the actual system it’s self.
--About UML:--
*Unified Modeling Language (UML)
*A graphical way of describing s/w system
*UML Sketching vs UML Blueprint
*Plateform Independetent /plate Specific.
UML Development Process
a. Waterfall
- Analysis, deisgn, Coding & Testing
b. Iterative(Most Common)
-Solve in pieces
UML Planning Process
i. Predictive Planning
ii. Adaptive Planning (Agile Dev)
iii. If you can easily list all requirements use predective planning. (when the requirements are
not going to change )
Use Case
a. List of steps a system needs to follw to reach a goal

3. - Define what is required and how those requiremets are met
- Don't try to write code in a Use Case Diagram
- Shall vs. Should Requirements
b. These steps normally include interactions with an Actor(Human / External System)
Use Case Description
a. Description
b. The user enters their card and PIN. Security verifies the card. The user selects the account to
use. They select an amount. Security verifies if the amount is avaiable. The system comes to a
conclusion on if money is provided. The user selects funds as $10s or $20s. Security provides the
fund if possible. Security provides a receipt and the users card.
c. Trigger
i. Machine receives a card
ii User enters a PIN
d. Actors
i. Customer
ii. Bank Security
e. Preconditions
i. Secure Connection to Bank
ii. Bank Has Cash
f. Goals (Successful Conclusion)
i. Secure Client Accounts
ii. Provide Customer with Funds
g. Failed Conclusion
i. Invalid Card
ii. Invalid PIN

4. iii. Customer Insufficient Funds
iv. ATM insufficient Funds
v. Over Daily Limit
vi. Stolen Card
h. Extensions (Alternatives)
i. If PIN is invalid 3 Times (Eat Card)
ii. If Card Marked as stolen (Eat Card)
>>Steps of Execution (Requirements)
1. Customer Insters Card
1A. Card is Invalid
1B. Eject Card
2. Card is Validated
3. Customer Enters PIN
3A. PINis INvalid
3B. PIN is Invalid 3 Times
3C. Card Marked as Stolen
4. PIN is Validated
5. Account is Selected
6. Amount is Selected
6A. Over Daily Maximum
6B. Over Account Funds Available
6C. Over Funds in Machine
6D. Ask for New Amount
7. Provide $10 or $20

5. 8. Provide Funds
9. Provide Receipt
10. Eject Card
Interaction Diagrams
This gives clarity on how the different elements (objects) within the system work together.
Activity Diagrams
This gives a display of the business process flow, it will utilize the Use case and can be likened to
a data flow diagram.
Class Diagrams
This displays properties and the way they behave in the classes within the system. An object is
an instance of a class. An Object diagram will display the objects in a similar manner to the class
diagram.
Sequence Diagrams
This diagram gives an orderly sequence of all the message transfer between the entities of the
system.
Component Diagrams
This displays how the components within the system, and what their dependencies are in the
architecture of the system as a whole
Deployment Diagrams
This shows the physical architecture and its deployment components.

6. >>. Although there are 7 diagrams, it is unusual for all of them to be used by a business analyst.
The main Diagrams he or she will use are; Use Case Diagram, Activity Diagram and sometimes,
Sequence and Class Diagrams.
The remaining three diagrams are generally utilized by a solution architect or designers.
The UML diagrams are a crucial part of the business analysts arsenal. They are the perfect tool
for giving clients, end users and stakeholders a better understanding of a system. They also help
aid the communications between different departments, especially the IT department and client
or stakeholder.

7. >>. Although there are 7 diagrams, it is unusual for all of them to be used by a business analyst.
The main Diagrams he or she will use are; Use Case Diagram, Activity Diagram and sometimes,
Sequence and Class Diagrams.
The remaining three diagrams are generally utilized by a solution architect or designers.
The UML diagrams are a crucial part of the business analysts arsenal. They are the perfect tool
for giving clients, end users and stakeholders a better understanding of a system. They also help
aid the communications between different departments, especially the IT department and client
or stakeholder.