Hotel Room Booking Database
Evaluation

I have created a booking system for the hotel which allows the user of the database, notably the hotel staff, to input all information in regards to a hotel booking, including room information and customer registration information. This is instead of the paper­based method of booking in, which the hotel uses at current. I have created the booking database as, after consideration, the hotel decided it would be a more up­to­date method of booking in and after they had several issues with loss of data whilst using the paper­based method. Although it still may be the case that data is occasionally/accidentally lost while using the booking database, this is much more less likely to happen as back up copies can be made of the data, which were not made when using the paper­based method as this would be too time consuming for the hotel. I have created a database with four main parts, which are: Customer, Booking, Booking/Room and Room tables ­ which each have a connected form. To use the Hotel Room Booking Database, the user should load the database file from the shortcut on the desktop. Then, a splash screen will be displayed ­ this will be the first thing that the user sees when the database file is loaded. After this, the user should click anywhere on the splash screen to display the message box “Hit the OK button to progress to the login screen”. The user then clicks OK, and then OK on the following message box “You will now be taken to the login screen, press OK”, and they will then be taken through to the username and password screen. If the user of the database enters the correct username and password, then the login will be successful and they will be transitioned through to the interface form, which is the main display screen of the database and is what users first see after logging in. This is how the user starts up the database. The interface screen features 17 buttons with links to all areas of the database, including a log off button. Before this system came into place, all the hotel did was simply manually write down all the booking information in a booking­in book, and stored customer registration details in a file after the customer manually wrote them out themselves. After looking back over User Interface Requirements, I have stayed to my original plans. In the user interface requirements, the plans were for the user interface of the database to be simple, yet effective. I have kept to the plan of the database being simple as it is easy to navigate and the user will be very unlikely to become confused at any time when using the database as everything is clearly signposted and laid out on all pages/screens of the database. I have also stuck to the plan of having macros on the database such as ‘Next’, ‘Previous’ and ‘Print’ as these are easy shortcuts for the user to make use of, which also fit in with the simplicity aspect of the database. The user interface of the database is form driven, which is what I originally planned for it to be and the validation checks, including date of birth and email, which were outlined in the user requirements, were present in the actual database itself ­ therefore sticking to the plan. I have created a splash screen as the first screen which the user will see. The splash screen has the simple title ‘Strathmore Hotel Booking System’ and then ‘Welcome!’, as well as the hotel logo.
The splash screen does look slightly amateur so this could be definitely be improved to embrace a more professional feel to it. After this screen, the login screen appears, which is where the user enters the username and password in order to progress through to the interface screen. This page has a similar feel to the splash screen, just with added boxes for the username and password to be entered, as well as an OK button. If the login is successful then the user will be able to transition through to the interface screen. However, if either the username, password or both are incorrect then an error message will be displayed asking the user to try again and preventing them from moving forward to the interface screen. If this process is successful, then the interface form will be loaded. This allows all routes throughout all areas of the database from this page. All tables, queries, forms, reports and the logout function can be accessed from this page.

Name: Matthew Brocklesby

Candidate Number: 7251

Hotel Room Booking Database
Evaluation

