問45
頻出度★★★
共通フレーム (Software Life Cycle Process) で定義されている内容として, 最も適切なものはどれか。
平成28年度 秋期 ITパスポート試験 問45
マネジメント系システム開発技術 › システム開発技術
This question's explanation and your answers so far.
解説
問 45
- ア
正解 The Common Frame (SLCP) is a shared yardstick that, across the entire life cycle from a software product’s concept and planning through requirements definition, development, operation, maintenance, and disposal, identifies the “work items” that both the acquirer (ordering side) and the supplier (receiving side) can use in common, and defines and standardizes their content. Its purpose is to clarify the scope of development and transactions and the division of roles, which tend to become vague, and thereby to ensure the appropriateness of software development and its transactions. Therefore, choice ア, which states this, is correct.
Incorrectイ
This describes methods for estimating the scale, effort, and cost of software development (such as the function point method or analogy-based estimation); estimation techniques themselves are not what the Common Frame defines. The Common Frame presents a framework of work items and does not specify concrete estimation formulas.
Incorrectウ
The body of knowledge required for project management describes PMBOK. The Common Frame is a framework that standardizes the work items of the entire life cycle; it is not a compilation of a project-management body of knowledge.
Incorrectエ
Information processing terminology established by law, and the quality and evaluation items of software products, are matters handled by standards such as JIS, not the content defined by the Common Frame. The Common Frame is not a legally established glossary or quality-evaluation standard, but a common framework that defines the work items of development and transactions.
ここがポイント
- Common Frame (SLCP) = a shared yardstick that, across the entire life cycle from a software product’s planning through maintenance and disposal, defines and standardizes the work items usable in common by the acquirer and the supplier, in order to ensure the appropriateness of development and transactions.
- Distinguishing similar terms: do not confuse it with estimation methods (scale, effort, cost) / PMBOK (project-management body of knowledge) / standards such as JIS (terminology, quality evaluation).