広告代理店の A 社では，申請者が経理部に回付した交通費精算伝票（以下，伝票という）を使って，顧客訪問時に発生した交通費の精算業務を行っている。 〔現在の交通費精算業務の流れ〕 （1）申請者は，伝票に申請者名，社員番号，経費科目，顧客番号，利用日，利用区間，金額及び合計金額を記入する。押印後，事務担当者に回付する。 （2）事務担当者は，申請内容を精査し，誤りがなければ伝票を承認者に回付する。誤りがあれば，伝票を申請者に差し戻す。 （3）承認者は，承認又は否認の決裁を行う。内容が適切であった場合には承認して，事務担当者に回付する。内容が適切でなければ否認して，申請者に差し戻す。 （4）（2）又は（3）で差し戻された場合，申請者は伝票を修正し，再度事務担当者に回付する。 （5）事務担当者は，承認者から回付された当日分の承認済み伝票を取りまとめ，伝票番号を採番し，経理部に回付する。 （6）経理担当者は，事務担当者から回付されてきた承認済み伝票の支払処理を行う。 交通費精算を効率よく行うために，データベースを活用して，次に示す機能要件の交通費精算システム（以下，精算システムという）を構築することにした。 〔精算システムの機能要件の一部〕 （1）社員番号でログオンする。社員番号によって，社員表から申請者名を抽出し，申請画面の共通項目として設定する。 （2）申請画面の明細として，顧客番号，利用日，利用区間と金額を入力する。1回の申請で複数の顧客訪問に対する明細が入力できる。また，合計金額の算出，経費科目の設定及び伝票番号の自動採番を行う。ここで経費科目として，交通費を自動設定する。 （3）申請後，事務担当者が精査を行い，自動的に承認者に通知が行く。承認者は決裁画面で承認か否認かを選択する。 （4）支払画面で承認済み申請を社員ごとに集計し，支払金額を算出する。 精算システムを導入しても, 事務担当者が精査する現在の申請内容のうち, 精査を廃止できないものはどれか。
平成26年度 秋期 ITパスポート試験 問98
This question's explanation and your answers so far.
問 98
※ Our check while writing this explanation could not fully confirm the published answer; scoring follows IPA's official key.
Incorrectア
Scrutiny of the expense category can be eliminated. Functional requirement (2) clearly states that the system performs “setting of the expense category” and “automatically sets travel expenses as the expense category”, so the applicant does not choose or write the category. The system always fills in the same value, so no error can slip in and the clerk no longer needs to check it.
Incorrectイ
Scrutiny of the total amount can also be eliminated. At present the applicant adds up the detail amounts and writes the total, so arithmetic mistakes can happen, but functional requirement (2) specifies that the system performs “calculation of the total amount”. It is totaled mechanically from the entered details, so re-checking the addition is no longer necessary.
Incorrectウ
Scrutiny of the applicant's name and employee number can also be eliminated. Functional requirement (1) says “log on with the employee number; extract the applicant's name from the employee table by the employee number and set it as a common item on the application screen”, so the employee number used at logon and the matching name in the employee table are entered automatically. Errors such as miswriting by hand or writing someone else's number cannot occur structurally, so cross-checking is unnecessary.
- エ
正解 The correct answer is エ (the amount for the usage section in the detail line). This question is solved by comparing the premises of group question D — the items the applicant writes on the slip in [the current flow of the travel-expense settlement work] (applicant's name, employee number, expense category, customer number, date of use, usage section, amount, and total amount) — with [part of the functional requirements of the settlement system]. The functional requirements state that when you log on with your employee number, the system extracts the applicant's name from the employee table and sets it on the application screen, and that when the details are entered, the system calculates the total amount, sets the expense category (travel expenses), and automatically assigns the slip number. In other words, the system generates these items mechanically, so there is no room for a person to write them incorrectly, and the clerk's visual scrutiny is no longer needed. In contrast, the usage section in the detail line and the amount for that section are items the applicant types in by hand, exactly as functional requirement (2) says: “enter the customer number, date of use, usage section, and amount as the details on the application screen”. And nowhere in the functional requirements is there a mechanism that cross-checks the entered section against fare data. Therefore the system cannot judge whether this amount is right as the fare for this section, so the clerk's scrutiny cannot be eliminated. Hence エ is correct.
- What systematizing a business process (BPR, introducing a workflow) can cut is the checking work for items the system generates or calculates automatically. Checking whether content that a person judges and types in by hand is correct will remain unless you build a function that verifies it. To see which tasks really decrease, match the functional requirements one to one against the tasks of the current operation.
- A basic rule for reading a requirements definition is to assume the system does not perform any processing that is not written in the functional requirements. Here there is no function for checking against fare data, so whether the amount for the usage section is correct has to be judged by a person.