Foodmood Application Report: Design, Implementation and Constraints

This report details the Foodmood application, a proposed online food delivery service. The report outlines the application's features, including order placement, delivery tracking, and payment options. It defines user classes (skilled and unskilled) and describes the operating environment, including the database management system and hardware interfaces. The report also discusses design and implementation constraints, such as the use of Java and visual basics, parallel operation, and a system reboot protocol. Finally, it lists assumptions and dependencies, such as sufficient processing capacity and wireless network support, providing a comprehensive overview of the application's design and functionality.

Running head: FOODMOOD
Foodmood
Name of the Student
Name of the University
Author Note

1FOODMOOD
Table of Contents
2.1 Product Perspective..............................................................................................................2
2.2 User Classes and Characteristics..........................................................................................2
2.3 Operating Environment........................................................................................................3
2.4 Design and implementation constraint.................................................................................3
2.5 Assumptions and dependencies............................................................................................3

2FOODMOOD
2.1 Product Perspective
Foodmood, an online food application will help people connect to restaurants, cafes, bars and
delis to get lighting fast food delivery at doorstep. Foodmood will be an app and as well as
website based delivery system. The product plans to connect people staying far from central
town to the majority food services available. The app will provide various kinds of services
which include order placing, acceptance of order, delivery, bill payment, cash payment,
cancel order, abort account usage, indication of item approach, ETA of order and customer
feedback. The app will run 24*7 with special midnight food delivery system to cater the
needs to customers and late night workers.
2.2 User Classes and Characteristics
The end users of Foodmood fall into 3 types- unskilled users and skilled users.
Unskilled users: The user are customers ordering food through the app or website and
therefore assumed to hold no relevant skills to run the app other than use the app to order
food and cancel orders. The delivery boys are expected to have basic knowledge, no prior
education but have the ability to operate and use the automated system. The restaurants who
take the orders also fall into this category.
Skilled workers: The building of the app and the website and running it successfully
throughout the day requires expertise. The user under this category is highly skilled IT
experts who control the working of the application and the website. Class of this type of users
is presumed to have extensive experience in the computer application domain.

3FOODMOOD
2.3 Operating Environment
Foodmood has an interface with Data Base Management System (DBMS) which stores the
necessary information for the operation of the application and the website. The DBMS is
expected to provide data containing restaurant name and menu, customer account information
and delivery details at low latency rate. The system should be able to archive data of all
orders and past transaction which will be used for accounting and accountability. The
hardware interface includes tablets, touch displays and surface computers. The devices must
be robust and have standardized industry design aesthetics. UI/UX needs to be well designed
and developed to take in multiple orders at a time. The application is build on Java and
supports all kind of user interface UI platforms.
2.4 Design and implementation constraint
The application is written in object-oriented language and has strong GUI and
accessible API network. Java and visual basics are used to build this application. The system
should support parallel operation and the application must not face glitches regarding
scalability of the interface when used on several types of computer surfaces. Audit chain
needs to be strong. Since foodmood will be operating 24*7, there should be a system reboot
protocol so that if the system crashes the end-users will not know about the crash.
2.5 Assumptions and dependencies
The application is assumed to have enough processing capacity and capability and will utilize
minimum battery life. The size of the application will be moderate to be easily loaded and

4FOODMOOD
can be used regularly and have a recovery system. For system interaction and
communication, deployment environment has the capability to support wireless network.