Paperless Restaurant - Project Plan

Project Code

May07-14

Client Senior Design

Faculty Advisor

Dr. Manimaran Govindarasu

Technical Advisor Dr. Randall L. Geiger

Team Members

Chris Ford Sean McVeigh Obioma Ohia

Nichole Taylor Anthony VanSant

Submitted October 10, 2006

DISCLAIMER: This document was developed as a part of the requirements of an electrical and computer engineering course at Iowa State University, Ames, Iowa. This document does not constitute a professional engineering design or a professional land surveying document. Although the information is intended to be accurate, the associated students, faculty, and Iowa State University make no claims, promises, or guarantees about the accuracy, completeness, quality, or adequacy of the information. The user of this document shall ensure that any such use does not violate any laws with regard to professional licensing and certification requirements. This use includes any work resulting from this student-prepared document that is required to be under the responsible charge of a licensed engineer or surveyor. This document is copyrighted by the students who produced this document and the associated faculty advisors. No part may be reproduced without the written permission of the senior design course coordinator.

i

TABLE OF CONTENTS Page

LIST OF FIGURES ....................................................................................................................... iii LIST OF TABLES......................................................................................................................... iv ACRONYMS AND ABBREVIATIONS....................................................................................... v Executive Summary........................................................................................................................ 1 1 Requirements ............................................................................................................................ 1-1

1.1 Problem Statement ............................................................................................................. 1-1 1.2 Operating Environment...................................................................................................... 1-1 1.3 Intended Use and Users ..................................................................................................... 1-1 1.4 Assumptions and Limitations ............................................................................................ 1-1

1.4.1 Assumptions................................................................................................................ 1-1 1.4.2 Limitations .................................................................................................................. 1-2

1.5 Expected End Product and Other Deliverables.................................................................. 1-2 2 Proposed Approach and Statement of Work............................................................................. 2-1

2.1 Proposed Approach............................................................................................................ 2-1 2.1.1 Functional Requirements ............................................................................................ 2-1 2.1.2 Constraints Considerations ......................................................................................... 2-2 2.1.3 Technology Considerations ........................................................................................ 2-2 2.1.4 Technical Approach Considerations ........................................................................... 2-3 2.1.5 Safety Considerations ................................................................................................. 2-3 2.1.6 Testing Requirements Considerations ........................................................................ 2-3 2.1.7 Security Considerations .............................................................................................. 2-4 2.1.8 Intellectual Property Considerations........................................................................... 2-4 2.1.9 Commercialization Considerations............................................................................. 2-4 2.1.10 Possible Risks and Risk Management ...................................................................... 2-4 2.1.11 Project Proposed Milestones and Evaluation Criteria .............................................. 2-4 2.1.12 Project Tracking Procedures ..................................................................................... 2-5

2.2 Statement of Work ............................................................................................................. 2-6 Task 1 – Problem Definition................................................................................................ 2-6 Task 2 – Technology Considerations and Selections .......................................................... 2-7 Task 3 – End Product Design............................................................................................... 2-8 Task 4 – End Product Prototype Implementation ................................................................ 2-8 Task 5 – End-Product Testing.............................................................................................. 2-9 Task 6 – End-Product Documentation............................................................................... 2-10 Task 7 – End-Product Demonstration................................................................................ 2-10 Task 8 – Project Reporting ................................................................................................ 2-11

3 Estimated Resources and Schedules ....................................................................................... 3-13 3.1 Estimated Resource Requirement .................................................................................... 3-13 3.2 Estimated Schedule Requirement ...................................................................................... 3-3

4 Project Team Information ......................................................................................................... 4-1 Client.................................................................................................................................... 4-1 Faculty Advisor.................................................................................................................... 4-1 Technical Advisor................................................................................................................ 4-1 Project Team ........................................................................................................................ 4-1

ii

5 Summary ................................................................................................................................... 5-1 6 References................................................................................................................................. 6-1

Endnotes................................................................................................................................... 6-1

iii

LIST OF FIGURES

Page Figure 1: A representation of the end product and how each device will communicate. ............ 1-2 Figure 2: This shows an example of the interface on the handheld device. ................................ 2-1 Figure 3: This shows an example of what will be displayed in the kitchen. ............................... 2-2 Figure 4: Intel PXA27x Processor Developer's Kit ..................................................................... 2-3 Figure 5: Estimated Project Schedule .......................................................................................... 3-4 Figure 6: Deliverables Schedule .................................................................................................. 3-5

iv

LIST OF TABLES

Page Table 1: Evaluation Scores for Milestones Completion .............................................................. 2-5 Table 2: Personnel Estimated Effort Requirements For Each Task (hours) .............................. 3-13 Table 3: Other Required Resources ............................................................................................. 3-2 Table 4: Estimated Project Costs ................................................................................................. 3-3

v

ACRONYMS AND ABBREVIATIONS

WHOS Wireless Handheld Ordering System HDK Hardware development kit LCD Liquid crystal display GUI Graphical user interface PCMCIA Personal Computer Memory Card International Association VPN Virtual Private Network MSDN Microsoft Developer Network

1

