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 to display objectives to the stakeholders and end users.
The official name of these Diagrams is the Unified Modeling Language (UML).
The Unified Modeling Language are the graphic noting techniques that are used when creating Diagrams for software-intensive systems.
Brief History & What Make’s UML’s A Perfect Match For A Business Analyst.
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 Diagrams also play a big role in giving clarity to the project and its objectives.
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.
[ez_youtube url=”http://youtu.be/OkC7HKtiZC0″ width=”590″ height=”360″ autoplay=”0″ autohide=”2″ controls=”1″]
This gives clarity on how the different elements (objects) within the system work together.
This gives a display of the business process flow, it will utilize the Use case and can be likened to a data flow diagram.
[ez_youtube url=”http://youtu.be/XFTAIj2N2Lc” width=”590″ height=”360″ autoplay=”0″ autohide=”2″ controls=”1″]
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.
[ez_youtube url=”http://youtu.be/3cmzqZzwNDM” width=”590″ height=”360″ autoplay=”0″ autohide=”2″ controls=”1″]
This diagram gives an orderly sequence of all the message transfer between the entities of the system.
[ez_youtube url=”http://youtu.be/cxG-qWthxt4″ width=”590″ height=”360″ autoplay=”0″ autohide=”2″ controls=”1″]
This displays how the components within the system, and what their dependencies are in the architecture of the system as a whole
This shows the physical architecture and its deployment components.
The Business Analyst’s Use of UML Diagrams
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.