COEPD – Center of Excellence for Professional Development Happy Learning
A Business Analyst is a professional who bridges the gap between the IT team and the business. Business analysts evaluate the business process, improve it, and deliver better business recommendations to the stakeholders. Business analytics refer to the skills, technologies, practices for continuous iterative and investigation of past business performance to gain insight and drive business planning
Types of Requirements of a Business Analyst
a) Project Requirements
Project requirements, which provides conditions or tasks that must be completed for a project. It also defines the scope of the project, with respect to the stakeholders, and gives clear picture for evaluating the quality of a project
b) Business Requirements
These are the statements of goals, objectives, and outcomes that describe why a change been initiated. What is required for business success. Identify business problems or opportunities. It defines stakeholders wants and needs or What stakeholders can perform from the final application.
c) Functional Requirements
Functional requirements define functionality of the system. It describes external behavior of the application and expected deliverables
How the product or application works?
What inputs the product should accept?
What outputs the product should produce?
What data system should store?
d) Non-Functional Requirements
Non-Functional Requirements are describing the conditions under which a solution must remain effective or qualities a solution must have. It examines the requirements for a solution that define how well the functional requirements must perform. It is clear how the constraints apply to the set of functional requirements. The non-functional requirements have a strong influence on whether a solution is accepted by the users.
e) System Requirements
System Requirements are collected by system analyst. System requirements define how an application will interact with system hardware such as operating speed, response time, accessibility, or security.
f) Stakeholder Requirements
These describe the needs of stakeholders that must be met in order to achieve the business requirements. These serve as a bridge between business and solution requirements.
g) Solution Requirements
These describes the capabilities and qualities of a solution that meets the stakeholder requirements.
h) Transition Requirements
These describe the capabilities of the solution must have and the conditions of the solution must meet to facilitate transition from the current state to the future state.
Responsibilities of a Business Analyst
a) Identify and recognize the organizations business objective
b) Improve the existing business. Gather and document the new business requirements
c) Interact with the development team to design the layout
d) Implement the newly designed features in the business
e) Gauge the functional and non-functional requirements
f) Communicate, hold meetings with the business team, stakeholders, and others
g) Verify that the project is running well with the help of user acceptance testing
h) Present, and document the results. Also deliver the maintenance reports.
Core Business Analysis Skills
a) Documentation and Presentation skills
Documenting is one of the best technical skills required for a business analyst. It mainly concentrates on writing reports, planning the implementation, documenting, analyzing the details. Having the ability to do clear and concise documentation.
b) Analysis Skills
Logic, reasonability, and analytical ability to use data to advantage
c) Business Analysis Tools
Technical expertise in using BA tools alongside basic office programs like Microsoft Excel, Microsoft PowerPoint, Microsoft Word, Microsoft Visio, and Balsamiq
d) Data Review & Analysis
Organizations to create effective business decisions by gathering and analysing data for their organization’s business and evaluating. The art of interpreting business insights and projects to non-technical members and management. This allows managers to understand their business more accurately, leading to better decision-making.
e) Elicitation skills
Business analytics run meetings called elicitation sessions to communicate project requirements to stakeholders
f) Use Case Modeling and Scenarios
A use case diagram provides any business analyst a high-level description of what system must do and who can interact with it. Use Case Studies grow when you notice situations (i.e., uses) that are similar to past conversations, and then use them to explain those situations in a more understandable and actionable way. Use cases describes the interactions between the primary actor, the solution and any secondary actors needed to achieve the primary actors’ goal.
g) Financial Analysis
It is used to understand the financial aspects of an investment, a solution approach. It allows to executive decision makers to objectively compare very different investments from different perspectives. Assumptions and estimations built into the benefits and costs, and into the financial calculations, are clearly stated that may be challenged or approved.
h) Prototyping
It is used to elicit and validate stakeholder needs through an iterative process that creates a model or design of requirements. It provides a visual representation for the future state. Allows for stakeholders to provide input and feedback early in the design process.
i) Root Cause Analysis
It is used to identify and evaluate the underlying causes of a problem. Helps to maintain an objective perspective when performing cause and effect analysis. Enables stakeholders to specify and effective solution at the appropriate points for the corrective action.
