TANAUAN INSTITUTE, INC.

COLLEGE DEPARTMENT

BACHELOR OF SCIENCE IN COMPUTER SCIENCE

(Automated marketing management ordering systems for fast food)

A Project in

CC 102

FUNDAMENTALS OF PROGRAMMING

By:

Condez Kaitlyn V.

Macapagal Nicole N.

Nuyles Jessa Mae D.

Panganiban Mark Vincent M.

Trajico Rachel Ann A.

BSCS 1-B

December 20, 2023

Automated marketing management ordering Page No.

systems for fast food

Title Page 1

Table of Contents 2

Project Description 3

Algorithm/Pseudocode 4

Program Flowchart 5

Source Code 6

Output of the System 7

This research project, titled This research project, titled Automated marketing management
ordering systems for fast food aims to comprehensively analyze the ordering experience within
the specified system. The scope includes assessing the user-friendly interface, diverse meal
options, order customization features, additional choices during the ordering process, and the
effectiveness of the order confirmation and feedback mechanism. The project will implement
features such as a dynamic menu display, robust order calculation system, efficient user input
handling, choice continuation, and a user feedback mechanism. However, it acknowledges
certain limitations, such as the absence of payment processing functionality, dependence on an
active internet connection, lack of real-time delivery tracking, and platform-specific design.
Through this study, insights into user behavior and system satisfaction will be gained, providing
a foundation for potential system enhancements and contributing to the broader understanding of
user experiences in online food ordering systems.

However, the limitations of an ordering system often extend beyond the coding aspects and
involve broader considerations related to business processes, user experience, strategy,
compliance, and effective communication. Successful system development requires a holistic
approach that combines coding with other non-technical elements.