Executive Summary In many restaurants when a server take an order of from the customer they must write it down and then enter it into a computer at one central location. The order is then printed out in the kitchen. When it is time to pay the server must go back to the central location and print out a copy of the customer’s bill. If the customer wants to pay with a credit card the server has to take the customer’s credit card back to this same central location in order to scan it in and then print the receipt. The current system waste a lot time because the server has to keep going back to one central location. It also waste a lot of paper since the order must be written down, printed in the kitchen, and final a receipt must be given to the customer. The purpose of this project is to develop a hand held system that can take the order while the server is stand at the table. It will then send the order directly to a screen in the kitchen. When the customer is done eating the server will be able to show the customer their bill on the hand held system. If the customer chooses to pay with a credit card the system will be able to scan the credit and print a receipt without having to leave the table. This system will reduce the time it takes for the server to enter order and settle the bill with the customer because the server will not have to leave the table as often. The system will also eliminate the amount of paper used because the only printout is the customer’s credit card receipt. The following report contains a description of the process that the May 07-14 group will use in order complete the project on time. It includes a section that addresses the following issues: Operating environment, intended users, assumption and limitations, and end product. It then lists all of the requirements and constraints of the project, including topics such as safety and testing. The last part of the report is a break down of the project by tasks and the expected amount of time for the whole project and for each individual.

1-1

1.1

1.2

1.3

1.4

1 Requirements To understand the problem statement this section will discuss the requirements that will be necessary to follow while developing the paperless restaurant system.

Problem Statement The purpose of the project is to develop a Wireless Handheld Ordering System (WHOS) to be used in a restaurant. The system will accept order information and send it to the kitchen while the server is standing at the table. The system needs the ability to notify the server when the order is done. When the table is done eating, the server will be able to display their bill and print off a final receipt that will be given to the customer. If they are paying by credit card the server will be able to swipe the credit card information using the WHOS. The system will be able to keep track of all orders taken each day. The solution will consist of a handheld device that will be able to communicate wirelessly to output screens in a kitchen and a central computer that will be used for recording all orders. How the device will be modeled will be by using a hardware development kit (HDK) based on the Intel PXA270. All inputs into the system will be done using a liquid crystal display (LCD) touch screen. Receipts given to customers will be printed from a small printer that will connect using Bluetooth communications. All the programming for the devices will be done using Microsoft Visual C++.

Operating Environment The product will be used indoors and outdoors, weather permitting. It will not be required to work in the rain or any other extreme weather conditions. It will be stored at room temperature in a dry place. Other wireless devices are possible sources for interference.

Intended Use and Users This product is intended to be used by servers in a restaurant environment. Customers will use the device to provide their electronic signature or pin number. Orders will be received in the kitchen where the cook will be able to view and arrange the orders. The product will be designed so it can be easily used by an adult. All parts of the system will be easy to learn with minimal amounts of training. The requirements for using this system are basic reading and writing skills.

Assumptions and Limitations To reduce the project to a manageable form assumptions and limitations are used to limit the project definition and scope.

1.4.1 Assumptions The following assumptions were made in regards to the product:

1. Similar products in existence – Experience will be gained by creating a similar device and integrating features that are not currently available with commercial systems.

2. Product will not be state of the art – Research shows that the resources are unattainable to make a state of the art product.

3. Since the prototype will be developed using an HDK it will not be handheld. The final commercial product can easily be developed from the prototype.

4. A maximum of 12 units will be used at once. 5. The maximum distance of transmission is within 10 meters (32 feet), about the range of

Bluetoothi. 6. There will be a maximum of 5 simultaneous transmissions. 7. Handheld devices are able to be recharged throughout the day. 8. Central computer is centrally located to maximize coverage. 9. Model can be developed into a handheld device.

1.4.2 Limitations The following limitations must be considered:

1. Wireless and Bluetooth distance 2. Power supply 3. Memory and processing speed 4. Size of monitor available in the kitchen

1.5 Expected End Product and Other Deliverables The expected end product is a model of the system that is ready for prototyping. The system will use simplified restaurant management software for demonstration. The following components will be available at the end of this project:

1. Handheld device – modeled on a HDK 2. Computer monitor – displays the orders to the kitchen 3. Wireless printer – compact and prints receipts 4. Central computer – keeps track of orders and makes updates to the system 5. Model – portrays final product

Figure 1: A representation of what the end product will be and how each device will communicate.

1-2

2 Proposed Approach and Statement of Work This section of the proposal addresses the components of the project that must be met in order to achieve a high probability of success. Also included in this section is a description of the overall functionality and the necessary tasks to complete the project.

2.1 Proposed Approach The following components are essential to the success of the project. In order to maintain a high probability of success, each component will be thoroughly analyzed.

2.1.1 Functional Requirements The following describes the functional requirements of the project:

• Handheld Device (Figure 2): The handheld device must be capable of wireless two way communication with the central computer, have a graphical user interface (GUI) and have data input and output functionality. This includes:

o Sending a customers order to the kitchen o Receiving notices from the kitchen o Sending order information to an “accounting database” on the central

computer o Receive menu customizations from the central computer o Display all menu information defined by software o Receive credit card information via a magnetic card swipe o Touch screen capabilities and support electronic signatures and pin entry o Communicate card information to the central computer for verification o Send receipt information to a Bluetooth printer o Stylus that allows easy navigation

Figure 2: This shows an example of the interface on the handheld device.

2-1

• Central Computer System: The central computer must be able to wirelessly communicate with handheld devices, track orders for the kitchen, and keep a database of orders. This includes:

o Receiving customer order information from handheld devices o Sending notices to handheld devices o Storing and updating “accounting database” based on order information

received and user input o Send menu customizations to handheld devices o Receive card information from handheld devices for authorization o Allow update of orders and change of order priority of the kitchen display

(Figure 3)

Item 1Option 1Option 2

Item 2Option 1Option 2