The first form which can be accessed from the interface screen is the Booking Form. This form automatically generates a booking number for the unique booking, and the user then enters the customer ID of the customer who will be staying in whatever particular room the user enters into the form. The date of booking will then be entered into the form, which is the exact date that the booking is being made, along with the arrival date and departure date of the booking. The total cost for the customers stay at the hotel will then be inputted into the form. Also, if a deposit has been paid the Deposit Paid checkbox will be ticked and if so, an amount which has been paid will be entered in the Deposit textbox. If a deposit has not been paid then the checkbox will be left unticked and no amount will be entered in the Deposit textbox, it will be left blank. A subform is present in this form which is simply a list of records which have been added using the booking form. The form features six macros which run along the bottom of the form, which are Create
New Record, Delete Record, Previous Record, Next Record, Print Record and Save Record. These can easily be identified by the symbols on the macros which represent which action they do. The
Booking Form met the user requirement of being simple yet effective to use as the form is straightforward to use and it is clear, even without instruction, what the user has to do in order to use the form. The user requirements stated that the booking form should be simple and smooth for the hotel to use and operate which it is, especially with the use of the six clear macros which are placed along the bottom of the form. As well, all of the macros which were described in the user requirements are present on this form so therefore this feature has been met. However, one problem with this form is that it does not include navigation back to the user interface form.
Instead, the user will have to reload the interface form themselves. This could be a time consuming process and does not look or feel very professional. To improve, I should add a navigation button, namely an arrow for example, which would take the user straight back through to the user interface form. The next form that can be accessed from the interface screen is the Customer Form. This form is where the user enters in all of the details about the customer who will be staying at the hotel.
These details include First name, Surname, Address Information, as well as Telephone Number and Email Address, amongst others. This page also features the exact same six macros as described previously in exactly the same position, just on a different form. This form links directly to the interface screen with the use of the Customer ID. As like the previous form, the Customer
Form features the hotel logo in a prominent position, to persistently reinforce the idea that the database belongs to the hotel. This form features a calculation ­ for age. The user enters in the date of birth of the customer, and the calculation automatically generates the age of the customer, in accordance with the present date at the time. This age also may help the hotel when deciding to target age­related offers to customers. Also on the customer form, the user can tick the checkbox for whether or not the customer is an executive member of the hotel, which again will help the hotel when deciding to target offers to people who are members­only, and also when the hotel is trying to convince people to become members of the hotel. This form has met the user requirements which were described. In the user requirements, it stated that it should be easy to understand when details are being entered into the customer form, which is true ­ as everything is clearly labelled and there is only one text box where each specific piece of information can be entered. Also in the user requirements for the customer form it stated that there would be space for the registration details to be inputted in the form of text to the right hand side of the label stating what information should be inputted, and this is exactly what happened. One thing changed however. In the user requirements, it stated that the customer form would have a tick box which could be checked by the user if the customer wished to have breakfast at the hotel. Instead, this was changed to be a tick box for whether or not the customer
Name: Matthew Brocklesby

Candidate Number: 7251

Hotel Room Booking Database
Evaluation

was an executive member, so that offers could be targeted to them. This was changed as the hotel found that it was extremely rare that somebody did not want to stay for breakfast as this was included in the price anyway, whether they wished to stay for breakfast or not, the price would not change anyway. So this was changed so that extra space was not being wasted on the database system for no reason. As like before, a problem with this form is that it does not include navigation back to the main interface screen of the database which is a problem if the user is in a hurry. To improve the customer form, the registration details could be more spread out because at current they are all crammed together. However, this would depend on how much space was available on the form. The third form which can be accessed from the interface page is the BookingRoom Form. This form is a small, simple form with only one main purpose. The point of this form is to link each booking number to a room number, for hotel reference purposes only. As like the other three forms, this form features the same six macros in exactly the same position. Also, the logo is featured in the same place. This form fit the user requirements as this was the simplest of the forms on the database and the whole ethos of the database system was to emphasise simplicity and ease of use for whoever is using it, so therefore the BookingRoom form matched this. This form is definitely easy for the user to understand as it has a clear purpose. Although this form can only include two boxes, it can be improved. The title could be made more bold and stand out more, and also be in a colour such as red to make it stand out and make it more visually appealing to the user. Also the colour scheme could be updated to more enticing colours and navigation to the interface form could be included. The final form which can be accessed from the interface form is the Room form. This form details information about each room in the hotel. When a room number is entered, it gives information about the Type of room, e.g. Single, Double, whether or not it is ensuite, how many people the room sleeps, the price per night of the room and whether or not the bedroom has disabled access. This form can be used by the hotel staff quickly and easily, for example to inform customers about any queries they may have about the room over the phone for example before they actually come to stay. Once again the hotel logo and the six macros are prominently featured on this form in the same location as they are on the other forms in order to build upon the ethos of consistency and simplicity that is featured throughout the database. The room form fit the requirements of the user, as, like above, it is simple to use and includes all of the six macros which were stated in the user requirements. Also, as a whole each of the four forms fit the user requirements because in this document it stated that the user interface of the hotel room booking database should be form­driven, which it is throughout the whole database. To improve upon this form I could arrange the form so that the objects are not all placed together in one corner of the page and make sure it is spread out to fill the whole page as this would look more visually appealing to the user. As well, like the other forms it should include navigation back to the interface form or maybe even to other forms on the database as at current, this is not a feature of the form. The forms which are featured on the database allow the user to input information as well as save information to the database to be used for future reference. The forms are not just a visual tool, they actually allow for change to be made on the database. For example, on the Room form, information about a room is entered manually by the user, such as Type and Price per night ­ this information can then be saved to the database using the Save button macro. Also, the forms as a whole allow for information to be removed from the database system. Also, on the Customer
Name: Matthew Brocklesby

Candidate Number: 7251

