BABOK v3 (English)

Appendix A: Glossary – o, p, q, r

03/12/202308/11/2023 admin

o

Term	Description
objective	See business objective.
observation (business analysis)	Studying and analyzing one or more stakeholders in their work environment in order to elicit requirements.
OLAP	See online analytical processing.
online analytical processing (OLAP)	A business intelligence approach that allows users to analyze large amounts of data from different points of view.
operational support	A stakeholder who is responsible for the day-to-day management and maintenance of a system or product.
operative rule	See behavioral business rule.
organization	An autonomous group of people under the management of a single individual or board, that works towards common goals and objectives.
organizational capability	A function inside the enterprise, made up of components such as processes, technologies, and information and used by organizations to achieve their goals.
organizational change management	See change management.
organization modelling	The analysis technique used to describe roles, responsibilities and reporting structures that exist within an enterprise.
organizational unit	Any recognized association of people within an organization or enterprise.

p

Term	Description
peer review	A formal or informal review of a work product to identify errors or opportunities for improvement. See also inspection.
plan	A detailed scheme for doing or achieving something usually comprising a set of events, dependencies, expected sequence, schedule, results or outcomes, materials and resources needed, and how stakeholders need to be involved.
policy	See business policy.
predictive approach	An approach where planning and baselines are established early in the life cycle of the initiative in order to maximize control and minimize risk.
prioritization	Determining the relative importance of a set of items in order to determine the order in which they will be addressed.
process	A set of activities designed to accomplish a specific objective by taking one or more defined inputs and turning them into defined outputs.
process model	A set of diagrams and supporting information about a process and factors that could influence the process. Some process models are used to simulate the performance of the process.
product (business analysis)	A solution or component of a solution that is the result of an initiative.
product backlog	A set of user stories, requirements, or features that have been identified as candidates for potential implementation, prioritized, and estimated.
product scope	See solution scope.
product vision statement	A brief statement or paragraph that describes the goals of the solution and how it supports the strategy of the organization or enterprise.
project	A temporary endeavor undertaken to create a unique product, service, or result.
project manager	A stakeholder who is responsible for managing the work required to deliver a solution that meets a business need, and for ensuring that the project’s objectives are met while balancing the project constraints, including scope, budget, schedule, resources, quality, and risk.
project scope	The work that must be performed to deliver a product, service, or result with the specified features and functions.
proof of concept	A model created to validate the design of a solution without modelling the appearance, materials used in the creation of work, or processes and workflows ultimately used by the stakeholders.
prototype	A partial or simulated approximation of the solution for the purpose of eliciting or verifying requirements with stakeholders.

q

Term	Description
quality	The degree to which a set of inherent characteristics fulfills needs.
quality assurance	A set of activities performed to ensure that a process will deliver products that meet an appropriate level of quality.
quality attributes	A set of measures used to judge the overall quality of a system. See also non-functional requirements.
questionnaire	A set of defined questions, with a choice of answers, used to collect information from respondents.

r

Term	Description
RACI matrix	See responsible, accountable, consulted, and informed matrix.
regulator	A stakeholder from outside the organization who is responsible for the definition and enforcement of standards.
repository	A real or virtual facility where all information on a specific topic is stored and is available for retrieval.
request for information (RFI)	A formal elicitation method intended to collect information regarding a vendor’s capabilities or any other information relevant to a potential upcoming procurement.
request for proposal (RFP)	A requirements document issued when an organization is seeking a formal proposal from vendors. An RFP typically requires that the proposals be submitted following a specific process and using sealed bids which will be evaluated against a formal evaluation methodology.
request for quote (RFQ)	A procurement method of soliciting price and solution options from vendors.
request for tender (RFT)	An open invitation to vendors to submit a proposal for goods or services.
requirement	A usable representation of a need.
requirements attribute	A characteristic or property of a requirement used to assist with requirements management.
requirements allocation	The process of assigning requirements to be implemented by specific solution components.
requirements architecture	The requirements of an initiative and the interrelationships between these requirements.
requirements artifact	A business analysis artifact containing information about requirements such as a diagram, matrix, document or model.
requirements defect	A problem or error in a requirement. Defects may occur because a requirement is poor quality (see requirements verification) or because it does not describe a need that, if met, would provide value to stakeholders (see requirements validation).
requirements document	See requirements package.
requirements life cycle	The stages through which a requirement progresses from inception to retirement.
requirements management	Planning, executing, monitoring, and controlling any or all of the work associated with requirements elicitation and collaboration, requirements analysis and design, and requirements life cycle management.
requirements management plan	A subset of the business analysis plan for a specific change initiative, describing specific tools, activities, and roles and responsibilities that will be used on the initiative to manage the requirements. See business analysis plan.
requirements management tool	Special-purpose software that provides support for any combination of the following capabilities: elicitation and collaboration, requirements modelling and/or specification, requirements traceability, versioning and baselining, attribute definition for tracking and monitoring, document generation, and requirements change control.
requirements model	An abstract (usually graphical) representation of some aspect of the current or future state.
requirements package	A specialized form of a business analysis package primarily concerned with requirements. A requirements package may represent a baseline of a collection of requirements.
requirements traceability	The ability for tracking the relationships between sets of requirements and designs from the original stakeholder need to the actual implemented solution. Traceability supports change control by ensuring that the source of a requirement or design can be identified and other related requirements and designs potentially affected by a change are known.
requirements validation	Work done to evaluate requirements to ensure they support the delivery of the expected benefits and are within the solution scope.
requirements verification	Work done to evaluate requirements to ensure they are defined correctly and are at an acceptable level of quality. It ensures the requirements are sufficiently defined and structured so that the solution development team can use them in the design, development, and implementation of the solution.
requirements workshop	A structured meeting in which a carefully selected group of stakeholders collaborate to define and/or refine requirements under the guidance of a skilled neutral facilitator.
residual risk	The risk remaining after action has been taken or plans have been put in place to deal with the original risk.
retrospective	See lessons learned process.
return on investment (ROI) (business analysis)	A measure of the profitability of a project or investment.
responsible, accountable, consulted, and informed matrix (RACI matrix)	A tool used to identify the responsibilities of roles or team members and the activities or deliverables in which they will participate, by being responsible (doing the work), accountable (approving the results), consulted (providing input) or informed of the completed item after it has been completed.
RFI	See request for information.
RFP	See request for proposal.
RFQ	See request for quote.
RFT	See request for tender.
risk (business analysis)	The effect of uncertainty on the value of a change, a solution, or the enterprise. See also residual risk.
risk assessment	Identifying, analyzing and evaluating risks.
ROI	See return on investment.
root cause	The cause of a problem having no deeper cause, usually one of several possible causes.
root cause analysis	A structured examination of an identified problem to understand the underlying causes.

Leave a Reply Cancel reply