This question's explanation and your answers so far.
問89
頻出度★★☆
日用雑貨の製造を行う W 社では，業務拡大に向けて販売管理のためのシステム（以下，販売管理システムという）構築を予定している。システム構築のメンバである G 君は，上司の指導の下に RFP を作成して，X 社から提案を受けた。RFP の概要と X 社からの提案は，次のとおりである。
なお，W 社にとって重要な顧客情報の扱いについては，契約時に必要な処置を講じることにした。
〔RFP の概要〕
システムの目的：製造した商品に関して，顧客に対する受注から出荷までの管理を行う。
システムの要件：商品数は，当初は 2,000 品目で，最大 5,000 品目を管理する。顧客数は，当初は 500 社で，最大 2,000 社を管理する。1 日の受注件数は，最大 200 件とする。弊社の規模と業務に合った適切なソフトウェアパッケージの利用を前提とする。
納期：発注から 6 か月以内とする。
〔X 社からの提案〕
導入費用：700 万円
前提条件：Y 社の販売管理ソフトウェアパッケージと Z 社のデータベースソフトを利用し，不足する機能の開発を行います。サーバは CPU が一つのものを 2 台導入します。1 台は本番機とし，もう 1 台は，本番機に障害が発生した場合に稼働させるコールドスタンバイ機とします。
契約条件：要件定義からシステムテストまでの一括請負契約とします。弊社の開発物に関する瑕疵担保期間は，検収後 6 か月とします。
導入期間：4 か月
保守：保守契約を結ぶことによって，導入したシステムに関する問合せ，障害の切分けの対応を行います。
W 社が作成した RFP の概要に示した内容には不足がある。RFP の内容として追記すべき事項はどれか。
出典 平成23年度 特別試験 ITパスポート試験 問89
解説
問 89
//
×Incorrectア
“Company W's performance last year” does not serve as material for a vendor to decide how to build the system. What an RFP should contain is information that directly affects the proposal: the purpose of the system to be built, functional requirements, non-functional requirements (performance, availability, security, and so on), the delivery deadline, the budget, and the contract conditions. Management figures such as past sales do not influence the content of a proposal; rather, they are information that need not be disclosed outside the company, so they cannot be called an item that should be added.
×Incorrectイ
“The number of records of product and customer data handled by the system” is already stated clearly in the “System requirements” part of the [Outline of the RFP]. It says that the number of products is 2,000 items initially and 5,000 items at most, and that the number of customers is 500 companies initially and 2,000 companies at most, so far from being missing, it is an item that is already written. What the question asks for is an item that should be added because it is not written, so content that already appears cannot be the answer.
○ウ
正解The correct answer is ウ, “Requirements concerning the performance of the system.” An RFP (Request For Proposal) is a document in which the ordering side tells vendors what it wants realized and how, so that the proposals from different companies can be compared on the same basis. Looking at Company W's [Outline of the RFP], the purpose, the data volume (up to 5,000 product items, up to 2,000 customer companies), the business volume (at most 200 orders received per day), and the delivery deadline are written, but nowhere does it say how fast that volume should be processed. Such performance requirements would be, for example, “the response time for order entry must be within 3 seconds,” “the nightly closing process must finish within 1 hour,” or “30 concurrent users.” Without them, Company W cannot judge whether the configuration proposed by Company X, namely 2 servers each with a single CPU (a production machine plus a cold-standby machine), will let the business run without trouble, and it cannot compare that proposal with those of other companies. Furthermore, even if it later turns out that the system is too slow to use, there is no basis for asking the vendor to correct it, because it was not written in the RFP. Therefore, the missing item that should be added to the RFP is the requirements concerning performance.
×Incorrectエ
What is to be built is a sales management system covering everything from receiving orders to shipping, not a system covering manufacturing processes. “Information about the machines used to manufacture the products” could be needed for a production management system, but it is outside the scope of the system in this case and does not affect the content of the proposal. In principle an RFP states information related to the scope of the target operations; adding unrelated information does not improve the accuracy of a vendor's proposal.
ここがポイント
An RFP (Request For Proposal) is a document with which the ordering side asks vendors for proposals, and it should state without omission the purpose of the system, the scope of the target operations, functional requirements, non-functional requirements (performance, availability, security, operation and maintenance), the delivery deadline, the budget, the contract conditions, and so on. An item that is omitted will not be reflected in the proposals, and the basis for comparing the proposals of the different companies is lost as well.
Merely writing down the data volume and the business volume (the number of cases) does not complete the requirements. A performance requirement, that is, at what speed and within what response time that volume must be processed, is a typical example of a non-functional requirement, and it is indispensable for evaluating whether the system configuration and the server performance are appropriate.