Development ProcessThe Waterfall Model was the process model that was used to plan and complete the project. It is a linear sequential life cycle model thus very easy to understand and use effectively. Using this model, each phase has to be completed fully before moving to the next phase. It is typically used for projects which are small and there are no uncertain requirements making it very suitable for this process. Following this method the project was developed in the stages of:User and system requirements and specification analysis. This is the requirement analysis phase of the project where the product perspective will outline the context of the project, product functions will detail the the use of the software, constraints will be identified on both the project and the user and any assumptions made in regards to the specification will be outlined. The critical, major and minor system requirements will be identified from the specification. Finally scenarios will be described to illustrate the how the user will interact whatt the system and for what purpose. Software Design and class and object modelling and planning. This phase the structure of the software will be identified and classes will be broken down to detail how they will work in the system. A use case diagram will be constructed to illustrate how the end users will interact with the software and affect the system. A design of the database will model how customer information will be secured and how the classes will have access to the data, this will illustrate how certain users will only have access to certain information and restrict sensitive information from lower authority end users. Implementation. The code will be implemented in chunks to ensure each class is functioning correctly and allow testing to better identify bugs. This section will include a state diagram to illustrate the implementation of the classes.and how they interact, diagrams to illustrate the controller class and state diagram of the system from start to end. Sequence diagrams of play, customer, gold membership and booking screens. Testing ********* Deployment of System and Maintenance. The project will be completed and submitted.In this model, at the end of each phase a review must take place to evaluate whether that part of the project has gone successfully, this was also the same time the report would be written on the section. The step that was applied differently to this project was the traditional method of only testing at the end; this was replaced with a more efficient method of testing than allowing bgs t potentially pile up. Due to the constraints put on the project and thus the team working on it due to schedule and workload, the waterfall method was determined as the best development process for the project. This model allowed progress on the project to be easily tracked and understood and allowed clear deadlines for each phase to be set in relation to the current progress due to its sequential nature. This allowed the project to be managed effectively tanks to its small scale.Diagram of Waterfall-model: The sequential nature of the project also has disadvantages with the planning stages being much more crucial as unlike agile or iterative methods the structure and planning of the software had to be very solid in the system design phase otherwise significant time would have been used to re organise or modify the design. The Agile model and Iterative model were not applied to this project as the specification was very clear and specific and thus did not need the freedom that agile development allows nor was it so large that an iterative design would have been more effective.