Consider that a management and tracking system developed for marathon runners is going into production tomorrow. The runners will begin using the site in the morning to sign up and track their entries into multiple races. Data was entered for racers that had signed up prior to the system going live. There is a race in four weeks, which allows friends to login and track where the runner is on the course. The season ends in six months and full reports are provided to each runner with their statistics. In your initial response, provide examples of post implementation items you will need to manage and support in the first five days, the first four weeks, and the first six months for the marathon runner management and tracking system.

In responding to your peers, select one of the post implementation items in their post and provide a failure scenario for the post implementation item and a possible resolution for the runners as well as management, assuming the item fails to resolve the problem. For example, an implementation item can be a checkpoint in the first five days in order to ensure runners can reset passwords.

A failure scenario may be that runners that had logins created prior to the production going live will be unable to reset their passwords. Assuming there is an issue where runners are unable to reset passwords, management can resolve the issue. However, management must resolve the issue by approving the database team to run a script to reset all user IDs with create dates, prior to going live. Below is the peer post chosen: "First Five Days Fault management - As errors in the system become apparent, the team will correct them. Maybe one of the data servers has sustained physical damage and must be replaced, for example. Better to take care of that as quickly as possible, before many users start experiencing problems (Rosenblatt, p. 519).

Security risk assessment - The team will closely monitor the network to ensure that no hackers are breaking into the system. Threat categories include human error (such as accidentally deleting files), technical obsolescence (parts of the system are so too out-of-date that they don't function well, or don't interface well with other parts), espionage, and natural disasters (flood, earthquake, etc.). Critical risks will be identified and marked for response during the first four weeks, possibly the first five days (Rosenblatt, p. 525).

Online training - Now that the system is up and running, many people will need training in its use. Online training system costs less than in-person training, and can accommodate busy schedules. Especially at first, it would be valuable to monitor trainees' experience and adjust the online training system to better accommodate their needs (Rosenblatt, p. 480).

First Four Weeks Perfective maintenance - The initial system would work well, but it could always perform even better! Speed of data loading could be increased, for example, letting people access pages faster (Rosenblatt, pp. 511-512).

Adaptive maintenance - I might add enhancements such as support for mobile devices. For example, the initial application might run only on Web browsers (so it would be ready on time), and once it was up and running, I could add iOS and Android mobile capabilities (Rosenblatt, p. 511).

Network security upgrades -Encryption levels might be raised, permissions adjusted to deny access to risky users, firewalls upgraded, and so on (Rosenblatt, pp. 531-540). First Six Months Maintenance releases - Updated versions of the marathon tracking system could be released as the project team responds to user requests and completes "nice-to-have" features.

For example, maybe users will complain that the system crashes at certain points, so the developers will fix those bugs in new maintenance releases (Rosenblatt, p. 517).

Risk control - Cyber-attacks can happen at any time. And unintentional errors can also expose the system to threats. The team will continue monitoring and responding to potential security risks (Rosenblatt, p. 526).

Backup and recovery - The system will collect data throughout its running period. This will become especially critical when reports are generated and delivered to marathon runners.

The team will back up data on hard drives and in the cloud, and will retain the data for a significant period of time after the marathons are over, in case anyone requests reports (Rosenblatt, pp. 540-542).