2025年最新の実際に出ると確認されたCCBA日本語試験問題集と解答でCCBA日本語無料更新
実際問題を使ってCCBA日本語問題集で100%無料CCBA日本語試験問題集
質問 # 183
ヘンリーとフレッドは、新しいソフトウェアの実装に関するビジネス分析業務に協力して取り組んでいます。
ビジネス アナリストのヘンリーは、現在の生産性を測定し、ソリューションが実装された後に再度測定する必要があることをフレッドに伝えます。このベンチマーク アプローチにより、ヘンリーとフレッドは、ソリューションがビジネス ニーズに与える実際の影響を確認できます。この測定にはどのような用語が割り当てられていますか。
- A. Sカーブ
- B. 実装後の要因
- C. 降伏
- D. 主要業績評価指標
正解：D
解説：
The term that is assigned to this measurement is key performance indicators. These are the metrics that are used to evaluate the performance and progress of the organization, the project, or the solution against the predefined goals and objectives12. Key performance indicators help to monitor and communicate the value and benefits of the solution, and to identify areas for improvement. Henry and Fred are using key performance indicators to compare the productivity before and after the implementation of the new software, and to see the real effect of the solution on the business need. The other options are not terms that are assigned to this measurement, but rather concepts or techniques that are related to the business analysis work, such as post implementation factor (A), which is a factor that affects the success of the solution after it has been deployed3, yield (B), which is a measure of the efficiency or effectiveness of a process or a solution4, or S-Curve (D), which is a graphical representation of the cumulative progress or performance of a project or a solution over time5. References: Business Analysis Expert Certification, CCBA® | IIBA®, Certification of Capability in Business Analysis™ (CCBA®), Business Analysis Certification Competencies, CCBA® | IIBA®, The Ultimate Guide to Business Capability Analysis, CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition
質問 # 184
ビジネス アナリスト (BA) が、プロジェクトで開発された要件の正式なウォークスルーを実施しました。利害関係者は、要件の解釈が異なっていたため、懸念を表明しました。共通の理解を確実にするためには、どのような活動が役立つでしょうか。
- A. 正しい用語が使用されていることを確認する
- B. 要件の一貫した参照を確保する
- C. 主要業績評価指標への準拠を確保する
- D. 引き出し全体を通して適切なテンプレートが使用されていることを確認する
正解：A
解説：
Correct terminology is essential for ensuring a common understanding of the requirements among stakeholders. It helps to avoid ambiguity, confusion, and misinterpretation. Appropriate templates, consistent referencing, and key performance indicators are also useful for eliciting and managing requirements, but they are not sufficient to ensure clarity and comprehension. References: BABOK Guide v3, page 50; CCBA Mock Test, question 4
質問 # 185
問題追跡とは何ですか?
- A. 不足している要件の特定です。
- B. 要件内の既知の欠陥のドキュメントです。
- C. 解決すべき問題を特定し、管理することです。
- D. 解決しなければならない要件に欠陥があるという前提です。
正解：C
解説：
According to the web search results12, problem tracking is a process of identifying and managing the causes of incidents on an IT service, and it is a core component of ITSM frameworks. Problem tracking is not the same as issue tracking, which is a way of recording and tracking the status of customer cases, tickets, or concerns3. Problem tracking is also not the same as bug tracking, which is the process of logging and monitoring bugs or errors during software testing4.
質問 # 186
要件を検証するタスクは、要件が顧客による正式なレビューと検証の準備ができていることを確認するために使用されますが、その他の目的は何ですか?
- A. プロジェクトの認可の承認を得るため
- B. ソリューションに基づいて望ましい将来の状態の仕様を定義するため
- C. コストとスケジュールの承認を得るため
- D. 追加作業を実行するための情報を定義する
正解：D
解説：
The task of verifying requirements is used to ensure that the requirements are ready for formal review and validation by the customers and for defining the information to allow additional work to be performed. This means that the requirements are checked for quality attributes such as clarity, completeness, consistency, testability, and traceability. The verification process also helps to identify any gaps, issues, or dependencies that need to be resolved or addressed before proceeding to the next phase of the business analysis work.
References: The information is aligned with the competencies and knowledge areas defined in the Business Analysis Body of Knowledge® (BABOK® Guide) and the Certification of Capability in Business Analysis™ (CCBA®) as provided by the International Institute of Business Analysis (IIBA®). For detailed references, please consult the CCBA® guide1 and the BABOK® Guide2 available through the IIBA® website and bookstore3. You can also find some useful resources and sample questions from other sources45.
質問 # 187
ビジネス アナリスト (BA) は、製品提供を改善するプロジェクトに取り組んでいます。問題は、提供フリーサイクルの後半段階で発生し、抽出フェーズからのビジネス分析情報の伝達が不十分なために発生します。その結果、BA は、テスト チームとトレーニング チームが今後 RACI マトリックスの利害関係者として識別されるようにしました。トレーニング チームとテスト チームは、どの RAG 指定に追加する必要がありますか?
- A. 通知済み
- B. 相談した
- C. 責任を負う
- D. 責任者
正解：B
解説：
Consulted is a RACI designation that indicates the stakeholders who need to be consulted before a decision or action is taken1. Consulted can help the BA to improve the communication of the business analysis information from the elicitation phase by involving the testing and training teams in the review and validation of the requirements and designs. By consulting the testing and training teams, the BA can ensure that the requirements and designs are feasible, testable, and aligned with the business needs and objectives2. The other options are not the best RACI designations for the training and testing teams, as they may not reflect their roles and responsibilities in the project. Responsible is a RACI designation that indicates the stakeholders who are assigned to do the work or complete the task3. Accountable is a RACI designation that indicates the stakeholders who have the authority and accountability for the work or task, and who approve the final outcome4. Informed is a RACI designation that indicates the stakeholders who need to be kept informed of the progress or results of the work or task. References:
1: RACI Matrix: Definition, Benefits and Examples
2: How to Consult Stakeholders Effectively
3: RACI Matrix: Definition, Benefits and Examples
4: RACI Matrix: Definition, Benefits and Examples
5: RACI Matrix: Definition, Benefits and Examples
質問 # 188
ビジネス アナリストとして、要件間の関係を理解することが重要です。次のすべては、要件間の有効な関係タイプですが、どれが例外ですか?
- A. サブセット
- B. リンク
- C. カバー
- D. 必要性
正解：B
解説：
Linked is not a valid relationship type among requirements. Requirements can have different types of relationships, such as derivation, satisfaction, verification, refinement, traceability, dependency, conflict, or overlap1. These relationships can help to analyze the impact, consistency, completeness, and quality of the requirements2. However, linked is not a specific or meaningful term to describe how requirements are related.
The other options are valid relationship types among requirements:
Necessity is a relationship type that indicates that a requirement is essential for achieving a goal or satisfying a need3.
Cover is a relationship type that indicates that a requirement addresses or fulfills a stakeholder need or expectation4.
Subset is a relationship type that indicates that a requirement is a more detailed or specific version of another requirement5.
References:
Relationship Analysis in Requirements Engineering, section "Relationship Types" A Guide to the Business Analysis Body of Knowledge® (BABOK® Guide), version 3, chapter 6, section 6.1.4.1 Necessity, section "Description of Change" Cover, section "Description of Change" Subset, section "Description of Change"
質問 # 189
ビジネス アナリスト (BA) がプロジェクトの制約を定義しています。次のどれが有効な制約ですか?
- A. 「ソリューションは 6 か月以内に実装する必要があります。」
- B. 「ソリューションは職場の安全を促進する必要があります。」
- C. 「ソリューションにより売上が 20% 増加する必要があります。」
- D. 「ソリューションによりサポートコールが 20% 削減される必要があります。」
正解：A
解説：
A constraint is a restriction or limitation that affects the performance or value of a solution1. Constraints can be related to time, cost, quality, scope, resources, or technology2. In this question, option A is a valid constraint because it specifies a time limit for the solution implementation. Options B, C, and D are not constraints, but rather objectives or goals that the solution should achieve or support.
References: The answer is based on the BABOK® Guide, which is a key resource for the CCBA® certification. Specifically, it relates to the Strategy Analysis knowledge area, where defining solution scope and business case is a key task for the BA13. It also relates to the Requirements Analysis and Design Definition knowledge area, where the BA should define design options and recommend a solution14.
1: Certification of Capability in Business Analysis™ (CCBA®) Handbook 2: Business Analysis Expert Certification, CCBA® | IIBA® 3: Certification of Capability in Business Analysis™ (CCBA®) 4: The Ultimate Guide to Business Capability Analysis
質問 # 190
要件の優先順位付けに関して、MoSCoW とは何を意味しますか?
- A. お金、スケジュール、コントロール、待機
- B. しなければならない、すべきである、できる、するだろう
- C. しなければならない、すべきである、できる、しない
- D. してはいけない、すべきではない、できない、しない
正解：C
解説：
MoSCoW is a prioritization technique used in business analysis and project management to categorize requirements into four levels of priority: Must have, Should have, Could have, and Won't have. This method helps teams focus on the most critical requirements that need to be satisfied for a project to be successful, while also identifying which requirements can be deferred or excluded if necessary.
Must have: These are non-negotiable requirements that are essential for the project's success. If these are not met, the project is considered a failure.
Should have: These are important but not critical requirements. They are high-priority items that can be scheduled for a future release without impacting the current one.
Could have: These are desirable requirements that do not affect the overall success of the project. They can be included if time and resources permit.
Won't have: These are the lowest priority requirements or those that are not necessary for the current delivery cycle. They are recognized but not planned for the current project timeline.
References: The MoSCoW method is detailed in the Dynamic System Development Method (DSDM) handbook and is widely used across various industries for effective project management
質問 # 191
あなたは、要件が少ない小規模プロジェクトのビジネス アナリストです。経営陣は、このプロジェクトの要件をトレースする方法をあなたに作成してほしいと考えています。この場合、どのタイプのマトリックスが最適ですか?
- A. 役割と責任のマトリックス
- B. RACI マトリックス
- C. 要件トレースマトリックス
- D. カバレッジマトリックス
正解：C
解説：
According to the BABOK® Guide, a requirements trace matrix is a table that links requirements to their origin and traces them throughout the project life cycle. A requirements trace matrix is useful for tracking the status, priority, and satisfaction of requirements, as well as identifying dependencies, gaps, and overlaps. A requirements trace matrix is suitable for smaller projects where there are few requirements, as it can provide a simple and effective way to trace the few requirements for the project1. References: 1: BABOK® Guide, version 3, section 10.32, page 344.
質問 # 192
ビジネス アナリストは、会社の定義済みテンプレートを使用して、自分の取り組みの要件パッケージを準備する必要があります。要件をパッケージ化するためのこの標準化されたテンプレートには、どのような用語を割り当てることができますか。
- A. 企業環境要因
- B. 必須
- C. 派生適応
- D. 組織プロセス資産
正解：D
解説：
The standardized template for packaging the requirements is an example of an organizational process asset.
Organizational process assets are the plans, processes, policies, procedures, and knowledge bases that are specific to and used by the performing organization. They help to guide and standardize the business analysis activities and deliverables. The other options are not terms that can be assigned to the standardized template for packaging the requirements. Derivative adaption is not a term used in business analysis, but a concept in evolutionary biology. Essential is an adjective that means absolutely necessary or extremely important.
Enterprise environmental factors are the conditions, factors, and influences that affect the organization and its projects, such as culture, structure, market, regulations, etc. References:
4. Prepare Requirements Package task Flashcards | Chegg.com
What term can be assigned to this standardized template for packaging ...
質問 # 193
新しい契約では、計画された段階のレビューと承認された承認を伴う徹底したレベルのドキュメントの作成と維持が必要です。この契約に適したアプローチはどれですか?
- A. 滝
- B. アジャイル
- C. スクラム
- D. 反復
正解：A
解説：
According to the BABOK® Guide, a waterfall approach is a sequential project life cycle that consists of distinct phases, such as initiation, planning, analysis, design, construction, testing, implementation, and maintenance. Each phase has a defined set of activities, deliverables, and exit criteria that must be completed before moving to the next phase. A waterfall approach is suitable for projects that have a clear and stable scope, well-defined requirements, and minimal changes or uncertainty. In this scenario, a new contract requires a thorough level of documentation to be developed and maintained with planned phases of reviews and authorized sign offs. This implies that the project has a high degree of formality, control, and documentation, which fits the characteristics of a waterfall approach. References:
[BABOK® Guide], section 2.5: Plan Business Analysis Approach
CCBA Exam Questions & Answers with Explanations, question 418
質問 # 194
特定された要件によって利害関係者のニーズが満たされていることに利害関係者が同意するかどうかを判断するためのレビュー会議で構成される手法はどれですか?
- A. リスク分析
- B. プロトタイピング
- C. 構造化されたウォークスルー
- D. ステークホルダー管理
正解：C
解説：
A structured walkthrough is a technique that consists of review meetings to determine if the stakeholders agree that their needs are being met with the identified requirements. A structured walkthrough is a formal and systematic process in which the business analyst presents the requirements to the stakeholders and solicits their feedback, comments, and approval. A structured walkthrough helps to ensure the quality, validity, and completeness of the requirements and to resolve any issues, conflicts, or ambiguities. A structured walkthrough can be done at various stages of the project, such as after the elicitation, analysis, documentation, or validation of the requirements. References:
Structured Walkthroughs - Business Analyst Learnings
Review Meetings: Types, Best Practices, and Template - Fellow.app
[Which technique consists of review meetings to determine if the ...]
質問 # 195
組織の能力ギャップを評価するには、どれを除く次のすべての入力が必要ですか?
- A. ビジネスニーズ
- B. エンタープライズアーキテクチャ
- C. ソリューションスコープ
- D. ソリューションのパフォーマンス評価
正解：D
解説：
A solution performance assessment is an output of the assess capability gaps process, not an input. A solution performance assessment evaluates how well the current or proposed solutions meet the business needs and objectives. It identifies the strengths and weaknesses of the solutions and provides recommendations for improvement1 The inputs of the assess capability gaps process are:
Enterprise architecture: This is a description of the structure, components, and relationships of the organization and its environment. It provides a holistic view of the current and desired states of the organization and its capabilities2 Solution scope: This is a statement that defines the boundaries and deliverables of the solution. It specifies what the solution will and will not include, and what problems or opportunities it will address3 Business need: This is a statement that articulates the problem or opportunity that the organization faces.
It defines the gap between the current and desired states of the organization and its capabilities.
References: Business Analysis Body of Knowledge (BABOK® Guide), Section 6.1: Assess Capability Gaps,
6.1.3: Outputs; Business Analysis Body of Knowledge (BABOK® Guide), Section 6.1: Assess Capability Gaps, 6.1.2.1: Enterprise Architecture; Business Analysis Body of Knowledge (BABOK® Guide), Section
6.1: Assess Capability Gaps, 6.1.2.2: Solution Scope; [Business Analysis Body of Knowledge (BABOK® Guide)], Section 6.1: Assess Capability Gaps, 6.1.2.3: Business Need.
質問 # 196
あなたは組織のビジネス アナリストであり、要件パッケージを作成しています。このドキュメントでは、利害関係者の要件をどのレベルまで文書化する必要がありますか?
- A. すべての要件は、技術、ビジネス、機能、非機能の属性で明確に定義する必要があります。
- B. すべての要件は、組織のプロセス資産が要求する範囲で定義する必要があります。
- C. すべての要件は、チームによる理解を確実にするために必要な範囲でのみ定義する必要があります。
- D. すべての要件は、WBS の作業パッケージ レベルまで詳細に定義する必要があります。
正解：C
解説：
According to the BABOK® Guide, a requirement is a usable representation of a need. The level of detail and formality of the requirement depends on the context and the audience of the requirement. The goal is to communicate the requirement effectively, not to adhere to a rigid format or level of detail1.
Option A is incorrect because not all requirements need to have technical, business, functional, and non-functional attributes. Some requirements may be more relevant to one or more of these aspects than others.
Option C is incorrect because the organizational process assets are not the only factor that determines the level of detail of the requirements. The stakeholder needs, preferences, and expectations also play a role.
Option D is incorrect because the work package level of WBS is not necessarily the same as the requirement level. The WBS is a project management tool that decomposes the project scope into manageable components, while the requirements describe the needs and expectations of the stakeholders. The WBS and the requirements may not have a one-to-one correspondence.
質問 # 197
ビジネス アナリスト (BA) が次の要件を導き出しました。「ソリューションでは、ポータルの応答時間が 2 秒未満であることを保証する必要があります。」この要件はどの要件分類スキーマに属しますか?
- A. 移行要件
- B. 機能要件
- C. 利害関係者の要件
- D. 非機能要件
正解：D
解説：
The requirement classification schema that this requirement belongs to is nonfunctional requirements.
Nonfunctional requirements are statements of conditions or restrictions on a solution or its components that affect its quality, performance, usability, reliability, security, etc. Nonfunctional requirements specify how well a solution should perform or behave.
The other options are incorrect because:
Option B is incorrect because stakeholder requirements are not a requirement classification schema, but a requirement type. Stakeholder requirements are statements of needs, expectations, preferences, or problems of stakeholders or an organization.
Option C is incorrect because transitional requirements are not a requirement classification schema, but a requirement type. Transitional requirements are statements of capabilities or conditions that enable a solution to transition from its current state to its desired future state.
Option D is incorrect because functional requirements are not a requirement classification schema, but a requirement type. Functional requirements are statements of features, functions, or behaviors of a solution or its components that enable it to provide value to stakeholders.
References:
BABOK Guide v3, section 6.1: Specify and Model Requirements
CCBA Exam Questions, question 35
質問 # 198
要件の品質を高くするには、どれを除いて、次の特性がすべて要件に存在する必要がありますか?
- A. 凝集性
- B. 制約あり
- C. 一貫性
- D. 完了
正解：B
解説：
According to the BABOK® Guide, high quality requirements should have the following characteristics:
atomic, complete, consistent, concise, feasible, unambiguous, testable, prioritized, and traceable. Cohesive, consistent, and complete are among these characteristics, while constrained is not. Constrained means that the requirements are limited by some factors, such as budget, time, or resources, which may affect their quality negatively. References: BABOK® Guide, section 4.2.5, page 98; CCBA Handbook, section 4.4, page 6.
質問 # 199
ビジネス アナリスト (BA) は、プロジェクトのガバナンス プロセスを確立するための一連のタスクに取り組んでいます。BA は、変更を提案する権限と責任を持つ人物、変更の議論に関与する人物、変更を文書化して伝達する方法などを特定しようとしています。BA がタスクを完了するのに役立つ入力は次のどれですか。
- A. ガバナンスアプローチとビジネス分析アプローチ
- B. ビジネス分析アプローチとステークホルダーエンゲージメントアプローチ
- C. ガバナンスアプローチとステークホルダーエンゲージメントアプローチ
- D. ステークホルダーエンゲージメントアプローチと情報管理アプローチ
正解：B
解説：
The scenario describes a task that involves establishing a governance process for the project, which is a part of the business analysis planning and monitoring knowledge area. According to the CCBA® Handbook and the IIBA® website, the inputs for this task are the business analysis approach and the stakeholder engagement approach12. The business analysis approach defines the activities, tasks, techniques, deliverables, and roles and responsibilities for the business analysis work. The stakeholder engagement approach defines the strategies and plans for engaging and communicating with stakeholders throughout the project. These inputs provide the BA with the necessary information and guidance to identify and document the governance process for the project.
References: The answer and explanation are consistent with the CCBA® Handbook and the IIBA® website, which provide the details and best practices for the business analysis planning and monitoring knowledge area, including the task of plan business analysis governance12. The CCBA® resources also describe the inputs and outputs for each task in the business analysis process12.
質問 # 200
ビジネス アナリストが要件トレースを実行する場合、要件の系統を遡ってトレースしたり、他の要件との関係を辿って要件を前方にトレースしたりする必要があるかもしれません。要件トレーサビリティでは、後方トレース アクティビティは何と呼ばれますか?
- A. 後方パス
- B. 割り当て
- C. 導出
- D. 系譜の追跡
正解：C
解説：
Derivation is the backwards tracing activity in requirements traceability. It involves identifying the source or origin of a requirement, such as a business need, a stakeholder request, a regulation, or another requirement. Derivation helps to ensure that the requirements are aligned with the business objectives, to validate the rationale and assumptions behind the requirements, and to assess the impact of changes or issues on the requirements12.
The other options are not correct because:
Option A is incorrect. Allocation is a forward tracing activity in requirements traceability. It involves assigning or distributing a requirement to one or more components of a solution, such as a system, a module, a function, or a process. Allocation helps to ensure that the requirements are covered by the solution, to verify the feasibility and consistency of the requirements, and to measure the progress and performance of the solution34.
Option B is incorrect. Lineage tracking is not a specific term used in requirements traceability. It may refer to the general process of tracing the history and evolution of a requirement from its origin to its current state, or vice versa. However, it is not a standard or widely accepted term in the business analysis domain5.
Option D is incorrect. Backwards pass is a term used in project management, not in requirements traceability. It is a technique for calculating the late start and late finish dates of the project activities by working backwards from the project end date. It is part of the critical path method for scheduling the project activities6.
References:
Requirements Traceability, section "Description of Change"
What is Traceability? - Jama Software, section "Backward to Requirements" Allocation, section "Description of Change" Requirements Allocation, section "What is Requirements Allocation?" Forward and backward traceability: Requirements and challenges (Keynote), section "Abstract" Backward Pass, section "Description of Change"
質問 # 201
新しいソリューションをビジネス環境と技術環境に統合するために必要な作業範囲の描写として最もよく説明できるソリューション範囲作成手法はどれですか?
- A. ユーザーストーリー
- B. 機能分解
- C. インターフェース分析
- D. スコープモデリング
正解：C
解説：
Interface analysis is a technique that identifies and describes the interactions and dependencies between the solution and its external components, such as other systems, people, or organizations. It helps to define the scope of work required to integrate the new solution into the business and technical environments, as well as to identify potential risks, issues, and requirements12. Scope modeling, user stories, and functional decomposition are other techniques that can be used to create the solution scope, but they do not focus on the integration aspects as much as interface analysis does3. References:
1: BABOK® Guide, Version 3.0, p. 128
2: Interface Analysis | IIBA® BABOK Extended
3: CCBA® and CBAP® Certifications Study Guide, Chapter 5
質問 # 202
要件管理計画の要件属性を文書化しています。要件を作成した人物を識別するには、どの属性を使用しますか?
- A. 要件の作成者
- B. 所有権
- C. 要件スポンサー
- D. 絶対参照
正解：A、B
解説：
A: Absolute reference: This is an incorrect answer, as it is not a requirement attribute, but a term used in spreadsheet software to refer to a cell address that does not change when copied or moved to another cell.
B: Ownership: This is a correct answer, as it is a requirement attribute that indicates who is responsible for the creation, approval, and maintenance of the requirement. Ownership helps to ensure the accountability, traceability, and quality of the requirement.
C: Requirements sponsor: This is an incorrect answer, as it is not a requirement attribute, but a role that provides the funding and support for the project or the solution. The requirements sponsor may or may not be the same person as the owner of the requirement.
D: Author of the requirement: This is a correct answer, as it is a requirement attribute that identifies the person who wrote the requirement. Authorship helps to provide the source and context of the requirement.
質問 # 203
ケリーは組織のビジネス アナリストであり、ビジネス分析活動に携わる人々の役割と責任を特定しています。彼女のマネージャーは、このタスクを達成するために RACI マトリックスを作成するようにケリーに依頼しました。RACI マトリックスとは何ですか?
- A. RACI マトリックスは、リスク、アクション、コスト、情報の凡例を使用する役割と責任のチャートです。
- B. RACI マトリックスは、責任者、アクション、制御、および通知の凡例を使用する役割と責任のチャートです。
- C. RACI マトリックスは、役割、アクション、制御、および情報の凡例を使用する役割と責任のチャートです。
- D. RACI マトリックスは、責任者、説明責任者、相談先、通知先という凡例を使用する役割と責任のチャートです。
正解：D
解説：
The RACI matrix is a technique that helps to define and communicate the roles and responsibilities of the stakeholders involved in a process or a project. It uses the legend of Responsible, Accountable, Consulted, and Informed to indicate the level of participation and authority of each stakeholder for each task or deliverable.
The RACI matrix helps to clarify expectations, avoid conflicts, and ensure accountability and collaboration among the stakeholders.
References: The information is verified as per the BABOK® Guide and related IIBA resources, which outline the standards and practices for business analysis. The BABOK® Guide is a key resource for understanding business analysis techniques and their applications across different contexts123. You can also find some useful resources and sample questions from other sources.
質問 # 204
ヘンリーは組織内のビジネス アナリストであり、実装する最適なビジネス分析の職務を決定するために専門家に協力を求めています。ヘンリーがビジネス分析の職務を定義するために専門家に協力を求めるのはなぜでしょうか。
- A. ヘンリーは新しいビジネスアナリストです。
- B. ヘンリーは時間を節約するために専門家を利用しています。
- C. Henry は専門家の判断に基づいて最適なビジネス分析アプローチを決定できます。
- D. ヘンリーは、ビジネス分析アプローチについて協議する際には常に専門家の判断を使用する必要があります。
正解：C
解説：
Expert judgment is a technique that involves consulting with individuals or groups who have specialized knowledge, skills, or experience in a relevant domain or discipline. Henry can use expert judgment to determine the optimal business analysis approach, which is the set of processes, activities, tasks, deliverables, roles, responsibilities, and governance that will be used to conduct the business analysis work. By asking an expert to help him define the business analysis duties, Henry can benefit from the expert's insights, opinions, recommendations, and best practices, and apply them to his specific project context and objectives. Expert judgment can help Henry to select the most suitable and effective business analysis approach for his project, and to ensure the quality and alignment of the business analysis outputs and outcomes12 Option A is incorrect because Henry being a new business analyst is not the reason why he would ask an expert to help him define the business analysis duties. While being a new business analyst may imply that Henry has less experience or confidence in defining the business analysis duties, it does not necessarily mean that he needs to consult with an expert. Henry may have other sources of information or guidance, such as the Business Analysis Body of Knowledge (BABOK® Guide), the organizational standards and policies, or the project manager and sponsor. Moreover, even if Henry is an experienced business analyst, he may still benefit from using expert judgment, as each project may have different challenges, complexities, and uncertainties that require expert input3 Option B is incorrect because Henry should not always use expert judgment to confer on the business analysis approach, but only when it is appropriate and feasible. Expert judgment is not the only technique that Henry can use to define the business analysis approach, but one of the many techniques that are available and applicable. Henry should consider the advantages and disadvantages of using expert judgment, such as the availability, reliability, and credibility of the experts, the cost and time of consulting with them, and the potential bias or conflict of interest that may arise from their involvement. Henry should also consider the other factors that may influence the business analysis approach, such as the stakeholder needs and expectations, the project objectives and constraints, and the organizational culture and environment4 Option C is incorrect because Henry using an expert to help save time is not the reason why he would ask an expert to help him define the business analysis duties. While using an expert may help Henry to save time by providing him with quick and ready answers, it may also introduce some risks or challenges, such as the accuracy, validity, and applicability of the expert's advice, the dependency and accountability of Henry on the expert's input, and the communication and coordination issues that may occur between Henry and the expert. Henry should not use expert judgment as a shortcut or a substitute for his own analysis and judgment, but as a supplement or a support for his decision making5 References:
Business Analysis Body of Knowledge (BABOK® Guide), Version 3, Chapter 2: Business Analysis Planning and Monitoring, Section 2.1: Plan Business Analysis Approach, p. 31-32.
Certification of Capability in Business Analysis (CCBA®) - Simplilearn, Module 5: Planning and Monitoring, Lesson 5.1: Plan Business Analysis Approach, p. 6-7.
Business Analysis Body of Knowledge (BABOK® Guide), Version 3, Chapter 1: Introduction, Section
1.2: What is Business Analysis?, p. 5-6.
Business Analysis Body of Knowledge (BABOK® Guide), Version 3, Chapter 10: Techniques, Section
10.14: Expert Judgment, p. 347-348.
Certification of Capability in Business Analysis (CCBA®) - Simplilearn, Module 5: Planning and Monitoring, Lesson 5.2: Plan Stakeholder Engagement, p. 6-7.
質問 # 205
ビジネス アナリスト (BA) が要件パッケージを準備し、関係者に提示する準備が整いました。パッケージを提示する目的は何ですか?
- A. 情報の共通理解を確保するため
- B. プロジェクトの完了を文書化する
- C. プロジェクトの進捗状況を確認する
- D. 分析アプローチを定義する
正解：A
解説：
The scenario describes a task that involves presenting a requirements package to the stakeholders. The requirements package is a document that contains the requirements and related information for the project and the solution. The purpose of presenting the package is to ensure a shared understanding of the information among the stakeholders, which is essential for achieving stakeholder alignment, agreement, and commitment.
Presenting the package also provides an opportunity for the BA to elicit feedback, validate requirements, and resolve any issues or conflicts.
References: The answer and explanation are consistent with the CCBA® Handbook and the IIBA® website, which provide the details and best practices for the communicate business analysis information task as part of the solution evaluation knowledge area12. The CCBA® resources also describe the types and formats of documents that can be used to communicate business analysis information, such as requirements packages1
質問 # 206
......
合格させるCCBA日本語試験問題は更新された522問あります：https://www.passtest.jp/IIBA/CCBA-JPN-shiken.html