Item 3Option 1Option 2

Item 4Option 1Option 2

Figure 3: This shows an example of what will be displayed in the kitchen.

2.1.2 Constraints Considerations In the development of this project there are constraints to be considered. Each constraint will cause a limitation on either the design and/or functionality of the project.

• Communication: The Bluetooth devices can only communicate within a range of approximately 32 feet or 10 meters via open air.

• Funds: The project has limited funds. Purchases must reflect this constraint. • Mobility: The HDK is a stationary device, not a handheld device. We cannot

thoroughly test all criteria of handheld devices (size, power consumption, etc).

2.1.3 Technology Considerations For all components of the project, the following considerations will be used:

• Processing: The processing power and system foundation will be provided by a hardware development kit, such as the one seen below.

2-2

Figure 4: Intel PXA27x Processor Developer's Kitii

• Display: The means of technology used in displaying the information will be done

with a standard touch-screen that is incorporated into the HDK. The kitchen display will also be a touch-screen.

• Card reading: The technology used to accomplish card reading will be a magnetic card swipe that connects to the HDK via USB.

• Data input and system navigation: Data input and system navigation will be accomplished through the touch-screen.

• Printing: Printing will be done on a Bluetooth printer. • Central computer: A standard personal computer will be used to receive and display

orders in the kitchen. • Wireless communication: The system will send information wirelessly through a

wireless router. It will receive information via a PCMCIA card, which can be connected to the HDK.

2.1.4 Technical Approach Considerations To complete this project successfully, there must be a focus on each system and subsystem. There will be two systems: the WHOS-based system and the central computer. The WHOS-based system is composed of the following subsystems: LCD touch-screen, magnetic card swipe, Bluetooth, wireless card, and Bluetooth printer. The central computer is composed of the following subsystems: wireless router and kitchen-based monitor.

2.1.5 Safety Considerations To complete this project successfully there are some safety considerations that must be met. The system can not be a shock hazard to the user, so there can be no exposed electrical connections or wires. The system can not have any sharp edges or glass, because of the increased chance or injury if the system were to be dropped or if the glass was broken. Finally the communication systems must run at frequencies that are not known to cause any adverse health effects.

2.1.6 Testing Requirements Considerations Before demonstrating a prototype, all components, software, and subsystems must be tested thoroughly. Each component will be continuously tested throughout the development process to insure functionality. Software will also be consistently tested throughout its development to insure the prototype will give the user as few problems as possible. Any wireless or Bluetooth

2-3

2-4

components will also be tested in various settings to insure that the signal will not be compromised.

2.1.7 Security Considerations Wireless communications present a security concern. To resolve this issue, Virtual Private Network (VPN) server software will be installed on the central computer and client software will be installed on the HDK.

2.1.8 Intellectual Property Considerations There will not be infringement on any intellectual property rights. All of the components and applications will be obtained with the knowledge of the manufacturer.

2.1.9 Commercialization Considerations Commercialization considerations will be aimed toward the restaurant industry.

2.1.10 Possible Risks and Risk Management The possibility of losing team members is of notable concern, as illness, family emergencies, and other causes can create conflicts. There is also a concern with a member of the team not contributing sufficiently to the project. To best deal with said risks, there will be an emphasis on communication. Regular meetings will be held to discuss individual progress. In regards to the risk of failure caused by any technical issues that may arise, the members of the project team and faculty have much of the background knowledge needed to complete the project. There are outside resources available for consultation if needed. In the case that the proposed plan should not reach the stated goals currently proposed, the team has some ideas of other possible routes through which the project could be completed. If, for example, the hardware development kit does not providing the foundation needed, a Pocket PC could be utilized, the HDK could be opened and altered internally, or, if absolutely necessary, the necessary components could be built to achieve said goals. In order to make the project as technically successful as possible, a list of priorities has been developed. The first priority, for example, is to establish wireless communications between the HDK and the kitchen-based system. This is followed by other priorities and sub-priorities. This approach will insure that the most necessary functions will be developed successfully, with other more obscure functions added on only after the higher priority items have been completed.

2.1.11 Project Proposed Milestones and Evaluation Criteria This section lists the project’s most important tasks and the estimated date of completion. The evaluation criteria are based on the ability to complete the task within the estimated dates agreed upon by the team and the faculty advisor. For each milestone, an evaluation score will be determined based on the evaluation criteria and the scores from Table 1. At the completion of the project the scores will be averaged together and a final score of 85% or better will be considered a success.

2-5

Table 1: Evaluation Scores for Milestones Completion Exceeded/Met 100% Partially Met 40%-90% Did Not Meet 0%

• Hardware: Design and Implementation

o Evaluate all components to verify that each is working properly. Card Swipe is able to send and receive data to and from the WHOS. Printer is able to receive data and print receipts. Central Computer is able to send and receive data to and from the WHOS. WHOS is able to receive data from the card swipe and central computer

and send data to the central computer and printer. • Software: Design and Implementation

o Order Interface Confirm that the order interface is working properly. • The Order Interface must be able to receive orders that are inputted

through a touch screen and send orders to the central computer. o Billing Interface

Confirm that the billing interface is working properly. • The Billing Interface must be able to display the bill and allow the

customer to sign or enter a pin for credit/debit card transactions. o Database

Confirm that the database is working properly. • The Database must be able to store orders that are sent wirelessly

to the central computer. o Communications (Card Swipe, Printer, Central Computer)

Evaluate all components to verify that the system is working properly. • The Card Swipe must be able to communicate with the WHOS. • The Printer must be able to communicate with the WHOS. • The Central Computer must be able to communicate with the

