The implementation of software functions is often divided into several processes. Today there are a variety of factors that interfere with the smooth execution of these processes.
A helpless network
The system is deployed in a variety of real-world environments
Network architecture and flow control in the environment are different
Of course, the stability of the network is also a variable
The network turbulence caused by the change of network hardware facilities
Just talk about the stability of the network, to a certain extent, it is easily affected
Simple is divided into hard and soft factors:
Hard factors such as weather change, signal interference, line damage, etc.
Soft factors such as routing, shunting, network setup, etc.
These factors are the potential dangers that affect the flow to the right
Multi-directional selection of flow direction
A function of the process, often does not simply "indomitable"
Branches, loops, retrace, and so on, are likely to appear
The multi-directional nature of the process, coupled with the diversity of the network, increases the risk of program errors
Considerations for backup costs
One way to ensure that the process executes correctly is to back up the status of the correct process node
But also consider the time, cost factors
and hardware environment limitations, such as hard disk storage capacity, database performance efficiency, program performance (time-consuming, memory-intensive)
Impact of multi-system interactions in processes
Today, it's unrealistic to have a single system complete all the functions
Often, it is necessary to integrate new system functions on a number of existing systems
Therefore, the interaction between systems must be considered
But each system because of the diversity of the network, the multi-directional nature of the process, the cost of consideration, and so on, the probability of error is greater, the more risk
This requires new systems to consider how to control these risks
For example, system A sends a message to system B, B receives a successful message, feedback to a success, a continues the following process
Assuming that there is a problem with the transmission of the message between a and B, system A is facing a risk of sticking to the dead
Explore software Engineering (risk)