Christian Baker
1/16/2016
IT - 331
SNHU
IT 331:
Network Delays
System confirming the user’s password during log-in According to Jakob Nielsen, there are three important time limits in a user oriented system. Those time limits are the time for a user to feel that the system has reacted instantaneously, 0.1 seconds. The time it takes for a user’s flow of thought to go uninterrupted, 1.0 second. The time it takes for a user to not lose his/her attention, 10 seconds. When a user is logging into a system, there is already a commitment made by the user. The user is there for a purpose and is not likely to find an alternative due to minor delays. In keeping with Nielsen’s rules, I believe the system should not delay the user more than 10 seconds. Most systems can authenticate faster than this, so anything slower would be an anomaly. This is assuming the user has a high speed connection and is not accustomed to delays due to low bandwidths. A network delay in this scenario could be caused by congestion in the system’s authentication server. If too many users are trying to authenticate, it will slow down the user look up speed. To remedy this situation, there could be multiple authentication servers to increase speed and provide redundancy.
Synchronous group editing of a document …show more content…
This scenario could experience up to a 10 second delay without negatively affecting the user. Asynchronous critiquing requires the changes to be compiled and attached, before sent to the destination. We experience this when we submit our course work to be graded by our instructors. We students do not notice any system delay because we are not aware of when the critiques are sent and they are not time sensitive. The instructor sending the critiques will notice if there is a delay because he/she is waiting for the items to be sent before moving to another
1/16/2016
IT - 331
SNHU
IT 331:
Network Delays
System confirming the user’s password during log-in According to Jakob Nielsen, there are three important time limits in a user oriented system. Those time limits are the time for a user to feel that the system has reacted instantaneously, 0.1 seconds. The time it takes for a user’s flow of thought to go uninterrupted, 1.0 second. The time it takes for a user to not lose his/her attention, 10 seconds. When a user is logging into a system, there is already a commitment made by the user. The user is there for a purpose and is not likely to find an alternative due to minor delays. In keeping with Nielsen’s rules, I believe the system should not delay the user more than 10 seconds. Most systems can authenticate faster than this, so anything slower would be an anomaly. This is assuming the user has a high speed connection and is not accustomed to delays due to low bandwidths. A network delay in this scenario could be caused by congestion in the system’s authentication server. If too many users are trying to authenticate, it will slow down the user look up speed. To remedy this situation, there could be multiple authentication servers to increase speed and provide redundancy.
Synchronous group editing of a document …show more content…
This scenario could experience up to a 10 second delay without negatively affecting the user. Asynchronous critiquing requires the changes to be compiled and attached, before sent to the destination. We experience this when we submit our course work to be graded by our instructors. We students do not notice any system delay because we are not aware of when the critiques are sent and they are not time sensitive. The instructor sending the critiques will notice if there is a delay because he/she is waiting for the items to be sent before moving to another