Question

General Instructions

In this project, you are going to work as a system analysts and perform various analysis & design activities for a new information system. To begin with, you identify an information system that you plan to design. Come up with a system that can be useful in your daily life, organization, or that you can sell to another company. Examples of systems include online order system,

Deliverables

You must submit a single document (professionally formatted) containing the followings:

1) System description

Document the goals of and need for the system, and how the proposed system can help the organization

2) Requirements document

A complete list of functional requirements

3) System design diagrams

Data flow diagrams (including context and level-1diagrams)

UML use case diagram

UML activity diagram

Answer 1

System Description:

This case study looks at the problem of setting up a fast food restaurant. The basic problem in the food service industry is that restaurants are not realizing efficiencies that would result from better applications of technology in their daily operations. Every fast food has counter where you can place your order and then make the payment. So every fast food needs an employee for taking the order and processing the payment. Labor rates are increasing every now and then and it is difficult to find employees in the middle of the highway, hence to solve this problem we plan to design a "Self Served Fast Food System."

This self-service fast food restaurant will be equipped with a user-friendly touch screen, a credit/debit card reader, and software for completing the process at the backend. For this system there will be a system administrator who will have the rights to enter the menu with their current prevailing prices. He/she can enter anytime in the system by a secured system password to change the menu contents by adding or deleting an item or changing its price.

Now when the customer enters the restaurant, he will place his order with the help of the touch screen using the intuitive graphical user interface, right from the selection of language till the payment confirmation. He will select from the food options according to his choice and the system will display the payment amount he has to make once he has finished with his order. He will have the option of paying the bill by cash, debit card or a credit card. The user will slide his card and the system will check for the validity of the card and the payment will be made. A receipt will be printed containing the order number and the order will be sent in the kitchen for processing.

The purpose of this analysis is to demonstrate the extent to which high-level systems concept and UML notation/semantics can be used to describe the functionality of this system. This study lays out a framework for a new system to be developed and brought to the market for maximum use. The following issues, which are useful in performing a detailed analysis of the system, will be addressed in this study:

1. What should the system do?
2. What are the systems requirements?
3. How does the system work?
4. Can the system work?
5. What objects should be chosen and each of the subsystems functionality?
6. How should the object/subsystem interact?
7. How to verify and validate the system?

Functional Requirements:

As can be seen in the system model diagramed above, each of the three system components essentially provides a layer of isolation between the end user and the database. The motivation behind this isolation is twofold. Firstly, allowing the end user to interact with the system through a rich interface provide a much more enjoyable user experience, particularly for the non-technical users which will account for the majority of the system’s users. In addition, this isolation layer also protects the integrity of the database by preventing users from taking any action outside those which the system is designed to handle. Because of this design pattern, it is essential to enumerate exactly which functions a user will be presented and these functions are outlined below, grouped by component.

The Web Ordering System

Users of the web ordering system, namely restaurant customers, must be provided the following functionality:

• Create an account.
• Manage their account.
• Log in to the system.
• Navigate the restaurant’s menu.
• Select an item from the menu.
• Customize options for a selected item.
• Add an item to their current order.
• Review their current order.
• Remove an item/remove all items from their current order.
• Provide delivery and payment details.
• Place an order.
• Receive confirmation in the form of an order number.

As the goal of the system is to make the process of placing an order as simple as possible for the customer, the functionality provided through the web ordering system is restricted to that which most pertinent to accomplish the desired task. All of the functions outlined above, with the exceptions of account creation and management, will be used every time a customer places an order. By not including extraneous functions, I am moving towards my goal of simplifying the ordering process.

Menu Management System

            The menu management system will be available only to restaurant employees and will, as the name suggests, allow them to manage the menu that is displayed to users of the web ordering system. The functions afforded by the menu management system provide user with the ability to, using a graphical interface:

• Add a new/update/delete vendor to/from the menu.
• Add a new/update/delete food category to/from the menu.
• Add a new/update/delete food item to/from the menu.
• Add a new/update/delete option for a given food item.
• Update price for a given food item.
• Update default options for a given food item.
• Update additional information (description, photo, etc.) for a given food item.

It is anticipated that the functionality provided by this component will be one of the first things noted by the restaurant user, as they will have to go through it to configure their menu, etc. before beginning to actually take orders. Once everything is initially configured, however, this component will likely be the least used, as menu updates generally do not occur with great frequency.

Order Retrieval System

                Of the three components, the order retrieval system is functionally the simplest. Like the menu management system, it is designed to be used only by restaurant employees, and provides the following functions:

• Retrieve new orders from the database.
• Display the orders in an easily readable, graphical way.
• Mark an order as having been processed and remove it from the list of active orders.

Dataflow Diagram :

Usecase Diagram :

Activity Diagram : For making payment

Activity Diagram for reading order :