cobalt-restaurant

byPuskar Acharya

2. Client Background Gokyo Bistro is a popular restaurant located at Jhamsikhel, Lalitpur. They have a very refreshing ambience with the provision of both outdoor and indoor dining. Recently they have been facing problems in their regular operations of table arrangement and order. There has been a massive surge in customers nowadays. A lot of customers have to return due to maximum occupancy. Also, a lot of customers have increased asking for home delivery. So, they are looking for an online system that can manage all these operations. Assuming you and your team have been approached for this project. You are required to carry out Object Oriented Analysis and Design for this project for below given specifications. DETAILED SPECIFICATION The proposed system is to have following functions 1. Login and Registration The system should have 3 types of users. Admin, visitors and members. Admin and Members can login with their respective credentials. 2. Book Table Visitors/Members can check the availability of tables and reserve the table for a particular date/time. 3. Set Beverage choices Though not compulsory, while booking, visitors can set the expected beverages choices they might prefer from the available list whereas premium members can reserve their wine/whiskey choices. 4. Payment There is a requirement to pay 1200 advance in order to reserve the table. Reservation can be cancelled before the final day whereas in case the reservation is cancelled on the very day, a fee of 500 is deducted from advance before returning the amount to the visitors/members. 5. Generate Report Admin should have a facility to generate the financial report. An advanced mechanism is needed for admin to predict the revenue for further years along with the recommendation of menu items. 6. Bill Generation There should be the privilege to generate bills for admin and generate receipts. 7. Order placement Members can place orders for food and beverages with an option of home delivery. Once again payment can be made online as well. 8. Update Menu Admins can add menu items, delete and update menu items. 9. Rate the experience Visitors/members can rate the overall experience of food, staff's behavior , ambience and feedback can also be provided. 10. Post offers and schemes Admin should be able to post various special offers and discount schemes from time to time. Questions 1. Prepare a Work Breakdown Structure as a part of Scope Identification. Also prepare a Gantt Chart showcasing the schedule of work with a reasonably assumed timeline. But please ensure that the Gantt chart is based upon a methodology of your choice and the activities/tasks should be relevant to the methodology chosen. 2. Produce a Use Case Model for the required system – including a Use Case diagram, and High-Level Use Case Descriptions for each Use Case. For two of the Use Cases of your choice, produce Expanded Use Case Descriptions. Choose one of these expanded Use Case Descriptions to model Collaboration or Sequence diagrams, in 3, below. 3. Produce a Collaboration diagram or a Sequence diagram for the chosen use case description as mentioned above. 4. Draw an activity diagram for the use case description that hasn't been chosen for the Sequence/Collaboration diagram above. 5. Prepare a table comprising all possible domain classes from all the respective use cases. Produce an Analysis Class diagram showing the domain classes. Your Diagram should include at least 2 inheritance, 2 aggregation and 2 composition relation and should have necessary association and multiplicities showcased. 6. Several tasks such as analysis and design diagrams have already been completed. How do you plan to proceed further in order to complete the project? Briefly explain your plan in words. While explaining the plan, you are required to select a development methodology that you think is feasible for this project, and your explanation of the subsequent steps should be related to the methodology you have chosen. (Note: the further planning should compulsorily include following things: 1) Architectural choice. 2) Design Pattern. 3) Development Plan (that includes tools/resources/programming platforms that are going to be used and priority order of artifacts/features that you have planned tentatively. 4) Testing Plan. 5) Maintenance Plan. 7. Develop some design prototypes for the proposed system for features which are listed in detailed specification. (Note: the prototypes should cover the major features and at least 15 separate prototypes (UI) need to be shown.