(1) User Experience Design: While coding handles the functionality, the overall user experience
design goes beyond code. Limitations in user interface (UI) design can impact how users interact
with the ordering system. (2) Business Process Understanding: The code can implement
functionalities, but understanding and optimizing the underlying business processes may require
collaboration with domain experts and business analysts. (3) Effective Communication: The
ability of the ordering system to facilitate clear communication between users, such as order
confirmations and status updates, may depend on factors outside the code, like messaging
strategies and content. (4) Quality of Product Information: The accuracy and completeness of
product information depend on data input and maintenance processes, which are not solely
addressed by the code but by data management practices. (5) Market Research and Strategy:
Coding alone cannot address market research needs or formulate business strategies.
Understanding customer behavior and market trends requires additional non-coding efforts. (6)
Regulatory Compliance: While coding can implement certain security measures, ensuring
regulatory compliance may involve legal and policy considerations that extend beyond the scope
of the code. (7) Customer Support: The code can automate certain aspects, but effective customer
support requires human interaction, understanding, and empathy, which coding cannot fully
replicate. (Supply Chain Management: If the ordering system is part of a larger ecosystem
involving supply chain management, coordinating inventory levels, and managing suppliers may
require integration with external systems and non-coding efforts Handling unexpected events,
such as system failures or security breaches, involves crisis management strategies that go
beyond the scope of coding alone. And lastly, While well-designed code can be flexible, the
ability to adapt to evolving business requirements may require continuous collaboration between
developers and business stakeholders.

This aims to comprehensively analyze the ordering experience within the specified system. The
scope includes assessing the user-friendly interface, diverse meal options, order customization
features, additional choices during the ordering process, and the effectiveness of the order
confirmation and feedback mechanism. The project will implement features such as a dynamic
menu display, robust order calculation system, efficient user input handling, choice continuation,
and a user feedback mechanism. However, it acknowledges certain limitations, such as the
absence of payment processing functionality, dependence on an active internet connection, lack
of real-time delivery tracking, and platform-specific design. Through this study, insights into
user behavior and system satisfaction will be gained, providing a foundation for potential system
enhancements and contributing to the broader understanding of user experiences in online food
ordering systems.

However, the limitations of an ordering system often extend beyond the coding aspects and
involve broader considerations related to business processes, user experience, strategy,
compliance, and effective communication. Successful system development requires a holistic
approach that combines coding with other non-technical elements.

While coding handles the functionality, the overall user experience design goes beyond code.
Limitations in user interface (UI) design can impact how users interact with the ordering system.
The code can implement functionalities, but understanding and optimizing the underlying
business processes may require collaboration with domain experts and business analysts. The
ability of the ordering system to facilitate clear communication between users, such as order
confirmations and status updates, may depend on factors outside the code, like messaging
strategies and content. The accuracy and completeness of product information depend on data
input and maintenance processes, which are not solely addressed by the code but by data
management practices Coding alone cannot address market research needs or formulate business
strategies. Understanding customer behavior and market trends requires additional non-coding
efforts. While coding can implement certain security measures, ensuring
regulatory compliance may involve legal and policy considerations that extend beyond the scope
of the code The code can automate certain aspects, but effective customer support requires
human interaction, understanding, and empathy, which coding cannot fully replicate. (Supply
Chain Management: If the ordering system is part of a larger ecosystem involving supply chain
management, coordinating inventory levels, and managing suppliers may require integration with
external systems and non-coding efforts Handling unexpected events, such as system failures or
security breaches, involves crisis management strategies that go beyond the scope of coding
alone. And lastly, while well-designed code can be flexible, the ability to adapt to evolving
business requirements may require continuous collaboration between developers and business
stakeholders.
 ALGORITHM/PSEUDOCODE

Step 1: Start

Step 2: Declare variables name, option, meal, order, amount, and choice.

Step 3: Display a welcome message and prompt the user to enter their name.

Step 4: Start a do-while loop to handle menu selections.

Step 5: Display the meal options and prompt the user to enter their choice (option).

Step 6: Use a switch statement based on the option:

Step 7: For each case, prompt the user to enter the amount of the chosen meal.

Step 8: Calculate the total amount based on the meal price and user-entered quantity.

Step 9: Display the total amount for the selected meal and user.

Step 10: Ask the user if they want to make an additional choice (choice).

Step 11: Continue the loop if the user enters 'Y' or 'y' for an additional choice.

Step 12: Exit the loop if the user enters any other character.

Step13: Display a "Thank you" message and indicate the end of the program.

Step 14: End

no
 SOURCE CODE

#include <iostream>

using namespace std;

int main() {

string name;

int option;

int meal,order;

double amount;

char choice;

cout<<"*******Welcome Pizza Queen**********"<<endl;

cout<<"please insert name:";

cin>>name;

do{

cout<<"*******Menu Meal***********"<<endl;

cout<<"1.All Meat Pizza, Cheese burger, coke, big apple pie P590.00"<<endl;

cout<<"2.Cheese Pizza, Spagetti meatballs, coke, big peach mango pie P450.00"<<endl;

cout<<"3.Chicken, burger, fries, Sunday P190.00"<<endl;

cout<<"4.Tacos, Hotdogs, Sweet Drinks P350.00"<<endl;

cout<<"5.Coffe, Ice coffe, Chocolate coffe P290.00"<<endl;

cout<<"Enter Meal Option"<<endl;

cin>>option;

switch (option) {

case 1:

cout<<"Enter the amount of order:"<<endl;

cin>>amount;

amount = 590.00 * amount;

cout<<"\nThe amount of " << name << " is: " << amount << endl;

break;

case 2:

cout<<"Enter the amount of order:"<<endl;

cin>>amount;

amount = 450.00 * amount;

cout<<"\nThe amount of " << name << " is: " << amount << endl;

break;

case 3:

cout<<"Enter the amount of order:"<<endl;

cin>>amount;
 amount = 190.00 * amount;

cout<<"\nThe amount of " << name << " is: " << amount << endl;

break;

case 4:

cout<<"Enter the amount of order:"<<endl;

cin>>amount;

amount = 350.00 * amount;

cout<<"\nThe amount of " << name << " is: " << amount << endl;

break;

case 5:

cout<<"Enter the amount of order:"<<endl;

cin>>amount;

amount = 290.00 * amount;

cout<<"\nThe amount of " << name << " is: " << amount << endl;

break;

case 6:

cout<<"Enter the amount of order:"<<endl;

cin>>amount;

amount = 150.00 * amount;

break;

default:

cout << "\nWrong Input";

break;

cout<<"\nWould you like to Enter Additional choice? (Y for yes/ N for No): ";

cin>>choice;

}while (choice == 'y' || choice == 'Y');

cout<<"Thank you, please come again...";

return 0;

}
OUTPUT OF THE SYSTEM