Hotel Room Booking Database
Evaluation

Form, this form allows information to be inputted in great detail. This form collects the most data out of the four forms which are present on the database system. Fourteen pieces of information are collected about the customer through the use of this form, which is the most on the database.
The form which collects the least amount of information would be the BookingRoom form. As well, the Booking form collects information and can be saved through the use of the form. I have featured six queries on my database. The first query is an Open Deposit Paid Query. This query simply displays a list of customers who have paid a deposit for their stay at the hotel. When this query is clicked, it runs instantly with nothing extra having to be clicked. It is displayed as a simple and concise list. This query met the user requirement of being effective as this was arguably one of the most important queries for the hotel to use as without this query the hotel could end up accidentally overcharging someone if they had already paid a deposit as they would not be aware if they had paid a deposit or not without this query. Therefore, this query is preventing any damage to customer relations and helping the hotel in the long run. The second query is an Open Customer Query. This query displays customer information when a Customer ID number is entered, after the query button is clicked on the interface screen. The query displays important information about the customer such as Names, Address and Contact Information. The query loads instantly after the Customer ID number has been entered. As well, this met the user requirement of being effective as this query is also very valuable for the hotel because the customer can use this hotel to check that the hotel makes any special requirements before the customer comes to stay at the hotel, for example if they are a disabled customer then the hotel can ensure that the adequate preparations are made for this. Another of the six queries on the database is the Open Booking Query. When this query button is clicked on the interface page, a table version of the booking form loads, allowing the user another quick and easy way to enter in valuable booking information into the database system. This meets the user requirement of being simple for the hotel to use ­ however, it can be improved so that it actually does something or brings something new to the database system instead of just reciting what is already there in the system and presenting it in a different way. There is also a Find ALL Bookings Query present on the database. This query is simple but very useful ­ it simply shows a list of all bookings which are currently present and saved in the database. This can be used for reference purposes by the hotel staff. This meets the user requirement of being easy to use by the hotel staff as they can quickly and easily run this query should they need to for any reason. The penultimate query is the Open
Room Number Query. After this query button has been clicked on the interface page, a box should appear on screen asking the user to input the number of the room they wish to run the query on.
Once a room number has been entered and the OK button has been clicked, information will be displayed on screen about this room such as the Type of Room, whether or not it is En­suite and how many people it Sleeps. This can be used by the hotel for example when responding to telephone enquiries about particular bedrooms. This query would be simple to use and should not be confusing even for a novice user, which is part of the user requirements for the database system. The reason it should not be confusing for a novice user is because all the user has to do is simply enter one number into the box which is not considered a particularly difficult task to complete. The final query which exists on the database is the Delete Expired Data Query. As the title suggests, this query deletes database data when it has become ‘out of date’. The database considers data to be expired when it has reached five years or older. There will be two confirmation boxes displayed after clicking the button and if these are OK on both, then the expired data will be instantly removed from the database. The hotel needed this query in order to comply with the Data Protection Act and to build upon the privacy and security of the customer data. This query met the user requirement that no confusion should occur as the user is warned
Name: Matthew Brocklesby

Candidate Number: 7251

Hotel Room Booking Database
Evaluation

