Project: Fast Food Automated Ordering System

17025 Words Mar 13th, 2013 69 Pages
Project: Fast Food Automated Ordering System

Students: Vimal Mayank and Deep Saraf
Faculty Advisors: Mark Austin and John Baras
TABLE OF CONTENTS 1. Introduction
Purpose : Define fast food automated ordering system.
Topics : Problem statement; benefits of the system; purpose. 2. Goals, Scenarios, and Use Cases
Purpose : Develop use cases, scenarios and system requirements.
Topics : Goals and Scenarios; initial use cases with activity diagrams. 3. Generation of Requirements from Use Cases
Purpose : Generate high-level requirements from use cases.
Topics : High-level requirements; synthesis and breakdown of requirements; requirements
…show more content…
3. The system will be less probable to make mistake, since it?s a machine. 4. This will avoid long queues at the counter due to the speed of execution and number of optimum screens to accommodate the maximum throughput. 5. The system will be available 24 hours for 365 days, because the machine is not going to take any sick or vacation leave.
Scope and Objectives
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?
System Framework and Boundary

Goals, Scenarios and Use Cases

Goals and Scenarios
Goal 1. The system has a user-friendly user interface. 1. Scenario 1.1. A particular user of the system has no difficulty in reading the text on the display. 2. Scenario 1.2. The system is navigable through intuition. 3. Scenario 1.3. Menu choices are presented in form of buttons, which
Open Document