12. Enter in time sequence which can be rather irritating especially when the writer does not have much space to write and the recorded information may drag to the next day’s time/date.
13.
14. Requests ReservationName: stringAddress: stringTelephone: stringDate: stringTime: stringNumber of Seat: stringOccasion: stringDepositBank account ManagerReceptionist Cook Waiter StaffName: StringAddress: StringTelephone: StringDOB: StringLook up availability on booking reservation Confirm table reservationsCreate bookingsRecord complaintCancel bookingsPersonName: StringAddress: StringTelephone: StringDOB: StringCustomersName: StringAddress: StringTelephone: StringBank account: DoubleRequest for reservationsCancel a reservationArrive for dinnerMake a complaint about the food
15. Table Name: stringAddress: stringTelephone: stringDate: stringTime: stringNumber of Seat: stringOccasion: stringType of Table Relationships: GeneralisationStaffManager Receptionist CookWaiter Deposit Seats Occasion Time & date Booking Entity Relationship Diagram PART 1 Records Includes HasMany S.ID StaffT.IDTable O.IDOccasion B.ID C.IDBooking S.IDC.ID Customer Entity Relationship Diagram PART 2 S.ID StaffB.ID C.IDBooking S.IDT.IDTable C.ID Customer R.ID B.IDReservation O.ID T_IDO.IDOccasionRecords Many IncludesHas Implementation 1905019050 This screen shot represents the interviews that I have created in order to get more information on how the database has affected the restaurant and what improvement could be made? This screen shot represents the results of the survey that I had attained after asking various questions related about the restaurant to customers and staffs.1841521653519050247650 This screen shot represents the evaluation on the fact finding. This section explains my ideas on the new system. After collecting all the basic facts it’s time to initialise the system 19050198120 This screen shot represents the conclusion; this will explain what kind of database would be ideal for the restaurant and what would be the best way to commence. This screen shot represents the booking table where the user can record customers time and date of call when requesting for a reservation. This would be an advantage for the staff to check the date/time of the calls in one click if there were any reasons to amend the bookings.This screen shot represents the switch board where the user can view all the daily reservations in detail; this will allow accuracy when customer comes in for a reservation. This switch board will allow them to view different tables for accuracy. This would save time and frustration. -47625-238125-476255181600This screen shot represents the customer table; this allows the user to view all the current customers’ information that is recorded for a reservation with the restaurant. This screen shot represents the staff table; this allows the user to view all the existing staffs’ information that records booking. -1809754343400161925-38100This screen shot represents the occasion table this table records information about the customers’ reservation i.e. what kind of occasion it is? How would they like the room decorations? This kind of detail would take over the page in the manual booking in diary; this would again save time and make it precise to understand.This screen shot represents the table for table; this is in records more in detail how they would want their seating plan. This is an additional table to help staff organise reservations for customers’ high expectations. -190503895725-19050257175This screen shot represents the reservation table this table records information about the booking, occasion, table, time/date of booking. This is the most important table in the whole database as it would allow users to see what is going on. This is table staff would use to confirm their reservations when customers come on.-19050-9525Evaluation This is the evaluation for my work based project that I have been undertaking for the past three months, it involved carrying tasks such as analysing, designing and implementing a booking system for the Raj Doot restaurant. How users will benefit from it? Many users will not only find this concise and reliable but they will also find this very knowledgeable. Everything could be easily done for example; adding a new column or a new row. It would not take as long as a paper and pen; this is a perfect way to add new lists of organisations for the business and the greatest thing is there would not be no changes in the field and system the way it is used, so users’ would not have any trouble adjusting to the new and enhanced database. All the tables will have their own unique beneficial for the business, for instance; the occasion table will be advantageous because it will have all the decorative and cakes listings with the an ID number for a straightforward reference, this will save time and lose all the frustration that staff usually have when recording a reservation. Furthermore, the booking table; not only is this going to be straightforward and easy to use but also very practical, the restaurant gets a lot of cancellations and can be time consuming to find the date of cancellations for the present customers’ who wants to make an appointment, the database will allow the staff to check this, on a click of the mouse. What’s more, the customer table is brilliant to store all the regular customers’ details in i.e. name, address, contact number etc for future reference. What improvements my database system brings in comparison to the old way of conducting the business? The database has loads of improvements compared to the traditional way of conducting the booking. Not only does this save time but also it is very reliable it would not make any human errors such as filling in the field with an incorrect data type. This is an excellent way to avoid any mistakes with the customers’ details in particular. Conclusion The main purpose of this project was to create a booking system for the restaurant as it was losing customers, due to lack of organisation on the booking system. I have found my journey from beginning to end of this project rather challenging; I have learnt many useful skills that would benefit me for future assignments. One of the main things I have learnt is resolving a problem is not as easy it may have sounded three months ago, after learning multiple ways of analysing the problems and arising problems. The big part of solving a problem is to acknowledge them first. I have done several missions to obtain a successful project, this has been demonstrated by; fact finding such as questionnaires and interviews; on a one on one basis, which gave me more information towards the right path for the methodology models. Comparing two methodology models that would be beneficial to the system, creating use case-case diagram etc these have been an interesting way of finding out more about the system, in a completely different way that I never thought I would carry out. I believe I could have done the system investigation better, I feel as though I did not capture the required information that could have emphasised the system needs in more detail, I feel I could have made it more comprehensive and more informative. Altogether I accept I have met all the given criteria of this project and have attained it in a professional manner, and have completed it within my time limit. Overall I feel satisfied with my work I have done for this project and I hope this will make an impact on the restaurant. `