twice about the removal of data from the system, therefore they should not be shocked or surprised once the data actually goes. The queries used on the database allow the user shortcuts so they do not have to do all of the mentioned actions manually themselves. I have placed queries on the database so that the user saves time when using the system and also to add to the simplicity aspect so that it is quick, easy and fluid process as they are not having to waste any time, especially if they are in a hurry such as if a client is on the phone who quickly wishes to enquire about a room for example. The report on my database shows the annual bookings. My report originally was set out to show a structured summary of one piece of information on the database. I decided that the piece of information from the database that would be best summarised is the bookings, as this is essentially the main purpose of the database ­ to take bookings for the hotel. This is summarised on the report as it is an Annual Booking Report, showing the bookings for each bedroom in the hotel throughout the year. So, in this respect, I set out with what I was supposed to do in my report as it is clear and concise and it does actually have a main purpose which it manages to fulfill. I wanted my report to show a summary for something as I wanted the report to be a document which could be looked at by hotel staff if they needed something simple to look at but also a valuable document, the report does this in a yearly view.This is, a visual summary of the year's bookings that were placed at the hotel. The information in my report comes from the booking table and is grouped by room number. So, the total bookings for each room in hotel throughout the year are summarised in the report. The report is sorted by date with the date that has the earliest bookings of the year, so January, being at the top of the report, with the date that has the latest bookings of the year, so December, as the hotel is open during the Christmas and
New Year period, being at the bottom of the report. I included this grouping and sorting so that the report would appear more professional to the user as well as easier and more understandable to interpret, especially as the bookings are grouped by room, so this can easily be added to the hotel records and used to identify trends, for example to identify which rooms are occupied the most and the rooms which are unoccupied more often, and therefore steps can then be taken to rectify this. To improve I could make the report better fit the ethos of the hotel and its simplicity as it does appear slightly long­winded as there are so many pieces of information which are fitted into the report at once. The database is very secure as a username and password are required in order to access data on the database. If either the username, password, or both are incorrect then whoever is trying to use the database would be unable to access it under any circumstances as there is no way to bypass the login screen. Only employees are able to access the database who have been given an authorised username and password and no customers or anybody else for that matter is able to access the system. To ensure that only employees can log on I programmed a predefined set of usernames and passwords in the system so that only these combinations can have access to the database, any other combinations would be unable to gain access to the system. This is to prevent anyone from gaining unauthorised access as the database contains personal information such as address details for customers which could be hazardous for the customer if the data was to get into the wrong hands. I had always planned to use the original date of birth and age calculation in the database and I followed through with this plan. The calculation calculates the age of the customer dependent on their date of birth as well as the accordance with the present date. This is a simple calculation for the database to make which takes place in seconds and is a useful calculation for the hotel to
Name: Matthew Brocklesby

Candidate Number: 7251

Hotel Room Booking Database
Evaluation

make use of as it means that it can now target age­specific offers for example. However, the hotel can not make use of this age data in a negative way as this could be considered to be ageism.
The age calculation comes as part of the customer form as this information is specifically about the customer as it comes as part of the customer's registration details on the database. The information which I aimed to collect as a priority and as the most important from the database was the customer information. This information involves everything that the database requires from the customer in order to fully make use of the customer staying at the hotel and specifically target things. The information that was collected about the customer includes the customer's First
Name and Surname, as well as Address, Telephone number and Email Address. This means that the hotel will be able to add the customer to their new mailing list that came with the introduction of the database, should the customer wish to be added. This also means that target­specific offers can be sent out, such as sending out members only offers to customers who are part of the executive member list at the hotel. Other trends can also be generated from this information as well as the room information such as trends telling which types of bedrooms certain customers prefer, and which rooms are the most popular. This means that the hotel can then adapt the hotel and suit different things to different customers. The ethos of the main database system was always meant to emphasise simplicity and ease­of­use, as anything over complicated would not suit the needs of the hotel and the experience level of the users. The users are novice users, as the use of a computerised system has never been present before in the hotel, as the previous method of using the paper­based booking system was in use at the the hotel ever since ownership and the staff were reluctant to make any change. Therefore, it was essential that the database system be simple for the hotel to use or this may persuade the staff at the hotel to revert back to the old method if the new method was going to be too complicated. I achieved this ethos of simplicity by making sure that the database was easy to use. For example, on the interface screen, everything is clearly signposted and it is easy for the user to decide which part of the database they are going to because each of the buttons on this page are clearly labelled and there should be no issues when choosing where on the system they wish to navigate to. However, the ethos of the database could have been improved to some degree because although the database needs to remain simple, it could become slightly more professional. For example, every form on the database system should include navigation back to the main interface form as this itself contributes to the simplicity ethos part of the system. In the user requirements, the house style I set out to incorporate was a font that was simple, striking and effective. I picked a font that was universally recognised, however it is doubtable whether it could be described as striking. In the future, to improve I would select a font that stood out as ‘different’ so that it could be easily recognised and when it was seen people would instantly know that it is associated with the hotel. I set out to use red and white colours as
I believed originally that these colours would actually compliment the logo. Although, it turns out that these colours did not compliment the logo, instead clashing with it. So instead I chose to opt for blacks and light blue colour schemes as I found that these did not outwash the logo and worked well with it instead however to improve I could choose a broader range of colours, maybe something a bit different. I kept the original colours of the company in the logo as these could not be changed as this is the official hotel logo and to change it would look unprofessional and would not be allowed as there would be no other logo to use as the only logo which the hotel has access to is its own. I used the generic buttons that came with the Microsoft Access software for the database as I felt that these were universally recognised symbols and therefore would not add confusing to the experience when using the database. In the future though I believe I would change these buttons so that they were more customised to the hotel and its individuality instead
Name: Matthew Brocklesby

Candidate Number: 7251

