Acceptance criteria: Criteria associated with requirements, products, or the delivery cycle that must be met to achieve stakeholder acceptance. (IIBA)

Actor: A human, device, or system that plays some specified role in interacting with a solution. (IIBA)

Adaptive approach: An approach where the solution evolves based on a cycle of learning and discovery, with feedback loops that encourage making decisions as late as possible. (IIBA)

Agile: A project management and software development methodology that promotes iterative development, collaboration, and flexibility.

Architecture: The design, structure, and behavior of a structure's current and future states regarding its components and their interaction. See also business architecture, enterprise architecture, and requirements architecture. (IIBA)

Artifact: Any solution-relevant object created as part of business analysis efforts. (IIBA)

As-Is Process: The current state of a business process, used as a baseline for analyzing improvements or changes. 

Assumption: An influencing factor that is believed to be true but has not been confirmed to be accurate or that could be true now but may not be in the future. (IIBA)

Backlog: A prioritized list of tasks or features that must be completed, often used in Agile methodologies.

Balanced Scorecard: A strategic planning and management system used to align business activities to the vision and strategy of the organization by monitoring performance against strategic goals. 

Behavioral business rule: A business rule that places an obligation (or prohibition) on conduct, action, practice, or procedure; a business rule that aims to shape (govern) day-to-day business activity. Also known as the operative rule. (IIBA)

Benchmarking: A comparison of a decision, process, service, or system's cost, time, quality, or other metrics to those of leading peers to identify opportunities for improvement. (IIBA)

Body of knowledge: The aggregated knowledge and generally accepted practices on a topic. (IIBA)

Brainstorming: A team activity that seeks to produce a broad or diverse set of options through the rapid and uncritical generation of ideas. (IIBA)

Business: An economic system where any commercial, industrial, or professional activity is performed for profit. (IIBA)

Business analysis: The practice of enabling change in the context of an enterprise by defining needs and recommending solutions that deliver value to stakeholders. (IIBA)

Business Case: A document that justifies initiating a project or task. It typically includes a Situation statement and alternatives with each's benefits, costs, risks, and potential return on investment. 

Business Process Modeling (BPM): A graphical representation of a company’s business processes or workflows, often created to analyze and improve current processes. 

Business requirements: Statements of goals, objectives, and outcomes that describe why a change has been initiated. They can apply to an enterprise, a business area, or a specific initiative. (IIBA)

Business Requirements Document (BRD): A formal document that details the business requirements for a project. It includes the objectives, scope, and detailed requirements.

Change Management: A systematic approach to dealing with change, both from the perspective of an organization and the individual. It involves preparing, supporting, and helping individuals, teams, and organizations in making organizational change.

Data Flow Diagram (DFD): A graphical representation of the flow of data within a system, showing how data is processed and stored. 

Enterprise Analysis: The analysis of the entire organization, identifying business needs, and devising solutions to business problems at a macro level.

Feasibility Study: An assessment of the practicality and potential success of a proposed project or system.

Functional Requirements: These describe a solution's capabilities regarding the behavior and information it will manage. They provide the appropriate level of detail to allow for the solution's development and implementation. They are subject to tests.

Gap analysis: A method of assessing the differences between the current state and the desired future state. It identifies what needs to be done to bridge the gap.

KPI (Key Performance Indicator): A measurable value that indicates how effectively an organization achieves its key business objectives.

Lean: A methodology focused on maximizing customer value while minimizing waste, often used in manufacturing and service industries.

Mind Mapping: A visual representation of information, capturing thoughts, ideas, and concepts around a central theme.

MVP (Minimum Viable Product): The version of a new product allows a team to collect the maximum amount of validated learning about customers with the least effort.

MoSCoW Method: A prioritization technique used to reach a common understanding with stakeholders on the importance of delivering specific requirements. It stands for 

1. Must have, 

2. Should have, 

3. Could have, and 

4. Won't have. 

Non-functional requirements (or quality-of-service requirements): do not relate directly to the behavior or functionality of the solution but rather describe conditions under which a solution must remain effective or qualities that a solution must have. They provide the appropriate level of detail to allow for the development and implementation of the solution.

Process mapping: A visual representation of the steps involved in a business process. It helps in understanding, analyzing, and improving the process.

Prototyping: Creating an early model of a product to test concepts and gather feedback. This can be a mock-up, wireframe, or an interactive model.

RACI Matrix: A responsibility assignment matrix that delineates the roles and responsibilities of various individuals in completing tasks or deliverables. It stands for 

• Responsible

• Accountable

• Consulted, and

• Informed. 

Requirement: A condition or capability a stakeholder needs to solve a problem or achieve an objective. 

Requirements can be

• business requirements,

• stakeholder requirements,

• functional requirements (what the system should do),

• non-functional requirements (how the system should be),

• transitional requirements.

Requirements Baseline: The list of requirements and their specifications that have been formally reviewed and agreed upon serve as the basis for further development or change. The baseline can be changed only through formal change control procedures or a type of procedure such as configuration management.

Requirements Elicitation: Collecting stakeholder requirements through various techniques such as interviews, surveys, and workshops.

Root Cause Analysis (RCA): A systematic process for identifying the root causes of problems or events and an approach for responding to them. RCA seeks to determine the underlying reasons for faults or problems.

Scope: The boundaries of what will be analyzed, designed, and delivered in a project. It includes what is included and excluded from the project.

Scope Creep: the uncontrolled expansion of a product or project scope without adjustments to time, cost, and resources. It often results in project overruns and challenges to project success.

Solution: A means of satisfying one or more needs in a context. This can be a new system, process, or methodology.

Stakeholder: Any individual, group, or organization that can affect, be affected by or perceive itself to be affected by a business decision or project.

Stakeholder Analysis: Identifying stakeholders and analyzing their needs and expectations about a project or business analysis task.

Stakeholder requirements: Describe the needs of stakeholders that must be met to achieve the business requirements. They may serve as a bridge between business and solution requirements. They are NOT subject to tests but indirectly tested by related functional and non-functional requirements.

SWOT Analysis: A framework for identifying and analyzing internal Strengths and Weaknesses and external Opportunities and Threats. Identifying these usually opens the door to finding synergies between them and using these pairs to form strategies or make decisions.

To-Be Process: The future state of a business process after implemented improvements or changes. 

Transition Requirements: Describe the capabilities the solution must have and the conditions the solution must meet to facilitate the transition from the current state to the future state but which are not needed once the change is complete. They are differentiated from other requirement types because they are temporary. Transition requirements address data conversion, training, and business continuity, etc.

Transversal requirements: Capabilities that are not specific to a certain solution but present in many. Usually, they are identified in a certain solution but, later on, generalized to many or all within a business domain. Any requirement (BR, SHR, FR, NFR, TR) can become transversal.

Use Case: A description of how a user will interact with a system to achieve a specific goal. It defines the interactions between the user and the system.

User Story: A brief, simple description of a feature or requirement from the end user's perspective. They are often used in Agile methodologies.

Value Chain Analysis: Analyzing the activities that create value for a customer within a company, identifying opportunities for optimization. 

Voice of the Customer (VOC): A process used to capture the requirements or feedback from the customer (internal or external) to provide the customers with best-in-class service or product quality. VOC is critical for driving customer-centric product development.

Waterfall: A linear and sequential approach to project management where each phase must be completed before the next one begins.

Wireframe: An essential visual guide to suggest the layout and placement of elements on a web page or application interface.

Work Breakdown Structure (WBS): A hierarchical decomposition of the total scope of work to be carried out by the project team, used to organize and define the total work of the project.