Elaboration Phase: Functional and Non-Functional Requirements

Running head: ELABORATION PHASE
Assignment 2
Name of the Student
Name of the University
Author’s Note:

2ELABORATION PHASE
Table of Contents
1. Functional and Non-Functional Requirements:...........................................................................3
2. Use Case:.....................................................................................................................................7
3. Domain Model Class Diagram:...................................................................................................9
4. Event Partitioned System Models:.............................................................................................10
5. SDLC Model Activities:............................................................................................................11
Bibliography:.................................................................................................................................12

3ELABORATION PHASE
1. Functional and Non-Functional Requirements:
The functional requirement will state the behavior of iDine system. Each of the
functional requirement would associated with one behavior of system. The system functional
requirements starts user recognition and ends after generating reports. Operation of a system is a
loop and functional requirements denotes the features of the loop.
Ordering: Each of the tables will have an individual tablet. This tablet will be called as
tabletop tablet. Each of these tablets will have a digital menu installed within it through which
orders can be made. All these tablets will be connected to the main system through a wireless
connection. Each electronic device has a MAC address and this address will be the unique
identification number of the tablet. Each device will be assigned to a fix table. However, the
table number can be changed if the management wants. The customers will select foods that they
want to order through this tabletop tablet digital menu. They can also customize the order if they
want. Some customers are not able to understand how to use the digital menu so they prefer old
fashioned way of giving order. The customer will click on call waiter button and the head waiter
will send a waiter to take the order. The waiters will have a handheld device that will also have a
digital menu. No matter how the order is placed, the processes like preparing food, delivering
food and other processes is done same way.
Involve Waiter: The waiters are inalterable part of Vallée de Goût. No matter how much
technological advancement is introduced to the organization, the waiters will be needed to take
order and deliver food to tables. The waiter head will manage all the waiter related activities. The
waiter will make orders for the customers if they request. After the food is ready, the waiter will
serve the food to the customer tables. The head of the waiter will see the notifications of

4ELABORATION PHASE
customer requesting a waiter and order is being marked as ready. The head waiter will assign an
available waiter to take orders or service food.
Order Processing: The system will forward the order after it is confirmed by the
customer. These orders will have different food items. The system will categorize each of the
ordered food based on predefined conditions. The system will have information on which area of
the kitchen is dedicated to prepare which food. Taken as an example, different areas of kitchen
will prepare salad, sauce, soup and many more category of food differently. The system will be
connected to the printers in each are so that orders can be printed. This will allow the
organization to prevent any order related issue that used to occur due to bad handwriting of the
waiters. The cook will have a UI through which they can mark an order as ready. It is not
mentioned whether the cook can mark the status of preparing or not.
Login: The login is an essential security related aspect of any system. The login function
allows the system to verify a user’s access to the system. The login is the authentication feature
of the proposed iDine system. To login, every user must have a unique identification number and
a password. The system will employ a security measure for maintaining quality of the password
so that guessing the password cannot be possible for third person. The users will have login
credentials are waiter, waiter head, cook and management. The tabletop tablets will be logged in
to the system using the hardware MAC address. This way the system will have complete control
over who will access the system.
Access to Function and Data: The system will protect the data and operations by
implementing different authorization levels. Each of the user authorization level will determined
based on the user’s unique identification number. The system will allow a user to access
requested data or function based on the authorization level. This illustrates that the system will