Acceptance criteria: Criteria associated with requirements, products, or the delivery cycle that must be met in order to achieve stakeholder acceptance.
验收标准：为了通过利益相关者的验收，所必须满足的与需求、产品或发布周期相关的标准。
Actor (business analysis): A human, device, or system that plays some specified role in interacting with a solution.
角色（业务分析）： 在一个解决方案的交互过程中起到一些特定作用的人、设备或系统。
Adaptive approach: An approach where the solution evolves based on a cycle of learning and discovery, with feedback loops which encourage making decisions as late as possible.
适应性方法：鼓励推迟决策，解决方案通过周而复始的反馈，基于发现式学习周期而演化的一种方法。
Agile Extension to the BABOK® Guide: A standard on the practice of business analysis in an agile context. The Agile Extension to the BABOK® Guide version 1 was published in 2013 by IIBA®, in partnership with the Agile Alliance.
Architecture: The design, structure, and behaviour of the current and future states of a structure in terms of its components, and the interaction between those components. See also business architecture, enterprise architecture, and requirements architecture.
Artifact (business analysis): Any solution-relevant object that is created as part of business analysis efforts.
工件（业务分析）：作为业务分析结果的一部分而创建的与解决方案相关的产物。
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.
假设： 一种被认为是正确的影响因素但并没有被证实是准确的，或者现在认为是正确的但是将来可能不是。
B
Behavioural business rule: A business rule that places an obligation (or prohibition) on conduct, action, practice, or procedure; a business rule whose purpose is to shape (govern) day-to-day business activity. Also known as operative rule.
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.
Body of knowledge: The aggregated knowledge and generally accepted practices on a topic.
知识体系： 在某一领域汇集的知识和通用实践
BPM: See business process management.
BPM:见业务过程管理。
Brainstorming: A team activity that seeks to produce a broad or diverse set of options through the rapid and uncritical generation of ideas.
头脑风暴：一种运用快速和不加批判的创意方式来产出大量的或者多样化选项的团队活动。
Business (business analysis): See enterprise.
业务（业务分析）：见企业分析。
Business (business world): An economic system where any commercial, industrial,or professional activity is performed for profit.
业务（业界）：一个商业，工业或者专业活动都具有趋利性的经济体系。
Business analysis: The practice of enabling change in the context of an enterprise by defining needs and recommending solutions that deliver value to stakeholders.
业务分析：通过定义对利益相关者有价值的需求以及建议解决方案使企业状况得到改变的一种实践
Business analysis information: Any kind of information at any level of detail that is used as an input to business analysis work, or as an output of business analysis work.
业务分析信息：任何一种无论在哪个细节级别都可被用来作为业务分析工作输入或者输出的的信息。
Business analysis package: A document, presentation, or other collection of text,matrices, diagrams and models, representing business analysis information.
业务分析包：代表业务分析信息的文档、演示文稿或者文本、表单、图标、以及模型。
Business analyst: Any person who performs business analysis, no matter their job title or organizational role. For more information, see Who is a Business Analyst? (p. 2).
Business analysis approach: The set of processes, rules, guidelines, heuristics, and activities that are used to perform business analysis in a specific context.
业务分析方法：在特定情境执行业务分析时，所使用流程、规则、指导原则、启发和活动的集合。
Business analysis communication plan: A description of the types of communication the business analyst will perform during business analysis, the recipients of those communications, and the form and frequency of those communications.
Business analysis effort: The scope of activities a business analyst is engaged induring the life cycle of an initiative.
业务分析工作：在计划行动的生命周期间，业务分析师投入活动的范围。
Business analysis plan: A description of the planned activities the business analyst will execute in order to perform the business analysis work involved in a specific initiative. See also requirements management plan.
Business architecture: The design, structure, and behaviour of the current and future states of an enterprise to provide a common understanding of the organization. It is used to align the enterprise’s strategic objectives and tactical demands.
Bsiness case: A justification for a course of action based on the benefits to be realized by using the proposed solution, as compared to the cost, effort, and other considerations to acquire and live with that solution.
Bsiness decision: A decision that can be made based on strategy, executive judgment, consensus, and business rules, and that is generally made in response to events or at defined points in a business process.
Business goal: A state or condition that an organization is seeking to establish and maintain, usually expressed qualitatively rather than quantitatively.
企业目标：组织寻求建立和维护的状态或条件，通常以质化而非量化的方式表现。
Business need: A problem or opportunity of strategic or tactical importance to be addressed.
业务需要：需要处理的体现战略或者战术重要性的问题或机会。
Business objective: An objective, measurable result to indicate that a business goal has been achieved.
业务目标：通过客观的、可衡量的结果来表明已达成企业目标
Business policy: A non-practicable directive that controls and influences the actions of an enterprise.
企业政策：非实际可行的指令，能控制和影响企业的行动。
Business problem: An issue of strategic or tactical importance preventing an enterprise or organization from achieving its goals.
业务问题：体现战略或者战术重要性的问题，这些问题会阻碍企业或组织达成目标。
Business process: An end-to-end set of activities which collectively responds to an event, and transforms information, materials, and other resources into outputs that deliver value directly to the customers of the process. It may be internal to an organization, or it may span several organizations.
business process management (BPM): A management discipline that determines how manual and automated processes are created, modified, cancelled, and governed.
业务流程管理：管理原则，用于决定如何创建、修改、撤销以及治理人工或自动流程。
Bsiness process re-engineering: Rethinking and redesigning business processes to generate improvements in performance measures.
业务流程再造：重新思考和设计业务流程，使其在绩效衡量方面有所改善。
Business requirement: A representation of goals, objectives and outcomes that describe why a change has been initiated and how success will be assessed.
业务需求: 通过对远景目标、阶段目标以及成果进行陈述来说明为何业务发生了改变，以及如何评估成功。
Business rule: A specific, practicable, testable directive that is under the control of the business and that serves as a criterion for guiding behaviour, shaping judgments, or making decisions.
业务规则: 在业务框架下的特定的、可操作、可测试的指导，用来作为行为引导、判断、决策的准则。
C
Capability: The set of activities the enterprise performs, the knowledge it has, the products and services it provides, the functions it supports, and the methods it uses to make decisions.
Change: The act of transformation in response to a need.
变更: 通过行为改变来对需求做出响应。
Change agent: One who is a catalyst for change.
变革者：促成变革的人。
Change control: Controlling changes to requirements and designs so that the impact of requested changes is understood and agreed-to before the changes are made.
变更控制：控制需求和设计的变更，以使要求变更的影响在变更做出之前是可理解和达成一致的。
Change management: Planned activities, tools, and techniques to address the human side of change during a change initiative, primarily addressing the needs of the people who will be most affected by the change.
Change strategy: A plan to move from the current state to the future state to achieve the desired business objectives.
变更策略：从当前状态转移到未来状态以达到预期的业务目标的计划。
Change team: A cross-functional group of individuals who are mandated to implement a change. This group may be comprised of product owners, business analysts, developers, project managers, implementation subject matter experts (SMEs), or any other individual with the relevant set of skills and competencies required to implement the change.
Checklist (business analysis): A standard set of quality elements that reviewers use for requirements verification.
检查单（业务分析）：一套标准的评审者用来做需求评审的质量要素。
Collaboration: The act of two or more people working together towards a common goal.
协作：两个或两个以上的人为了共同的目标而合作的行为。
Commercial off-the-shelf (COTS): A prepackaged solution available in the marketplace which address all or most of the common needs of a large group of buyers of those solutions. A commercial off-the-shelf solution may require some configuration to meet the specific needs of the enterprise.
Competitive analysis: A structured assessment which captures the key characteristics of an industry to predict the long-term profitability prospects and to determine the practices of the most significant competitors.
竞争分析：为了预测长期盈利前景以及确定最重要竞争对手的做法，通过体系化评估来捕捉行业的关键特点。
Component: A uniquely identifiable element of a larger whole that fulfills a clear function.
组件： 大型整体中的独一可识别元素，能够实现一个明确的功能。
Concept model: An analysis model that develops the meaning of core concepts for a problem domain, defines their collective structure, and specifies the appropriate vocabulary needed to communicate about it consistently.
Constraint (business analysis): An influencing factor that cannot be changed, and that places a limit or restriction on a possible solution or solution option.
约束（业务分析）：无法改变的影响因素，使可能的解决方案或方案选项受到限制或制约。
Context: The circumstances that influence, are influenced by, and provide understanding of the change.
情境：影响、被影响、和提供理解变更的环境。
Core concept (business analysis): One of six ideas that are fundamental to the practice of business analysis: Change, Need, Solution, Context, Stakeholder, and Value.
Cost-benefit analysis: An analysis which compares and quantifies the financial and non-financial costs of making a change or implementing a solution compared to the benefits gained.
Create, Read, Update, and Delete matrix (CRUD matrix): A two-dimensional matrix showing which user roles have permission to access specific information entities, and to create new records in those entities, view the data in existing records, update or modify the data in existing records, or delete existing records. The same type of matrix can be used to show which processes,instead of users, have the create, read, update and delete rights.
CRUD matrix: See create, read, update, and delete matrix.
CRUD矩阵：见 创建，读取，更新，和删除矩阵
Customer: A stakeholder who uses or may use products or services produced by the enterprise and may have contractual or moral rights that the enterprise is obliged to meet.
顾客:使用或可能使用企业的产品或服务的干系人，该企业有义务满足其合同或道德权利。
D
Decision analysis: An approach to decision making that examines and models the possible consequences of different decisions, and assists in making an optimal decision under conditions of uncertainty.
决策分析：一种决策方法，用于检验和模拟不同的决定带来的可能后果，并协助作出不确定条件下的最优决策。
Decomposition: A technique that subdivides a problem into its component parts in order to facilitate analysis and understanding of those components.
分解：将问题细分成组件，以促进分析和理解这些组件的一种技术,。
Defect: A deficiency in a product or service that reduces its quality or varies from a desired attribute, state, or functionality.
缺陷：产品或服务因质量降低、或违背了所期望的属性、状态或功能的缺点
Ddefinitional business rule: A rule that indicates something is necessarily true (or untrue); a rule that is intended as a definitional criterion for concepts, knowledge, or information. Also known as a structural rule.
Deliverable: Any unique and verifiable work product or service that a party has agreed to deliver.
可交付成果:当事人同意交付的任何独特的和可核查的工作产品或服务。
Design: A usable representation of a solution. For more information see Key Terms (p. 14) and Requirements and Designs (p. 19).
设计：一个解决方案可用的表达形式。更多信息见 关键术语(p. 14)和需求与设计(p. 19)。
Document analysis (business analysis): An examination of the documentation of an existing system in order to elicit requirements.
文档分析：为了引出需求而对一个现有系统的文档进行的检查。
Domain: The sphere of knowledge that defines a set of common requirements, terminology, and functionality for any program or initiative solving a problem.
域： 为任一解决问题的安排和倡议而定义的一组共同需求、术语和功能的知识范围
Domain subject matter expert: A stakeholder with in-depth knowledge of a topic relevant to the business need or solution scope.
领域主题专家：一个对业务需求或解决方案范围相关主题有深入知识的利益相关者。
DSDM: See dynamic systems development method.
DSDM: 见动态系统开发方法
Dynamic systems development method (DSDM): A project delivery framework which focuses on fixing cost, quality, and time at the beginning while contingency is managed by varying the features to be delivered.
Elicitation: Iterative derivation and extraction of information from stakeholders or other sources.
（需求）捕获：从利益相关者或其它干系人处反复推衍并提取信息。
End user: A stakeholder who directly interacts with the solution.
最终用户：与方案直接交互的利益相关者。
Enterprise: A system of one or more organizations and the solutions they use to pursue a shared set of common goals.
企业：一个或多个组织、以及他们用以追求共同目标的解决方案所构成的系统。
Enterprise architecture: A description of the business processes, information technology, people, operations, information, and projects of an enterprise and the relationships between them.
企业架构：对企业的业务流程、信息技术、人、操作、信息、项目及其之间的关系的描述。
Enterprise readiness assessment: An assessment that describes the enterprise is prepared to accept the change associated with a solution and is able to use it effectively.
企业准备就绪评估：对企业是否准备好接受一个方案带来的相关变化，并能够有效使用该方案的评估。
Entity-relationship diagram: A graphical representation of the entities relevant to a chosen problem domain and the relationships between them.
实体关系图：对已选的问题域相关的实体、以及实体之间关系的图形化表示。
Estimate: A quantitative assessment of a planned outcome, resource requirements, and schedule where uncertainties and unknowns are systematically factored into the assessment.
估算：对计划的产出、资源需求和时间表进行定量评估，评估时会系统地考虑到的不确定性和未知性因素。
Evaluation: The systematic and objective assessment of a solution to determine its status and efficacy in meeting objectives over time, and to identify ways to improve the solution to better meet objectives. See also indicator; metric, monitoring.
Event (business analysis): An occurrence or incident to which an organizational unit, system, or process must respond.
事件（业务分析）：一个组织化的单元、系统或是流程必须要响应的事件。
Evolutionary prototype: A prototype that is continuously modified and updated in response to feedback from stakeholders.
演进原型：根据利益干系人的反馈不断修改和更新的原型。
Experiment: Elicitation performed in a controlled manner to make a discovery, test a hypothesis, or demonstrate a known fact.
实验：在可控方式下通过启发去发现、假设检验、或是论证已知事实。
External interface: An interaction that is outside the proposed solution. It can be another hardware system, software system, or a human interaction with which the proposed solution will interact.
Facilitation: The art of leading and encouraging people through systematic efforts toward agreed-upon objectives in a manner that enhances involvement, collaboration, productivity, and synergy.
引导：领导和鼓励人们的技术，通过一贯努力朝着一致的目标以便加强参与、合作、生产率和协作。
Feasibility study: An evaluation of proposed alternatives to determine if they are technically, organizationally, and economically possible within the constraints of the enterprise, and whether they will deliver the desired benefits to the enterprise.
Feature: A distinguishing characteristic of a solution that implements a cohesive set of requirements and which delivers value for a set of stakeholders.
特征：解决方案具备的的可识别的特性，它能实现一组紧密相关的需求、并能够为一组利益相关人交付价值。
Fishbone diagram: A diagramming technique used in root cause analysis to identify underlying causes of an observed problem, and the relationships that exist between those causes. Also known as an Ishikawa or cause-andeffect diagram.
Focus group: A group formed to to elicit ideas and attitudes about a specific product, service, or opportunity in an interactive group environment. The participants share their impressions, preferences, and needs, guided by a moderator.
Force field analysis: A graphical method for depicting the forces that support and oppose a change. Involves identifying the forces, depicting them on opposite sides of a line (supporting and opposing forces) and then estimating the strength of each set of forces.
Functional requirement: A capability that a solution must have in terms of the behaviour and information the solution will manage.
功能需求：依据解决方案要支撑的行为和信息而应具有的功能。
G
Gap analysis: A comparison of the current state and desired future state of an enterprise in order to identify differences that need to be addressed.
差距分析：为了识别需要被解决的问题而进行的企业现状与未来期望的比较分析
Goal: See business goal.
目标：看业务目标。
Governance process (change): A process by which appropriate decision makers use relevant information to make decisions regarding a change or solution, including the means for obtaining approvals and priorities.
Guideline (business analysis): An instruction or description on why or how to undertake a task.
指南（业务分析）：为什么或如何承担一项任务的指南或说明。
H
Horizontal prototype: A prototype that is used to explore requirements and designs at one level of a proposed solution, such as the customer-facing view or the interface to another organization.
Initiative: A specific project, program, or action taken to solve some business problem(s) or achieve some specific change objective(s).
举措：用来解决一些业务问题或达到一些特定变更目标所采取的具体的项目、程序或者行动。
Input (business analysis): Information consumed or transformed to produce an output. An input is the information necessary for a task to begin.
输入（业务分析）：输入是一种被消耗或转化的信息，以便用来产生输出。输入是一项任务启动所需的信息。
Inspection: A formal review of a work product by qualified individuals that follows a predefined process, and uses predefined criteria, for defect identification and removal.
Interface: A shared boundary between any two persons and/or systems through which information is communicated.。
接口（界面）：在任何两个人与/或系统之间传递信息的共享边界。
Interoperability: Ability of systems to communicate by exchanging data or services.
互通性：系统通过交换数据或服务进行通信的能力。
Interview: Eliciting information from a person or group of people in an informal or formal setting by asking relevant questions and recording the responses.
访谈：以非正式的或正式的形式，通过询问相关问题并记录回复结果，从一个人或一组人中获得信息。
Ishikawa diagram: See fishbone diagram.
石川图：见鱼骨图。
Iteration (business analysis): A single instance of progressive cycles of analysis, development, testing, or execution.
迭代（业务分析）：分析、研发、测试或实施工作所形成的递进循环的一个实例。
K
Knowledge area (business analysis): An area of expertise that includes several specific business analysis tasks.
知识域(业务分析)：包含许多特定业务分析工作的专业领域。
L
Lessons learned process: A process improvement technique used to learn about and improve on a process or project. A lessons learned session involves a special meeting in which the team explores what worked, what didn’t work, what could be learned from the just-completed iteration, and how to adapt processes and techniques before continuing or starting anew.
Life cycle: A series of changes an item or object undergoes from inception to retirement
生命周期：一个项目或对象在从开始到结束所经历的一系列的变化
M
Matrix: A textual form of modelling used to represent information that can be categorized, cross-referenced, and represented in a table format.
矩阵： 文本形式的建模方式，用来展示可以分类的、交叉引用的信息，然后以表格的形式展示出来。
Metadata: A description of data to help understand how to use that data, either in terms of the structure and specification of the data, or the description of a specific instance of an object.
元数据：从数据的接口与规格方面对数据进行描述，或就对象的特定实例进行描述，以帮助理解如何使用该数据
Methodology: A body of methods, techniques, procedures, working concepts, and rules used to solve a problem
方法论：用以解决问题的方法、技术、步骤、工作理念、和规则的体系。
Metric: A quantifiable level of an indicator measured at a specified point in time.
度量：在特定时间内对指标的可量化水平进行测量
Mission statement: A formal declaration of values and goals that expresses the core purpose of the enterprise.
使命宣言：表达企业核心目的价值观和目标的正式声明
Model: A representation and simplification of reality developed to convey information to a specific audience to support analysis, communication, and understanding.
模型：一种对实际情形的陈述和简化表示，用来将信息传达到特定受众，以便支持分析，沟通和理解。
Monitoring: Collecting data on a continuous basis from a solution in order to determine how well a solution is implemented compared to expected results. See also metric; indicator.
监控：基于某一解决方案持续收集数据，以确定和预期相比解决方案实施的效果；另参见度量、指标
N
Need: A problem or opportunity to be addressed.
需求：需要被解决的问题或机会。
Non-functional requirement: A type of requirement that describes the performance or quality attributes a solution must meet. Non-functional requirements are usually measurable and act as constraints on the design of a solution as a whole.
Observation (business analysis): Studying and analyzing one or more stakeholders in their work environment in order to elicit requirements.
观察(业务分析)：为了捕获需求，在利益相关者的工作场所，研究和分析一个或多个利益相关者。
OLAP: See online analytical processing.
OLAP（练级分析处理英文首字母）：见联机分析处理
Online analytical processing (OLAP): A business intelligence approach that allows users to analyze large amounts of data from different points of view.
联机分析处理（OLAP）：一种商业智能方法，允许用户从不同的视角分析大体量数据
Operational support: A stakeholder who is responsible for the day-to-day management and maintenance of a system or product.
运营支持：负责系统或产品的日常管理和运维的利益相关者。
Operative rule: See behavioural 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.
组织变更管理：参见变更管理（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
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.
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 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 endeavour 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
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
RACI matrix: See responsible, accountable, consulted, and informed matrix.
RACI矩阵：见执行、负责、咨询和知情矩阵。
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.
信息邀请书(RFI)：一个正式的启发方式，以收集有关供应商的能力或与潜在的即将采购相关的任何信息。
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.
报价邀请书(RFQ)：一种从供应商处获取价格和解决方案的采购方法。
Request for tender (RFT): An open invitation to vendors to submit a proposal for goods or services.
投标邀请书（RFT）：请求供应商提交商品或服务的提案的公开邀请。
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 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.
投资回报率(ROI)(业务分析):一个项目或投资的盈利能力的度量。
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.
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.
ROI：见投资回报
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.
根本原因分析：问题的最深层的原因，通常是几种可能的原因之一。
S
Scope: The boundaries of control, change, a solution, or a need.
范围：控制、变更、解决方案或需求的边界。
Scope model: A model that defines the boundaries of a business domain or solution.
范围模型：定义业务域或解决方案的边界的模型。
Secondary actor: An actor external to the system under design that supports the execution of a use case.
次要参与者：设计中系统的外部参与者，该参与者为用例的执行提供支持。
Sequence diagram: A type of diagram that shows objects participating in interactions and the messages exchanged between them.
时序图：一种显示参与交互的对象和它们之间交换的消息的图表类型。
Service (business analysis): The performance of any duties or work for a stakeholder, from the perspective of the stakeholder.
服务（业务分析）： 从干系人的角度来看，为干系人提供的任何义务或工作。
SIPOC: See suppliers, inputs, process, outputs and customers.
SIPOC：见供应商、输入、流程、输出和客户。
SME: See subject matter expert.
SME：见行业专家
Software engineer: See developer.
软件工程师：见开发者。
Solution: A specific way of satisfying one or more needs in a context.
解决方案： 在情境中满足一个或多个需要的特定方式。
Solution component: A sub-part of a solution that can be people, infrastructure, hardware, software, equipment, facilities, and process assets or any combination of these sub-parts.
Solution option: One possible way to satisfy one or more needs in a context.
解决方案选项：在情境中满足一个或多个需要的可能方式。
Solution requirement: A capability or quality of a solution that meets the stakeholder requirements. Solution requirements can be divided into two sub-categories: functional requirements and non-functional requirements or quality of service requirements.
Solution life cycle: The stages through which a solution progresses from inception to retirement.
解决方案生命周期：解决方案从开始到退役的各阶段。
Solution scope: The set of capabilities a solution must deliver in order to meet the
business need.
解决方案范围：解决方案必须提供的一组功能，以满足业务需要。
SOW: See statement of work.
SOW：见工作说明书。
Sponsor: A stakeholder who is responsible for initiating the effort to define a business need and develop a solution that meets that need. They authorize the work to be performed and control the budget and scope for the initiative.
Stakeholder: A group or individual with a relationship to the change, the need, or the solution.
利益相关者：与变更、需求或解决方案相关的一个群组或个人。
Stakeholder analysis: Identifying and analyzing the stakeholders who may be impacted by the change and assess their impact, participation, and needs throughout the business analysis activities.
Stakeholder list: A catalogue of the stakeholders affected by a change, businessneed, or proposed solution, and a description of their attributes and characteristics related to their involvement in the initiative.
Stakeholder proxy (business analyst): The role a business analyst takes when representing the needs of a stakeholder or stakeholder group.
利益相关者代理（业务分析师）：当代表干系人或干系人群体的需求时，业务分析师所承担的角色。
Stakeholder requirement: A description of the needs of a particular stakeholder orclass of stakeholders that must be met in order to achieve the businessrequirements. They may serve as a bridge between business requirementsand the various categories of solution requirements.
State diagram: An analysis model showing the life cycle of a data entity or class.
状态图：显示数据实体或类的生命周期的分析模型。
Stated requirement: A requirement articulated by a stakeholder that has not been analyzed, verified, or validated. Stated requirements frequently reflect the desires of a stakeholder rather than the actual need
Statement of work (SOW): A written description of the services or tasks that are required to be performed.
工作说明书（SOW）：需要执行的服务或任务的书面说明。
Strategy: A description of the chosen approach to apply the capabilities of an enterprise in order to reach a desired set of goals or objectives.
战略：应用企业能力以达成期望目标或目的而选择的方法的描述。
Strengths, weaknesses, opportunities, and threats analysis (SWOT): An analysis model used to understand influencing factors and how they may affect an initiative. Also known as SWOT analysis.
Supplier: A stakeholder outside the boundary of a given organization or organizational unit who provides products or services to the organization and may have contractual or moral rights and obligations that must be considered.
Suppliers, inputs, process, outputs, and customers (SIPOC): A tool used to describe relevant high-level elements of a process. May be used in conjunction with process mapping and ‘in/out of scope’ tools, to provide additional detail.
Survey: Collecting and measuring the opinions or experiences of a group of people through a series of questions.
调查：通过一系列的问题收集和判断一组人的意见或经验.
Swimlane: A horizontal or vertical section of a process diagram that shows which activities are performed by a particular actor or role.
泳道：一个水平或垂直的流程图，用以显示哪些活动由特定参与者或角色行。
SWOT analysis: See strengths, weaknesses, opportunities and threats analysis.
SWOT分析：参见优势，劣势，机会和威胁分析。
System: A set of interdependent components that interact in various ways to produce a set of desired outcomes.
系统：一组相互依存的组件，以不同的方式相互作用，产生一组期望的结果。
T
Task (business analysis): A discrete piece of work that may be performed formally or informally as part of business analysis.
任务（业务分析）：一份独立的工作，可以正式或非正式地作为业务分析的一部分。
Technique: A manner, method, or style for conducting a business analysis task or for shaping its output.
技术：用于进行业务分析任务或塑造其输出的方式、方法或风格。
Temporal event: An event based on time that can trigger the initiation of a process, evaluation of business rules, or some other response.
时间事件：基于时间的事件，可以触发一个流程的启动，业务规则的评估，或其他响应。
Tester: An individual responsible for determining how to verify that the solution meets the requirements defined by the business analyst, and conducting the verification process.
测试人员：负责确定如何验证该解决方案是否符合业务分析师定义的要求，并进行验证过程的个人。
Throw-away prototype: A prototype used to quickly uncover and clarify requirements or designs using simple tools, sometimes just paper and pencil. It is intended to be discarded when the final system has been developed.
Time-box: An agreed-upon period of time in which an activity is conducted or a defined deliverable is intended to be produced.
时间盒: 事先决定的时间段，其中决定要执行的活动，或要输出的交付物。
Traceability: See requirements traceability.
可追溯性: 见需求可追溯性。
Transition requirement: A requirement that describes the capabilities the solution must have and the conditions the solution must meet to facilitate transition from the current state to the future state, but which are not needed once the change is complete. They are differentiated from other requirements types because they are of a temporary nature.
UML®: See unified modelling language. unified modelling language™ A notation specified by the Object Management Group for describing software application structure, behaviour, and architecture. It can also be used for describing business processes and data structures. The most common UML® diagrams used by business analysts are use case diagrams, activity diagrams, state machine diagrams (also known as state diagrams), and class diagrams.
Use case: A description of the observable interaction between an actor (or actors) and a solution that occurs when the actor uses the system to accomplish a specific goal.
Use case diagram: A type of diagram defined by UML® that captures all actors and use cases involved with a system or product.
用例图：UML定义的一种图，用于展示一个系统或产品所包括的所有参与者和用例。
User: See end user.
用户：见最终用户。
User acceptance test (UAT): Assessing whether the delivered solution meets the needs of the stakeholder group that will be using the solution. The assessment is validated against identified acceptance criteria.
User story: A small, concise statement of functionality or quality needed to deliver value to a specific stakeholder.
用户故事： 为特定的干系人提供价值的一个小的、简洁的功能或质量的声明。
V
Validation (business analysis): The process of checking that a deliverable is suitable for its intended use. See also requirements validation.
验证（业务分析）：检查交付物是否符合预期用途的流程。参见需求确认。
Validated requirement: A requirement that has been reviewed and is determined to support the delivery of the expected benefits, and is within the solution scope.
已验证需求：在解决方案范围内的、已经经过评审并且确认能够支持期望效益交付的需求。
Value (business analysis): The worth, importance, or usefulness of something to a stakeholder in a context.
价值（业务分析）：在上下文中某事对干系人的益处、重要性或有用性。
Value stream mapping: A complete, fact-based, time-series representation of the stream of activities required to deliver a product or service.
价值流程图：一个完整的、以事实为基础、时间序列表示的活动流，描述交付产品或服务的必要活动。
Verification (business analysis): The process of determining that a deliverable or artifact meets an acceptable standard of quality. See also requirements verification.
验证（业务分析）：决定交付物或制品符合验收质量标准的流程. 参见需求核实。
Verified requirement: A requirement that has reviewed and determined to be defined correctly, adheres to standards or guidelines, and is at an acceptable level of detail.
已核实需求：已经审查并被判定为定义正确、符合标准或指导原则、并具有可接受详细程度的需求。
Vertical prototype: A prototype that is used to drill down into a proposed solution to uncover requirement and design considerations through multiple layers of a solution that are not easily understood or that are not discernible on the surface. It may include interaction between several solutions components.
Viewpoint: A set of conventions that define how requirements will be represented, how these representaions will be organized, and hwo they will be related.
视点：一组定义需求如何被呈现、呈现如何组织及相互关系如何的约定。
VSM: 参见value stream mapping
VSM: 见价值流程图
W
Walkthrough: A review in which participants step through an artifact or set of artifacts with the intention of validating the requirements or designs, and to ideentify requirements or design errors, inconsistencies, omissions, inaccuracies, or conflicts.
Work breakdown structure (WBS): A deliverable-oriented hierarchical decomposition of the work to be executed to accomplish objectives and create the required deliverables. It organizes and defines the total scope of the projects.
Work product (business analysis): A document or collection of notes or diagrams used by the business analyst during the requirements development process.
工作产品（业务分析）：业务分析师在需求开发流程中使用的笔记或图表的文件或汇总。
Workshop: A facilitated and focused event attended by key stakeholders for the purpose of achieving a defined goal.