WHOS. o Kitchen Interface

Confirm that the kitchen interface is working properly. • Kitchen Interface must be able to send and receive data to and

from the WHOS and allow the user to confirm when orders are completed.

• Model Design o Confirm that the model design is working properly.

All components must be communicating with each other, simultaneously, for the model design to be considered a success.

2.1.12 Project Tracking Procedures Objectives for the project were stated at the beginning of the semester. Each member of the team has been given specific objectives and a timeline to follow. A project layout for the life of the project has also been created and should be followed for the remainder of the ongoing project. Weekly meetings will be conducted to ensure that the schedule is being held to. If at any point

2-6

2.2

the project is found to be behind, the team must take the necessary steps to put the project back on schedule. This may include the reevaluation of the timeline, to ensure that the current goal is feasible in the time allotted. If the goal is found to be unattainable, changes to the overall timeline of the project must be made. Additionally, if more personal effort is required to complete the current task, team members with lighter work loads may be reassigned to help complete the task that is behind schedule.

Statement of Work This outline will show the tasks throughout the project. There are many objectives that must be completed. The plan is to work through each task and subtask as scheduled in order to produce a product that meets the expected results.

Task 1 – Problem Definition Subtask 1a - Problem Definition Completion

Objective: Develop a complete problem definition Approach: The team discussed the problem and expectations with the faculty

advisor. The faculty advisor has approved the direction in which the project team is approaching the project.

Result: The team has clearly defined a possible solution in written format for advisor and client approval.

Subtask 1b - End Uses Identification

Objective: To identify the end use(s) for the project. Approach: The team has received direction from the client on who would use the

system, as well as how it would be used. Result: The team has clearly defined possible uses for the end product.

Subtask 1c - Constraint Identification

Objective: To identify the constraints of the project. Approach: The team will discuss the constraints with the project advisor. The initial

constraints are listed in the constraints section Result: The team will clearly identify the constraints expected of the end project.

2-7

Task 2 – Technology Considerations and Selections Subtask 2a - Identification of Possible Technologies

Objective: To identify possible technologies to incorporate into the end product. Approach: Existing technology will be utilized whenever it is possible to do so. For

example, a simple card swipe with a USB interface is a technology the team plans on incorporating into the system. This will avoid the cost and time involved with developing a reader, which would be a pointless task, considering this technology is cheap and easy to find.

Result: The team has identified the technologies to be implemented into the end product. Possible technologies have been determined be researching the restaurant market and finding out what is available. Products intended for incorporation into the project include the following: Card swipe, wireless card, wireless router, printer, HDK, and an LCD touch-screen.

Subtask 2b - Identification of Selection Criteria

Objective: To identify the selection criteria for the technology in the project. Approach: The team has discussed these criteria with the project advisor. The

selection criteria will be based on cost, ease of system integration (size, weight, type of connections available), and overall effectiveness (i.e. Will it do exactly what is required of it?).

Expected Result:

The team has defined and identified the selection criteria. There are many various forms of the products available to be incorporated into the project, and these criteria will assist in narrowing down the possibilities to the specific products that will be the most useful.

Subtask 2c - Technology Research

Objective: To research various technologies that could be used to implement the project.

Approach: Research for these technologies has been done by looking into companies that produce products that could be integrated into the system. More research will be done throughout development, primarily by attempting to implement what products are immediately available (through the school or another source) and analyzing their effectiveness. If a product is not effective, then the information learned from that product test will be used to find a product that will be more suited to the project.

Expected Result:

The team will select the appropriate technologies based on research data and input from the faculty and technical advisor.

Subtask 2d - Technology Selection

Objective: To select the appropriate technologies to use for the project. Approach: The team will select the appropriate technologies based on their

performances during research and their cost. Expected Result:

Approved technologies will be selected that are capable of completing the tasks needed.

2-8

Task 3 – End Product Design Subtask 3a - Identification of Design Requirements

Objective: To identify the design requirements for the project. Approach: The team has reviewed the description of the product expected by the

client and has created a list of design requirements. Expected Result:

The following requirements have been identified: Secure wireless communications between the HDK and the kitchen-based system in a “restaurant-like” setting (with a range of use large enough for any reasonably-sized restaurant), an easy-to-learn user interface for both systems, credit card-reading capabilities, and printing capabilities.

Subtask 3b - Design Process

Objective: To create a design plan for implementation. Approach: The team will work with the advisor to determine what should be

considered when looking at the design process. Expected Result:

The team will have a design plan for implementation

Subtask 3c - Documentation of Design

Objective: To document the design process. Approach: The team will keep notes detailing all steps of the design before and

during the implementation. These notes will be useful when developing different scenarios to use during testing and to determine how the ideal result can be obtained.

Expected Result:

The team will record each step of the process. Any problems encountered will be recorded along with solutions.

Task 4 – End Product Prototype Implementation Subtask 4a - Identification of Prototype Limitations

Objective: To identify the prototype limitations and develop design alternatives. Approach: The team will discuss the various limitations of the prototype and decide

on different alternatives. The full list of limitations can be found in the assumptions and limitations section

Expected Result:

A comprehensive report will be developed that will have all of the prototype’s limitations and alternatives for future development. This report will be delivered to the client. The team will insure the limitations will not pose a problem for the completion of a working prototype.

2-9

Subtask 4b - Implementation of Prototype End-Product Objective: To successfully implement the prototype according to design

