What's changed: Initial version
5.1System concept & planning
Covers the division of roles between the system concept, which draws the overall picture and policy of systematization from the management and information-systems strategy, and the system plan, which then makes concrete the target scope, structure, investment, schedule, effects, and risks; and the judgment of gauging premises, constraints, and risks through a feasibility study (technical, economic, operational) before committing to a plan.
The starting point of system planning is not to pick a development target on a whim, but to draw the overall picture of systematization from the management and information-systems strategy, gauge its feasibility, and then bring it down into a plan. Drawing the overall policy upstream is the system concept; making the target scope, structure, investment, schedule, effects, and risks concrete on that basis is the system plan. Before committing to the plan, assessing whether it can really be realized from the technical, economic, and operational sides is the feasibility study. This section covers upstream planning decisions from the viewpoint of an IT strategist judging which realization approach and investment scale to choose within premises, constraints, and risks.
5.1.1The roles of the system concept and the system plan
Continue reading — free sign-up
You're reading the free preview. Sign up free to read this section in full, plus every chapter (including 4+) and all questions.