Upgrade to remove ads
Course: Introduction to Business Analysis
Terms in this set (143)
A competency enabling both listening and interpreting what other people are communicating beyond just words.
A unit of work performed to complete a step, effect a change, or respond to an event.
The division of work into small iterative tasks with the ability to rapidly adapt to changing circumstances.
A rapid assimilation of information to identify relevance.
An unconfirmed theory or belief that can influence a requirement or solution.
Information about a written requirement, such as the source or importance of the requirement. See also requirement.
A technique used to record, track, and prioritize outstanding work items.
A technique used to manage performance of various business models, business processes, and organizational structures.
A reference point for requirements comparison in the future, based on the state of reviewed requirements at a particular point in time.
A set of best practices found in competitor organizations, government, or industry associations that can be used to verify compliance and assess relative performance.
An elicitation technique in which members of a team spontaneously share ideas and solve problems.
A competency enabling the understanding of business needs through past experience and knowledge gained.
The set of tasks and techniques used to identify and analyze the needs of an organization and, through communication among stakeholders, recommend solutions that enable the organization to achieve its goals.
business analysis approach
The activities, processes, and templates that will be used to perform business analysis work on a particular initiative.
Business Analysis Body of Knowledge®
Abbreviated as BABOK, The most credible and authoritative source of knowledge and source of best practices for business analysis profession.
business analysis communications plan
A documented description of how, when, and why the business analyst will communicate with stakeholders, including the form those communications will take. See also business analysis.
Business Analysis Core Concept Model™
Abbreviated as BACCM™, a business analysis model comprised of six core concepts that provide a common meaning when discussing business analysis and its relationships.
business analysis plan
A document identifying and scheduling the activities and resources required to produce an accurate and complete set of requirements related to a solution. See also business analysis.
An expert who studies requirements and recommends appropriate business actions.
An enterprise model that illustrates how stakeholders' strategic concerns are met and supports the ongoing business transformation.
The justification for undertaking or continuing a project in terms of associated costs and benefits.
A state or condition an organization must satisfy to achieve its vision.
Data transformed into valuable information that supports business decision making.
business model canvas
A technique used to describe the rationale for requirements.
business process management
Focuses on the optimization of cross-functional processes to maximize value across the whole organization.
A condition that will enable an organization to improve service, increase revenue, meet regulatory requirements, or avoid costs.
A specific, actionable, and testable directive that is under the control of the organization and supports an organizational policy.
Policies and rules that guide day-to-day business operations.
business rules analysis
Involves the capture, expression and validation of business rules and refining them to align with business goals that can be managed and reused.
A function of an organization that enables it to achieve a business goal or objective; the ability of a process to achieve an objective; or the ability of a system to achieve a goal.
See Certified Business Analysis Professional™.
Certified Business Analysis Professional™
Abbreviated as CBAP®, professional certification for individuals with extensive business analysis experience.
A standard set of quality elements used to verify and validate requirements.
A group technique that encourages participants to collaborate via an elicitation activity.
An individual's ability to perform a task or action and successfully generate the desire outcome.
A technique that organizes business vocabulary for consistent communication.
A competency that enables the understanding of links between contexts, solutions, needs, changes, stakeholders, and value in the bigger picture.
A limitation imposed on a solution which may restrict the implementation of requirements.
A core concept that defines circumstances that influence, or are influenced by, and provide an understanding of the change.
Any of the business analysis fundamental ideas: change, need, solution, context, stakeholder, and value.
A competency that enables the generation of new ideas, concepts, and connections using existing information.
The present set of circumstances.
A stakeholder who uses the products or services of an organization.
A collection of standardized definitions of data elements for common interpretation.
data flow diagram
A representation of the flow of data into a process, the activities that process the data, and how the output is used.
A technique that searches for useful patterns and insights in data to improve decision making.
A representation of data objects and their relationships that provides a common set of semantics for analysis and implementation.
An approach used to make effective decisions when conditions are uncertain; involves studying the potential consequences of various decisions.
Define Design Options
The exercise of defining the solution approach, opportunities for improvements, and requirements allocation to achieve the future state.
A means of eliciting requirements by extracting relevant information from the documentation of an existing system.
Abbreviation for domain subject matter expert.
domain subject matter expert
Abbreviated as domain SME, a person with specific expertise in or in-depth knowledge of a field related to the business need or solution scope.
The activity of identifying sources of requirements and then gathering requirements from those sources.
A technique used to forecast future costs and benefits.
1. An assessment of a solution to determine its status and efficacy in meeting objectives.
2. A means of ensuring that requirements are stated clearly enough to devise a set of tests that can prove that the requirements have been met.
A competency enabling the skillful moderation of discussions and meetings.
A technique used to measure the financial return of possible options.
An interactive group facilitated by a moderator to elicit ideas, attitudes, and preferences about a specific product, service, or opportunity.
A technique used to facilitate understanding of a problem by dividing it into its component parts.
The outcomes of a solution, product, or service that are expected by its users.
A description of the future set of circumstances expected after transitioning from the current state.
An exercise that identifies the differences between the current state and the desired future state.
A depository of business term definitions.
See International Institute of Business Analysis™.
An assessment of the effects that a proposed change will have on a project, system, or stakeholders.
Abbreviation for implementation subject matter expert.
implementation subject matter expert
Abbreviated to implementation SME, a stakeholder whose expertise enables him or her to design, develop, and implement changes to a solution, as well as determine the difficulty of implementing requirements or changes.
Any work undertaken with a defined goal or objective.
International Institute of Business Analysis™
Abbreviated as IIBA, international nonprofit business analyst association responsible for developing and maintaining standards for business analysis and administering the CBAP® certification.
A technique used to elicit information about requirements from stakeholders by asking relevant questions.
A technique used to ensure that outstanding issues are tracked and resolved.
key performance indicator
Abbreviated as KPI, a metric used to evaluate the quality of requirements.
Any of the six groups of related tasks that support a key function of business analysis: Business Analysis Planning and Monitoring, Elicitation and Collaboration, Requirements Life Cycle Management, Strategy Analysis, Requirements Analysis and Design Definition, and Solution Evaluation.
Abbreviation for key performance indicator.
Understanding new information and modifying existing knowledge to effectively adapt to changing environments.
The process of documenting successes, opportunities, failures, and recommendations for improving future projects.
A technique used to understand what customers want and the competitive position of the organization in the market.
A measurable level of an indicator that an organization wants to achieve at a particular time.
A note-taking technique that captures ideas and thoughts in a diagram.
A physical representation of a subject, such as a process or requirement, used to illustrate information.
A problem or opportunity faced by an organization, or the impact a solution should have on its environment.
negotiation and conflict resolution
A competency enabling mediation between groups to assist them in recognizing differences and reaching agreements.
Quality attributes or quality of service requirements that are associated with systems, processes, and people aspects of solutions. They are used to identify constraints on requirements, describe quality attributes of a solution and augment a solution's functional requirements.
A means of determining requirements by assessing a stakeholder's work environment.
A team of stakeholders who support end users and help to maintain an implemented solution on an ongoing basis.
A clearly defined autonomous unit within an enterprise that works toward a particular goal or set of goals.
A technique used to align roles, responsibilities, and the reporting structure to the organizational goals.
The process of ranking items or activities according to their importance to determine the order in which to address them.
A technique used to assess the efficiency and effectiveness of a process and to help identify possible areas for improvement.
The work done to implement a solution, which results in a unique product, service, or outcome.
A document that formally approves a project and authorizes the application of organizational resources to the project.
The stakeholder who manages the work required to implement a solution.
The extent of the work that needs to be done to implement a solution in line with specified features and functions.
The creation of a partial or preliminary working model of a system.
The degree to which an outcome, product, or service satisfies specified requirements.
A stakeholder responsible for the definition and enforcement of standards, including legal and governance regulations.
The connection between entities or concepts.
A condition or capability that is desired in a product or system; the formal, documented version of such a condition or capability.
The process of assigning requirements to systems and components.
The interrelationship between the various requirements of an initiative.
The process of controlling requirements development, including attribute definition, traceability, and change control.
requirements management tool
A software application used to capture requirements, attributes, and associations, store requirements information, and generate requirements reports.
Formal approval of a set of requirements by a stakeholder who has the authority to do so, such as a sponsor.
The ability to track a requirement's derivation, allocation, and relationship to other requirements.
The process of confirming that the stated requirements are aligned with the goals and objectives of the organization.
The process of evaluating requirements to ensure correct definition and quality so they can be used as reliable points of reference during the design, development, and implementation of the solution.
The chance that either a positive or a negative event or condition would influence the objectives of a proposed change.
risk analysis and management
A technique to identify risk and find ways of limiting or eliminating any negative impact.
The amount of risk that a stakeholder is willing to accept for a potential return of value.
roles and permissions matrix
A tool used to identify stakeholders and assess their interests and probable participation.
root cause analysis
A technique used to identify and address underlying problems rather than treating the symptoms alone.
The extent of an activity or process. See also project scope and solution scope.
A model of how processes operate and interact with one another.
Abbreviation for subject matter expert.
An aspect of a solution that meets both the business and stakeholder requirements.
The work done to resolve a problem or take advantage of an opportunity in order to meet a business need.
A stakeholder with the authority to approve a project by contracting or paying for the project.
An identified person who has an interest in or influence over a solution.
The process of identifying stakeholders and assessing their interests and probable participation.
roles, and responsibilities, A list of stakeholders affected by a solution that also documents the stakeholders' respective roles and responsibilities. This list is an outcome of the stakeholder analysis process.
A statement of a need of a stakeholder, including the stakeholder's involvement with the proposed solution.
A technique that describes different possible states of an entity within a system.
subject matter expert
Abbreviated as SME, a stakeholder with specific expertise related to a need or the requirements and potential solutions to meet that need.
A stakeholder who provides products or services to an organization.
An elicitation technique that uses questionnaires to gather information from large groups of stakeholders in a short period of time.
A model used to understand factors that might influence a solution. SWOT stands for strengths, weaknesses, opportunities, and threats.
A competency that enables the holistic consideration of a system rather than just its components.
A method that defines how a business analysis task is to be performed or describes the form that the output of a task is to take.
A stakeholder who studies and uses a software application to assess its quality and identify errors.
A requirement related to the capabilities that a solution must have to successfully transition the enterprise from its current state to its intended future state.
A model that describes a system in terms of the tasks it will perform and what those tasks will achieve for the stakeholders.
A stakeholder, system, or system component that interacts with a solution.
An informal description of functionality needed to deliver value to a specific stakeholder.
A requirement that delivers value to the organization and support its goals and objectives.
The difference between expected outcomes and actual outcomes.
A technique used to determine if a vendor can meet its commitments.
A requirement that is cohesive, complete, consistent, correct, feasible, modifiable, unambiguous, and testable.
A set of conventions that define how requirements are represented, organized and related.
A competency enabling the graphical representation of concepts or systems.
Abbreviation for work breakdown structure.
work breakdown structure
Abbreviated as WBS, a method of defining the total scope of a project by organizing the work hierarchically according to objectives and required deliverables.
A structured meeting, guided by a neutral facilitator, to define and refine requirements.
Other sets by this creator
14.Managing Project-Management Information Systems
Business Process Improvement