iDine Information System for Vallée de Goût - Object Modelling

Running head: OBJECT MODELLING
iDine Information System for Vallée de Goût - Object Modelling
Name of the Student:
Name of the University:
Author Note

1OBJECT MODELLING
Table of Contents
Introduction................................................................................................................................2
Functional and nonfunctional requirements...............................................................................2
Use Cases...................................................................................................................................3
Use Cases identified...............................................................................................................3
Use Case Diagram..................................................................................................................5
Model Class Diagram.................................................................................................................6
Event-partitioned system model.................................................................................................6
iDine information system review...............................................................................................7
Object oriented methodology.....................................................................................................9
SDLCC phases for the iDine information system....................................................................10
Conclusion................................................................................................................................11
Bibliography.............................................................................................................................13

2OBJECT MODELLING
Introduction
The aim of this report is to discuss about the information system implemented by the
restaurant Vallée de Goût. It is very important to develop an information system for any type
of organization, the Vallée de Goût is no exception, and hence the description of an
information system named iDine has been included in this report.
The report will identify the functional and nonfunctional requirements of the
developed information system. Apart from this with the help of use case diagram the new
information system will be described. This also includes defining all the major cases and
actors involved with the system. Based on the developed system an UML class diagram will
be represented.
Functional and nonfunctional requirements
There are two types of requirements that are to be served by the iDine system which is
to be implemented for the Vallée de Goût organization. These are:
Functional Requirements:
The most important functional requirements are:
 Stock information: The system should be able to provide the information about the
stocks to the cooks so that they are able to take the orders accordingly.
 Automated ordering: The system should provide the customers with the opportunity
to make orders on the tablets so that the need for waiters are eliminated.
 Automated bill generation: The system should be able to generate the bill for the
customers and display it on the tablet as soon as they finish their meal.
Non-Functional Requirements:

3OBJECT MODELLING
The most important functional requirements are:
 Availability: The system should be available as long the restraint is open.
Unavailability during the hours that the restaurant is open would result in customer
dissatisfaction and decrease in business efficiency.
 Usability: The system should be made usable for the customers and it is to be made
sure that there are functions implemented in the system for the customers who are not
very apt with using technology.
Use Cases
Use Cases identified
The use cases for the system, which have been identified in this report, are described
in the table below:
Use Cases Description
View Menu The customer would be able to view the menu on the tablet which
has been provided to them.
Make Order The customers would be able to make an order from the tablet that is
provided to them.
Make Additions The customers can make additions to the orders which are already
placed by them.
Call Waiter The customers can call the waiter with the call waiter button
provided to them.
Send Waiter The headwaiter would be sending the waiter to a particular table
when they receive a notification that a customer is looking for a
waiter or the food is ready to be served to a particular table.
Take Orders The waiter would be taking orders from the customers who are not