Professional Documents
Culture Documents
Business Analyst Training
Business Analyst Training
Business Analyst Training
MindsMapped Consulting
Some of the areas that you will have to be aware of are listed below:
• BA Training Details
• Knowledge Base Information
• Knowledge Assessment Module
Introduction BA Directives
Requirement
Engineering
• What is Requirement?
Types of Requirement
• Who is stakeholder?
A business analyst works along with the technical team and acts as a liaison between stakeholders of Client and the technical team.
He is the face of the technical team to client and all client communications will happen through a business analyst . He /She will elicit ,
analyze ,communicate and validate requirements for change to business process , policies and information system in the existing
business proves of the client. The business analyst understands business problems and opportunities in the context of the requirements
and recommends solution that enable the organization to achieve its goals.
A requirement is basically the need of the client. This need or requirement will transform into a solution while taking various shapes
and forms as it progresses from each stage of SDLC.
Requirements serve as the foundation of systems or system components. A requirement can be thought of as something that is
demanded or obligatory; a property that is essential for the system to perform its function. Requirements vary in intent and in kinds of
properties. They can be functions, constraints or other elements that must be present to meet the needs to solve a problem or achieve
an objective. For clarification purposes, a descriptor should always precede requirements; for example, business requirements, user
requirements, functional requirements.
Business Requirements
Stakeholder Requirements
Solution Requirements
Functional Requirements
Non-Functional Requirements
Transition Requirements
The BA always ensure that the client Requirements are properly gathered or collected, communicates the same to the Technical Team in
UML language which is more understood to them. He communicates to client in business language . BA nurtures these requirements into
an IT solution with the help of the technical team. Generally the technical team will be headed by the Project Manager (PM). PM takes
care about the technical aspects of the Project, Team management and delivery of the project within Time Frames. BA will be in
continuous track of the client requirements through all the different stages of Project development Life Cycle. He helps the technical
team to understand the Requirements clearly and participates in UAT along with Client. In short , we can say that “BA takes the
ownership of the client requirements”.
A “stakeholder” is any person or a group of Person or an organization that is directly or indirectly effected or impacted by the proposed
IT solution.
Project Stakeholders: People inside your organization who provide knowledge and expertise necessary to necessary to quantify
technical and business constraints.
Business Analyst
Project Manager
Development (Sr. Software Engineer, Software Eng, Project Engineer)
Quality Assurance
Testing
Operations (networks, training) -> Environment
Business /Subject Expert
Business Data Modeler
Future Ideas Specialist
Current Automation Specialist
Usability Expert
System Architect
Marketing Specialist
Sales Specialist
Technology Expert
Standards Specialist
Testing Specialist
Organizational Architect
Aesthetics Specialist
Graphics Specialist
A “stakeholder” is any person or a group of Person or an organization that is directly or indirectly effected or impacted by the proposed
IT solution.
2. Business Stakeholders: People inside your organization who provide knowledge and expertise necessary to necessary to quantify
technical and business constraints.
Project Manager
Business Owner(On Paper)
Business Sponsor(Agreement Sign/Amount)
Executive Sponsor/Owner(Executes)
Operation Team
SPOC – Single
Process Experts/Owners/SME
Ambassador Users
End Users
A “stakeholder” is any person or a group of Person or an organization that is directly or indirectly effected or impacted by the proposed
IT solution.
3. 3rd Party Stakeholders: People inside your organization who provide knowledge and expertise necessary to necessary to quantify
technical and business constraints.
Auditors
Focus Group
Security Specialist
Environmental Specialist
Safety Specialist
Outsource
Cultural Specialist
Legal Specialist
Packaging Designer
Manufacturer
Negotiator
Public Opinion
COTS Supplier
Inspector
Negative Stakeholders: People or organizations who do not want your project to succeed:
Competitor
Hacker
Political Party
Pressure Group
Public Opinion
BA Directives
BA Competencies
SDLC
Technical Skill OOA, UML
Functional Skills – Domain
Requirements Engineering
Tools and Documents
BA Contribution in Projects