Author Topic: Tools used by a Business Analyst  (Read 10470 times)


  • Global Moderator
  • Newbie
  • *****
  • Posts: 10
Re: Tools used by a Business Analyst
« Reply #30 on: May 22, 2020, 01:41:03 pm »
Business Analysts Uses Tools Like Excel & Visio 3 tools commonly used by business analysts to complete data modelling are:
• Visio is used for creating ERD’s, It’s a fully featured software tool that many companies already have.
• There are many web-based diagramming tools offering similar functionality to Visio, If you don’t have access to Visio.
• For Data Dictionary or Data Mapping, Microsoft Excel is commonly used.


  • Global Moderator
  • Newbie
  • *****
  • Posts: 5
Re: Tools used by a Business Analyst
« Reply #31 on: May 29, 2020, 12:44:48 pm »
Different Categories of tools..
1.   BPM – Business Process Modelling Tools
2.   OOA – Object Oriented Approach
3.   UML – Unified Modelling Language
4.   Mockups

BPM facilities the users and tech team to understand the current or proposed processes and then analyze and optimize those processes through an IT Solution. (Here, we flowcharts similar to activity diagrams to represent the process flow).

OOA – Object Oriented Analysis. (Object, Class, Component, Package, and Subsystem).

UML is a general-purpose, developmental, modeling language in the field of software engineering that is intended to provide a standard way to visualize the design of a system.

UML is used by a BA to communicate the requirements to the tech team of the project according to the industry standards.

•   Use Case Diagrams (User Perspective)
•   Class
•   Component
•   Package
•   Deployment

•   Activity Diagrams (System Perspective)
•   Sequence Diagrams
•   State Chart
•   Collaboration

•   Axure (Navigate through pages)
•   Balsamiq (Cannot Navigate)

Using one or more of these tools in a project helps to accurately reflect the actual needs and underlying concerns of the project stakeholders.
 Diagrams/mockups can be viewed while discussing requirements and shall facilitate identification of missing data thereby avoiding gaps and complexities, also illustrates implications of proposed changes and determine specifications for the development phase.
Diagrams and other tools simplify communications with project stakeholders and the tech team. Graphic images can clearly encapsulate many words, promoting a common and clearer understanding of what the requirements actually are.