International Postgraduate Research Conference (IPRC)

Permanent URI for this communityhttp://repository.kln.ac.lk/handle/123456789/155

Browse

Search Results

Now showing 1 - 2 of 2
  • Thumbnail Image
    Item
    T-Moms for Restaurants
    (Faculty of Graduate Studies, University of Kelaniya, Sri Lanka, 2016) Medhavi, Y.A.U.; Wijegunasekara, M.C.
    The aim of this study was to identify the drawbacks of a restaurant order management system and suggest a solution. Several such systems were studied and it was identified that customers waiting time to receive an order is considerably high. This is because during peak hours the waiter staff is not sufficient and the service offered is not to the required standard. In addition, the paper menus can be flimsy, hard to navigate, and outdated. To reduce customer’s wait times, management must ensure sufficient staff to present during peak hours and that they are properly trained to provide excellent customer service. These staffing issues can lead to substantial costs for the business. As a result, the Tablet based Menu and Order Management System (T-MOMS) was implemented to resolve these problems using mobile devices. The T-MOMS contains four systems, a mobile application for customers and three web based systems for the admin panel, kitchen and cashier. The order is taken by a mobile device namely, a tablet placed on the restaurant table which acts as a waiter. The mobile application is started by a waiter by logging into the system and assigning the table number and a waiter identification. The waiter identification and table number are saved in the application until that particular waiter logs out. The mobile application has four subsystems namely, display subsystem, assistance subsystem, commenting subsystem and ordering subsystem. The display subsystem displays the complete restaurant menu by categories, special offers’ information and allows the customer to browse all the currently available menu items by category. The assistance subsystem allows the customer to call a waiter for any assistance needed. The commenting subsystem allows customers to create user accounts for adding comments and share experience on Facebook/Twitter. The ordering subsystem allows to select the desired items and make the order. Once the customer makes the order, first he will be able to view the order information that he has ordered including the payment with/without tax and service charge. After the customer confirms the order, the order is transmitted to the kitchen department via Internet for meal preparation. The kitchen web system displays all order information that are received from the tablets. This include the customer details, table number, the waiter identification and the details of the order. After the order is prepared, the waiter will deliver the order to the customer. At the same time, the cashier web system receives the details of the delivered order and the bill is prepared. The web based admin panel system allows the restaurant’s management to add/view/remove/ update menu items and waiters, view reservation information and their cooking status/payment status, update service charge/tax, viewing revenue information over a time period. The T-MOMS system consists of a central server and a database. All ordering and expenditure information is stored in a central database. Eclipse and PHPStorm used as the IDEs. Mainly used languages are HTML, JavaScript, PHP, JAVA, XML. The menu application is designed to be used on 7" tablets as well as it will be supported on smaller screen sizes. As future development, features such as restaurant statistics should be implemented, paying the bill directly through the menu application should be created.
  • Thumbnail Image
    Item
    'PATH FINDER' Application for android
    (Faculty of Graduate Studies, University of Kelaniya, 2015) Dasanayaka, D.M.N.K.; Weerasinghe, K.G.H.D.
    The population growth and technology development has increased traffic congestion in urban areas. If people can get traffic information before starting their journey, they can use alternative routes to avoid traffic instead of sticking in the traffic congestion. And also when it comes to long trips, it is better if the driver can roughly get an idea about how much of money will be needed to be spent on fuel. Our intention was to develop an android application which is able to find the best route between source and the destination, considering the traffic jam and the minimum distance. Additionally the proposed system will facilitate users to reach the nearest fuel filling station when fuel is running low by providing information about the fuel condition of the vehicle while they are driving. The traffic information forecasting has been done with the use of previous traffic count of selected route. Generally, prior data pattern labels have been used to train the Artificial Neural Network (ANN) to identify the traffic conditions. The shortest path is generated with the use of ‗Dijkstra's Algorithm‘. The challenge that we had to face was gathering data regarding traffic count in Sri Lankan roads at a given time because there is no proper way to collect traffic data. So we had to observe daily traffic count (vehicle count) in a selected route. We collected vehicle count during 10 days of period. According to the observation results we created simulated data set. Our total number of records was 388. In this case 70% of the data was used to train the network, 15% was used to validate and rest was used to testing purpose. The accuracy of the traffic prediction was 99.5% according to the results of data trained using ANN. Another challenge that we had to face was creating communication between neural network and the android application. To transfer data between JAVA program and the MATLAB neural network we had to use transferring medium. So to overcome this challenge we used TCP/IP socket communication which has the ability to call Java directly from within MATLAB. This application follows client server architecture where MATLAB environment is the server and android application is the client.