The final projects that I am choosing to do is the hotel guest interface application. This hotel guest interface application will be something that can be used in a hotel app. This would be an application that serves as the menu of the hotel restaurant and then the information inputted from the menu would be outputted to the kitchen for the order to be made. This application would make a much smoother interface for a hotel to do because there would be less call traffic for the kitchen and stuff, and it is a lot easier and smoother process for the customer side as well. This is an amazing project idea for hotels to have such an interface because they are swarmed with called daily. The niche of people that go to hotels are people from different places in the world, this application is beneficial to both the customer and staff because it will make communication a lot easier then on the phone. Some of the details and specifications that would be in this project would be to allow the guest to create a profile with an authentication number enter their room number and phone number in their room, add payment option. We would have the menu with prices, different configurations for meals and combos, and other instructions

Again it seems that most of you have had good progress with your work to this point.

Now that we know what the Activities (i.e. functionalities) of your system are to be, it is time to figure out how they will occur. The most basic of all thoughts in a system is the IPO (Input-Process-Output) that makes it up. Now that you have described what the system is to do (its Activities or Functionalities), you have described what the Processing of the system is to be. Given that, it is time to figure out what the Inputs will need to be to provide all that the Processing will need to have to do the Processing, and then figure out what will be done with the results of the Processing - the Output.

Inputs typically take one of two forms - something provided by an External Entity to the system, or some data within the system that has to be updated in some form. Likewise, Outputs typically take two forms as well - something provided to an External Entity of the system, or some data that is written or re-written to some data store within the system.

So, now it is time to define what these Inputs, Outputs, and Data Stores will be. Often these are referred to as Forms, Reports, and Files within the system's Database. Thus, the next step is to identify all of these Inputs, Outputs, and Files, in a manner that is detailed enough for one to know what the data elements will be within each.

One way of going about this is to identify each individual activity, and then note what data must go into it, and what the system will produce via its actions performed wtihin the processing activity. If this sounds like a Data Flow Diagram, that is entirely correct! Reall that a DFD contains Circles (Activities), Squares (External Entities - providers or receivers of data), Open-Ended Rectangles (Data Stores/Files), and Arrows (Data Flows). Always accompanying a DFD should be Pseudocode for each Activity, a Notation of all the Data Elements (fields) within each Data Store, and finally a notation of what Data are being transferred by each Arrow (i.e. data flow).

A Data Flow Diagram is the single best graphic tool for illustrating what the system is doing and how it is going about doing it. So, your biggest challenge so far is this next assignment - create a DFD for your system. The DFD should have two parts to it, first the Context Diagram, and second Level-0 Data Flow Diagram. And as all DFDs should have, each Level-0 Activity (circle) within the diagram must have a separate listing of its Pseudocode (sometimes referred to as Structured English), and each Data Store (file) must have all the data elements listed that it contains.

• Based on that which is noted above, this Assignment requires the completion of a Data Flow Diagram for your system. Note that for purposes of this assignment, Data Flow Diagram means both a Context Diagram and Level-0 DFD of your system. Recall that each Activity must contain Pseudocode for that Activity, and that each Data Store much be identified in terms of its contents (i.e. fields within it).