specifications. Approach: The team will construct the prototype to meet all requirements initially

defined. A final product will have all of the same capabilities as the prototype, but would be presented in a smaller, hand-held package.

Expected Result:

A working prototype will be delivered to the client on time

Task 5 – End-Product Testing Subtask 5a - Test Planning

Objective: To devise a plan that will test the end-product using multiple scenarios. Approach: The team will give thought to what possible scenarios could be tested to

verify the functionality of the prototype. The scenarios tested will include extended use (simply by using the system a lot, the team will be test whether it can stand up to being used constantly), environmental conditions (the team plans on testing the system in conditions similar to a restaurant, with lots of people, walls, obstructions, cell phones, and other wireless networks in the vicinity), ease of use (by having people unfamiliar with the project try to use the product, the team can analyze its level of ease of use), and any other appropriate scenarios that may come up in the development process.

Expected Result:

The team will have a list of possible scenarios with which to test the end-product

Subtask 5b - Test Development

Objective: To devise a system in which the prototype can be tested. Approach: Testing of the prototype will include a similar environment to which it

will be used by the end-user. The team will either set up or find an environment that has the following: lots of people, walls, obstructions, cell phones, and other wireless networks in the vicinity. This will likely be either an actual restaurant or somewhere on the Iowa State University campus (i.e. Memorial Union Food Court).

Expected Result:

The team will look into restaurant environments in order to test the system under similar conditions

Subtask 5c - Test Execution

Objective: To test the prototype against scenarios devised by the project team and advisor.

Approach: During testing, members of the team will use the product just as an end-user would. The prototype will be evaluated to find strengths and weaknesses.

Expected Result:

The team will have a working prototype by the end of this stage

2-10

Subtask 5d - Test Evaluation Objective: To determine the success of the prototype built. Approach: The team will evaluate the prototype by defining strengths and weakness

in the overall design. Once the weaknesses are defined, the prototype will be modified accordingly. Criteria for testing will include signal integrity and range, along with ease of use and functionality.

Expected Result:

The prototype will pass all evaluation tests

Subtask 5e - Documentation of Testing

Objective: To create comprehensive documentation of the testing of the prototype. Approach: The team will keep accurate and detailed records pertaining to the testing

procedure and results. Expected Result:

The client will be presented with a comprehensive and detailed analysis of the functionality of the prototype.

Task 6 – End-Product Documentation Subtask 6a - Development of End-User Documentation

Objective: To create a user’s manual of the end-product. Approach: The team will write a comprehensive user manual on how to use the

product. This document will be both digital and printed format. Expected Result:

The team will have completed the user’s manual.

Subtask 6b - Development of Maintenance and Support Documentation

Objective: To create a troubleshooting guide and frequently asked questions portion of the final document.

Approach: The team will create a manual to enable the users to troubleshoot faults that may arise, as well as instructions on performing simple, preventative maintenance.

Expected Result:

The documentation will be created using the lessons learned from testing the prototype.

Task 7 – End-Product Demonstration Subtask 7a - Planning the Demonstration

Objective: To come up with the demonstration plan to show to the faculty advisor, client, and industrial review panel.

Approach: The team members must develop the plan to demonstrate the end-product.

Expected Result:

The team will be prepared to demonstrate the prototype

2-11

Subtask 7b - Demonstrating to the Faculty Advisor Objective: To demonstrate the end-product to the faculty advisor. Approach: The team members must carry out the demonstration plan for the faculty

advisor. Prior to any public display of the prototype, the faculty advisor should be confident in the end product.

Expected Result:

The faculty advisor will know that the team possesses a complete understanding of the project and their prototype, and will know that the prototype is functioning as intended.

Subtask 7c - Demonstrating to the Client

Objective: To demonstrate the working prototype to the client. Approach: The team members must demonstrate to the client that all of the

requirements have been met. The team will expect the client to have a basic understanding of the method used to design and build the prototype.

Expected Result:

The client will know that the prototype meets all of the expectations defined at the start of the project.

Subtask 7d - Demonstrating to the Industrial Review Panel

Objective: To demonstrate the working prototype to the industrial review panel. Approach: The project team will prepare a presentation to the industrial review

board to display the capabilities of the prototype. Expected Result:

A successful demonstration to the industrial review panel.

Task 8 – Project Reporting Subtask 8a - Development of Project Plan

Objective: To come up with the detailed and comprehensive plan for the project. Approach: The team must follow the project plan in order to remain on schedule.

Involved parties understand that not all problems can be predicted at the planning stage. It is also understood that modifications to the project plan will be cheaper the earlier the changes are made in the project.

Result: The project plan has been completed.

Subtask 8b - Development of the Project Poster Objective: To create a poster that accurately describes the prototype and its

capabilities. Approach: The poster must identify the important aspects of the prototype. It also

must meet all of the poster requirements. The poster should be developed using the team members’ input. The team will ensure that the poster is attractive, readable, and comprehensive. Once it is completed, it will be printed and submitted to the appropriate office.

Expected Result:

The project poster will be completed.

2-12

Subtask 8c - Development of the Design Report Objective: To develop the documentation that reports the design procedures and

capabilities of the prototype. Approach: The design report will be developed after the successful demonstration to

and the approval of the client. Expected Result:

The completed design report.

Subtask 8d - Development of the Project Final Report

Objective: To develop the final report that provides the detailed explanation and justification of the success of the project and team.

Approach: The final report will be created after every element in the project is a success and understood by all team members, the faculty advisor, and the client.

Expected Result:

