System Design and Analysis for iDine Information System

Running head: SYSTEM DESIGN AND ANALYSIS
Assignment 2
Name of the Student
Name of the University
Author’s Note:

1SYSTEM DESIGN AND ANALYSIS
Table of Contents
1. Functional and Non-Functional Requirements:...........................................................................2
1.1 Functional Requirement:.......................................................................................................2
1.2 Non-Functional Requirement:...............................................................................................2
2. Use Case:.....................................................................................................................................3
3. Domain Model Class Diagram:...................................................................................................5
4. Event Partitioned System Models:...............................................................................................6
5. SDLC Model Activities:..............................................................................................................9
Bibliography:.................................................................................................................................12

2SYSTEM DESIGN AND ANALYSIS
1. Functional and Non-Functional Requirements:
1.1 Functional Requirement:
Make Order Directly: The customer must be able to place order directly through the table
top tablets. The tablets placed in the tables must have the information of in which table it is
installed and the menu of iDine.
Request Waiter: The system must allow the customers with zero technical knowledge to
request for orders. The request for waiters are shown as notification to the head waiter.
Make Order Through Waiter: The waiter must place orders for customers if they
request. The waiter will add the table number along with the order details.
Food Preparation: The system will send the order details to the kitchen after it is
confirmed. The ordered foods will be printed on a paper in respective kitchen areas. The cook
will prepare the food and ask the waiter to serve it to the table.
Payment: Each order must have a successful payment. For the customer satisfaction, the
system must accept payment through cards or cash both.
1.2 Non-Functional Requirement:
Security: The system will process the payment request and hold the details of cards. For
this reason, the system must protect the information from outside and inside security threats.
Each payment will be processed through many security layers. The data transmission will be
occurring through encryption and decryption technology.

3SYSTEM DESIGN AND ANALYSIS
Availability: The system should be able to serve its purpose as long as restaurant is open.
All the maintenance, installation and update related works will be done after the restaurant is
closed.
Usability: As the users will be experiencing something new, they must easily understand
how to use the system.
2. Use Case:
Figure 1: iDine Information System Use Case Diagram
(Source: Created by Author)
The iDine information system has the following actors.
Customer: Customer is the external entity of the system. Customer place order and make
payment.