0829687February 112009This assignment consists of a Scenario, Analysis, System Investigation, Design Phase, Summary, Evaluations,And Conclusions.Work Based Project WorkshopSubmission date 13th May 2009<br />Acknowledgement <br />I would like to acknowledge and show my appreciation to the following people who have made the completion of this project achievable: I would like to thank Juliet Alfred Lewars for her patience and guidance throughout the course duration. Her vital encouragement and support has helped me through this course.<br />I would also like to thank my family for the constant reminders and much needed motivation. <br />Abstract <br />Raj Doot of Downe is a successful Indian restaurant that has a lot potential, however recently they have been experiencing a number of problems with their booking system which has affected their restaurant and therefore it has affected the profit. Manager’s intentions are clear on what action he wants to take. He has decided to put all this in a professional’s hand, and wants it completed within a time limit.<br />Contents<br /> <br />Project Plan.................................................................................................5-6<br />Introduction………………………………………………………………………………………….........7<br />Project Outline………………………………………………………………………………………….…..8<br />System Request ………………………………………………………………………………………….…9<br />Case Study………………………………………………………………………………………………..….10-11<br />Methodology Models………………………………………………………………………….……….12-16<br />Comparison of Tools………………………………………………………………………..……………17<br />System Analysis……………………………………………………………………………………………..18-21<br />Fact Finding……………………………………………………………………………………………………19-21<br />System Design………………………………………………………………………………..................22-28<br />Use Case Design…………………………………………………………………………………………..…23-24<br />Class Diagram (UML)………………..……………………………………………………………………25<br />Relationship Generalisation……………………………………………………………………………26<br />Entity Relationship Diagram………………………………….……………………………………..27-28<br />Implementation…………………………………………………………………………………………29-34<br />Evaluation………………………………………………………………………………………………….35 <br />Conclusion……………………………………………………………………………………………..….36 <br />IDTask NameDuration1Title This will cover the main topics that I will be doing in this assignment1 day2Project OutlineI will be looking at the project goal and objectives. 0-2 days3Scenario 0-8 daysReport on the scenario of the business requirements1 dayWrite Business System Requirements’1 dayInvestigate requirements for the development of an information system (software and hardware tools)2 dayResearch into the different types of System Lifecycle Methodologies2 daysConclude on the appropriate methodology for this project2 days4Analysis11 daysAnalyse the requirements of Raj Doot’s Booking System.4 daysAnalyse the existing Booking system. 4 daysReport on the results of the analysis of the System.3 days5System Investigation 10 days5.1. Prepare fact finding techniques1 day5.2. Prepare Interview content1 day5.3. Conduct Interview with Sponsor and Users1 day5.4. Record Interview results1 day5.5. Prepare observations 1 day5.6. Conduct observation process of the existing System 1 day5.7. Record observation results 2 days6Design Phase9 daysDesign Use Case Diagram2 days6.2. Design Class Diagram2 days6.3. Design Entity Relationship Diagram5 days7Creating the Database2-3 weeksImplement a prototype version of the Booking System1 weekVerify that the prototype meets its stated objectives4 daysInclude the screen design 3 daysConduct testing of the new booking system 1 week 8Summary At this moment I will be writing a brief statement that presents the main points in a concise form.3 days9EvaluationThis is where I will be comparing the pros and cons from my investigation. 1 day10ConclusionThis part of the assignment will have a decision made after careful consideration.1 day 11References2 days<br />Introduction <br />My responsibility of this project is to discover the exact problems the restaurant is going through, I am going there as professional database creator. I am not only going to solve their considered necessary problem but also do further investigation on the restaurant booking system and how they handle it when the restaurant gets hectic. <br />This is a time dated project, so I have to use time appropriately and consider anything that comes on the way. <br />Case study <br />In this section I am going to write about the introduction of my case study and the problem the restaurant is experiencing. Now, this section is going to cover areas such as a title, project outline and scenario. After writing all the key evidence I will write further to why this project is being undertaken. Due to lack of source the restaurant has, it has affected the business in various ways. <br />Analysis <br />After addressing the most important problem in the business, it is the moment where I have to carry out the analysis in a variety of ways to see if there are any further problems arising. To start with this procedure I will work on the fact finding, this is simply asking questions to staffs on a one on one basis for more complex answers. Thus I prepare myself, write couple of questions related to the restaurant and its booking operation it would assist me further to my system investigation. <br />Methodology models<br />This chapter will be covering the methodologies; I will be explaining to the readers the difference and similarities between the life cycles I have chosen. For example how each stage of operate - what has to be done in each stage, how each stage interacts with each other. Then I will conclude on the methodologies and select the model that is more convenient for the project.<br />Implementation <br />This chapter will be showing the screen shots of my outcomes from my project fact finding. I will be presenting screen shots of my work, feedback, questionnaire results and interview results how the new system is running, this will highlight the outcome of my project.<br />Evaluation <br />In this section I will be stating my opinion about the project. I will be talking about my personal experiences during the duration of the project, I will also be talking about certain subject matter that I could have done better.<br />Conclusion <br />In this section will be mostly talk about my personal prospect about the whole project and any problems that I may have encountered.<br />Foundation Degree Implementation Project<br />P R O J E C T O U T L I N E<br />**********************************************************************************<br />Course: Foundation Degree BISYear: 2009<br />Student No: 0829687Name: Shima BEGUM Email: Shimab23@Yahoo.com<br />Title: To analyse, design and implement a booking system for the Raj Doot restaurant.<br />Aim(s): To analyse the requirements of the Raj Doot’s restaurant booking system, design an appropriate booking system and implement a trial of the new system to corroborate analyse and design for trouble-free booking.<br />Objectives:<br /><ul><li>To analyse the Raj Doot’s booking system
Printer</li></ul>System Request – Create Database Project<br />Project Sponsor: Shima Begum, Manager of the Project<br />Business Need: This project has been initiated to increase sales by reaching new customers and to construct a consistent database for straightforward booking.<br />Business Requirements:<br /><ul><li>Hold the following information; customers’ booking details, staff contact number and address, and suppliers contact details. √
Work collaboratively √</li></ul>Business Value: <br />The business values their employees, without employees the restaurant would not be running as successfully as it is doing now.<br />Customer- they play a huge role to the business, with customers there is a business, and feedback how the restaurant could improve. <br /> Supplier value- without a good retailer, there won’t be quality dishes that stand out from the crowd. <br />Special Issues or Constraints: <br />There is a recommended constraint by the manager himself asking for a possible weekly reservation booking. <br />Case Study<br />Raj Doot of Downe<br />Introduction <br />Raj Doot is an extremely well-known Indian restaurant in Kent, customer focused, full service restaurant which relies on high levels of service to keep people coming through the door. Raj Doot was launched in the UK in the mid 1990’s it started as a local restaurant with limited serving of food and bookings, but since the restaurant was dealing with numerous demanding customers, the owner decided to expand the menu and the restaurant itself for more bookings. <br />By the early 2000’s the restaurant was very well recognized by customers all over Kent. <br />Raj Doot has a diary which keeps all the day to day information regarding the restaurant including; restaurant bookings, stock control, suppliers; customers contact numbers and customers who order takeaway.<br />Storing all the above information in a diary can be pretty exhausting, writing it down every time, changing times of bookings or even have to do cancellations. This can make the diary messy which can lead to misleading information and this will result into arguments and aggravation by the staff members and even customers.<br />Problem Areas<br />The problems began when there started to be more Indian restaurants around the area making Raj Doot less popular with the customers. Customers generally look for something inexpensive and more convenient. So Raj Doot was in a dilemma, they had to work something up to make it stupendous, original and convenient. The main problem areas the restaurant has are; booking customers in; staffs’ do struggle to handle more than one customer at the same time, they also find it frustrating to take orders from the phone and taking it in person at the same time, which can make both customers impatient. The restaurant also lets down customers who request for goods that are not available at the last minute, thus the restaurant needs a new updated database to hold accurate information on the product quantity.<br />Resolving the problem <br />Resolving the problem will not only cost money but it will require a lot of training for some of the staffs.<br />If all the bookings were to be done on the computer it would be less frustrating, it would be easier, faster, information can be viewed and sorted in multiple ways, information is more secure and duplicate data entry is reduced. <br />When comparing the pros and cons the decision is reasonably clear to get an updated database with the latest features. In order to do this, Raj Doot will have to hire a professional database developer.<br />Methodology <br />RequirementsDesignImplementationVerificationMaintenance<br />Figure 2Waterfall Development-basedMethodology<br />Waterfall model versus prototyping model<br />Planning <br />System prototype Figure 3A prototyping basedMethodologySystem ImplementationAnalysis DesignImplementation<br />What is a methodology model?<br />A methodology model is part of a systems development life cycle (SDLC), this allows the systems analyst to identify the business situations and recognizes prospective improvements, and designs an information system to implement them. <br />There are a variety of SDLC’s, which have different ways of operating. There are structured methodologies, RAD methodologies and Agile methodologies; they all have their differences, which is why I have narrowed my preferred models to two. <br />Both methodology models will include the following; <br />Feasibility Study; the intended project, determines to have a booking system at any cost as this would have an effect on the business once after the successful completion. It desperately needs a new model because it lacks in inputting detailed information on the subject of the customers and reservations. The existing system writes over other scheduled dates when it does not have enough space to write and this happens regularly. On the whole this creates confusion. Some staff would not be able to familiarise themselves to the system due to lack of knowledge of the application and this could cause risks to the system.<br />The key priority is the users must find it user friendly, easy, and basic to use as most of the staffs has never used a computer.<br />System analysis; this part of the project is to understand the process of the entire process, this is where the software structure and its lay out are defined. Analysis and design are very crucial at this point, where the development process is in occurrence, any error arises may be costly to solve. So to avoid any of those errors I will do investigation on the system this would be asking questions relating to the system to the staffs and customers also a survey to broaden my findings.<br />Design; after examining the system analysis I will then move on to the designs where I will be drawing several diagrams to demonstrate this process. This would include creating the following diagrams; Use Case Diagrams, ER diagrams, Class diagrams etc<br />Testing; after successfully completing the system, the testing would be done in a manual test checklist.<br />Implementation I intend to present the project by either using a waterfall/prototype model. <br />Maintenance this should be done by regularly checking the facilities these facilities could be voltage management, contingency plans. <br />Ability to Develop SystemsWaterfall (fig 2)Prototyping (fig 3)With unclear user requirements.Poor Excellent With unfamiliar technology Poor Poor That are complex Good Poor That are reliable Good Poor With short time schedule Poor Excellent With schedule visibility Poor Excellent <br />Figure 4 <br />The two methodologies that I will be discussing are Waterfall model and Prototype model and only one of them is going to be used for this project.<br />I have chosen a Waterfall Development model which does sequential software development process and a Prototyping model which does incredible quick process.<br />First I will begin with the Waterfall Development model; is an original structured design methodology that is still used today. It has all the attributes for a typical methodology. It is the first model that has been highly successful by business users.<br />Moving on to Prototyping, Prototyping based methodologies stages are done as one, repeatedly running in a cycle until the system is complete. This system has been designed to do three main functions which are analysis, design and implementation. After completion of the routine, it immediately works on the system proto-type; this proves a minimal amount of attributes which makes it faster to provide a system for the users to interact with.<br />Figure 4 shows that both models have qualities that one another do not have, all the abilities listed are important to a methodology model. <br />Prototyping shows its highest ranking is “excellent” whereas Waterfall is only “good”. However there are abilities that both contrast on, so I have to take in account which abilities would be most important to the system.<br />The similarities <br />They both have are they proceed in sequentially from one phase to another, which is good; I would want something to work in a sequential order, they also are easy and basic to operate which will hugely benefit the users especially when they don’t have much knowledge on how to operate systems. They also both contribute to the same functions in similar order.<br />All together it is a very simple model to implement and needs very few resources to implement.<br />The Differences<br />Unclear user requirements, Waterfalls’ user requirements are poor, because of the unclear system requirements, it is difficult to understand them by talking about those, users normally need to interact with technology to understand what the system can or can’t do and how to best apply it to their needs. However, Prototype models are usually more suitable when the user requirements are unclear because they provide prototypes for users to interact with early in the SDLC. <br />Short time schedule- Waterfall is not designed to increase the speed of development, whereas the key benefit of a prototype it is, it is not much of a benefit when the user does not know how to handle the system, as this would create risky problems.<br />Schedule visibility- one of the supreme challenges in system development is knowing whether a project is on schedule, where as Prototype have many important design decisions earlier in the project to help project managers to be familiar with the risks factors and keep expectation in regular checks. <br />The differences of the models are; waterfall model you cannot go to the previous stage whilst in operation, whereas with the Prototyping you can, now given this opportunity this would be a fine way of going back to amend any bits of the system. Prototype also does a special function called “system prototype”, this begins operating once the completion of the three main functions are done, making the operating system faster to proceed with the tasks, whilst Waterfall does not offer any kind of these stages, that would make the process faster and consistent. This overall makes the prototype model faster to operate with. <br />Advantages of a Waterfall<br />The advantage of Waterfall is that it is beneficial, because its user friendly, it is easy to use without having any risky problems that could endanger the system. Waterfall is reliable, because it carries out a careful analysis and designs stages to test different approaches through before completing the design, complex, a traditional structured design can deal with complex systems.<br />Advantages of a Prototyping <br />Whereas in Prototyping users can use the system and it gives you appropriate criticism about errors that may occur. Furthermore Prototyping ensures the sure requirements are clear, because they offer prototypes to interact with early in the SDLC.<br /> <br />Disadvantages of a Waterfall <br />Waterfall does not solve the arising problems during the operation instead it completes all the stages of the model and then at a later stage it resolves any problems for instance if any error occurred at any stage of software development, it can’t be corrected in that build, this is time consuming and could affect the success rate of the software development. <br />Disadvantages of a Prototyping<br />The drawback on Prototyping model is that its fast-paced system releases challenge attempts to carry out careful, precise examination. Prototyping involves in creating separate requirements/functionality, and refining it over time as requirements become clearer. It is not reliable or complex. <br />Conclusion <br />After comparing both models, I have gathered that figure 2 would be more suitable for the project than figure 3; the reason for this decision is the ability Waterfall offers is more beneficial to Prototyping. <br />I believe waterfall would be suitable for this system as it is user friendly, complex and reliable. Not much training would be required as it would be for figure 3, the abilities Prototype offer is not much necessary for the system as it is just a basic design for now.<br />I will have to go with figure 2; my reasons are; it is straightforward to use, and less training required. It would be so much simpler for the users and would feel much more relaxed whilst using it. These things are more important than couple of additional stages because when being contacted by a customer the user has to be fully confident to use programs in order to follow up the customers’ requests. <br />But the question is will the staff be able to provide the right system maintenance and keep up with the regular tasks in order for it to do all its tasks. Some employees never used a computer before and it would necessary to train them up.<br />References<br />Dennis, wixtom, Roth (2006). Systems analysis design. United States of America: hermitage publishing services. 10-20, 25-30. <br />http://www.allinterview.com/viewpost/35159.html <br /> http://articles.techrepublic.com.com/5100-10878_11-6118423.html?part=rss&tag=feed&subj=tr <br />http://www.buzzle.com/editorials/1-13-2005-64082.asp <br />http://www.investmentrealestateromania.eu/the_feasibility_study_unde_the_sop_iec_pos_cce <br />Comparison of Software Tools<br />Micro Soft Excel is mainly used to store data for business purposes and to compile worksheets, they work completing differently and for different purposes when it comes to their full potential. Its main priority is to work out calculations between cells also this could be for business purposes such as working out wages, tax payments and so on. <br />However, Micro Soft Access is built to store and organise information on the database which could be amended. There are different ways of viewing specific data from the database; this could be running queries, forms, reports, and switchboards. The best thing about Access is you can hyperlink any documents on to the switchboard if you want to refer to any work that is in associated with it, so the user will have more detailed information. The drawback of Excel is that the usage of this software is limited and you can’t further your creation of documentation.<br />After the careful consideration I have chosen to work on Micro Soft Access as this meets my needs more than Excel can offer, it would be more suitable for the system as it is tailored to do what the system requires. <br />This part of the project is fact finding and this would consist of Interviews and surveys.<br />This part of the project is to solve the problem in a suitable way. I have to gather all the required information to go on to the next stage; this could be only done after I do my fact findings. <br />Questions StaffWhen booking customers in, how long does it take you?It depends on how many bookings there are on that day, because it gets a little messy when the day has already bookings. In general it takes about five minutes.How do you use the existing system? We use a booking diary; we use a pen to write. We also have to flick through the book to look for cancellations.What do you keep in the current system?We keep all the necessary information regarding the customer/booking. I.e. name, address, time/date, number of seats, occasion.Do you struggle answering telephones and dealing with customers at the same time?Yes a lot of time it is quite frustrating trying to book customers over a telephone which takes longer to do In person along with having customers waiting to be served at the same time can be demanding.What is it about booking, makes you nervous?The customers staring at me with irritation.What improvements can you suggest to the manager for booking?Definitely a computer, it is a must have item for business.<br />QuestionsCustomersHow long have you waited to reserve a table?Not that long about two – five minutes.Do you think they could have done it faster?Possible yes, however they did have other customers waiting to be served. Did you have any problem with booking before in here?In fact last week I had booked a table for four and when I went there they said there were no booking for that day. But fortunately they had a vacant table and apologised for the inconvenience. What do you think Raj Doot can do to improve their customer service?Raj Doot is extremely popular with their customers and to keep them coming I think they should consider using a database for future bookings.<br />Interview 1Interview 2<br />Figure 1<br />rightbottomThis survey was completed by our regular and new customers. This visibly shows the booking lacks big time. <br />Evaluation <br />The database has loads of improvements compared to the traditional way of conducting the business. 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. It also can be viewed in forms and reports for easier view of the sum of the profits of each week or month. <br />All the tables will have their own unique identification (ID) for each record based on the business requirements, for example; the product table will be advantageous because it will have all the product listings with its own ID number for a straightforward reference, such as, Prod_01. In the same row for that product identification, it will state the product description, the product price, etc. This will save time and lose all the frustration that staff usually has when booking an appointment for the customer. 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 is more, the customer table is brilliant to store all<br />The regular customers’ details in i.e. name, address, contact number etc for future reference. <br />Conclusion <br />After gathering all the information from the interviewees it was a confirmation to where we are going wrong.<br />Staffs has had enough of embarrassment when asked to find a specific date when a customer requests for it or reservation seating’s in the booking diary while a customer is waiting for response.<br />There are a lot of disadvantages on using a booking diary; <br /><ul><li>You must write clearly and quickly and also very neatly, because it is a manual booking in system.
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.
Try to keep extra room for the cancellations. </li></ul>Now taking in all the above pointers, it is now clear why the restaurant is losing out on making profit. Database would be the finest thing for the restaurant as it would benefit without a doubt. <br />It would be faster, accurate and consistent, and right now that’s what the restaurant needs. <br />The best way to do this is seek professional advice and then carry it out efficiently. <br />By doing this, it would allow us to discover more about our weaknesses.<br /> <br />This Part of the Project Will Consist of a; <br />Use Case Diagram-<br />The main purpose of a use case diagram is to show what system functions are performed for which actor. Roles of the actors in the system can be depicted.<br />Class Diagram- <br />A class diagram in the Unified Modelling Language (UML) is a type of static structure diagram that describes the structure of a system by showing the system's classes, their attributes, and the relationships between the classes.<br />Entity Relationship Diagram- <br />An Entity-Relationship Model (ERM) is an abstract and conceptual representation of data. <br />This method is mostly used for a database modelling; it is used to create a relational database.<br />Reference<br />http://en.wikipedia.org/wiki/Class_diagram<br />http://en.wikipedia.org/wiki/Unified_Modeling_Language<br />http://en.wikipedia.org/wiki/Entity_relationship_diagram <br />Arrive for dinner Create bookingsMake a complaint about the foodConfirm Tables reservationLook up availability on booking reservationsRequest for table reservation UML: Use-Case-DiagramCustomerStaff <br />New System<br /> <br />Cancel reservation without chargeCancel bookings Record complaint Uses <br />Users/Actor User Goal Staff Look up availabilityCreate bookings Update database CustomerOrdering/reserving table Order cancellationComplaint about service <br />Users’ Goal and Documentation of Use Case Diagram<br />Model: Project Management Date: Wednesday, April 04, 2009Time: 20:30Name: CustomerType: Actor Description: requests for a reservation for a specific time and date, customers can also cancel orders over the phone within 20minutes of order. They can also make complain about the service if not satisfied. Model: Project Management Date: Wednesday, April 04, 2009Time: 20:30Name: StaffType: Actor Description: has to check availability when a customer requests for reservation in person or on the phone, availability of the reservation requested has been recorded, updating the database when customers make a cancellation or complaint.<br /><ul><li>Occasion Name: stringAddress: stringTelephone: stringDate: stringTime: stringNumber of Seat: stringOccasion: stringPrivate/non-privateClass Diagram - Functions and Data of the System
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
Table Name: stringAddress: stringTelephone: stringDate: stringTime: stringNumber of Seat: stringOccasion: stringType of Table Relationships: Generalisation</li></ul>StaffManager Receptionist CookWaiter<br />Deposit Seats Occasion Time & date Booking <br />Entity Relationship Diagram PART 1<br />Records Includes HasMany S.ID StaffT.IDTable O.IDOccasion B.ID C.IDBooking S.IDC.ID Customer <br />Entity Relationship Diagram PART 2<br />S.ID StaffB.ID C.IDBooking S.IDT.IDTable C.ID Customer R.ID B.IDReservation O.ID T_IDO.IDOccasionRecords Many IncludesHas<br /> Implementation <br />1905019050<br />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?<br />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 <br />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<br />19050198120<br />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.<br />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 <br />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.<br />How users will benefit from it?<br />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. <br />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. <br />What improvements my database system brings in comparison to the old way of conducting the business?<br />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. <br />Conclusion <br />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. <br />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.<br />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.<br />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.<br />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. <br />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. <br />Overall I feel satisfied with my work I have done for this project and I hope this will make an impact on the restaurant.<br />`<br />