The project final report will be completed.

Subtask 8e - Development of the Design Review

Objective: To develop the design report that provides a detailed review of the project.

Approach: The design review will be developed after the successful completion of the project.

Result: The complete design review. Subtask 8f - Development of the Class Presentation

Objective: To create a presentation to be presented to the class describing the project details.

Approach: The presentation must identify the important aspects of the project. It also must meet all of the presentation requirements. The presentation should be developed using the team members’ input. The team will ensure that the presentation is professional, readable, and comprehensive.

Expected Result:

The presentation will be created and presented to the class.

Subtask 8g - Development of the IRP Presentation

Objective: To develop the presentation to be presented to the Industrial Review Panel, IRP, that describes the project and project details.

Approach: The presentation will be similar to the class presentation, but configured towards the industrial review panel.

Expected Result:

The presentation will be created and presented to the IRP.

3-13

3.1

Subtask 8h - Development of the Weekly Reports Objective: To develop reports that will be submitted on a weekly basis to track the

progress of the project. Approach: The reports will be created weekly follow the specified format and

template created. All members of the team will participate in the weekly reports.

Expected Result:

Weekly reports will be submitted on a weekly basis.

3 Estimated Resources and Schedules The main concern of the estimated resources and schedules section will be the cost of the project and the estimated time for each part of the phase of the project. The first part will primarily deal with the estimated resources required for completing the project and the second part will deal primarily with the schedule and how much time will be spent on each phase of the project.

Estimated Resource Requirement This can be broken down into three different categories. They being the estimated man hours for each task, an estimated inventory list and the cost associated with each item and the estimated total cost of the project. The information to know would be the estimated man hours required to complete the project and is shown in Table 2. Within this table is the break down of the tasks stated in the statement of work section and the corresponding estimates of hours to complete each task. The hours that are given for each team member are closely related to their expertise in programming and how much responsibility they will be able to take for a given task. Table 2: Personnel Estimated Effort Requirements For Each Task (hours) Personnel Name Task 1 Task 2 Task 3 Task 4 Task 5 Task 6 Task 7 Task 8 Total Chris Ford 6.50 14.0 21.0 40.0 44.0 11.5 4.6 42.0 183.60 Sean McVeigh 7.00 19.0 14.0 49.0 36.0 14.0 4.2 56.0 199.20 Obioma Ohia 5.50 13.0 15.5 48.0 38.0 9.5 5.0 35.0 169.50 Nichole Taylor 5.75 11.5 16.0 43.0 46.0 12.0 5.0 45.0 184.25 Anthony VanSant 5.25 12.5 13.5 45.0 36.0 13.0 5.2 38.0 168.45

Total 30.0 70.0 80.0 225.0 200.0 60.0 24.0 216.0 905.00

Task 1 – Problem Definition Task 2 – Technology Considerations and Selections Task 3 – End Product Design Task 4 – End Product Prototype Implementation Task 5 – End-Product Testing Task 6 – End-Product Documentation Task 7 – End-Product Demonstration Task 8 – Project Reporting

3-2

The next important information that is necessary to know is the estimated cost for each item that is required to complete the project. The materials necessary to complete the project are shown in Table 3. This table shows the cost for each item disregarding that some of these items will possibly get donated or are currently available for free. For instance, there are three items in this table that are already available for free and they would be the wireless 802.11g PCMCIA card, the Microsoft Windows CE .NET 4.2 and the Microsoft Visual Studio Pro 2005 with MSDN Pro. The reason for including the cost for everything is so that there is a good understanding of what the total cost of the project would cost if everything was not freely provided. As for where the costs for each item comes from they were mostly found by going to companies on the internet that provided these items and seeing how much they cost that an estimate could be obtained. The references of where the prices come from are all contained in the endnote for each item. Table 3: Other Required Resources

Item Team Hours Other Hours Cost Parts and Materials: a. Hardware Development Kit Assemblyiii 3 0 $1,399 b. Card Swipeiv 0 0 $75.80 c. Wireless 802.11g PCMCIA Cardv 0 0 $59.99 d. Bluetooth Printervi 0 0 $725.00 e. Bluetooth Adaptervii 0 0 $30.00 f. Miscellaneous Parts 0 0 $20.00 g. Print Project Poster 8 0 $50.00 h. Dell Dimension B110viii 0 0 $569.00 i. Linksys WRT54G Wireless Routerix 0 0 $49.99 Software: a. Microsoft Windows CE .NET 4.2x 0 0 $995.00 b. Microsoft Visual Studio Pro 2005 w/MSDN Proxi 0 0 $644.00 Totals 11 0 $4,617.78

3-3

3.2

The final information that is important is the estimated cost of the project. This would include both the cost for the materials and the labor associated with the project. The labor was calculated by assuming that the team would receive $25 per hour on this project and then the cost per hour was multiplied by the total hours each person is estimated to work to get the total cost for one team member to work on the project. The $25 per hour comes from an estimate of what a recently graduated engineer would make per hour and what an inter would make on an internship. The cost estimate for the whole project is shown in Table 4. Table 4: Estimated Project Costs

