試験CBAP-JPN トピック2 問題298 スレッド
IIBA CBAP-JPNのリアル試験問題集
問題 #: 298
トピック #: 2
問題 #: 298
トピック #: 2
ワンダは彼女の組織のビジネスアナリストであり、現在、要件の指定とモデル化のプロセスに取り組んでいます。このプロセスの要素の1つは、テキスト要件の文書化です。
Wandaは、ソリューションの機能、要件が機能するために存在しなければならない条件、およびテキスト要件の3番目のコンポーネントを説明する必要があります。
Wandaは、ソリューションの機能、要件が機能するために存在しなければならない条件、およびテキスト要件の3番目のコンポーネントを説明する必要があります。
おすすめの解答：A 解答を投票する
Explanation
According to the BABOK Guide, textual requirements are one of the forms of specifying and modeling requirements. Textual requirements are written statements that describe the characteristics of the solution in a clear, concise, and consistent manner. Textual requirements typically consist of three components: the capability of the solution, the condition under which the requirement is applicable, and the constraint that may limit the solution. The capability describes what the solution must or should do, the condition describes the situation or scenario in which the requirement is relevant, and the constraint describes the restriction or limitation that may affect the solution's ability to meet the requirement. For example, a textual requirement for a banking system could be:
The system shall allow customers to withdraw cash from any ATM machine (capability) within the network (condition) up to a maximum of $500 per day (constraint).
References:
[A Guide to the Business Analysis Body of Knowledge (BABOK Guide)], version 3, page 402, section
10.31.2.11
Textual Requirement Artifacts - Blueprint Online Help - HelpDocs, paragraph 1 How to Model Textual Requirements - Formal Mind GmbH, paragraph 2
According to the BABOK Guide, textual requirements are one of the forms of specifying and modeling requirements. Textual requirements are written statements that describe the characteristics of the solution in a clear, concise, and consistent manner. Textual requirements typically consist of three components: the capability of the solution, the condition under which the requirement is applicable, and the constraint that may limit the solution. The capability describes what the solution must or should do, the condition describes the situation or scenario in which the requirement is relevant, and the constraint describes the restriction or limitation that may affect the solution's ability to meet the requirement. For example, a textual requirement for a banking system could be:
The system shall allow customers to withdraw cash from any ATM machine (capability) within the network (condition) up to a maximum of $500 per day (constraint).
References:
[A Guide to the Business Analysis Body of Knowledge (BABOK Guide)], version 3, page 402, section
10.31.2.11
Textual Requirement Artifacts - Blueprint Online Help - HelpDocs, paragraph 1 How to Model Textual Requirements - Formal Mind GmbH, paragraph 2
工藤** 2024-09-11 07:57:47
コメント
他人の解答コメントを賛成するのも、その解答に一票を入れることになります。したがって、すでに同じ意見の投票コメントが存在する場合、新規コメントをする代わりに賛成することもできます。
コメントを通報する
コメント中
今すぐ 新規登録 / ログイン （無料です）。