問37
頻出度★★★
ソフトウェア受入れにおいて実施される事項はどれか。
平成23年度 特別試験 ITパスポート試験 問37
マネジメント系システム開発技術 › システム開発技術
This question's explanation and your answers so far.
解説
問 37
Incorrectア
Interviewing users to hear their requests for new systemization is work carried out in the planning process and the requirements definition process, before development begins. It corresponds to the stage where management issues and problems in current operations are identified, a systemization concept and a systemization plan setting out what kind of system should be built are compiled, and then user requests are organized and documented as business requirements and system requirements. This is still work that decides what should be built, and it belongs to a different stage from acceptance, which checks and takes delivery of software that has already been completed, so it is incorrect.
Incorrectイ
Examining the access rights to assign to each user and designing how access right settings are to be made is work in the system design process. Taking up the security requirements fixed in requirements definition, it turns the permission scheme — who is allowed to view and update which data and functions — into a concrete mechanism; this is what is called security design. During acceptance, acceptance testing may confirm that the rights work as designed, but designing the content of the rights themselves belongs to the developer's design stage, a different point in time, so it is incorrect.
Incorrectウ
Distributing questionnaires to users and surveying the usability and other aspects of the system in operation is work carried out in the operation and evaluation stage, after the system has gone live. Usage and satisfaction are measured after go-live and fed into evaluating the return on the investment and grasping requests for improvement, and if necessary fed back into maintenance or the planning of the next system. As the choice explicitly says “the system in operation,” it presupposes a state where acceptance has already been finished and the system is running in production; it is not work of the acceptance stage, which checks and takes delivery of what has been delivered, so it is incorrect.
- エ
正解 The correct answer is エ. Software acceptance is the stage in which software that the developer (supplier) has built and delivered is checked by the client (acquirer, i.e. the user department) to confirm that what was ordered has actually been produced, is formally accepted, and is brought to a state where it can start to be used in real business operations. In the flow of system development — planning → requirements definition → system design → programming → testing → acceptance and deployment → operation → maintenance — it sits at the boundary where the developer's work ends and the leading role passes to the user side. Three activities are typical of this stage. First, acceptance testing (approval testing), in which the users themselves operate the system along their actual business flow and confirm that it satisfies the functions and performance fixed in requirements definition. Second, preparing documents, above all the user manual, which sets out operating procedures and how to deal with exceptions and is received as a deliverable. Third, education and training for users, in which the staff who will actually use the system are trained so that they can operate it according to the manual, while preparations for the business transition are also advanced. Choice エ states exactly the second and third of these, namely preparing the user manual and conducting education and training for users. No matter how high the quality of the software, business cannot run if the people who use it do not know how to operate it. Handing over the developer's deliverables in a state that the user side can actually make use of is the very purpose of acceptance, and manual preparation and training are its core activities. Therefore, the activity performed during software acceptance is エ.
ここがポイント
- What is carried out in software acceptance — Acceptance is the stage in which the client and the user department check and take delivery of the software and bring it to a state where it can be used in business. Its main activities are three: (1) acceptance testing (approval testing) led by the users, confirming that the requirements are satisfied; (2) preparing and receiving documents such as the user manual; and (3) education and training for users, plus preparation for the business transition.
- Telling apart the work of each development stage — Planning and requirements definition is the stage where interviews with users decide what to build; system design is the stage where mechanisms such as access right design are made concrete; operation and evaluation is the stage where usability and effectiveness are measured after go-live using questionnaires and the like. Words in the question text such as “in operation” and “new systemization” are clues to which stage is being talked about.
用語