ソフトウェア開発プロジェクトにおける,コストの見積手法には,積み上げ法,ファンクションポイント法,類推見積法などがある。見積りで使用した手法とその特徴に関する記述a~cの適切な組合せはどれか。 a プロジェクトに必要な個々の作業を洗い出し,その作業ごとの工数を見積もって集計する。 b プロジェクトの初期段階で使用する手法で,過去の事例を活用してコストを見積もる。 c データ入出力や機能に着目して,ソフトウェア規模を見積もり,係数を乗ずるなどしてコストを見積もる。
令和6年度 ITパスポート試験 問49
This question's explanation and your answers so far.
問 49
- ア
正解 The correct answer is “ア”. Match the three estimation methods to the characteristics in descriptions a-c. Description a (“identify each individual task, estimate the effort for each, and total them up”) builds the estimate from the bottom up by breaking work into small tasks, so it is the bottom-up method. Description c (“focus on data inputs/outputs and functions to estimate software size, then estimate cost by multiplying by a coefficient”) quantifies size from the number of functions (function points), so it is Function Point analysis. Description b (“estimate cost in the early stage by leveraging past cases”) infers from similar past projects, so it is analogy-based estimation. Therefore bottom-up method: a, Function Point analysis: c, analogy-based estimation: b, and the combination matching this is “ア”.
Incorrectイ
This assigns b to the bottom-up method and a to Function Point analysis, but b (“leveraging past cases”) is the characteristic of analogy-based estimation and a (“identifying tasks and totaling effort”) is the characteristic of the bottom-up method, so the correspondences are swapped.
Incorrectウ
Although analogy-based estimation: b is correct, this assigns c to the bottom-up method and a to Function Point analysis. Description c (multiplying functions/size by a coefficient) is the characteristic of Function Point analysis, while a (building up from individual tasks) is the characteristic of the bottom-up method, so these two are swapped, making it wrong.
Incorrectエ
Bottom-up method: c (multiplying size by a coefficient = the characteristic of Function Point analysis), Function Point analysis: b (past cases = the characteristic of analogy-based estimation), and analogy-based estimation: a (building up from tasks) — all three correspondences are misaligned, so it is wrong.
- Summary of the definitions of cost estimation methods: the bottom-up method breaks work into tasks and totals the effort (a bottom-up approach); Function Point analysis quantifies software size from data inputs/outputs and functions and multiplies by a coefficient; analogy-based estimation infers from similar past cases and is used in the early stage.
- Each method can be distinguished by what it focuses on when estimating (task units / functional size / past cases).