• Deployment
  • Functional Changes
  • Procedural Changes

Conclusion

Overall this project has been successful. All of the minimum requirements were implemented very early in the project life-cycle, which left sufficient time to implement many more features, far in excess of the minimum requirements.

Also, the system was at this stage sufficiently early in the project life-cycle to allow more time to be spent on evaluation and testing than had originally been planned, which enabled the system to be further improved, both in terms of fixing bugs and improving its usability.

Unfortunately, it was not possible to implement all of the features required by the Sports Centre, some of which were only specified quite late on in the project. These features are mainly related to periodic bookings. First, it is not possible to specify two sets of periodic bookings, as specified in Section (page ). Second, it is not possible to define periodic restrictions, also specified in Section .

Despite the lack of these features, the system created was technically very good, and would not need many modifications before deployment. Issues related to deployment are discussed in more depth in the following section.

Deployment

Before this system could be deployed for production use by the Sports Centre, there are a number of points to be considered. These are primarily in one of two categories, (functional changes and procedural changes) both of which will be discussed in this section.

Functional Changes

The most important functionality that is required, but not present, in this online system, is full support for periodic bookings and periodic restrictions (see Section , page ). The other missing functionality listed in Section (page ) would be very useful, but are not essential to the operation of the system.

Procedural Changes

The primary consideration would be how the online system would replace the current system. This replacement could either be a complete replacement, probably during a quiet period such as the summer holidays, or a gradual period where the current system is phased out. An example of the latter scenario would be introducing the online system for Squash and Sunbed bookings only -- this has the benefit of not needing periodic restrictions (although periodic bookings are still required).