CONTENTS Introduction 3 Client Background 3 Operations of Vu Sydney 4 Purpose and objectives 4 Scope and Exclusion 4 Assumptions and constraints 5 Deliverables 6 Schedule 6 Budget 7 Resources, roles and responsibility 8 Meeting schedule for group 8 References 9 Introduction: Online restaurant management system is developed to automate the activities of a restaurant. Restaurant is a sort of business that serve individuals with cooked food by chefs. The restaurant management framework is designed to improve services at a restaurant and to ease and benefit the customers. This management system can be accessed by the administrator, customers and employees. The administrator has the full access of system whereas the employees and customers has limited access. The employees by using staff login id can place orders of food for customers, book tables and take their payments and can also perform various other tasks according to set privileges by using the system. The customer can access the menu without becoming a member but for ordering food, reserving a table and making payments through system management framework they need to become members to avoid fake ordering and reservations. The system will have detailed menu with different dish categories and pricelist. As per VU Sydney it will be Regular (For all), Gluten free and Vegan further with subcategories such as starters, drinks, main course, desserts, add ons(refills) etc. This project is developed by keeping in mind the day to day difficulties in smooth running and management of business such as dishes turnaround time from kitchen, manual table reservation and manual order taking etc. This system will resolve such difficulties as well as the difficulties in managing the records where a customer place an order or reserve a table and later wants to change or cancel the order or reservation. So web based online restaurant management framework will help the administrator in managing his business and it will also ease the customers. Client Background: Vu Sydney is one of the most famous purely vegetarian restaurant opened four years back with a special focus on purely vegetarian customers. There is a huge population of purely vegetarian customer in Sydney. Because ofhuge popularity among targeted vegetarian customers it was facing long waiting time during dine-in due to rush at restaurant. To solve problem of long wait time and on customer demand it recently opened a new branch at Bella Vista. Now our client Vu Sydney has the problem to manage their restaurant business smoothly. They are facing problem in managing the changes in orders and also in changes or cancellation of online table reservations. The Vu Sydney wants such a system which can avoid wastages in terms of wrong order, changes in orders, confusion in table allocations due to cancelled or rescheduled reservations etc. So to manage all such tasks we are developing a system for VU Sydney. OPERATIONS OF VU SYDNEY: There is always a long list of tasks and operations in a business but here we will list only a few basic and important operations of VU Sydney which are as follows: • Provide purely vegetarian food having options for Gluten free and Vegan dishes. • Taking online orders. • Taking online reservations. • Staff timesheet and payroll generations. • Changes in menu and pricelist. • Introducing new seasonal dishes and taking them off after the season end. • Updating information about non-availability of particular dish and table reservations. PURPOSE AND OBJECTIVES OF SYSTEM: The main purpose of the framework is to help the administrator in handling the business. To help in reducing the staff cost. To avoid fake orders. To reduce order turnaround time by system based order placement instead of manual ordering. To avoid customer confusion regarding orders and table reservations. To help the customers in better understanding of dishes and clear idea about their prices so that they can place correct orders without any confusion. To provide information to customer about new entries in menu. To provide information to customers about promotional offers on dishes on special occasions. In nutshell we can say, the purpose of developing this system for VU Sydney is to enhance the services and information in order to make the business more successful and helping it in earning more profit. SCOPE AND EXCLUSION 1. The scope of the project will be able to fetch the target audience which consists of vegetarian, vegan and gluten free followers. 2. According to Han wen | junehee kwon (2017), Communication between and among customers with food allergies and food service staff has become aconcern in the restaurant industry. So the system will provide details about dishes and ingredients. 3. Customer and administrator can use this system. 4. Customer can access only limited information. 5. Administrator or manager will manage the whole system and edit the menu likeprice of the dishes, items, and the dishes that are currently not available. 6. The website provides knowledge about restaurant location map, background. 7. When special offers are going on, then customers can access to special meals available in the menu list for example seasonal dishes and occasional dishes. 8. Administrator can change the price of products and information as per requirements and admin can give permission to different accounts. 9. The main purpose of the project is to make web application in computer language so that it can be helpful for client to manage database and customers to see menu, place online orders and make reservations for tables. 10. Customers can reserve the tables on phone for 8 to 10 people. 11. Customer can make payments via PayPal, debit card, cash, credit card etcetera. 12. There is no delivery system, customer can give online order but have to pick up the order. ASSUMPTIONS AND CONSTRAINTS: Defining assumptions and constraints is the key component for any successful project. According to Rosemary Teresa Prunyne (2014) Once identified, these assumptions and constraints shape a project in specific, but diverging ways - assumptions bring possibilities, whereas constraints bring limits. There are few assumptions and constraints about the project is given below: ASSUMPTIONS 1. In this project, agile methodology and Gantt chart will be use to keep the proper track of database. 2. The project is assumed to be completed within a pre-estimated time frame and budget. 3. For the project satisfaction, there is proper meeting with the client at every stage of the project so that the proposed project satisfies the customer needs. 4. New technology, tools and techniques are used in the project so that it will be easier for staff members to use the website and understand the concept. 5. Staff to properly trained to handle the database of the website and any other technical advancements. 6. If minor error occur it can be possible for the client to fix that error by themselves. CONSTRAINTS 1. The budget described in the project is the main constraint. Although in the end the project can also face overbudget situation. 2. The specified time for project completion is also a main constraint. 3. The cost of the infrastructure, labor and errors are the limitation for the project. 4. Customers might lack interest due to poor communication. 5. Poor communication between project team members can clash the project . 6. Lack of technical skills among employees is a big constraint. DELIVERABLES 1. Firstly, filled a project allocation form in order to nominate supervisor and team members. 2. In the second delivery phase, by proper meetings with client and team membersrequirement list is generated for the project. 3. Project proposal is written which defined scope of the project, client profile, their operation and constraints etc. 4. Documentation is done for proposedproject . 5. Meeting the requirements of client and fulfilling their expectations and needs for the success of the project. 6. A technical communication document is also provided to user and administration which gives help to using a particular system. 7. Report will explain the analytical method and research design used in the study of the project. 8. In first phase only Menu access, Restaurant history and location along with contact details will be made functional in website. 9. In second phase other functions of website will be delivered such as order placement and table reservation etc. 10. In the last phase, the data analysis and implementation in the project is completed that comes with a proper website for client. SCHEDULE: Project Scheduling means, what are the stages of the project, number of days to complete each stage and number of staff members to complete the tasks of each stage. There are six stages to complete the project that are 1)Project Initiation and Planning: The main tasks of this stage are setting of objectives, defining the scope, determine a work breakdown structure. It means break the project into small and more manageable tasks and set the budget of the project. Selection of employee (to work in the project) is also done in project initiation and planning. 2)System Analysis and Design: There is a complete analysis of the system i.e. What are the requirements of the system. Basically, there are two types of requirements: User requirement, System requirement. After analysis, project becomes ready to be designed. Design means a description of the system which we have to implement in the next stage. 3)Implementation: Now, the system is implemented after System Analysis and Design. 4)Testing: In this stage, system is tested by showing whether the system meets its functional and non-functional requirements. System is tested with the real values from customers. 5)Evolution: After testing, if any change is required then system evolution takes place for the system maintenance. 6)Closure: Now, the system is ready to deliver to the client. TABLE TO SHOW PROJECT SCHEDULING: Stages Number of days Number of employee 1)Initiation and Planning 4 11 2)System Analysis and Design 7 14 3)Implementation 20 100 4)Testing 16 65 5)Evolution 4 25 6)Closing 3 22 BUDGET: Stages Number of hours per day Number of days Total hours 1)Initiation and Planning 6 4 24 2)System Analysis and Design 7 7 49 3)Implementation 8 20 160 4)Testing 8 16 128 5)Evolution 5 4 20 6)Closure 6 3 18 Estimated Cost to spend on each of the stage Stages Number of Employee Total hours Rate per hour Total cost 1)Initiation and Planning 11 24 $30 $7,920 2)System Analysis and Design 14 49 $30 $20,580 3)Implementation 100 160 $30 $480,000 4)Testing 65 128 $30 $249,000 5)Evolution 25 20 $30 $15,000 6)Closure 22 18 $30 $11,880 Total number of Employee needed to complete the project= 237 Number of days to complete the project= approximately 54 days Total Budget of the project= $784,980 RESOURCES, ROLES AND RESPONSIBILITY: In every project, it is very important to understand the roles and responsibilities of each person. The following table highlights the Resources, Roles, Responsibilities and Skills: Resources Roles Responsibilities Skills Amandeep Kaur Project Manager Management of project My SQL, WAMP Navjot Kaur System Analyst Analyze the system requirements phpmyadmin, Visual basic Monika moun Tester Validate the system My SQL, phpmyadmin, WAMP Ekta Assistant Manager Helps the project manager to manage the project Visual basic, My SQL Meeting Schedule For the group To discuss the project requirements, scope of the project, deliverables, assumptions and constraints, budget of the project, Resources, Roles and Responsibilities we organize weekly meetings. The following table depicts the information regarding the meeting schedule: Weeks Topic Date Time Week 1 Project requirements, Scope and exclusion, Deliverables 31-03-2017 5.00 pm Week 2 Assumptions and constraints, budget of the project 07-04-2017 5.00 pm Week 3 Resources, Roles and Responsibilities 14-04-2017 5.00 pm References: Cleland, D.L. and Ireland, L.R., 2006. Project management. McGraw-Hill Professional. Coleman, J.H., Joe, C.D.I. and Morgan, R.L., Coleman, James Hamilton, Davis, Ii, Joe Charles, Morgan and Richard Lloyd, 2000. Restaurant management system. U.S. Patent 6,088,681. Cho, C.S. and Gibson Jr, G.E., 2001. Building project scope definition using project definition rating index. Journal of architectural engineering, 7(4), pp.115-125. Conforto, E.C. and Amaral, D.C., 2010. Evaluating an agile method for planning and controlling innovative projects. Project Management Journal, 41(2), pp.73-80. Newton, P., 2015. Managing the Project Budget. pmtips. (2016). Defining Project Constraints. [Online] Available at: http://pmtips.net/blog-new/defining-project-constraints [Accessed 10 Dec. 2016].