1.Business Analyst: BA is a professional who bridges gap between business needs and technology solutions. They work with stakeholders to identify the business requirements, analyze data and develop solution to improve process, operation and overall performance.
2.Roles and responsibility of BA: The prime responsibility of business analyst is
•	CLIENT INTERACTION
•	OWNERSHIP OF REQUIREMENTS
•	PROCESS RE ENGINEERING
     Business Analyst will do the following role in project
•	Gather requirement using elicitation technique
•	Documents the requirements using industry standard
•	Model the requirements using UML
•	Communicates the requirement to the technical team
•	Track the requirements during development stage
•	Handle change request
•	Facilitate the UAT

3.Requirement: A Requirement is basically a need of the client. Requirement serve as the foundation of system or system components. The need or requirement will transform into solution while taking various shapes and forms as it progress from each stage of SDLC.

4.Types of requirement: Generally, four types of requirements are there
•	Business Requirement
•	Stakeholder Requirement
•	Solution requirement
•	Transition requirements

5.Business Requirement: Business Requirements refer to the needs and expectations of an organization or stakeholders that a project or solution must meet to achieve its objectives. They describe what the business wants to achieve, the problems it wants to solve, or the opportunities it wants to seize.

6.Stakeholder Requirement: Stakeholder Requirements refer to the needs, expectations, and constraints of individuals or groups who have a vested interest in a project, product, or service. These requirements are critical to ensuring that the solution meets the needs of all stakeholders.

7. Solution Requirement: Solution Requirements describe the characteristics, features, and behaviors of a solution that meets the business and stakeholder requirements. They outline what the solution must do, how it should perform, and the constraints it must operate.

8.Functional Requirement: Functional Requirements (FRs) describe what a solution must do to meet business and stakeholder needs. They outline the specific behaviors, functions, and features of a solution.

9. Non-Functional Requirement: Non-Functional Requirements (NFRs) describe the characteristics, constraints, and quality attributes of a solution that are not related to its functionality. They outline how the solution should perform, be used, and behave.

10.Transition requirement: Planning and managing the transition of a new solution or system is crucial to ensure a smooth deployment and minimize disruptions to the business. Transition Requirements outline the necessary steps, activities, and timelines for transitioning from the current state to the future state.

11.Business Process Modelling: Business Process Modeling (BPM) is a technique used to visualize, document, and analyze business processes to improve efficiency, productivity, and quality. It involves creating a graphical representation of a business process, using standardized symbols and notations, to better understand and communicate the process.

12.Gnatt chart: Project manager generally plan their projects by using Gantt chart. A Gantt chart is a type of bar chart that illustrates a project schedule, showing the tasks, dependencies, and timelines for a project. It's a popular project management tool used to plan, coordinate, and track progress.

13.Risk Analysis: Risk Analysis is a crucial step in Business Analysis to identify, assess, and prioritize potential risks that could impact the project or business. Business Analysts use risk analysis to
•	Identify potential risks: Determine what could go wrong and what the impact would be.
•	Assess risks: Evaluate the likelihood and potential impact of each risk.
•	Prioritize risks: Focus on the most critical risks that require mitigation or management.
•	Develop mitigation strategies: Create plans to minimize or eliminate risks.

14.SDLC: SDLC (Software Development Life Cycle) is a framework used to plan, design, develop, test, and deliver software projects. It provides a structured approach to software development, ensuring that all aspects of the project are considered and that the final product meets the required quality standards.

15.Agile Methodology: Agile Methodology is an iterative and flexible approach to software development, project management, and product development. It emphasizes collaboration, customer feedback, and continuous improvement.

16.Scrum: Scrum is a popular Agile framework used for managing and completing complex projects. It emphasizes teamwork, accountability, and iterative progress toward well-defined goals.
     SCRUM ROLES:
1. Product Owner: Responsible for the product backlog and prioritizing features.
2. Scrum Master: Facilitates Scrum processes and removes impediments.
3. Development Team: Cross-functional team that develops the product

17.SPRINT: A Sprint is a core component of the Scrum framework, representing a short, time-boxed period (usually 2-4 weeks) during which a specific set of work is completed. Sprints are iterative and incremental, allowing teams to deliver working software in short cycles.

18.User story: A User Story is a natural-language description of a software feature or requirement from the end-user's perspective. It's a tool used in Agile development to capture user needs and guide development.

19.Use case Diagram: A Use Case Diagram is a visual representation of a system's functional requirements, showing how users interact with the system to achieve specific goals. It's a tool used in software development and systems engineering to identify, clarify, and organize system requirements.

20.Use case specification: A Use Case Specification is a detailed document that describes a specific use case, outlining the steps, actions, and interactions between the actor and the system to achieve a particular goal. It provides a clear understanding of the system's behavior and requirements.