Let’s now assume that one of the NMS clients makes an operational request: "Back up the configuration data on routers R2, R5, R6, and R7." This procedure will involve a more complex series of actions by the NMS. Let’s also imagine that at the same time, one of the other clients wants to upgrade the software on some of the routers in Figure 2. Given that the NMS is the gateway for all such operations, how does the NMS manage all these operations? Especially given that operations such as backup and restore can be complex long-running processes. Clearly, the NMS needs some sort of queuing mechanism.
Once queued, the client requests can then be serviced in turn in an orderly fashion. We pretty much have our software requirements now.