This document discusses the roles and responsibilities of a business analyst, including eliciting requirements, preparing documentation, and using techniques like UML diagrams. It also covers the business analyst's involvement in the software development lifecycle from different methodologies. Finally, it discusses how clearly defining business requirements early can help reduce project failures, align with business goals, and reduce costs.

1. Who is business analyst?
What is business analysis?
Roles & responsibilities of BA?
Do's and Don't of BA?
Skills Required for BA?
Elicitation Technics,facilitation?
Analysis Technics?
What are the Documents prepared by BA?
Types of requirements?
What is SDLC and How BA is involve in each Phase?
What are the Methodologies & Model?
Agile?
Waterfall?
XP(Extreme Programming)?
Karbon?
Iterverative?
UML Diagrams?
Use Case & Usecase Description Doc?
Activity Diagrams?
Swimlanes?
Tools used by BA?
Types of Industries in IT??
Reduce Project failure:
Structured explanation of a business process or method
defined early in the life cycle helps reduce project failures that occur due to
misaligned or misrepresented requirements leading to failure of user
expectations.
Connects to broader business goals:
Well-defined business requirements help lay out a project
charter, a critical step in executing business strategy or business goals, and
to take it to the next logical step of developing it into an IT system. This
helps monitoring overall project health and provides for positive traction with
key project stakeholders including sponsors.
Saves costs:

2. Good quality of business requirements when captured early
on not only improves success of a project but also save overall costs associated
with change requests, and related investments in training, infrastructure, etc.