Hotel Room Booking Database
Evaluation

of just using what was already there and present on the software. The colour buttons however do seem to fit with the rest of the database without any significant problem. Also in the future I think
I would make the buttons slightly bigger as at current they are relatively small in size and because of this size the quality and size of the image on the macro buttons is slightly compromised. The buttons are consistent though as they are featured in exactly the same position in each form on the database which adds a certain aspect of consistency to the database. The hardware which I intended for the company to purchase was firstly an average desktop computer, as without this, the Microsoft Access software which is what the database uses, would have nothing to run on. An average computer is all that is required as it is not particularly strenuous to the computer as it is a simple program to run, therefore an average desktop computer with a 1GHz 32­bit processor and an average CPU speed is all that should be necessary in order for it to run. As well, the hotel needed to purchase a regular monitor along with this, coupled with a mouse and keyboard. An ergonomic keyboard was the one that was recommended to the hotel in order to optimise comfort at times when a lot of typing was needed, for example when entering all of the customer information in the customer form. A wireless mouse was also the one that was recommended to the hotel as the hotel had quite a limited space for the computer to go, and a wire would just add extra clutter to the desk, so therefore a wireless mouse can simply be tucked to the side when the computer is not in use, for example at night when the hotel said they were going to switch off the computer system. I also importantly suggested to the hotel that they purchase an external hard drive so that data could be backed up permanently in case there was an error with the original hard drive and also just to add an extra layer of security. From a software point of view, the only thing that needed to be purchased was the Microsoft Access package as this without this there would be no way that the database would be able to run. I think the database will definitely be able to run on the database I recommended because Microsoft Access does not require much processing power at all and there are also all of the necessary hardware requirements in place in order to use the software. Even though the company could grow in size and orders, especially growing in orders in busy periods, mainly summer, there will still be plenty enough space as each records takes up a tiny amount of the hard drive disk space and there is also an external hard drive should any extra space be needed, which it won’t be. I think the hard drive and external hard drive are definitely too big for the space that is required of it by Microsoft Access however I felt it was better for the hotel to have too much space than too little space as there could be a situation in the future where the hotel would require the computer for something which required extra space. However, at current, the only purpose the hotel will be using the computer system for is the database booking system and nothing else. The users requirements for the user interface of the database system were that it was to be a form­driven user interface with data entry forms. The reason that they felt this would be the best type of user interface was because it is simple and easy to program and nobody who was involved in the process of setting up the database had an advance user status. As well, the hotel and I felt that it would be fast to enter data using this specific type of user interface. Also, this type of user interface does not use large amounts of memory or processing power so after all these factors were considered we felt that this would be the best type of user interface to use for the hotel. We met these needs exactly with the hotel as it is now a form driven user­interface which has all of the advantages that were described above. It looks well as a fit for the company as the original paper­based method was simple looking and well liked by the guests due to how quick and easy it was to fill out when it came to them giving the hotel their registration details. The electronic
Name: Matthew Brocklesby

Candidate Number: 7251

Hotel Room Booking Database
Evaluation

database method follows this same use as it is still easy to use so therefore I feel that this makes it a good fit for the hotel. It could look more professional and better designed and to meet this improvement I would need to consult somebody who was better when it came to the actual design and computer design in general in order to make sure the professional nature of the hotel was fully captured in the database system. There are seventeen macros on the user interface page of the database as well as six macros on each form in exactly the same place and position ­ the main purpose of these macros was to allow for ease of navigation around the database without the user having to get to places manually themselves which would be more time consuming and could not be a possibility due to lack of skill level for some of the hotels staff. The user interface meets the requirements of the hotel due to the simplicity and there is nothing about it at all that would make it complicated or difficult for somebody to use who is only a novice user and this was appreciated by the hotel when it was explained to them. Looking at my Entity Relationship Diagram (ERD), it was followed exactly when creating the database as it made perfect sense to begin with so no changes were made to this process at all.
Also, all the tables that were designed in the first place were kept and none were changed as they also made good sense and nothing needed altering. Unfortunately, there were several problems that were encountered during the creation of the database system. However, this was expected. Firstly, there was a problem with designing the forms. As I have no creative background whatsoever, it was difficult to know what the forms should look like and how they should feel. Especially when it came to placing logos, text and especially colour schemes and ensuring that this all matched at the same time. I did come through this problem slightly however the forms are still not looking as good as they could be due to the fact that I am not skilled in design at all. Another problem that was encountered was the report not printing out correctly. When the print button was clicked on the report, the report did not fit the print preview and therefore did not proceed to print out correctly. Parts of the report ended up being missed out when the print out appeared as there must have also been a sizing issue with the report. This issue became quite prominent as several attempts were made to fix it, without success. However this problem was eventually rectified when asking other people for assistance. There was also a problem on the report with the delete query, this was probably the biggest problem that was encountered during the setup of the database as this problem took the longest amount of time to fix. Even though the coding for the delete process was correct, the query still simply did not work. When clicked, the correct two message boxes appeared one after the other asking the user to click OK. However, after both of these OK buttons were clicked, and the confirmation of the deletion of the data was accepted, the data on the database which was five years or older did not actually get deleted and disappear from the database which it was supposed to do. This problem with the system lasted for a significant amount of time until finally it was rectified by a classmate who had experienced a similar problem with their database system. However, there were also some good points with my database system. Firstly, the speed at which the database runs is a positive point. All of the processes in the database, through logging in and opening different forms runs quickly. There is never any waiting on the database, not even for a few seconds, apart from loading and this is because I have kept the database as minimal and simplistic as possible to ensure that exactly this would happen, as the hotel is always busy and the
Name: Matthew Brocklesby

