問29
頻出度★☆☆
企画プロセス, 要件定義プロセス, 開発プロセス, 保守プロセスと続くソフトウェアライフサイクルにおいて, 企画プロセスの段階で行う作業として, 適切なものはどれか。
平成23年度 秋期 ITパスポート試験 問29
ストラテジ系システム企画 › システム化計画
This question's explanation and your answers so far.
解説
問 29
Incorrectア
Defining functional requirements and non-functional requirements is work in the requirements definition process, which comes right after the planning process. Taking the management needs and issues confirmed in the planning process as input, you organize the business requirements and clarify the functions the system should provide (functional requirements) as well as the conditions other than functions, such as performance, availability, security, and operability (non-functional requirements). These can only be written once the deliverables of planning are available, so they are not activities of the planning process stage.
- イ
正解 The software life cycle proceeds in the order planning → requirements definition → development → maintenance, and the further along it goes, the more it shifts from “what to build” to “how to build it”. The planning process, at the very top of this flow, comes before the shape of the system is decided; it is the step that settles, from a management point of view, what the system is being built for in the first place. Here you check management needs and issues against the management strategy and the business goals, draw up a systemization concept that solves them, and put together a systemization plan covering the target operations, the timing of implementation, the rough cost, the organizational structure, and so on. Therefore the activity that is appropriate at the stage of the planning process is “Confirmation of management needs and issues”, and the correct answer is イ. If the issues are misjudged here, then no matter how correctly the later requirements definition and development are carried out, the result will be a system that does not help the business — that is why the planning process matters.
Incorrectウ
Designing and evaluating the system architecture is work in the development process. It allocates the system requirements fixed in requirements definition to hardware, software, or manual operations, and decides the overall structure of the system; this corresponds to what is usually called external design. It is the stage where the means of implementation are decided, so it sits far downstream of the planning process, which decides whether to build a system at all and what is to be solved.
Incorrectエ
Designing and evaluating the software architecture is also work in the development process, and it comes even later than the system architecture design in ウ. For the part that the system architecture design allocated to software, you design the structure of components and programs, the interfaces, the database structure, and so on. It is the most concrete stage, where how the inside of the software is built is decided, and it stands at the opposite extreme from the planning process.
ここがポイント
- In the software life cycle of the Common Frame (SLCP), the order is planning → requirements definition → development → maintenance. The planning process is the most upstream step, where the management needs and issues are confirmed, the systemization concept is drawn up, and the systemization plan is drawn up; its role is to connect the management strategy with the system.
- Memorize each process together with its representative activities. The requirements definition process defines the business requirements and the functional and non-functional requirements; the development process first performs system architecture design (the overall structure of the system) and then software architecture design (the internal structure of the software) — the further downstream you go, the more concrete the means of implementation become.
用語