Item W/O Labor With Labor Parts and Materials: j. Hardware Development Kit $1,399 $1,399 k. Card Swipe $75.80 $75.80 l. Wireless 802.11b PCMCIA Card $59.99 $59.99 m. Bluetooth Printer $725.00 $725.00 n. Bluetooth Adapter $30.00 $30.00 o. Miscellaneous Parts $20.00 $20.00 p. Project Poster $50.00 $50.00 q. Dell Dimension B110 $569.00 $569.00 r. Linksys WRT54G Wireless Router $49.99 $49.99 Subtotal $2,978.78 $2,978.78 Software: c. Microsoft Windows CE .NET 4.2 $995.00 $995.00 d. Microsoft Visual Studio Pro w/MSDN Pro $644.00 $644.00 Subtotal $1,639.00 $1,639.00 Labor at $25.00 per hour: a. Ford, Chris $4,590.00 b. McVeigh, Sean $4,980.00 c. Ohia, Obioma $4,237.50 d. Taylor, Nichole $4,606.25 e. VanSant, Anthony $4,211.25 Subtotal $22,625.00 Total $4,617.78 $27,242.28

Estimated Schedule Requirement The estimated schedule requirement has two components to it and they are a schedule for when a task will start and finish and the second component is the project deliverables schedule. The estimated schedule for when a task begins and ends is shown in Figure 2, which is on the following page. The figure following Figure 2 is the deliverables schedule and this is shown in Figure 3.

3-4

IDTa

sk N

ame

1P

roje

ct D

efin

ition

2P

roje

ct D

efin

ition

Com

plet

ion

3E

nd U

ser(s

) and

End

Use

(s)

4C

onst

rain

t Ide

ntific

atio

n5

Tech

nolo

gy C

onsi

dera

tions

6Id

entif

icat

ion

of T

echn

olog

ies

7Id

entif

icat

ion

of C

riter

ia8

Tech

nolo

gy R

esea

rch

9Te

chno

logy

Sel

ectio

n10

End-

Pro

duct

Des

ign

11Id

entif

icat

ion

of R

equi

rem

ents

12D

esig

n P

roce

ss13

Doc

umen

t Des

ign

14P

roto

type

Impl

emen

tatio

n15

Iden

tific

atio

n of

Lim

itatio

ns16

Impl

emen

tatio

n of

Pro

toty

pe17

End-

Pro

duct

Tes

ting

18Te

st P

lann

ing

19Te

st D

evel

opm

ent

20A

ctua

l Tes

ting

21R

esul

t Eva

luat

ion

22Te

st D

ocum

enta

tion

23En

d-P

rodu

ct D

ocum

enta

tion

24E

nd-u

ser D

ocum

enta

tion

25M

aint

ence

Doc

umen

tatio

n26

End-

Pro

duct

Dem

onst

ratio

n27

Dem

onst

ratio

n P

lann

ing

28Fa

culty

Adv

isor

(s) D

emon

stra

tion

29C

lient

Dem

onst

ratio

n30

Indu

stria

l Rev

iew

Pan

el D

emon

stra

tion

31P

roje

ct R

epor

ting

32U

nbou

nd P

roje

ct P

lan

33B

ound

Pro

ject

Pla

n34

Unb

ound

Des

ign

Repo

rt35

Bou

nd D

esig

n R

epor

t36

Pro

ject

Pos

ter

37U

nbou

nd F

inal

Rep

ort

38B

ound

Fin

al R

epor

t39

Wee

kly

Em

ail R

epor

ting

273

1017

241

815

2229

512

1926

310

1724

317

1421

284

1118

254

1118

251

815

2229M

ayA

pr '0

7M

ar '0

7Fe

b '0

7Ja

n '0

7S

ep '0

6O

ct '0

6N

ov '0

6D

ec '0

6

Figu

re 5

: Est

imat

ed P

roje

ct S

ched

ule

Formatted: Font: 10 pt

3-5

IDTa

sk N

ame

1P

roje

ct R

epor

ting

2U

nbou

nd P

roje

ct P

lan

3B

ound

Pro

ject

Pla

n4

Unb

ound

Des

ign

Repo

rt5

Bou

nd D

esig

n R

epor

t6

Pro

ject

Pos

ter

7U

nbou

nd F

inal

Rep

ort

8B

ound

Fin

al R

epor

t9

Cla

ss P

rese

ntat

ion

10In

dust

rial R

evie

w P

rese

ntat

ion

11W

eekl

y E

mai

l Rep

ortin

g

9/22

10/1

011

/10

12/1

32/

273/

305

4/10

4/25

273

1017

241

815

2229

512

1926

310

1724

317

1421

284

1118

254

1118

251

815

2229M

aypr

'07

AM

ar '0

7Fe

b '0

7Ja

n '0

7S

ep '0

6O

ct '0

6N

ov '0

6D

ec '0

6

Figu

re 6

: Del

iver

able

s Sch

edul

e

Formatted: Font: 10 pt, Checkspelling and grammar

4-1

4 Project Team Information The following information is who the client is for the project and the contact information for all of the team members and the faculty advisor and technical advisor that will be used in the completion of the project.

Client Senior Design

Faculty Advisor Dr. Manimaran Govindarasu 3219 Coover Hall Ames, IA 50011-3060 Office Phone: (515) 294-9175 Fax: (515) 294-8432 Email: gmani@iastate.edu

Technical Advisor Dr. Randall Geiger 351 Durham Hall Ames, IA 50011-2252 Office Phone: (515) 294-7745 Fax: (515) 294-1152 Email: rlgeiger@iastate.edu

Project TeamChristopher Ford Electrical Engineering 15411 Horton Avenue Urbandale, IA Home Phone: (515) 975-7088 Email: cford@iastate.edu Sean McVeigh (Project Manager) Electrical Engineering 420 South 4th Street #11 Ames, IA 50010 Home Phone: (515) 233-3360 Email: smcveigh@iastate.edu Obioma Ohia Electrical Engineering 103 Stanton Ave #25 Ames, IA 50014 Home Phone: (515) 710-9177 Email: oohia@iastate.edu

