Introduction The restaurant information system will capture aspects of the diner, bar staff, kitchen personnel and management personnel. This paper will assess the information systems that are needed for the restaurant. It will also identify the objects and the classes that are required in a given system. In a restaurant, there are different use cases that are encountered. These use cases play a role in the whole system.
Some of the use cases include staff, departments, and the various objects that are found in the system. The relationships that exist in this system make things to work well. With automation of systems in networking, there is a need to ensure that proper analysis is done to achieve the best system that will solve the problem that is given. A restaurant information system spans a wide area because of the staff that is working on the system. This system will also enable clients to log in to the system and make the necessary reservations in the system. This is the reason as to why it spans a wide geographical area.
All this information should be captured in the system. The scenario that is presented here entails a system that has a bar, and a normal hotel system. The food served is varied and the drinks are also as varied. There are various actions and verbs that will be used to represent various issues in the system. The nouns that are seen in the system include order, request, book, and fill. These represent actions that are undertaken in the system.
Use case Nouns for the case The identification of the nouns which will be used to get the objects is as follows: Bar- this is not relevant in our case. Bill - this is taken to be a class Completion indication - this is taken to be the attribute of Order Dessert - this is an attribute and also could be taken to be together with meal Diner - this is taken to be a class Discount - this is also another class which can be regarded to be inheritance with bill Drinks - this is regarded as class and can be taken to be together with bill Kitchen - this is not necessary and is irrelevant in our case Kitchen staff - this is a role and in our case is the system user Meal - this is another class which could be inheritance with order Main course- this is an attribute and could be an inheritance with meal Management - this is role and is one of the system users Money - this is an attribute and it could be taken to be an inheritance with payment Order - this is a class Orders - Redundant - this is the same as the order Payment - this is another class Restaurant - this is not relevant as it is regarded to be too general Screen - is out of system as it is an operation Specials - Attribute - can be taken to be an inheritance with meal Starters attribute - this is taken to be an inheritance with the meal Statistics - this is the output of the system and it is an operation System - this is regarded to be general as we are trying to model the classes of the system Table - this is a class Tables - Redundant - the same case with table Terminal - Redundant - is the same as the screen Waiter - this is a role and is the user of the system Waiters - Redundant - this is regarded to be the same as the waiter. Object description and their attributes Waiter - this is the object that is tasked with taking orders that have been placed by the client. These objects will make use of the system to know the availability of given dishes. They will also make use of the system to know the status of the food that is if they are ready to be served to the diners. After the diners have had their meal, the waiter will also make use of the system to have the meal printed and also enter the payment details (Dines 2006).
Attributes The attributes of the waiter object include: name, employment ID, address, job title, age, PIN. Kitchen staff - this object will make use of the system to view the orders that have been placed for them to serve and will use the same system to inform the waiter that the meal is ready to be taken for serving. Attribute The attributes of the bar staff include name, employment ID, address, job title, age, PIN. Bar staff - They will make use of the system to look at the orders and inform the people concerned if the order is ready to be served. The attributes include name, employment ID, address, job title, age, PIN. Management - this is the senior-most object and will make use of the system to get eth statistics that have been achieved and will print the results.
The attributes include the job title, name, employment ID, address, age, PIN. Diner - this object does not make use of the system. The object is seen to be outside the organization.
Dines, B 2006, Software engineering 3: Domains, requirements, and software design, Birth " user, Basel.
Leffingwell, D & Wid rig, D 2003, Managing software requirements: A use case approach, Addison-Wesley Professional, London.
Vult, S 2007, 'Pro to software engineering', Computerworld, vol 4, no.