Candidate Number: 7251

Hotel Room Booking Database
Evaluation

staff simply do not have the time to be waiting for the computer system. Another good point about the database is the ease of use. The databases is very use to use even for an amateur/novice user and a user would not require prior expert IT knowledge in order to use this database as everything is clearly signposted and also all of the posts on the system are labelled so a person should never get confused when using it. The layout of the interface page is also a good point about the database. This is the main page of the database and will most likely be the page that users see most of. This page is designed well with everything in perfect symmetrical order allowing for easy navigation around the page. The logout button is on this screen also allowing for the user to logout of the system, should they wish. Overall, this is a good page as it is the first page people see after the login screen and you could not get to other pages of the database without it therefore it makes a good first impression after the user logs in. All of the validations on the database now work. There were some errors along the way however.
Firstly, the format check for the first name encountered a difficulty as the coding was so precise that even if one character was incorrect then the validation method would simply just not work.
There were errors in making sure the coding was entered in completely correctly but after this was amended then the format check validation for first name started to work correctly. Secondly, the arrival and departure date validation checks for the format ensuring date was entered in the short form took a lot of difficulty to ensure the correct date format was used and also took a bit of getting used to once it was implemented. The rest of the validation checks, such as length check for telephone number, format check for Y or N for disabled access and length check for telephone number all ran smoothly as these were all relatively simple validation techniques that could be simply understood and did not require too much difficulty when fitting them into the database system. If the hotel expanded, then I feel that the database would definitely still be able to cope. There is plenty enough processing power and memory with both the main hard drive and the external hard drive combined that would mean the database would have no trouble in dealing with an expansion in size, even by a considerably large amount. If another hotel was to open by the
Strathmore then they would use the exact same database as the one that is currently in use and they could be synced together i.e. customers may visit both hotels and therefore when they are at the new hotel their details could simply be loaded from the current database system and this would mean they would not have to sign in twice. The two hotels would need to link to share data and to ease and smooth the process for example if customers visit both hotels, also it would mean they would be able to share resources on the database and they would not have to create and setup a brand new system for the new hotel which could be expensive and time consuming. The database would be able to process the large amount of data if the hotel were to expand as the computer system has the necessary processing power if needed, so there would be no difficulties where this was concerned. The hotel would be able to cope with the demand and it could continue to keep adding customers and products/services to the database as the database at current is only taking up a tiny amount of storage space on the hard drive and there is plenty room for expansion. A new field would need to be added to the database in the booking table stating which hotel the customers were going to in order to avoid any confusion and to prevent the customers from becoming annoyed, if for example they were accidentally booked into the wrong hotel by the user of the database. This is an important field and time should be taken to ensure that this field would be implemented correctly. The hotel would be of the same size as the hotel currently has no plans to expand into larger hotel sizes.
Name: Matthew Brocklesby

Candidate Number: 7251

Hotel Room Booking Database
Evaluation

To improve further the database could be set up to send an automatic, instant confirmation of booking to the customer's email address when it is input into the customer form of the database system. At current, the only way the customer would know their booking had been confirmed would be going off the hotels verbal confirmation. However, in today’s world most customers would value an electronic confirmation email of their booking. I could provide a report for the booking confirmation emails in order to improve my database system further in the future.

Name: Matthew Brocklesby

Candidate Number: 7251