Nichole Taylor Electrical Engineering 1400 Coconino Rd #213 Ames, IA 50014 Home Phone: (563) 505-4735 Email: nikkit@iastate.edu Anthony Vansant Electrical Engineering 123 Sheldon Ave #13 Ames, IA 50014 Home Phone: (515) 708-1291 Email: vansant@iastate.edu

5-1

5 Summary The goal of this project is to design a "paperless" restaurant. A system will be designed that will allow servers to take orders on a handheld device and to communicate with the kitchen. Also, this device will be able to process table-side transactions for customers using credit/debit cards, allowing the customer to swipe, sign, and obtain a receipt. Finally, the order will be sent to an "accounting database" for inventory purposes. This goal will be achieved by developing two systems: the handheld system and a central computer system. The handheld system must integrate an LCD touch-screen, a magnetic card swipe, Bluetooth, a wireless card and a Bluetooth printer. The central computer system must integrate a wireless router and a monitor. The approach will be to focus on two systems: the handheld device for the servers and the central computer system. The technology to be selected will meet our requirements and the handheld device will be modeled using a HDK. This will allow focus on the integration of the components of the handheld device. The central computer system will be a desktop computer. Both systems will be tested throughout the design phase for functionality. The solution will consist of a functional model of the handheld device, a computer monitor to display orders in the kitchen, a wireless printer to communicate with the device model, a central computer to track orders and make updates, and a nonfunctional model of the device to simulate the dimensions of the device.

6-1

6 References "Digital Dining Handheld POS." Digital Dining. Menusoft Systems Corporation. 11 Sept. 2006

<http://www.menusoft.com/POS/PrdHandBody.html>. "Intel Handheld and Handset Components." Intel. Intel Corporation. 11 Sept. 2006

<http://www.intel.com/design/pca/applicationsprocessors/tools_software/devboards.htm>. "Magnetic Stripe Readers." PDA Palm Pocket PC Magnetic Stripe Readers. Grabba

International. 11 Sept. 2006 <http://www.grabba.com/index.cfm?pg=grabbamall_listing&cat=54&con=934&rg=eu>.

"PB20 Direct Thermal Portable Printer." RFID Tags - Supply Chain Management - Asset

Management. Intermec. 11 Sept. 2006 <http://www.intermec.com/eprise/main/Intermec/Content/Products/Products_ShowDetail?Product=PRTRPB20>.

"Pocket PCs with Bluetooth Wireless Onboard." Pocket PC Central V3.0. Pocket PC Central. 11

Sept. 2006 <http://pocketpccentral.net/bluethppcs.htm>. "Restaurant POS." Restaurant Manager. Action Systems Inc. 10 Sept. 2006

<http://www.actionsystems.com/>.

Endnotes i "Bluetooth Frequently Asked Questions Components." MobileInfo.Com. MobileInfo. 18 Sept. 2006 <http://www.mobileinfo.com/Bluetooth/FAQ.htm>. ii "Intel PXA27x Processor Developer's Kit." Download.Intel.Com. Intel Corporation. 14 Sept. 2006 <ftp://download.intel.com/design/pca/applicationsprocessors/manuals/27882705.pdf>. iii "PXA270 - PhyCORE-XScale/PXA270 Rapid Development Kit." 9 Oct. 2006 <http://www.phytec.com/products/rdk/ARM-XScale/phyCORE-XScale-PXA270.html>. iv "Tracks 1, 2, & 3 Credit Card Reader." BarcodesInc. Barcodes Inc. 7 Sept. 2006 <http://barcodesinc.com/cats/credit-card-readers/1-2-3.htm>. v "NetGear WG511 54 Mbps WL PcCard (NetGeat - WG511)." PriceGrabber.Com. 9 Oct. 2006 <http://amdmb.pricegrabber.com/search_getprod.php/masterid=691890>. vi "Auto ID Solutions by Integrated Labeling Systems, Inc." 11 Sept. 2006 <http://www.product-catalog.com/preview_item.cfm?line=Intermec%20PB20%20Direct%20Thermal%20Portable%20Printer&page_name=vendor&manu=Intermec&item=&BAToken=ils>.

6-2

vii "Network Adapter Bluetooth USB Wireless Networking." PriceGrabber.Com. 9 Oct. 2006 <http://amdmb.pricegrabber.com/search_attrib.php/page_id=371/popup2%5B%5D=40:1012/popup1%5B%5D=50:227/popup3%5B%5D=10:264>. viii "Basic Desktops." Dell. Dell Inc. 20 Sept. 2006 <http://www.dell.com/content/products/features.aspx/featured_basdt?c=us&cs=19&l=en&s=dhs>. ix "Linksys WRT54G Wireless G-Router." Amazon.Com. Amazon. 20 Sept. 2006 <http://www.amazon.com/Linksys-WRT54G-Wireless-G-Router/dp/B00007KDVI>. x "BSQARE Store." BSQUARE. BSQUARE Corporation. 21 Sep 2006 <http://store.bsquare.com/catalog/index.cfm?fuseaction=product&theParentId=142&id=2469>. xi "Visual Studio 2005 Professional Edition w/MSDN Pro." Pricegrabber.com. Price Grabber. 21 Sep 2006 <http://amdmb.pricegrabber.com/search_getprod.php/masterid=13954436>.