Business Analyst-8
UML: Unified Model Language Diagram.
Unified: One
Modeling: The Way You Draw.
Language: The way you represent.
Behavior Diagrams:
1)Use Case Diagram
2)Activity Diagram
3)State Diagram
4)Sequence Diagram
5)Collaboration Diagram
Structural Diagram:
1)Class Diagram
2)Object Diagram
3)Component Diagram
4)Deployment Diagram
Apart from the Use Case, Activity, and State Diagram all others are technical Diagrams
so we as in BA kind of stay away from them.
Activity Diagram:
- An activity diagram is used to show a business process workflow.
- Flow Chart, WorkFlow, and Process Flow are the other names of Activity Diagrams in
general.
- So any activity that is in the fork/synchronization bar, they are always happening in
parallel at the same time.
- Swimlane in an activity diagram is used to separate the actors, separate the activities
and decisions by the actor.
- An activity diagram may also be referred to as a swimlane diagram.
- Swimlane is used to divide activity diagrams via actors
Every activity and decision documented in the swim lane is executed by the actor
displayed in the swim lane.
State Diagram: A State Diagram is used to show all the potential states that a particular
process can attend as well as shows the conditions and the transition from one state to
the other.
- The Activity Diagram talks about the process flow whereas the state diagram does not
talk about what actions the user is taking to complete the process.
- The Activity Diagram talks about what are the different states of the process and talks
about what condition changes from one state to the other.
Q: If you had to create an activity diagram for this process, what would your activities
say in that diagram? What would it look like?
1)There will be a start point and then the user will click on the new application.
2)Then System will display the Application Form.
3)Users will enter the data.
4) The user will submit the data.
5) The system will validate the entered data.
6)If everything is valid, go to the review queue.
7)Somebody will pick the application for review
8)Then the application will either be selected or rejected.
9)Then it goes to the scheduled exam queue.
Use Case Diagram: A Use Case Diagram shows the interaction between the actors and
the use case as well as shows the relationship between the use cases.
The System Boundary represents the System for which you are creating your Diagram.
Actors will never be within or inside the system Boundary.
Q: What is the difference between a Bank Customer and a Guest Customer of An ATM?
Suppose you have an ICICI Bank Account and you visit the ICICI ATM then you’re a Bank
Customer & If you have an SBI bank account and visit the ICICI ATM then you’re a Guest
Customer.
Actors are role-based and not human-based.
The Same Person can play multiple actors in the system based on how they log in to the
System.
Q: An Actor can be a human or can be a system. How?
Example: Transfer funds, Deposit Funds or withdraw funds, or check Balance, these are
some of the use cases or functionalities based on human action whereas ATM Locks
down or stops performing when the ATM has an issue so that gets no human touch so
the system shuts down self and that is how an actor role played by a human.
Every time you receive Email alerts, Text alerts, or call alerts those are automated
functions. So anything that is done automatically without human intervention where the
actor is the system.
So there comes the two use cases: actor as system or actor as Human.
Example: where they both come together.
Suppose a customer sets up a recurring transfer of 500$ from Account A to Account B
on the very 1st date of the upcoming month then when it is set up the Actor is Human
but once set up and then at the very 1st date of a month recurring transfer start getting
automated itself without human intervention on the decided date then the actor is
System.
Q: Explain Includes and Excludes in the Use Case Diagram.
A: Relationship between Use Cases:
1)Includes or Uses:
An Include is a relation wherein the sequence of flow of one use case is included in the
sequence of flow of another use case.
2)Extends:
An Extended relationship is pretty much an optional relationship.
It's an add but it is a one-time option.
Q: How does the Extended relationship increase your step in the flow?
Let's say in a total of 10 steps you can book /register your flight and the 8th step asks
you for the flight insurance then by clicking or adding the insurance it will add 3 to 4
steps more in the total steps required for booking a flight. So this is how extended
relations will simply increase the length of use cases in total.
An Extend is a relationship wherein the flow of one use case is extended by the flow of
another use case.
- Visio is the one tool that is found among the most industry to make in use.
So we can use this software for creating wireframes, and screen mockups.
You can also use this for creating UML Diagrams like use case diagrams, activity
diagrams, state diagrams
- When an arrow is connected to an action state then a red point will be popped up so
that red point is called Glue Point which means the arrow is connected to the action
state.
- You move the action state then Arrow is going to move along with that.
