2
Review of development structure
After determining an overall development schedule, the structure in place
for system development is reviewed.
The development structure should be considered not only by the System
Development Department, but also the business operations departments
that will actually use the system.
If only one side is involved, the system could end up different than the actual operations or incompatible with the company-wide system. By having
both sides involved in computerization, the system can be developed in
line with the business strategy.
When doing this, it is necessary to ensure proper assignment of personnel,
including the person responsible for overall development, the person responsible for system development, and the person in charge of operations.
3
Risk analysis
“Risk analysis” is the act of determining what kinds of risks are involved
in the construction and operation of the system, where they exist and what
level of loss would result from their occurrence, and measuring the degree
of their impact. The possible risks based on the estimated probability of occurrence and size of the potential loss are prioritized, and addressed according to their priority.
The possible risks involved in computerization and their causes are summarized below.
Risk
103
Cause
Hardware failure
•Forgetting to turn on the power
•Incorrect device settings
•Device connection error
•Device failure, etc.
Software failure
•Incorrect operation by user
•Software bug
•Incorrect OS or software settings •Computer virus, etc.
Network failure
•Disconnected cable
•Incorrect IP address setting
•Incorrect network device settings •Constraint violation, etc.
•Network device failure
Data failure
•Data corruption
•Wrong data type
•Improper format
•Insufficient storage space, etc.
Performance
failure
•Insufficient memory
•Insufficient disk space
•File fragmentation, etc.
•Increased volume of data
Disaster-related
failure
•Fire, flood, earthquake, etc.