PIR MEHAR ALI SHAH

ARID AGRICULTURE UNIVERSITY RAWALPINDI

Online Cake Bakery System

CS – 699 Software Project
BSCS

SESSION
2019-2024

SUPERVISED BY:
Ms Sadia Razaq
SUBMITTED BY:

Iqra Bibi 19-Arid-352

DEPARTMENT OF COMPUTER SCIENCES

BARANI INSTITUTE OF SCIENCES
BUREWALA CAMPUS
All rights reserved. Reproduction in whole or in part in any form requires the prior
written permission of Iqra Bibi or designated representative.

ii
 DEDICATED
To
Our beloved Parents, Family, Teachers and Friends
&
Everyone from whom I learnt – even a single word.

iii
 DECLARATION
We hereby declare that the report being presented is our own work this study does not
incorporate without acknowledgment any material previously submitted for a degree
diploma in any university and that to the best of our knowledge and belief it does not
contain any material previously published or written by another person where due
reference is not made in the text.

Iqra Bibi
19-ARID-352

February-2024

iv
 CERTIFICATE OF APPROVAL
It is certified that the project titled “Online Cake Bakery System” carried out by Iqra
Bibi Reg No. 19-ARID-352 under the supervision of Mis Sadia., ARID University
Barani Institute of Sciences Burewala, is fully adequate in scope and in quality as a
final year project for the degree of Bachelor of Science in Computer Sciences.

Supervisor: ----------------------------
Ms Sadia Razaq
Lecturer
Dept. of Computer Sciences
ARID University, Barani Institute of Science Burewala

Internal Examiner 1: ---------------------------

Ms. Sana
Lecturer
Dept. of Computer Sciences
ARID University, Barani Institute of Science Burewala

Internal Examiner 2: --------------------------

Mr.Suhail Akraam
Assistant Professor
Dept. of Computer Sciences
ARID University, Barani Institute of Science Burewala

Project Coordinator: --------------------------

Mr. Muhammad Irfan
Lecturer
Dept. of Computer Sciences
ARID University, Barani Institute of Science Burewala

In charge Department: --------------------------

Mr. Muhammad Iran
Head of Department
Dept. of Computer Sciences
ARID University, Barani Institute of Science Burewala

v
 ACKNOWLEDGMENT
ALLAH THE ALMIGHTY, who gave us the strength to work to complete this project
on time and with the best possible quality and our family and friends who supported
us in every step of life and mostly the past four years of university life. We would like
to thank and sincerely acknowledge the help of our supervisor Mis Sadia whose
complete guidance, support and encouragement gave us a real motivation in doing
this project.
We would like to thank all the volunteers who helped us out while testing of this
application. Lastly, we would like to thank all the faculty members of Computer
Science department for their help, time, and support that was gladly given to us on the
time of need.

Iqra Bibi
19-ARID-352
 ABSTRACT
The Online Cake Bakery System (OCBS) is a comprehensive web-based application
designed to streamline the process of ordering and managing cakes from a bakery
online. In today's digital age, the demand for convenient and efficient online services
continues to rise, and the bakery industry is no exception. The OCBS aims to bridge
the gap between traditional brick-and-mortar bakeries and modern e-commerce
platforms by providing a user-friendly interface for customers to browse, customize,
and order cakes from the comfort of their homes.
 TABLE OF CONTENTS
DECLARATION.........................................................................................................IV
CERTIFICATE OF APPROVAL.................................................................................V
ACKNOWLEDGMENT..............................................................................................VI
ABSTRACT...............................................................................................................VII
TABLE OF CONTENTS..........................................................................................VIII
LIST OF FIGURES.......................................................................................................X
LIST OF TABLES.......................................................................................................XI
CHAPTER 1...................................................................................................................1
INTRODUCTION..........................................................................................................1
1.1 Overview.............................................................................................................1
1.2 Statement of Problem........................................................................................ 1
1.3 Purpose of the Project..........................................................................................2
1.4 Applications of the Research..............................................................................2
1.5 Theoretical Bases and Organization....................................................................3
1.6 Summary.............................................................................................................4
CHAPTER 2...................................................................................................................5
LITERATURE REVIEW...............................................................................................5
2.1 Systems................................................................................................................5
2.1.1 Existing System...........................................................................................6
2.1.2 Proposed System..........................................................................................6
2.2 Related Projects...................................................................................................6
2.3 Related Studies....................................................................................................7
2.3.1 About the Organization...............................................................................7
2.3.2 Vision...........................................................................................................8
2.3.3 Mission........................................................................................................8
2.4 Limitations and Bottlenecks................................................................................8
2.5 Summary.............................................................................................................9
CHAPTER 3.................................................................................................................10
TOOLS AND TECHNIQUES.....................................................................................10
3.1 Hardware Used With Technical Specifications.................................................11
3.2 Software, Simulation Tools Used......................................................................11
3.2.1 Visual Studio.............................................................................................11
3.2.2 MY SQl......................................................................................................12
Database...........................................................................................................12
3.2.3 Google Chrome..........................................................................................12
3.2.4 Edraw Max................................................................................................13
3.2.5 Node Js......................................................................................................14
3.3 Summary...........................................................................................................14
CHAPTER 4.................................................................................................................15
METHODOLOGIES....................................................................................................15
4.1 SDLC Models....................................................................................................16
4.2 Incremental Model............................................................................................17
4.3 Verification of Functional Requirements..........................................................19
4.3.1 Functional Requirements...........................................................................20
4.3.2 Admin Module...........................................................................................21
4.3.3 User Module..............................................................................................21
 4.4 Non-functional Requirement.............................................................................21
Advantages of Non-Functional Requirement...................................................22
Disadvantages of Non-functional requirement.................................................22
4.4.2 Reliability..................................................................................................22
4.4.3 Performance...............................................................................................23
4.5 Design................................................................................................................23
4.5.1 Use Case Diagram.....................................................................................24
4.5.2 Activity Diagram.......................................................................................26
4.5.3 Sequence Diagram.....................................................................................29
4.6 SUMMARY...........................................................................................................31
CHAPTER 5.................................................................................................................33
SYSTEM TESTING....................................................................................................33
5.1 Objective Testing..............................................................................................33
5.2 Usability Testing...............................................................................................34
5.3 Software Performance Testing..........................................................................34
5.4 Compatibility Testing........................................................................................36
5.5 Load Testing......................................................................................................37
5.6 Security Testing.................................................................................................38
5.6.1 Focus Areas....................................................................................................39
5.7 Installation Testing............................................................................................40
5.8 Test Cases..........................................................................................................41
CHAPTER 6.................................................................................................................49
RESULTS AND CONCLUSION................................................................................49
6.1 Presentation of the Findings..............................................................................49
6.1.1 Hardware Results.......................................................................................50
6.1.2 Software Results........................................................................................51
6.2 Fornt Page..........................................................................................................53
6.3Button.................................................................................................................54
6.4 Back Button.......................................................................................................55
6.5 Picture Box........................................................................................................56
6.6 Manu Script Bar................................................................................................58
6.7 Cart....................................................................................................................60
6.8 Search................................................................................................................60
6.9 Home.................................................................................................................61
6.10 Catagories........................................................................................................62
6.11 Admin..............................................................................................................63
6.12 Supervisor Project...........................................................................................63
6.13 Description......................................................................................................65
6.14Discussion Of The Finding...............................................................................66
6.15 Limitations.......................................................................................................66
6.16 Conclusion.......................................................................................................66
6.17 Summary.........................................................................................................67
CHAPTER 7.................................................................................................................69
FUTURE WORK.........................................................................................................69
REFERENCES.............................................................................................................70
 LIST OF FIGURES
Figure 4.1 Incremental Life Cycle...............................................................................18
Figure 4.2 Use Case Diagram of User..........................................................................25
Figure 4.3 Activity Diagram of User...........................................................................28
Figure 4.4 Sequence diagram of FYP..........................................................................31

Figure 6.1 Front page 54

Figure 6. 4 Next Button................................................................................................55
Figure 6. 4 Back Button...............................................................................................55
Figure 6.5 Picture box
Figure 6.6 Manu script Bar
Figure 6.7 cart
Figure 6.8 Search
Figure 6.9 Home
Figure 6.10 Catagories
Figure 6.11 Admin
Figure 6.12 Supervisor Project

LIST OF TABLES
Table 5. 1 Software Performance Testing....................................................................36
Table 5. 2 Compatibility Testing..................................................................................37
Table 5. 3 Load Testing................................................................................................38
Table 5. 4 Security Testing..........................................................................................40
Table 5. 5 Installation Testing......................................................................................40
Table 5. 6 Test Case 1 sign in......................................................................................42
Table 5. 7 Test Case 2 supervisor performance...........................................................43
Table 5. 8 Test Case 3 Student.....................................................................................44
Table 5. 9 Test Case 4 Panel........................................................................................45
Table 5. 10 Test Case 5 Admin...................................................................................46
Table 5. 11 Test Case 6 Add panel...............................................................................48
Table 5. 12 Test Case 7 Add supervisor.......................................................................36
Chapter 1
INTRODUCTION
In this chapter introducing an Online Cake Bakery System, designed to revolutionize
the digital interaction between customers and bakery services. This system simplifies
ordering and delivery processes, offering seamless experiences and personalized
customization options. With a focus on efficiency and convenience, it aims to set new
standards within the online bakery industry.

1.1 Overview
The Online Cake Bakery System represents a sophisticated solution that
combines cutting-edge technology with the artistry of baking to deliver a delightful
experience for both customers and bakery staff. By leveraging the power of
digitalization, automation, and data analytics, this system empowers bakeries to thrive
in the competitive online marketplace while delighting customers with delicious,
customized cakes delivered with efficiency and precision.

1.2 Statement of Problem

An online website for a bakery is a very common system that been used by the entire
bakery out there. Yet, there is some bakery which failed to provide a good service for
the Customers out there due to some problems. Well, let’s see what the problems that
lead are. The bakery to bankruptcy. The first reason why a bakery fails to satisfy their
customers though they have good websites is, due to the difference between received
product and displayed item. Last, but not the least, customers tend to lose their trust
towards the website of a bakery because of the delay of the goods delivery service.
People lose their patience if they didn’t receive their ordered items on time right after
Idea, which is an online website for a bakery system. This documentation is aimed to
create website which, handle ordering and delivering cakes, pastries, cookies and
cupcakes via Online.
1.3 Purpose of the Project
The purpose of the Online Cake Bakery System project is to provide a convenient
and efficient platform for customers to browse, order, and customize cakes online. In
today's fast-paced world, where online shopping has become increasingly prevalent,
this system aims to streamline the process of purchasing cakes for various occasions
such as birthdays, weddings, and celebrations. By digitizing the bakery experience,
customers can explore a wide range of cake options, flavors, and designs from the
comfort of their own homes. Moreover, the system aims to enhance customer
satisfaction by offering personalized customization options, ensuring that each cake
meets the unique preferences and requirements of the customer. Additionally, the
project seeks to optimize bakery operations by automating order management,
inventory tracking, and delivery logistics, thereby increasing efficiency and reducing
the likelihood of errors. Ultimately, the Online Cake Bakery System endeavors to
revolutionize the way cakes are ordered and enjoyed, providing a seamless and
delightful experience for both customers and bakery staff alike.
1.4 Applications of the Research
The application of research findings in the development of an Online Cake
Bakery System is pivotal in enhancing the efficiency and effectiveness of the
platform. Through thorough research, insights into consumer preferences, market
trends, and technological advancements can be gathered, which directly influence the
features and functionalities of the system. By analyzing the market demand for
various types of cakes, such as flavors, designs, and dietary requirements, the system
can be tailored to offer a wide range of options to cater to diverse customer needs.
Moreover, research on emerging technologies, such as AI-driven recommendation
engines or IoT-enabled inventory management systems, can inform the integration of
innovative solutions to streamline processes and improve user experience.
Understanding the competitive landscape through market research allows for
differentiation strategies to be devised, ensuring the system stands out amidst similar
offerings. Additionally, research on online payment gateways, cybersecurity
measures, and data protection regulations is essential for implementing robust security
protocols to safeguard customer information and financial transactions. Overall, the
application of research in every stage of development is fundamental for creating a
robust, customer-centric Online Cake Bakery System that meets the demands of
today's dynamic market landscape.

1.5 Theoretical Bases and Organization

Online Cake Bakery System revolves around the fundamental principles of
e-commerce, baking industry practices, and user-centric design. At its core,
the system integrates theories from business management, digital marketing,
and user experience to create a seamless online platform for ordering custom
cakes. The organization of the project is structured to address key
components essential for the successful implementation and operation of the
system. This includes detailed research on consumer behavior in the context
of online food ordering, understanding the intricacies of baking processes and
ingredient sourcing, as well as exploring efficient logistics and delivery
mechanisms. Moreover, emphasis is placed on the utilization of technology
such as website development, payment gateways, and customer relationship
management systems to streamline operations and enhance user satisfaction.
The theoretical framework also encompasses considerations for scalability,
sustainability, and adaptation to market trends to ensure the long-term
viability of the Online Cake Bakery System. By integrating these theoretical
underpinnings into the organization of the project, we aim to develop a
robust and user-friendly platform that caters to the evolving needs of both
consumers and the baking industry.

1.6 Summary
The Online Cake Bakery System documentation encapsulates a
comprehensive overview of a digital platform designed to facilitate cake ordering and
delivery services. This documentation serves as a detailed narrative, delineating the
functionality, architecture, and user experience of the system. It outlines the intricate
processes involved in placing orders, managing inventory, processing payments, and
orchestrating timely deliveries. Emphasizing seamless user interaction, the
documentation explores the intuitive interfaces and navigation pathways engineered
to enhance customer satisfaction. Additionally, it delves into the backend
infrastructure, elucidating the robust database management, security protocols, and
administrative tools essential for system operation and maintenance. By encapsulating
the essence of the Online Cake Bakery System, this documentation provides a holistic
perspective, illuminating its role in modernizing and streamlining cake procurement
processes in the digital era.
Chapter 2
LITERATURE REVIEW
Online Shopping play a huge role in the today’s business. Online shopping has
provided wide range of opportunities and advantages to small/big organizations. This
paper analyzed the different issue of online shopping. The research aims to provide
theoretical contribution in understanding the present status of online shopping for
bakery shop. The Study Discuss the need of online bakery shop.
Marketing helps, the consumer has needs more effectively and efficiently with good
product and services with best price and delivery. A good marketer continuously
satisfying consumer needs in better way. Internet has changed the way consumers buy
any goods and services, and has evolved into an online market. Rowley Jennifer,
(1998) has examined that internet
is becoming a nest of advertising, shopping. Hsieh et al., (2013) stated that internet is
influencing and becoming part of people’s daily life as compared to past. People’s
day-to-day activities have moderately shifted from physical environment to virtual
environment. A consumer may buy bakery products from the comfort of their own
home via an online store. The growth in number of online shopping has increased
than the growth in Internet users,
specifying that more internet users are nowadays becoming more comfortable to shop
products online than before. According to recent study, the consumers visit online
websites to book hotel rooms, buy air tickets, rail or movie tickets, books and gadgets.
2.1 Systems
Online Cake Bakery System outlines the comprehensive structure and
functionality of the platform designed to facilitate the seamless ordering and
delivery of cakes. This system encompasses various modules including user
authentication, product catalog management, order processing, payment
integration, delivery scheduling, and customer feedback management.
Through a user-friendly interface, customers can browse through an extensive
range of cake options, customize their orders, make secure payments, and
track delivery status. Administrators have access to backend functionalities to
manage inventory, monitor sales, analyze customer data, and update website
content. The system aims to enhance user experience, streamline business
operations, and ultimately establish a reliable and efficient online bakery

service.

2.1.1 Existing System

The current system is manual that means customers need to visit the bakery to
purchase the items. Sometimes the product might be unavailable than the customers
might search another shop where the product is available. This might take a lot of
time. This will create a negative impression about the shop.

2.1.2 Proposed System

The proposed system aims to revolutionize the traditional bakery experience by

introducing an Online Cake Bakery System. This system will allow customers to
conveniently browse through a wide range of cake options, customize their orders
according to preferences such as flavors, sizes, and decorations, and securely place
orders online. Through seamless integration of payment gateways, customers can
complete transactions effortlessly, ensuring a smooth and efficient purchasing
process. Additionally, the system will feature a user-friendly interface for bakery
administrators to manage orders, track inventory, and update product offerings in real-
time. By leveraging the power of technology, this Online Cake Bakery System
promises to enhance customer satisfaction, streamline operations, and ultimately
redefine the way individuals engage with their favorite baked goods.

2.2 Related Projects

There are many websites or web based applications/systems that provide online baker
yservices. These systems are owned by some private companies. They provide
customer the facility of online purchasing of their bakery items. Some of the similar
systems that provide the online facility to customers are ribbonsandbaloons.com,
monogynies, parkashbakery.com etc.

2.2.1 Ribbonsandballoons.com
Ribbonsandballoons.com is a webbased system that allows customer from all over Ma
harashtra to order bakery items online using their website. They sell various items
such as cakes, pastries, bread and biscuits, savory, desserts, tidbits etc. Customers are
needed to register themselves into the system. They are needed to enter their personal
details into the system such as name, mobile number, email and password. This is a
compulsory to use the system. Than the users can login to the system using the email
and the password, they entered during the registering phase. After that, users can buy
any of the bakery items that
are provided by the system. Ribbons and balloons provide payment options such as ca
sh ondelivery, credit/debit, net banking and Paytm and various other e-wallets. The
systemalso provides a cart/basket option where users can buy multiple bakery items.
The system provides two delivery options as delivery and pickup.

Advantages:
1. Allows users to buy bakery items online.
2. Provides bakery items for special occasions such as Birthday, valentine’s day etc.
3. Vast menu of bakery items for customer to buy from.
Disadvantages:
1. In delivery user is charged 100 rupees more as delivery charges and the item is than
delivered to the respective address. The order is delivered between 12pm to 6 pm
only.
2.2.2 Fantasybakery.com
Fantasybakery.com is a website that sells various bakery products such as cakes,
desserts, pizzas, pasta, sandwiches, snacks etc. The company is based in Indore. It
was started in 1985.Customers are not required to register into the system. They can
order directly. It provides various payment options such as cash and online. They
provide delivery of food items to the customers. While at the time of checkout users
are required to submit their mobile number. The number is than verified and an OTP
is send to the customer is mobile and is asked to enter the OTP. It verifies whether the
OTP entered by the customer matches with the OTP sent by the system, if yes than
only user is allowed to enter various details such as delivery address.
Advantages:
1. Provides delivery of bakery items.
2. Cash and online payment options.
Disadvantages:
1. No signup and login mechanism.
2. Customers are charged 80 rupees as delivery charges.
3. Minimum order amount must be more than 300 rupees. Since the bakery is based in
Indore customers outside of, Indore cannot buy the items using the system.

2.3 Related Studies

Success and Happiness always Begins With a Sweet Note. So to fulfill this beautiful
tradition Ribbons and Balloons has been there for its customers since 2005. Straight
from the ovens of the finest bakery, we bring you the fresh taste of goodness. Here,
you get a wide choice of rich delicious Pastries, Birthday Cakes, Custom and Fancy
Cakes for all occasion, Tea Cakes, Puffs, Rolls, Sandwiches… & more.
Leading and growing strongly with around 100 stores in Mumbai and Pune our
growth has been an inspiring success story to tell. We have accomplished all this
through our closely understanding of Ribbons and Balloons customer needs,
excellent products, state of the art manufacturing, motivated employees, efficient
supply chain management and satisfied franchise partners. Ribbons and Balloons
expansion plan in the coming years is to create our presence in all the cities Pan India.
To be a world class organization committed to delight our nationwide customers by
creating happy memorable moments in their lives through our line of products.
Provide professional and courteous service to our customers with highest standard of
freshness, quality and product value. Constantly focus and evolve through innovation
and cutting edge technology for superior product line. Establish beneficial
relationship with our customers, supplier and franchised operations. Provide an
exceptional and memorable experience for our customers through our graciousness,
professionalism, integrity, service and products. Contribute to the society through our
profits.

2.3.1 About the Organization

The Online Cake Bakery System is an innovative digital platform dedicated to

revolutionizing the way customers experience and interacts with the confectionery
industry. Our organization is committed to providing a seamless and delightful online
shopping experience for customers seeking high-quality, freshly baked cakes for
various occasions. With a user-friendly interface and a wide array of customization
options, we aim to cater to the diverse tastes and preferences of our clientele. Our
team of skilled bakers and tech-savvy professionals collaborates tirelessly to ensure
prompt delivery, exceptional customer service, and a consistently superior product.
Through cutting-edge technology and a passion for culinary excellence, we strive to
redefine the boundaries of convenience and indulgence in the realm of online bakery
services.

2.3.2 Vision

The vision for the documentation of the Online Cake Bakery System embodies
a comprehensive narrative that illustrates the essence and aspirations of the project.
This documentation serves as a cohesive narrative thread, seamlessly weaving
together the conceptualization, development, and implementation stages of the
system. Through meticulous detail and clear articulation, it paints a vivid picture of a
virtual bakery where customers can effortlessly browse, customize, and order
delectable cakes from the comfort of their homes. By integrating innovative
technologies with user-centric design, the vision is to create a seamless online
platform that not only simplifies the cake ordering process but also fosters delight and
satisfaction among users. This documentation stands as a testament to our
commitment to excellence, innovation, and customer-centricity, driving the project
towards its ultimate goal of redefining the digital bakery experience.

2.3.3 Mission

Provide professional and courteous service to our customers with highest standard of
freshness, quality and product value. Constantly focus and evolve through innovation
and cutting edge technology for superior product line. Establish beneficial
relationship with our customers, supplier and franchised operations. Provide an
exceptional and memorable experience for our customers through our graciousness,
professionalism, integrity, service and products. Contribute to the society through our
profits.

2.4 Limitations and Bottlenecks

The Online Cake Bakery System encounters several limitations and
bottlenecks that may impede its seamless operation and efficiency. One significant
constraint lies in the potential challenges associated with inventory management,
wherein fluctuations in demand could lead to either understocking or overstocking of
ingredients, affecting production schedules and profitability. Moreover, the reliance
on internet connectivity poses vulnerability, as any disruptions or downtimes may
hinder customers' ability to place orders or access the platform, thus impacting
revenue generation and customer satisfaction. Additionally, ensuring data security and
privacy amidst the digital transactions and customer information storage presents an
ongoing concern, necessitating robust measures to safeguard against potential
breaches or cyberattacks. Furthermore, scalability issues may arise as the business
grows, necessitating upgrades to infrastructure and systems to accommodate
increasing user traffic and transaction volumes without compromising performance or
user experience. Addressing these limitations and bottlenecks demands proactive
planning, strategic investments, and continuous monitoring to sustain the system's
functionality and competitiveness in the online bakery market.

2.5 Summary
The documentation for the Online Cake Bakery System presents a
comprehensive overview of the platform's design, development, and functionalities. It
outlines the seamless user experience facilitated by the system, allowing customers to
browse through a diverse range of cakes, customize orders, and securely make
payments online. The document delves into the technical aspects, detailing the
architecture, database management, and security measures implemented to ensure
smooth operations and data integrity. Additionally, it highlights the administrative
features empowering bakery owners to manage inventory, track orders, and analyze
business performance efficiently. With its user-friendly interface and robust backend
infrastructure, the Online Cake Bakery System offers a streamlined solution for both
customers and bakery owners in the digital marketplace.
Chapter 3
TOOLS AND TECHNIQUES
Tools and techniques for the Online Cake Bakery System, various tools and
techniques have been employed to ensure clarity and effectiveness in conveying
project details. Leveraging tools such as Microsoft Word for document creation and
organization, diagrams and flowcharts were designed using Lucid chart to illustrate
system architecture and user workflows. Additionally, collaborative platforms like
Google Drive facilitated team communication and document sharing throughout the
project lifecycle. Techniques such as requirement gathering sessions, stakeholder
interviews, and prototyping were utilized to ensure alignment with client expectations
and end-user needs. The documentation encompasses detailed descriptions of system
functionalities, user interactions, database schemas, and implementation strategies,
supported by screenshots and code snippets where applicable. Continuous feedback
loops and version control mechanisms were established using platforms like GitHub
to track changes and ensure document accuracy. The documentation serves as a
comprehensive reference for developers, testers, and stakeholders, facilitating
seamless understanding and successful implementation of the Online Cake Bakery
System.

3.1 Hardware Used with Technical Specifications

The Online Cake Bakery System employs a robust array of hardware components to
ensure seamless functionality and efficient operations. At the forefront is a high-
performance server equipped with a multi-core processor and ample RAM to handle
concurrent user requests and database operations swiftly. Complementing the server is
a network infrastructure comprising routers, switches, and firewalls to facilitate secure
data transmission and protect against cyber threats. Additionally, client devices such
as desktop computers, laptops, tablets, and smartphones are supported, ensuring
accessibility across various platforms. Point-of-sale terminals equipped with barcode
scanners and receipt printers streamline in-store transactions, while kitchen display
systems enhance communication between staff for order fulfillment. Finally, backup
servers and uninterruptible power supplies safeguard against data loss and downtime,
ensuring the system's reliability and availability.
  Processor: Intel® Core ™ i7 CPU M 640 @ 2.80GHz 2.80 GHz
 Installed memory (RAM): 4.00GB
 System Type: 64-bit Operating System, x64-based processor
 Windows: 10Pro

3.2 Software, Simulation Tools Used

Software is used to build APP. Software’s use for application Visual Studio,
Google Chrome and Edraw Max. Languages are used Node js and CSS.

3.2.1 Visual Studio

Visual Studio is an integrated development environment (IDE) from

Microsoft. It is used to develop computer programs including websites, web apps,
web services and mobile apps. The Visual Studio IDE is a creative launching pad that
you can use to edit, debug, and build code, and then publish an app. Microsoft Visual
C++ (MSVC) refers to the C++, C, and assembly language development tools and
libraries available as part of Visual Studio on Windows. Visual C# is Microsoft's
implementation of the C# programming language specification, included in the
Microsoft Visual Studio suite of products. Node js and CSS is much slower than C++,
since the code passes through CLR. Visual Studio empowers you to complete the
entire development cycle in one place. For example, you can edit, debug, test, version
control, and deploy to the cloud. With the diversity of features and languages in
Visual Studio, you can grow from writing your first piece of code to developing in
multiple project types. “Visual Studio” and “Visual Studio Code” are not the same
thing. Visual Studio is an integrated development environment (IDE) and Visual
Studio Code is a rich text editor like Sublime Text and Atom. But the difference
between the tools is more than just IDE and text editor. An IDE is a robust tool for
writing, editing, debugging, and running your code. A text editor only lets you write
and edit your code. You might have to step out of a text editor to run your code or
download plugins to help it do the running for you. In this article, you'll learn the

main differences between Visual Studio and Visual Studio Code.

3.2.2 MY SQL
 MySQL is a relational database management system (RDBMS) developed by
Oracle that is based on structured query language (SQL). MySQL is an open-source
relational database management system. As with other relational databases, MySQL
stores data in tables made up of rows and columns. Users can define, manipulate,
control, and query data using Structured Query Language, more commonly known as
SQL. It may be anything from a simple shopping list to a picture gallery or the vast
amounts of information in a corporate network. To add, access, and process data
stored in a computer database, you need a database management system such as
MySQL Server. MySQL is a relational database that uses structured query language.
Relational databases are a type of database that uses a structure that allows us to
identify and access the data in relation to another piece of data inside of the database.
This format is often organized as tables. MySQL is an open source
relational database management system (RDBMS) with a client-server
model. RDBMS is a software or service used to create and manage databases
based on a relational model. Now, let’s take a closer look at each term:

Database

A database is simply a collection of structured data. Think of taking a

selfie: you push a button and capture an image of yourself. Your photo is data,
and your phone’s gallery is the database. A database is a place in which data is
stored and organized. The word “relational” means that the data stored in the
dataset is organized as tables. Every table relates in some ways. If the software
doesn’t support the relational data model, just call it DBMS.

3.2.3 Google Chrome

first released in 2008 for Microsoft Windows, built with free software
components from Apple WebKit Google Chrome is a cross-platform web browser
developed by Google. It was and Mozilla Firefox. Versions were later released for
Linux, macOS, iOS, and also for Android, where it is the default browser. Google
Chrome is a fast, easy to use, and secure web browser. Designed for Android, Chrome
brings you personalized news articles, quick links to your favorite sites, downloads,
and Google Search and Google Translate built-in. Download now to enjoy the same
Chrome web browser experience you love across all your devices. Google Chrome
browser is a free web browser used for accessing the internet and running web-based
applications. The Google Chrome browser is based on the open-source Chromium
web browser project. Google released Chrome in 2008 and issues several updates a
year. Google Chrome is a great browser for everyday use as far as the browser's
capabilities are concerned. However, Google's data collection practices make Chrome
one of the worst browsers for privacy, and we recommend using a more privacy-
conscious browser. Google Chrome is a free Web browser developed by Google. It's
based on the Chromium open-source project. Some key differences are described on
Browser Stack. Chrome supports its own layout called Blink.

3.2.4 Edraw Max

Edraw Max is a 2D business technical diagramming software which helps

create flowcharts, organizational charts, mind map, network diagrams, floor plans,
workflow diagrams, business charts, and engineering diagrams. EDraw Max offers a
very intuitive point and click interface for Gantt charts, fault tree diagrams, UML,
wiring plans, architectural diagrams, and much more. These are all standardized with
colorful elements that are very easy to digest. You can easily lay out office space or
other concerns like fire escape plans, entity relationship (ER) diagrams, and much
more with EDraw Max. If you need to create standard business charts, BPMN, P&ID,
or value stream mapping, EDraw Max makes it quick and easy and allows the
bringing in of other data for relevance. Edraw Max, from Wonder share, is an all-in-
one diagram software designed to make it simple to create professional-looking
flowcharts, organizational charts, network diagrams, business presentations, building
plans, mind maps, science illustration, fashion designs, UML diagrams, workflows,
program structures, web design. Edraw Max is a 2D business technical diagramming
software which helps create flowcharts, organizational charts, mind map, network
diagrams, floor plans, workflow diagrams, business charts, and engineering
diagrams. EDraw Max offers a very intuitive point and click interface for Gantt
charts, fault tree diagrams, UML, wiring plans, architectural diagrams, and much
more. These are all standardized with colorful elements that are very easy to digest.
You can easily lay out office space or other concerns like fire escape plans, entity
relationship (ER) diagrams, and much more with EDraw Max. If you need to create
standard business charts, BPMN, P&ID, or value stream mapping, EDraw Max makes
it quick and easy and allows the bringing in of other data for relevance.

3.2.5 Node Js

Node.js is a powerful runtime environment that allows developers to execute

JavaScript code outside of a web browser, enabling server-side scripting and building
scalable network applications. Leveraging Google's V8 JavaScript engine, Node.js
provides an event-driven, non-blocking I/O model, making it efficient and lightweight
for handling concurrent connections. Its package manager, npm, hosts a vast
ecosystem of reusable modules, simplifying the development process. Node.js finds
extensive use in building web servers, APIs, microservices, and real-time
applications, fostering a thriving community and contributing to its rapid adoption.
On the other hand, CSS (Cascading Style Sheets) is a fundamental language for
styling web documents, defining the presentation of HTML elements. CSS enables
developers to control layout, typography, colors, and other visual aspects of a
webpage, enhancing its aesthetics and user experience. With CSS, designers can
create responsive and visually appealing interfaces, utilizing features like Flexbox and
Grid for efficient layout design. CSS preprocessors such as Sass and Less offer
advanced features like variables, mixins, and nested rules, streamlining stylesheet
authoring. Integrating Node.js with CSS workflows enhances development efficiency,
allowing for automated tasks like compiling, optimizing, and bundling stylesheets
through build tools like Webpack or Gulp, ultimately facilitating the creation of
robust and visually stunning web applications.

3.3 Summary
This chapter we have discussed about the hardware and software used in our project.
We use different tools like Visual Studio, Google Chrome and Edraw Max.
Languages are used in Node Js, CSS. Discussed the details of software’s used in our
project.
Chapter 4

METHODOLOGIES
A methodology is a set of ideas or guidelines about how to proceed in gathering and
validating knowledge of a subject matter. The methodology section of your
paper describes how your research was conducted. This information allows readers to
check whether your approach is accurate and dependable. A good methodology can
help increase the reader's trust in your findings. Writing a methodology is an essential
part of presenting research findings. Your methodology is a detailed description of the
research process you used to support your findings and it explains your techniques
and creates a roadmap for how you reached your conclusions. A methodology will
give you that path. And choosing a wholly suitable and sound method that is right for
your research project will give you the path to help you succeed. A methodology will
give you the guidelines to make your project manageable, smooth and effective.
Different areas of science have developed very different bodies of methodology on
the basis of which to conduct their research. We might say that a methodology
provides a guide for carrying out some or all of the following activities:

 Probing the empirical details of a domain of phenomena

 Discovering explanations of surprising outcomes or patterns
 Identifying entities or forces
 Establishing patterns
 Providing predictions
 Separating noise from signal
 Using empirical reasoning to assess hypotheses and assertions

4.1 SDLC Models

Software Development life cycle (SDLC) is a spiritual model used in project
management that defines the stages include in an information system development
project, from an initial feasibility study to the maintenance of the completed
application. There are different software development life cycles models specify and
design, which are followed during the software development phase. These models are
also called "Software Development Process Models." Each process model follows a
series of phase unique to its type to ensure success in the step of software
development. A software development life cycle (SDLC) model is a conceptual
framework describing all activities in a software development project from planning
to maintenance. This process is associated with several models, each including a
variety of tasks and activities. Software development is a cumbersome activity
requiring proper identification of requirements, their implementation, and software
deployment. However, the activities do not end there. After the distribution of the
software, proper maintenance has to be provided in a timely manner. SDLC is a
systematic process for building software that ensures the quality and correctness of
the software built. SDLC process aims to produce high-quality software that meets
customer expectations. The system development should be complete in the pre-
defined time frame and cost. SDLC consists of a detailed plan which explains how to
plan, build, and maintain specific software. Every phase of the SDLC life Cycle has
its own process and deliverables that feed into the next phase. SDLC stands
for Software Development Life Cycle and is also referred to as the Application
Development life-cycle. Proper planning is an essential aspect of the software
development life cycle. From there, team members develop and execute plans into the
software. In this guide, you’ll learn the basic components of the SDLC. We’ll show
you how these phases can be implemented to manage any development effort
successfully. Lastly, we’ll review some of the most popular software development life
cycle methodologies. Software development life cycle methods are continually
evolving. Since its inception with the Waterfall model, the SDLC has changed to fit
various scenarios. As a result, software development teams have multiple models to
reference. Successful pieces of these models have been hybridized into newer, more
refined models. There are numbers of methods/models in software development life
cycle but the method we choose is the following:
 Incremental/iterative Model
4.2 Incremental Model
There are some situations in which requirements for a software well defined. There
may be need to provide some set of software features to customers first and then do
the necessary changes to the product based on the feedback of customers in later
releases. The incremental model suits this approach. In incremental model, the first
increment is a base/core product. It means that some basic requirements of customers
are fulfilled. This core product examined by customer and is evaluated. Based on
customer evaluation, a plan for next increment is developed. This process is continued
after the delivery of each increment, and goes on until the entire software is
developed.

Figure 4. 1 Incremental Life Cycle

The various phases of incremental model are as follows:

Requirement analysis: In the first phase of the incremental model, the product
analysis expertise identifies the requirements. And the system functional requirements
are understood by the requirement analysis team. To develop the software under the
incremental model, this phase performs a crucial role.
Design & Development: In this phase of the Incremental model of SDLC, the design
of the system functionality and the development method are finished with success.
When software develops new practicality, the incremental model uses style and
development phase.
Testing: In the incremental model, the testing phase checks the performance of each
existing function as well as additional functionality. In the testing phase, the various
methods are used to test the behavior of each task. Implementation: Implementation
phase enables the coding phase of the development system. It involves the final
coding that design in the designing and development phase and tests the functionality
in the testing phase. After completion of this phase, the number of the product
working is enhanced and upgraded up to the final system product

4.3 Verification of Functional Requirements

Functional requirements may involve calculations, technical details, data
manipulation and processing and other specific functionality that define what a
system is supposed to accomplish. Functional requirements are those which are
related to the technical functionality of the system. A functional requirement defines
the function of a system and its components. A function is described as a set of inputs,
the behavior, and outputs. In simpler terms, Requirements verification is the process
of confirming that the system requirements contain all the necessary elements of well-
written requirements. Requirements validation is the process of confirming that the
system meets its objectives and functions as intended. In other words, verification is
about checking whether the requirements are complete, correct, and consistent.
Validation is about checking whether the system meets its objectives and functions as
intended. VI sure Requirements is a Requirements Lifecycle Management platform
that can be used for Requirements Verification. VI sure Requirements helps
organizations manage, trace, and verify requirements throughout the software
development process. The platform provides various features and tools that can be
used in requirements verification, including, A Requirements Traceability Matrix that
can be used to trace requirements from the requirements document to the test cases.
Requirements Management tools that can be used to manage and track changes to
requirements. A Requirements Verification Report that can be generated to check the
completeness, correctness, and consistency of the requirements.
4.3.1 Functional Requirements

Functional requirements are product features or functions that developers must

implement to enable users to accomplish their tasks. So, it’s important to make them
clear both for the development team and the stakeholders. Generally, functional
requirements describe system behavior under specific conditions. For example: The
system sends an approval request after the user enters personal information. A search
feature allows a user to hunt among various invoices if they want to credit an issued
invoice.
In our project functions requirement given below:

 User
 Admin

4.3.2 Admin Module

The Admin Module of the Online Cake Bakery System facilitates efficient
management of the platform, enabling administrators to oversee various aspects
seamlessly. Through this module, administrators can regulate user accounts, monitor
inventory levels, manage orders, and update product listings. It offers a
comprehensive dashboard where administrators can access vital statistics, analyze
sales data, and generate reports to inform decision-making processes. Additionally,
the Admin Module streamlines communication with customers, allowing
administrators to address inquiries promptly and ensure customer satisfaction. With
its intuitive interface and robust features, the Admin Module plays a pivotal role in
ensuring the smooth operation and growth of the Online Cake Bakery System.

4.3.3 User Module

 The User Module within the documentation of the Online Cake Bakery
System encompasses three crucial components: Customer Interface, Admin Panel,
and Baker Dashboard. The Customer Interface serves as the primary point of
interaction for users, facilitating seamless browsing, selection, and purchase of cakes.
It incorporates features like personalized accounts, intuitive navigation, and secure
payment gateways to enhance user experience. The Admin Panel empowers bakery
administrators with tools for managing inventory, processing orders, and monitoring
customer feedback, ensuring efficient operations and quality control. Meanwhile, the
Baker Dashboard provides pastry chefs with real-time updates on order specifications,
enabling timely preparation and delivery of freshly baked goods. Together, these
modules synergize to deliver a cohesive and user-centric online bakery experience,
catering to the needs of customers, administrators, and bakers alike.

4.4 Non-functional Requirement

 Reliability: The system is expected to preserve a backup of the data in case of
data loss.
 Design: The desktop application will be built with the JAVA programming
language Using, MYSQL as the database.
 Flexibility: Because the program is written in JAVA, it is scalable and quickly
ready for new modifications. Any new updates can be effectively implemented
without any hassle.
 Security: To identify the user and provide them access, the program employs
high-Level encryption.
 Response time: The system will respond to any inquiries with lightning
speed. The Files will open rapidly, and the user interface will be fluid and
responsive.
 Guidelines Compliance: Throughout the program, the User Interface and
User Experience will have a constant appearance and feel. Because the Bakery
Management System is a desktop program, it may be moved from one
computer to another.
 Availability: The system will be available 24 hours a day, 7 days a
week. Furthermore, if any important changes or maintenance is required, the
user groups will be alerted in advance.
4.4.2 Reliability

The Reliability section of the documentation for the Online Cake Bakery
System emphasizes the system's consistent performance and dependable functionality.
Users can rely on the platform to consistently deliver a seamless experience, ensuring
that orders are processed accurately and efficiently. Through rigorous testing and
meticulous development, the system maintains a high level of reliability, minimizing
downtime and errors. From placing orders to payment processing and delivery
tracking, every aspect of the system operates reliably to meet customer expectations.
Additionally, robust security measures are in place to safeguard sensitive information,
enhancing trust and confidence in the system's reliability. Overall, the Online Cake
Bakery System prioritizes reliability to ensure a smooth and dependable experience
for both customers and administrators alike, fostering long-term satisfaction and
loyalty.

4.4.3 Performance

The Performance section of the documentation for the Online Cake Bakery
System emphasizes the operational efficacy and functional excellence of the platform.
Through rigorous testing and meticulous development, the system demonstrates
remarkable efficiency in handling user interactions, order processing, inventory
management, and delivery logistics. Performance benchmarks indicate swift response
times for user queries, seamless navigation across the platform, and expedited
checkout processes, ensuring a satisfying user experience. Additionally, the system
showcases robust scalability, capable of accommodating fluctuating user demands
without compromising performance metrics. Continuous monitoring and optimization
strategies have been employed to uphold optimal performance levels under varying
load conditions. By prioritizing reliability and speed, the Online Cake Bakery System
exemplifies its commitment to delivering a seamless and delightful online shopping
experience for users, thereby enhancing customer satisfaction and fostering sustained
business growth.

4.5 Design
The documentation for the Online Cake Bakery System encapsulates a
comprehensive overview of the system's design, functionality, and implementation.
The system aims to provide users with a seamless online platform to browse through a
diverse array of cakes, place orders, and manage their accounts effortlessly. At its
core, the system comprises several interconnected modules, including user
authentication, product catalog management, order processing, payment integration,
and administrative tools. Users are greeted with an intuitive interface upon accessing
the platform, allowing them to navigate through various cake categories, view
detailed product descriptions, and add desired items to their shopping carts. The
system employs robust security measures to ensure the confidentiality and integrity of
user data, incorporating features such as encryption protocols and secure payment
gateways. Furthermore, an administrative dashboard empowers bakery staff to
manage inventory, track orders, and analyze sales data efficiently. Seamless
integration with third-party delivery services streamlines the fulfillment process,
ensuring timely delivery of orders to customers' doorsteps. Throughout the design
process, careful attention has been paid to scalability, extensibility, and usability,
enabling the system to adapt to evolving business requirements and technological
advancements seamlessly. Overall, the Online Cake Bakery System represents a
sophisticated yet user-friendly solution, poised to revolutionize the way customers
interact with and enjoy baked goods in the digital age.

4.5.1 Use Case Diagram

A use case is a methodology used in system analysis to identify, clarify, and

organize system requirements. The use case is made up of a set of possible sequences
of interactions between systems and users in particular environment and related to a
particular goal. Models the goals of system/actor interactions. The main purpose of a
use case diagram is to show who interacts with your system, and the main goals they
achieve with it. Use case diagram show the various activities the user can perform on
the system. The system is something that can perform a function. They model the
dynamic aspects of the system. As mentioned before use case diagrams are used to
gather a usage requirement of a system. Depending on your requirement you can use
that data in different ways. Below are few ways to use them. The system is used
to define the scope of the use case and drawn as a rectangle. This optional element but
useful when you’re visualizing large systems. For example, you can create all the use
cases and then use the system object to define the scope covered by your project. Or
you can even use it to show the different areas covered in different releases.
It provides a user's particular of the system:
Actor: Actor specifies a role played by a user or any other system that interacts with
the subject.
Use case: Use case is a list of steps, typically defining interactions between an actor
and a system, to achieve a goal.
Relationship: Relationship is simply illustrated with a line connecting actors to use
cases.
 Figure 4. 2 Use Case Diagram

4.5.2 Activity Diagram

An activity diagram visually presents a series of actions or flow of control in a

system similar to a flowchart or a data flow diagram. Activity diagrams are often used
in business process modeling. They can also describe the steps in a use case diagram.
Activities modeled can be sequential and concurrent. Activity diagram is another
important diagram in UML to describe the dynamic aspects of the system. Activity
diagrams are graphical representations of workflows of stepwise activities and actions
with support for choice, iteration and concurrency. Although activity diagrams
primarily show the overall flow of control, they can also include elements showing
the flow of data between activities through one or more data stores. Activity diagrams
are constructed from a limited number of shapes, connected with arrows. Activity
Diagrams describe how activities are coordinated to provide a service which can be at
different levels of abstraction. Typically, an event needs to be achieved by some
operations, particularly where the operation is intended to achieve a number of
different things that require coordination, or how the events in a single use case relate
to one another, in particular, use cases where activities may overlap and require
coordination.
The most important shape types:
 Rounded rectangles represent actions.
 Diamonds represent decisions.
 An encircled black circle represents the end.

A UML activity diagram helps to visualize a certain use case at a more

detailed level. It is a behavioral diagram that illustrates the flow of activities through a
system.UML activity diagrams can also be used to depict a flow of events in a
business process. They can be used to examine business processes in order to identify
their flow and requirements. Activity diagrams can be used to model business
requirements, create a high-level view of a system’s functionalities, analyze use cases,
and for various other purposes. In each of these cases, here’s how to draw an activity
diagram from the beginning. Here you need to identify the various activities and
actions your business process or system is made up of. If you already have figured out
who the actors are, then it’s easier to discern each action they are responsible for.
Mark down the conditions that have to be met in order to carry out certain processes,
which actions occur at the same time and whether you need to add any branches in the
diagram. The flow of execution is modeled as activity nodes connected by activity
edges. A node can be the execution of a subordinate behavior, such as an arithmetic
computation, a call to an operation, or manipulation of object contents. Activity nodes
also include flow of control constructs, such as synchronization, decision, and
concurrency control. Activities may form invocation hierarchies invoking other
activities, ultimately resolving to individual actions. In an object-oriented model,
activities are usually invoked indirectly as methods bound to operations that are
directly invoked. As a behavior activity could have pre- and post-condition
constraints. If present, these are shown with the keyword’s «precondition» and «post
condition», respectively. The keyword «single Execution» is used for activities that
execute as a single shared execution (singleton), otherwise, each invocation executes
in its own space. The round-cornered activity border may be replaced with the frame
notation for diagrams. The kind of the frame in this case is activity or act in short
form. Activity Diagrams describe how activities are coordinated to provide a service
which can be at different levels of abstraction. Typically, an event needs to be
achieved by some operations, particularly where the operation is intended to achieve
a number of different things that require coordination, or how the events in a single
use case relate to one another, in particular, use cases where activities may overlap
and require coordination. It is also suitable for modeling how a collection of use
cases coordinates to represent business workflows. The activity diagram example
below describes the workflow for a word process to create a document through the
following steps:
 Open the word processing package.
 Create a file.
 Save the file under a unique name within its directory.
 Type the document.
 If graphics are necessary, open the graphics package, create the graphics, and
paste the graphics into the document.
 If a spreadsheet is necessary, open the spreadsheet package, create the
spreadsheet, and paste the spreadsheet into the document
 Save the file.
 Print a hard copy of the document.
 Exit the word processing package.
 The registrar inspects the forms.
 The registrar determines that the forms have been filled out properly.
 The registrar informs student to attend in university overview presentation.
 The registrar helps the student to enroll in seminars
 The registrar asks the student to pay for the initial tuition.
 An applicant wants to enroll in the university.
 Figure 4. 3 Activity Diagram of User

4.5.3 Sequence Diagram

A sequence diagrams will show object interactions arranged in time sequence.

It will depict the objects and classes involved in the scenario and the sequence of
messages exchanged between the objects needed to carry out the functionality of the
scenario. Sequence diagrams are typically associated with use case realizations in the
logical View of the system under development. Sequence diagrams are sometimes
called event diagrams or event scenarios. Sequence diagrams, commonly used by
developers, model the interactions between objects in a single use case. They illustrate
how the different parts of a system interact with each other to carry out a function,
and the order in which the interactions occur when a particular use case is executed.
In simpler words, a sequence diagram shows how different parts of a system work in a
‘sequence’ to get something done. Sequence diagram or system sequence
diagram (SSD) shows process interactions arranged in time sequence in the field
of software engineering. It depicts the processes involved and the sequence of
messages exchanged between the processes needed to carry out the functionality.
Sequence diagrams are typically associated with use case realizations in the 4+1
architectural view model of the system under development. Sequence diagrams are
sometimes called event diagrams or event scenarios. For a particular scenario of a use
case, the diagrams show the events that external actors generate, their order, and
possible inter-system events. All systems are treated as a black box; the diagram
places emphasis on events that cross the system boundary from actors to systems. A
system sequence diagram should be done for the main success scenario of the use
case, and frequent or complex alternative scenarios. This sequence diagram
tutorial is to help you understand sequence diagrams better; to explain
everything you need to know, from how to draw a sequence diagram to the
common mistakes you should avoid when drawing one. There are 3 types of
Interaction diagrams; Sequence diagrams, communication diagrams, and
timing diagrams. These diagrams are used to illustrate interactions between
parts within a system. Among the three, sequence diagrams are preferred by
both developers and readers alike for their simplicity. A sequence diagram is
structured in such a way that it represents a timeline that begins at the top
and descends gradually to mark the sequence of interactions. Each object
has a column and the messages exchanged between them are represented by
arrows. No two lifeline notations should overlap each other. They represent
the different objects or parts that interact with each other in the system
during the sequence.A lifeline notation with an actor element symbol is used
when the particular sequence diagram is owned by a use case.
 Figure 4. 4 Sequence diagram of FYP

This sequence diagram tutorial is to help you understand sequence diagrams

better; to explain everything you need to know, from how to draw a sequence
diagram to the common mistakes you should avoid when drawing one. There
are 3 types of Interaction diagrams; Sequence diagrams, communication
diagrams, and timing diagrams. These diagrams are used to illustrate
interactions between parts within a system. Among the three, sequence
diagrams are preferred by both developers and readers alike for their
simplicity.

4.6 Summary
In this chapter we have discussed about the methodology which is used to
develop our project. Its phases and detail about some of those phases. Also discussed
the function and non-function requirements. Discussed about the use case diagram,
activity diagram and sequence diagram. A sequence is defined as an arrangement of
numbers in a particular order. On the other hand, a series is defined as the sum of the
elements of a sequence. An arithmetic sequence is a sequence where the difference d
between successive terms is constant. The general term of an arithmetic sequence can
be written in terms of its first term a1, common difference d, and index n as follows:
An=a1+ (n−1) d. An arithmetic series is the sum of the terms of an arithmetic
sequence. The main aim of research is not merely to gather information. Instead, it
goes beyond that. The true goal of research is to seek answers to previously
unanswered questions to contribute to the body of knowledge in a discipline Goddard
and Melville (2001, p.1). But for your peers, and indeed the whole world, to
recognize your newly discovered or created knowledge, you have to show evidence of
its validity or truthfulness. For novice researchers, writing the methodology of a
research paper can be an overwhelming process, especially considering the intricate
elements covered by this section (J. Ellis & Levy, 2009, p. 323). The goal of this
article is to guide novice researchers in writing an effective research methodology by
helping them gain a clear understanding of a research methodology’s structure. To
summarize these definitions, methods cover the technical procedures or steps taken to
do the research, and methodology provides the underlying reasons why certain
methods are used in the process Research methods lay down the foundation of your
research. According to Neil McInroy, the chief executive of Centre for Local
Economic Strategies, not using the appropriate research methods and design creates
“a shaky foundation to any review, evaluation, or future strategy (Macdonald et al.,
2008, p. 3). In any type of research, the data you will gather can come either in the
form of numbers or descriptions, which means you will either be required to count or
converse with people (Macdonald et al., 2008, p. 9). In research, there are two
fundamental methods used for either approach quantitative and qualitative research
methods. Even if you take the path of a philosophy career, these are still methods that
you may encounter and even use.
Chapter 5
SYSTEM TESTING
System testing, also referred to as system-level tests or system-integration testing, is
the process in which a quality assurance (QA) team evaluates how the various
components of an application interact together in the full, integrated system or
application. The purpose of system testing is to ensure that a system meets its
specification and any non-functional requirements that have been agreed with its
users. System testing is a series of different type of tests with the purpose to exercise
and examine the full working of an integrated software computer system against
requirements. To check the end-to-end flow of an application or the software as a user
is known as System testing. In this, we navigate all the necessary modules of an
application and check if the end features or the end business works fine, and test the
product as a whole system. It is end-to-end testing where the testing environment is
similar to the production environment
5.1 Objective Testing
The objective of this documentation is to comprehensively assess the Online
Cake Bakery System, covering its functionality, usability, reliability, scalability, and
security aspects. Through rigorous testing procedures, we aim to evaluate the system's
capability to seamlessly facilitate online cake ordering, payment processing, order
management, and delivery tracking. The assessment will focus on ensuring that the
system meets the requirements outlined in the project specifications, adheres to
industry standards for e-commerce platforms, and delivers a satisfying user
experience. Additionally, performance testing will be conducted to gauge the system's
responsiveness under varying loads and to identify potential bottlenecks for
optimization. Security testing will scrutinize the system's defenses against common
vulnerabilities such as SQL injection, cross-site scripting, and unauthorized access,
ensuring robust protection of sensitive customer data and financial transactions.
Usability testing will involve assessing the intuitiveness of the user interface, ease of
navigation, and clarity of instructions, aiming to enhance user satisfaction and
minimize friction in the ordering process. Moreover, compatibility testing will verify
the system's functionality across different devices, browsers, and operating systems,
ensuring broad accessibility for users. Ultimately, this comprehensive testing
approach seeks to validate the Online Cake Bakery System's readiness for
deployment, ensuring its reliability, performance, security, and user-friendliness.

5.2 Usability Testing

Usability testing is a technique used in user-centered interaction design to evaluate
a product by testing it on users. This can be seen as an irreplaceable usability practice,
since it gives direct input on how real users use the system. Usability testing refers
to evaluating a product or service by testing it with representative users. Typically,
during a test, participants will try to complete typical tasks while observers watch,
listen and takes notes. Usability testing refers to evaluating a product or service by
testing it with representative users. Typically, during a test, participants will try to
complete typical tasks while observers watch, listen and takes notes. The goal is to
identify any usability problems, collect qualitative and quantitative data and
determine the participant's satisfaction with the product. To run an effective usability
test, you need to develop a solid test plan, recruit participants, and then findings.
Benefits of Usability Testing Usability testing lets the design and development teams
identify problems before they are coded. The earlier issues are identified and fixed,
the less expensive the fixes will be in terms of both staff time and possible impact to
the schedule. During a usability test, you will:
 Learn if participants are able to complete specified tasks successfully and
Identify
 how long it takes to complete specified tasks
 Find out how satisfied participants are with your Web site or other product
 Identify changes required to improve user performance and satisfaction and
analyze the performance to see if it meets your usability objectives

5.3 Software Performance Testing

Performance testing is a non-functional software testing technique that determines
how the stability, speed, scalability, and responsiveness of an application holds up
under a given workload. In software quality assurance, performance testing is in
general a testing practice performed to determine how a system performs in terms of
responsiveness and stability under a particular workload.
 Identify the Test Environment and Tools. Identify the production environment,
testing environment, and testing tools at your disposal.
 Define Acceptable Performance Criteria
 Plan and Design Tests
 Prepare Test Environment and Tools
 Run the Performance Tests
 Resolve and Retest.
 Figure 5.3 Testing Life Cycle

Performance testing is a type of testing for evaluating the non-functional error

prone scenarios like the application’s efficiency, the behavior of the application to act
under certain conditions, the volume of data flowing through the application
databases/ interfaces, etc. For performance testing, the life cycle starts from analyzing
the non-functional areas, test strategy required, testing flow design, and analysis for
test results. A few of the various types of performance testing are Testing load, testing
stress, testing endurance and testing the volume. Performance testing is required in
software engineering before the commercialization of any software product. It
guarantees customer satisfaction and protects an investor from a product failure.
Performance testing is a non-functional software testing technique that determines
how the stability, speed, scalability, and responsiveness of an application holds up
under a given workload. It’s a key step in ensuring software quality, but
unfortunately, is often seen as an afterthought, in isolation, and to begin once
functional testing is completed, and in most cases, after the code is ready to
release. The goals of performance testing include evaluating application output,
processing speed, data transfer velocity, network bandwidth usage, maximum
concurrent users, memory utilization, workload efficiency, and command
response times.

Res Completion Time Bug / Error

ult Type (In seconds) (If yes give detail)
Format 2s No
Color 3s No
Open 4s No
Save 5s No
Size 2s No
 Table 5. 1 Software Performance Testing

5.4 Compatibility Testing

Compatibility Testing is a type of Software testing to check whether your
software is capable of running on different hardware, operating systems, applications,
network environments or Mobile devices. The full compatibility testing process
involves typing; screening for antibodies against other blood group systems; and
crosshatching, which involves testing the recipient's blood plasma against the donor's
red blood cells as a final check for incompatibility. Compatibility Testing is a type of
Software testing to check whether your software is capable of running on different
hardware, operating systems, applications, network environments or Mobile devices.

The most important steps during the process are correct identification of

the patient and selecting blood of the correct ABO group for the patient.

Cross matching is a relatively simple process but if not carried out

correctly, can lead to the wrong blood being transfused into the patient,

with possible disastrous consequences. When this happens, it is usually

the result of patient misidentification and/or the switching of patient

samples, either in the hospital or in the crosshatching laboratory/blood

bank. By the end of this section, the student should be able to describe

compatibility testing, the selection of blood in various situations and the

use of replacement fluids and red cell substitutes, relating all aspects of

cross matching to quality standards. The student should also be able to

discuss the importance of patient identification and records, and the

preliminary investigation of transfusion reactions. Concepts of crossmatchingPatient
and sample identification. Compatibility or pretransfusion testing involves the cross
matching of selected donor blood of appropriate ABO and RhD type for a patient
requiring a blood transfusion.

Testin Version Compatible (Yes / No)

g Tool
Chrome Browser Any version Yes
Internet Explore 11 Yes

Table 5.2 Compatibility Testing

5.5 Load Testing

Load testing is the process of putting simulated demand on software, an

application or website in a way that tests or demonstrates its behavior under various
conditions. Some basic examples of load testing are: Testing a printer by transferring
a large number of documents for printing. Testing a mail server with thousands of
concurrent users. Testing a word processor by making a change in the large volume of
data. On the editor toolbar, you set the test duration. Readapt will simulate requests to the
target web server until the specified timeout elapses, or until the test stops for some other
reason. If no timeout is specified, you need to stop the test manually. The progress bar at
the top of the editor shows the test run progress. IN this panel, you can select a load type
and configure your load test scenarios. In the Load Type drop-down list, you select
the load type you want to use in your load tests:

 VUs – Readapt will simulate virtual users that will send requests to the target web
service.
 Rate – Readapt will send requests to the target web service at the specified rate.

To edit the simulated load, click the load scenario you want to edit and edit the values in
the Scenario section of the Editor panel. To create an assertion, click the scenario or test
step you want to assert and create it in the Editor panel. Some basic examples of load
testing are: Testing a printer by transferring a large number of documents for printing.
Testing a mail server with thousands of concurrent users. Testing a word processor by
making a change in the large volume of data. Load testing is the process of putting
simulated demand on software, an application or website in a way that tests or
demonstrates its behavior under various conditions.

Test Environment No. of Users Sustainability

Application 1 Yes

Table 5.3 Load Testing

5.6 Security Testing
Security testing is a process intended to reveal flaws in the security
mechanisms of an information system that protect data and maintain functionality as
intended. A password must be stored in an encrypted way. Invalid users should not be
allowed to access the application or system. For application, check cookies and
session time. The browser back button should not operate on financial sites. Security
testing is a sort of software testing that identifies vulnerabilities, hazards, and dangers
in a software program and guards against intruder assaults. The goal of security tests
is to find any potential flaws and vulnerabilities in the software system that might lead
to a loss of data, income, or reputation at the hands of workers or outsiders. It is
universally acknowledged that deferring security testing until after the software
implementation process or after deployment would increase costs. As a result,
security testing must be included early in the SDLC life cycle. A password must be
stored in an encrypted way. Invalid users should not be allowed to access the
application or system. For application, check cookies and session time. The browser
back button should not operate on financial sites. Security Testing is a type of
Software Testing that uncovers vulnerabilities of the system and determines that the
data and resources of the system are protected from possible intruders. It ensures that
the software system and application are free from any threats or risks that can cause a
loss. The main benefit of security testing is that it can help identify potential security
risks in the software or application before it is released to the public. This can help
avoid devastating consequences, such as data breaches and loss of customer trust. You
should use security testing to verify that there are secure interfaces between internal
systems, and that insider threats or compromised accounts cannot be used to escalate
privileges. This moves your organization closer to a zero-trust security model. The
main benefit of security testing is that it can help identify potential security risks in
the software or application before it is released to the public. This can help avoid
devastating consequences, such as data breaches and loss of customer trust.

5.6.1 Focus Areas

Editors focus on a few major areas while editing papers, including grammar,
punctuation, spelling and sentence structure; sometimes, they may also focus on
clarity, consistency and organization. Editing involves looking at each sentence
carefully, and making sure that it's well designed and serves its purpose. Proofreading
involves checking for grammatical and punctuation errors, spelling mistakes, etc.
Proofing is the final stage of the writing process. Editors focus on a few major areas
while editing papers, including grammar, punctuation, spelling and sentence structure;
sometimes, they may also focus on clarity, consistency and organization. Editing
involves a proactive editor making changes and suggestions that will improve the overall
quality of your writing, particularly in relation to language use and expression. After
editing, your language will be sharp and consistent, your expression clear and the overall
readability of your writing enhanced. Spell checkers are not always the best at deciding if
you are using the right form of a word. I love Grammar because it usually does an
excellent job of being able to tell if I am using the correct form of a word for the sentence
I am writing. For those words like too, to, and two or their, they’re, and there you want to
make sure that you read the sentences those words are in and understand the context.
Sometimes we get keyboard happy, and this causes us to misspell words unnecessarily.
We may know how to spell a word, but as we are typing it comes out wrong. Word
processors like Microsoft Word are usually able to catch some of these things, but it does
not always happen that way. You need to be ready to step in if that is the case. Grammar
and readability. You need to make sure there aren’t any obvious errors. However, you
also need to make sure your reader can understand what you wrote. Your sentence, plot,
etc. could make sense to you but be gibberish to your reader. A second pair of eyes is
always a good idea. The importance of editing after writing your paper is to make sure
that it is persuasive and well-rounded to the reader. No matter how significant your
research is, to be successful during the peer review process your
manuscript must be properly edited. The effectiveness of your writing style and
clarity of your work can be significantly improved by good editing. The purpose of
the editing step is to make sure your paper is written in an order that
communicates your research, and your ideas are presented in the best way.

Test Type Result (Pass or Fail)

Risk Assessment Test Pass
Security Test Pass
Installation Test Fail
Security Scanning Fail
Security Auditing Pass
 Table 5.4 Security Testing
5.7 Installation Testing
Most software systems have installation procedures that are needed before
they can be used for their main purpose. Testing these procedures to achieve an
installed software system that may be used is known as installation testing. This
procedure may involve full or partial upgrades, and install/uninstall processes.
Installation testing may look for errors that occur in the installation process that affect
the user's perception and capability to use the installed software. There are many
events that may affect the software installation and installation testing may test for
proper installation whilst checking for a number of associated activities and events.
Some examples include the following:
 A user must select a variety of options.
 Dependent files and libraries must be allocated, loaded or located.
 Valid hardware configurations must be present.

Installation Environment Result (Pass or Fail)

Windows OS Pass
 Software systems may need connectivity to connect to other software
systems.

Table 5.5 Installation Testing

5.8 Test Cases
 A test case is a specification of the inputs, execution conditions, testing
procedure, and expected results that define a single test to be executed to achieve a
particular. A test scenario measuring functionality across a set of actions or
conditions to verify the expected result. They apply to any software application, can
use manual testing or an automated test, and can make use of test case management
tools. A test case template is a document that comes under one of the test artifacts,
which allows testers to develop the test cases for a particular test scenario in order to
verify whether the features of an application are working as intended or not. Test
cases are the set of positive and negative executable steps of a test scenario which has
a set of pre-conditions, test data, expected results, post-conditions, and actual results.
Most of the companies are using test case management tools such as Quality Center
(HP QC), JIRA, etc., and some of the companies still using excel sheets to write test
cases. In this post we are going to discuss test cases for online text editor. There are
plenty of online text editor. And some of them are now even being used as an IDE.
However, we are going to limit our discussion to the online text editor. Here you may
write the code in text format and able to save the file in specific extension. And at the
end of the coding, you can download the file. So, let’s take a look at the test scenario
and some of the test cases for the online text editor. Test Scenario for Online Editor.
Online text editors are designed to replace the desktop dependency for text editing.
Here you get all the features necessary for editing the text. You can use different
fonts. You can format the text with different options such as italicize, justify the
alignment and do many other texts processing. All of these settings can be preserved
depending on the exported format from the text editor. So, we are going to test the
online text editor with following test cases in mind. If you have any specific text
editor’s test cases then feel free to let me know in the comments. These are some of
the generic levels of the test cases that you can check for the online editor. This can be
used with both online and offline text editors and IDE. And you can manage to add
and remove more test scenarios depending on the available set of features. You may
also find test cases for notepad handy if you’re trying to test similar type of
applications. Feel free to let me know about the test scenarios and the test cases for
editor in this case. Select the down arrow to the right of the Assigned To field and
select the checkbox next to the name of the tester you want to assign to this test case.
In the Description text box, enter a description of the Test Case.
Test ID 001 Test Name Button

Written By: Iqra Bibi Document Date: 02-jan-2024

Software Online Cake Bakery Test Level Unit testing

Name: System

Test objectives The purpose of testing to ensure that all buttons

are working accurately.
Test environment Visual Studio, RAM 4GB

Step 1 Open Application

Step 2 Fill all options of First layout

Step 3 Type the Questions

Expected result User Successful register if data is validated, if

data is not valid error show, please enter your
valid information.
Post condition Successfully
Actual result User must be successfully register after providing
valid user type

Status Success

Table 5.6 Test Case 1 Open Application

Test Case is a detailed step-by-step instruction on how to perform certain tests on

your system, software, or application. It is the first level action for the test execution
and is derived from test scenarios. These are usually written by the QA team
members. A set of test inputs, execution conditions, and expected results developed
for a particular objective, such as to exercise a particular program path or to verify
compliance with a specific requirement. In order to fully test that all the requirements
of an application are met, there must be at least two test cases for each requirement:
one positive test and one negative test. If a requirement has sub-requirements, each
sub-requirement must have at least two test cases. More specifically, a test case
design is a document that includes the test's scope, the test strategy, the test
environment, and the software pieces for testing, the intended test actions within the
project, the resources, and a schedule. A test case template is a document containing
an organized list of test cases for different test scenarios that check whether or not the
software has the intended functionality. A test case is a set of steps carried out to test a
specific feature of an application. Essentially, the test case details the steps, data,
prerequisites, and post conditions necessary to verify a feature.

Test ID 002 Test Name Buttons

Written By: Iqra Bibi Document Date: 02 Jan 2024
Software Name: Online Cake Test Level Unit testing
Bakery System

Test objectives The purpose of testing to ensure that all

buttons are working accurately.
Test environment Visual Studio, RAM 4GB
Step 1 Open Application
Step 2 Fill all options of First layout
Step 3 Type the Questions
Expected result User Successful register if data is validated, if
data is not valid error show, please enter your
valid information.
Post condition Successfully
Actual result User must be successfully register after
providing valid user type
Status Success

Table 5.7 Test Case 2 Supervisor Performance

It is an ongoing, collaborative process between supervisor and employee that

aims to establish and clarify expectations as well as set performance and development
goals. Individuals who are successful in this role often possess both interpersonal and
management skills, plus an approachable, confident and supportive personality. A
great supervisor is one who strives to continually learn, build upon their strengths and
identify any areas of weakness in which to improve. Performance appraisal is
generally done in systematic ways which are as follows: The supervisors measure the
pay of employees and compare it with targets and plans. The supervisor analyses the
factors behind work performances of employees. The employers are in position to
guide the employees for a better performance. Successful supervisors multiply talent,
making everyone smarter and better at their jobs. They cultivate talent and
intelligence throughout their team by teaching and mentoring their employees,
bringing people together to participate and generate ideas; and giving their team
autonomy, authority, and responsibility.

Test ID 003 Test Name Button

Written By: Iqra Bibi Documented Date: O2 Jan 2024

Software Name: Online Cake Test Level Unit testing
Bakery System

Test objectives The purpose of testing to ensure that all buttons

are working accurately.
Test environment Visual Studio, RAM 4GB
Step 1 Open Application
Step 2 Fill all options of First layout

Step 3 Type the Questions

Expected result User Successful register if data is validated, if

data is not valid error show, please enter your
valid information.
Post condition Successfully

Status Access

Table 5. 1 Test Case 3 Student

For a Test Scenario: Check Login Functionality there many possible test cases
are: Test Case 1: Check results on entering valid User Id & Password. Test Case 2:
Check results on entering Invalid User ID & Password. Test Case 3: Check response
when a User ID is Empty & Login Button is pressed, and many more. A test case
template is a document containing an organized list of test cases for different test
scenarios that check whether or not the software has the intended functionality. A test
case is a set of steps carried out to test a specific feature of an application.
Functionality Test Case. User Interface Test Case. Performance Test Case. Integration
Test Case. It is simply a catalog of tasks that you record for easier tracking. A
software test checklist details the tests that you should run in a specific procedure.
Using a software test checklist allows you to identify all the tests you should run, the
number of successful and failed tests. A test case is a document with instructions on
testing the specific functionality of an application. Test Script is a program that runs
various test data on the functionality of an application.

Test ID 004 Test Name Button

Written By: Iqra Bibi Document Date: 02 Jan 2024
Software Name: Online Cake Test Level Unit testing
Bakery System

Test objectives The purpose of testing to ensure that all buttons are
working accurately.
Test environment Visual Studio, RAM 4GB
Step 1 Open Application
Step 2 Fill all options of First layout
Step 3 Type the Questions

Expected result User Successful register if data is validated, if data

is not valid error show, please enter your valid
information.
Post condition Successfully

Status Access

Table 5.9 Test Case 4 Panel

A test case template is a document containing an organized list of test cases for
different test scenarios that check whether or not the software has the intended
functionality. A test case is a set of steps carried out to test a specific feature of an
application. Each user story will often have at least four or five test cases. If you add
edge cases the number of test cases can increase exponentially. Writing test cases
often gives you your first thorough look into a user story and is a good time to ask
questions. Creating one test case usually takes about 10 minutes. The more test cases
your product needs, the more time you should estimate for their development.
However, not all projects require full test case coverage. The developer creates new
features and completes existing ones; 2. The tester tests all this and writes various. On
the white box side of the data testing, the developers prepare the production data. That
is where QA's need to work touch base with the developers for furthering testing
coverage of AUT. One of the biggest challenges is to incorporate all possible
scenarios (100% test case) with every single possible negative case. The Test
information panel shows test statistics of current issue, the section with related to the
issue defects, and a list of available actions. Panel also allows you to export tests
to HTML or PDF file.
Each of the test issues has common section names in the Test information panel but
each panel uses a different data source.

Test ID 005 Test Name Button

Written By: Javeria Document Date: 02 Jan 2024

Software Name: Online Cake Test Level Unit testing

Bakery System

Test objectives The purpose of testing to ensure that all buttons are
working accurately.
Test environment Visual Studio, RAM 4GB

Step 1 Open Application

Step 2 Fill all options of First layout

Step 3 Type the Questions

Expected result User Successful register if data is validated, if data

is not valid error show, please enter your valid
information.
Status Successfully

Table 5.10 Test Case 5 Admin

They are developed for various scenarios so that testers can determine whether the
software is working the way it should and producing the expected results. The test
case should include its number, a description, the test data, expected result, actual
result and status (whether the test passed or failed). Test cases define how to test a
system, software or an application. A test case is a singular set of actions or
instructions for a tester to perform that validates a specific aspect of a product or
application functionality. If the test fails, the result might be a software defect that the
organization can triage. Knowledge of planning and scheduling techniques. Ability to
communicate effectively, both orally and in writing. Knowledge of computer-based
testing and machine scoring. Database management skills. Test cases are typically
written by members of the quality assurance (QA) team or the testing team and can be
used as step-by-step instructions for each system test. Testing begins once the
development team has finished a system feature or set of features. Most commonly,
administrative work includes filing information, managing an office and its supplies,
answering and directing phone calls, writing and answering emails and scheduling
appointments. Higher-level administrators can oversee the daily administrative
operations of an entire company or project. If you add edge cases the number of test
cases can increase exponentially. Writing test cases often gives you your first
thorough look into a user story and is a good time to ask questions. Creating one test
case usually takes about 10 minutes. The more test cases your product needs, the more
time you should estimate for their development. However, not all projects require full
test case coverage. A test case is a set of steps carried out to test a specific feature of
an application. Functionality Test Case. User Interface Test Case. Performance Test
Case. Integration Test Case, these are usually written by the QA team members. A set
of test inputs, execution conditions, and expected results developed for a particular
objective, such as to exercise a particular program path or to verify compliance with a
specific requirement. In order to fully test that all the requirements of an application
are met, there must be at least two test cases for each requirement: one positive test
and one negative test. If a requirement has sub-requirements, each sub-requirement
must have at least two test cases.
Test ID 006 Test Name Button

Written By: Iqra Bibi Documented 02 Jan 2024

Date:
Software Name: Online Cake Test Level Unit testing
Bakery System

Test objectives The purpose of testing to ensure that all buttons

are working accurately.
Pre-condition Visual Studio, RAM 4GB

Step 1 Open Application

Step 2 Fill all options of First layout

Step 3 Type the Questions

Expected result User Successful register if data is validated, if

data is not valid error show, please enter your
valid information.
Post condition Successfully
Actual result Access

Status The purpose of testing to ensure that all buttons

are working accurately.

Table 5.11 Test Case 6 Add Panel

Verify whether the button is clickable or not. Check that when the user clicks on
submit button without entering data in the mandatory filed then the error message for
the mandatory field shows or not. Check whether the page redirects to the expected
page or not when the user enters the valid data in all the fields. Add-on tests are tests
that are performed on an existing specimen previously submitted to the pathology
service with an earlier test order. Verify if a user will be able to login with a valid
username and valid password. Verify if a user cannot login with a valid username and
an invalid password. Verify the login page for both, when the field is blank and
Submit button is clicked. In order to add a group, ensure that in the dropdown menu
"Desktop users and groups", the option "All groups" is selected. Highlight the group
that needs to be added to the ACL, select the Access Permission desired at the bottom
of the window, and click 'OK'.
Chapter 6
RESULTS AND CONCLUSION
In this chapter we are about to discuss presentation of finding, hardware
results and software result. Show the image of project like Save, Open, Format, size
and color etc. The Discussion section follows the Results and precedes the
Conclusions and Recommendations section. It is here that the authors indicate the
significance of their results. They answer the question, “Why did we get the results
we did?” This section provides logical explanations for the results from the study.
Those explanations are often reached by comparing and contrasting the results to prior
studies’ findings, so citations to the studies discussed in the Literature Review
generally reappear here. This section also usually discusses the limitations of the
study and speculates on what the results say about the problem(s) identified in the
research question(s). This section is very important because it is finally moving
towards an argument. Since the researchers interpret their results according to
theoretical underpinnings in this section, there is more room for difference of opinion.
The way the authors interpret their results may be quite different from the way you
would interpret them or the way another researcher would interpret them.

6.1 Presentation of the Findings

Structure the paper well, with a clear introduction, body, and conclusion. Use
language that is simple and clear. Do you want to tell someone else about the impact
you've made, or what you've learned from the process? Do you need to convince
someone else of the issues the presentation of findings should clearly explain how the
topic was researched, and summarize what the results are. The findings should be
presented in the context of any similar previous research and or theories. A discussion
of the existing literature and how this present research contributes to the area should
be included. A consideration must also be made about how transferrable the research
would be to other settings. The principal outcomes of a research project; what the
project suggested, revealed or indicated. This usually refers to the totality of
outcomes, rather than the conclusions or recommendations drawn from them. A
summary of findings table presents the key information about the most important
outcomes of a treatment, including the best effect estimate and the certainty of the
evidence for each outcome. Data should be summarized as simply as possible so that
it is understandable by people without a scientific background. This is called
presenting your findings. You can present your findings in a number of different
ways. Quickly define the technical terms that you are going to use and a recap is
always nice. Follow to time limits: Generally, paper presentation sessions at
conferences are 20-30 minutes long. Taking the information and graphics provided by
you, our highly-skilled content specialists will condense the text, ensure language
accuracy, and then transform your findings into an eye-catching poster that
summarizes your work while meeting any event-specific requirements.

 A well-designed poster will

 Attract attention
 Make a great conversation starter with peers and colleagues
 Help you communicate your research quickly
 Improve an understanding of your research

6.1.1 Hardware Results

It is the aim of this paper to investigate a system, which, with no manual or

mechanical interference, permits the building, changing, processing and destruction of
real digital hardware. It can be seen, that by the above nothing else than a hardware-
editor is outlined. Therefore, first a “mini-model” of a usual text-editor is given within
this paper. Then this model is transferred to problems of the editing of hardware. The
main problem in particular, i.e., the problem of keeping the timing under control, will
be discussed on the basis of an exact algebraic model of the time-behavior of digital
circuits. The result of these discussions will be the concept of an automatic hardware-
editor. Finally, a realization of this concept built by the author within the University
of Dortmund, W. Germany, will be discussed. Hardware refers to the physical
components of a computer. Computer Hardware is any part of the computer that we
can touch these parts. These are the primary electronic devices used to build up the
computer. Examples of hardware in a computer are the Processor, Memory Devices,
Monitor, Printer, Keyboard, Mouse, and the Central Processing Unit. We will make
your hardware article immediately and freely accessible. We will make your hardware
article easy to find and download. Receive recognition for the work that you've done
to develop scientific hardware with a peer-reviewed article with a distinct DOI. We
will help you drive traffic to your hardware article. We will help you write a hardware
article that is easy to digest and interpret. Your article will be reviewed by experts in
open-source hardware. Reduce duplication of effort with detailed descriptions of your
hardware that make it easy for your peers to replicate and reproduce. Hardware is
open to input from all scientific, technological, and medical disciplines. Scientific
infrastructure will be interpreted in the broadest sense. Including hardware
modifications to existing infrastructure, sensors and tools that perform measurements
and other functions outside of the traditional lab setting (such as wearable’s, air/water
quality sensors, and low-cost alternatives to existing tools), and the creation of wholly
new tools for either standard or novel laboratory tasks. Authors are encouraged to
submit hardware developments that address all aspects of science, not only the final
measurement, for example, enhancements in sample preparation and handling, user
safety, and quality control. Although computers are potentially useful for various
editorial tasks, much editing continues to be done in traditional ways, on paper,
raising questions about whether the tool is ineffectively exploited or whether it is
unsuitable for editing. A survey of 94 editors reveals that 62.8% use computers in
editing; however, even editors who use computers for editing also depend on hard
copy. Editors who use computers have more responsibility for the visual aspects of
the text and for managerial tasks than editors who use hard copy only. The computer
remains a tool; it is not a replacement for editors. Technical Communication includes
both quantitative and qualitative research while showcasing the work of some of the
field’s most noteworthy writers. Among its most popular features are the helpful book
reviews. The Society for Technical Communication is the world’s largest and oldest
professional association dedicated to the advancement of the field of technical
communication. The Society’s members span the field of the technical
communication profession from students and academics to practitioners and
managers. Our members represent every industry segment and many countries around
the globe.
6.1.2 Software Results

Software Results means any right to the outcome of Software operation, run or
execution or Software parameterization that is not related to its source code, but is an
effect of regular Software use as stipulated in Attachment 1 to the Agreement.
Software results include but are not limited to reports generated by or from the
Software, configuration objects created within the Software, test scripts, Software set
up, automation objects, notifications. Software Results means any Action Objective
Results which is a Software. Depending on how the Access Rights on Software
Results are approached, certain key deliverables such as predictive
models/algorithms, empty database platform, etc. can be excluded from Software
Results and included in a specific category of Results with customized Access Rights.
Software is a collection of instructions, procedures, and documentation that performs
different tasks on a computer system. We can say also Computer Software is a
programming code executed on a computer processor. The code can be machine-level
code or the code written for an operating system. Examples of software are MS Word,
Excel, PowerPoint, Google Chrome, Photoshop, MySQL, etc. Software, on the other
hand, refers to a set of instructions which enable the hardware to perform a specific
set of tasks. The software must be installed in the hardware to function properly and
similarly, the hardware must be present for the tasks to be performed. Both are
interdependent, yet they are also different from each other. Software Results means
any right to the outcome of Software operation, run or execution or Software
parameterization that is not related to its source code, but is an effect
of regular Software use as stipulated in Attachment 1 to the Agreement. Software
results include but are not limited to reports generated by or from the
Software, configuration objects created within the Software, test scripts,
Software set up, automation objects, notifications. Software Results means any
Action Objective Results which is a Software. [Note: depending on how the Access
Rights on Software Results are approached, certain key deliverables such as
predictive models/algorithms, empty database platform, etc. can be excluded from
Software Results and included in a specific category of Results
with customized Access Rights. Each Party may take appropriate actions to
protect Software Results developed by such Party under the Project by such rights as
are available under such Party's national legal system including without limitation
copyright or any other. These programs can help you detect plagiarism in your work,
fix grammar mistakes and punctuation errors, and even make suggestions for changes
in your writing style. Hemmingway Editor is one of those great tools that people don’t
talk about it first because it doesn’t have a strong affiliate incentive program. But we
like to use it to make sure our readability is around Grade 6. And, that is the primary
use for us editors at scijournal.org.It handles the basic stuff like spelling errors. We
ask our writers to use the free version for self-editing. But as you scale up and
produce more writing, you might need something that can work more efficiently. Our
conclusion, sadly, is that Grammar does a great job of being editing software.
Education companies have named White Smoke the top proofreading tool on the
Internet.

6.2 Front Page

On the Insert tab, click Cover Page. Click a cover page layout from the gallery
of options. After you insert a cover page, you can replace the sample text with your
own text by clicking to select an area of the cover page, such as the title, and typing
your text. If you are using Visual Studio, this walkthrough assumes that you selected
the Web Development collection of settings the first time that you started Visual
Studio. Visual Studio creates a new project that includes prebuilt functionality based
on the Web Forms template. It not only provides you with a Home.aspx page,
an About.aspx page, a Contact.aspx page, but also includes membership functionality
that registers users and saves their credentials so that they can log in to your website.
When a new page is created, by default Visual Studio displays the page
in Source view, where you can see the page's CSS elements. The following
illustration shows what you would see in Source view if you created a new Web page
named. Visual Studio creates a new project that includes prebuilt functionality based
on the Web Forms template. It not only provides you with a Home.aspx page,
an About.aspx page, a Contact.aspx page, but also includes membership functionality
that registers users and saves their credentials so that they can log in to your website.
When a new page is created, by default Visual Studio displays the page in view,
where you can see the page's CSS elements. The following illustration shows what
you would see in view if you created a new Web page named BasicWebApp.aspx.
 Figure 6.2 Front page

6.3 Button
The Button control represents a standard Windows button. It is generally
used to generate a Click event by providing a handler for the Click event. Let's create
a label by dragging a Button control from the Toolbox ad dropping it on the form. So,
I have two screens, one called SearchClientDetails, which allows me to view my list
of records and select one, which then opens another screen called Client Details. This
is where I want to have my buttons set but I'm having trouble trying to work out what
syntax I should be using and unfortunately there's just way too much inconsistent
content on the NET about trying to do this. Any help with the syntax I should be using
(even if it's just for the NEXT button) or a helpful website on this would be very
much appreciated. In the screen designer for your details screen, you should see that
there is a Query for your entity and a query parameter, which in your case is probably
something like ClientDetailId. This is what you need to change in order to switch to a
different record.
As far as finding the "next" or "previous" records, this obviously depends on how you
want things sorted. Let's say that your Client Detail entity has an InvoiceNum field
that you sort by. To switch to the "next record”. Rate it where it is used. Connections
need to be closed and disposed. Using blocks accomplish this for you even if there is
an error. You don't seem to need a Data Adapter or a Dataset in the code you
presented. Just use a Data Table and a Command. Since you haven't shared where or
how you declared Current row, I can't tell you why it isn't updating. Also, you haven't
shared the Show Data method so I can't tell if something is going wrong there.

Figure 6.3 Button

6.4 Back Button

Show back and forward buttons on status bar, as can be seen in other IDEs.
They are equivalent to the shortcut on the top menu (Go->Back/Forward). The
buttons are located towards the bottom left of the screen. You can go back to your
previous location with the Go > Back command or Ctrl+Alt+-. Android maintains
a back stack of destinations as the user navigates throughout your application. This
usually allows Android to properly navigate to previous destinations when the Back
button is pressed. However, there are a few cases where your app might need to
implement its own Back behavior in order to provide the best possible user
experience. For example, when using a Web View, you might want to override the
default back button behavior to allow the user to navigate back through their web
browsing history instead of the previous screens in your app. Move about code with
Navigate Back and Navigate Forward, much like you move about with an Internet
browser. Navigate to previously visited locations in your code, and forward again to
your most recent location

Figure 6.1 Back Button

6.5 Picture Box

You can set the Image property to the Image you want to display, either
at design time or at run time. You can programmatically change the image displayed
in a picture box, which is particularly useful when you use a single form to display
different pieces of information. There are five different PictureBoxSizeMode is
available to Picture Box control. Auto Size - Sizes the picture box to the image.
Center Image - Centers the image in the picture box. Normal - Places the upper-left
corner of the image at upper left in the picture box Stretch Image - Allows you to
stretch the image in code. The Picture Box is not a selectable control, which means
that it cannot receive input focus. The following C# program shows how to load a
picture from a file and display it in streach mode. Typically, the Picture Box is used to
display graphics from a bitmap, metafile, icon, JPEG, GIF, or PNG file. Set the Image
property to the Image you want to display, either at design time or at run time. Select
New Project--->Visual C#-->Windows Forms App (. NET Framework), give your
project a name and click OK. This action creates a Win Forms project with a default
form and you should see the Windows Designer. Let's add a Picture Box control to
the form by dragging it from Toolbox and dropping it to the form. The Windows
Forms Picture Box control is used to display graphics in bitmap, GIF, JPEG, metafile,
or icon format. Open the Visual Designer of the form containing the control to
change. Select the control. In the Properties pane, select the Image or Background
Image property of the control. Select the ellipsis ( ) to display the Select Resource
dialog box and then select the image you want to display. The picture that is displayed
is determined by the Image property, which can be set at run time or at design time.
You can alternatively specify the image by setting the Image Location property and
then load the image synchronously using the Load method or asynchronously using
the Load sync method. The Size Mode property controls how the image and control
fit with each other. For more information, see how to. Modify the Size or Placement
of a Picture at Run Time. Picture box is a control in Visual Basic 2017 that is used to
display images. In lesson 3, we have already learned how to insert a picture box on
the form in Visual Basic 2017. However, we have not learned how to load a picture in
the picture box yet. In this lesson, we shall learn how to load an image into the picture
box at design time and at runtime. Besides that, we shall also learn how to use a
common dialog control to browse for image files in your local drives and then select
and load a particular image in the picture box. First, insert a picture box on the form
and change its text property to Picture Viewer, its border property to Fixed Single and
its background color to white. You might also want to change the size mode of the
image to stretch Image so that the image can fit in the picture box. Now right-click on
the picture box to bring out its properties window. First, we add a button and change
its text to View and its name to BtnView. Next, we add the OpenFileDialog control
on the form. This control will be invisible during runtime but it facilitates the process
of launching a dialog box and let the user browse his or her local drives and then
select and open a file. In order for the OpenFileDialog to display all types of image
files, we need to specify the types of image files under the Filter property. Before that,
rename OpenFileDialog1 as OFGSelectImage. Next, right-click on the
OpenFileDialog control to access its properties window. Beside the Filter property,
specify the image files using the format. Typically, the Picture Box is used to display
graphics from a bitmap, metafile, icon, JPEG, GIF, or PNG file. Set the Image
property to the Image you want to display, either at design time or at run time. Select
New Project--->Visual C#-->Windows Forms App (. NET Framework), give your
project a name and click OK. This action creates a Win Forms project with a default
form and you should see the Windows Designer. Let's add a Picture Box control to
the form by dragging it from Toolbox and dropping it to the form. An image editing
application for digital photos. It is used to crop and touch up photos, as well as
organize them into albums and slide shows. After you have specified the image that
the picture box would display, by default, it is located from the top-left corner of the
control. Open the Visual Designer of the form containing the control to change. Select
the control. In the Properties pane, select the Image or Background Image property of
the control. Select the ellipsis ( ) to display the Select Resource dialog box and then
select the image you want to display. In digital imaging, a pixel (abbreviated PX), pel,
or picture element is the smallest addressable element in a raster image, or the
smallest point in an all-points addressable display device. In most digital display
devices, pixels are the smallest element that can be manipulated through software.
 Figure 6.5 Picture Box

6.6 Menu Script Bar

Menus are vital to any application. Depending on the program, the

menus enable the user to physically use your program. The user chooses
whichever menu and the program responds accordingly. Whether it is
showing a dialog box, or changing the color of the words, or exiting.
Menus allow you to arrange commands in a logical and easy-to-find
fashion. A menu shouldn’t contain paragraphs of text, or even long
sentences; its sole purpose is to help you navigate through the entire
program. You may have noticed that the various products in Microsoft’s
Office Suite have similar menus; this is true with many other software
packages. This standardization technique is pivotal, because it enables
the application’s user to learn other applications quickly. Application
Standardization includes the structure of your toolbars, menus, and
overall look and feel of your applications. All Windows applications look
similar, and yours should be designed to enable the users to learn the
application quickly. For example: Most Windows applications have a File
menu dealing with file-oriented tasks. Imagine how difficult it would be for
a new user to figure out that you have put your printing functionality
under a menu called, for example, Technical Tasks -> Hardware -> Printers
-> Print. If you do not know what an Alt key shortcut key is, let me explain:
An Alt key shortcut enables you to press the Alt key and then the
underlined letter to display the menu. For example: If you press Alt + F, it
should open the File menu. To make a letter in the menu display
underlined and act as an Alt key shortcut, follow these steps. Click the
desired Menu item. Open the Properties Window. Add an ampersand in
front of the desired letter to be used as a shortcut. In Figure 3, I have
added an ampersand in front of the O in Open. Shortcut keys are usually a
combination of Ctrl and a letter. For example, Ctrl + C is the keyboard
shortcut for Copy and Ctrl + V is the Keyboard shortcut for Paste.
Otherwise, your changes won't persist after you close and reopen Visual
Studio. On the menu bar, select Tools > Customize. The Customize dialog
box opens. On the Commands tab, select the option button for the type of
element that you want to customize. In the Solution Explorer, right-click the
project node and select Add > New Item. In the Add New Item dialog, go to
Visual C# / Extensibility and select Command. In the Name field at the bottom
of the window, change the command file name to Test Command. Built-in
menus appear on the menu bar across the top of the Visual Basic window.
Users may also press Ctrl + M to toggle the menu bar on and off. In Microsoft
Windows, the menu bar is beneath the title bar. The menu bar in Windows
may be accessed via keyboard shortcuts. Pressing the Alt and the menu-
specific hotkey (which appears as an underlined letter in the menu) activates
that menu choice. A menu bar is a thin, horizontal bar containing the
labels of menus in a GUI. The menu bar provides the user with a
place in a window to find program's essential functions. These
functions include opening and closing files, editing text, and quitting
the program. Although menu bars are usually present in most GUIs,
they may differ depending on the operating system you're using. In
Microsoft Windows, the menu bar is beneath the title bar. The menu
bar in Windows may be accessed via keyboard shortcuts. The menu
bar on a Mac is a thin bar found anchored to the top of the screen.
Unlike Microsoft Windows menu bars, which appear in each window,
menu bars in OS X always appear at the top of the screen. When
you switch to another application, the menu bar changes
accordingly.
 Figure 6.6 Menu script bar

6.7 Cart

Welcome to our Online Cake Bakery System documentation, where every

aspect of creating and managing an exquisite online bakery experience is
meticulously detailed for your convenience. Delve into the intricacies of designing a
seamless user interface, implementing secure payment gateways, and crafting
delectable cake catalogs to tantalize your customers' taste buds. Explore the nuances
of backend architecture, from database management to order processing algorithms,
ensuring smooth operations and customer satisfaction. Gain insights into marketing
strategies, customer engagement techniques, and data analytics to elevate your
bakery's online presence and profitability. Whether you're a budding entrepreneur
venturing into the world of online bakeries or an experienced developer seeking
inspiration and best practices, our comprehensive documentation serves as your
indispensable guide. With Times New Roman font, our documentation exudes
professionalism and readability, facilitating your journey towards creating the
ultimate online cake bakery experience.
 Figure 6.7 Cart

6.8 Search

The search functionality in the Online Cake Bakery System serves as a pivotal tool for
users to swiftly navigate through the extensive array of cakes and bakery products
offered. Seamlessly integrated into the platform's interface, the search feature
empowers customers to efficiently locate their desired items by simply inputting
relevant keywords or filters. Leveraging advanced algorithms, the search engine
swiftly scans the comprehensive database, instantly retrieving matching results based
on criteria such as cake type, flavor, occasion, dietary preferences, and more. This
intuitive search capability enhances user experience by streamlining the browsing
process, enabling users to quickly discover delectable treats tailored to their
preferences. Whether customers seek a classic chocolate cake for a birthday
celebration or a specialized vegan option for dietary requirements, the search function
ensures they effortlessly find the perfect confectionery delight. Furthermore, the
system's robust architecture ensures reliability and accuracy, guaranteeing that search
results consistently align with user expectations. Through this indispensable feature,
the Online Cake Bakery System exemplifies its commitment to delivering
convenience, satisfaction, and joy to customers seeking delectable treats for any
occasion.

Figure 6.8 Search

6.9 Home
 The Home section of the documentation for the Online Cake Bakery System
encapsulates the essence of this innovative platform designed to revolutionize
the experience of ordering cakes online. At the heart of our endeavor lies a
commitment to seamlessly blend technology with the timeless joy of indulging
in delectable confections. With an intuitive interface and robust backend
infrastructure, our system offers customers a delightful journey from selection
to delivery. Users are greeted with an inviting homepage that not only
showcases a tempting array of cake designs but also provides personalized
recommendations based on their preferences. Through seamless navigation,
customers can effortlessly browse through various categories, customize their
orders, and securely checkout, ensuring a hassle-free transaction process.
Furthermore, our system prioritizes transparency, offering real-time updates on
order status and delivery timelines. Leveraging cutting-edge technologies, we
have integrated features such as AI-powered recommendation engines and
secure payment gateways to enhance user satisfaction and streamline
operations. Whether it's a celebration or a simple craving, the Online Cake
Bakery System stands as a testament to our dedication to redefining
convenience and joy in the realm of online cake ordering.

Figure 6.9 Home

6.10 Catagories

Categories for the documentation of the Online Cake Bakery System encompass
various essential aspects crucial for understanding and implementing the system
effectively. These categories include System Overview, which provides a
comprehensive understanding of the purpose, scope, and functionalities of the bakery
system. User Interface Design delineates the layout, navigation, and aesthetics of the
system's interface, ensuring user-friendly interaction. Functional Requirements
specify the system's features and operations, including order placement, payment
processing, and inventory management. Non-functional Requirements address
performance, security, and scalability aspects vital for the system's reliability and
robustness. Database Design elucidates the organization and structure of data within
the system, facilitating efficient data storage and retrieval. Testing and Quality
Assurance outline the methodologies employed to ensure the system's functionality,
accuracy, and reliability through rigorous testing processes. Implementation Details
delineate the deployment and configuration procedures necessary for integrating the
system into the operational environment. Lastly, Maintenance and Support elucidate
the strategies and protocols for ongoing maintenance, updates, and user support,
ensuring the system's longevity and user satisfaction. Each category plays a crucial
role in the comprehensive documentation of the Online Cake Bakery System,
providing stakeholders with valuable insights into its design, functionality, and
maintenance requirements.

Figure 6.10 Categories

6.11 Admin
In the administrative section of the Online Cake Bakery System documentation,
emphasis lies on comprehensive coverage of managerial functionalities aimed at
efficient operation and oversight of the platform. This section delineates the intricate
array of tools and controls furnished to administrators, empowering them to
streamline processes, manage resources, and uphold service quality standards.
Administrators wield authority over user management, with capabilities ranging from
account creation and authentication to privilege assignment and revocation. They
exercise supervision over inventory, overseeing stock levels, procurement, and
replenishment to ensure uninterrupted service provision. Additionally, administrative
functionalities extend to order management, affording administrators the means to
monitor, track, and facilitate timely fulfillment while accommodating customizations
and modifications as necessary. Furthermore, the administrative suite encompasses
analytics and reporting tools, furnishing valuable insights into sales trends, customer
preferences, and operational performance metrics to inform strategic decision-making.
Through this comprehensive administrative toolkit, administrators navigate the
intricacies of the Online Cake Bakery System adeptly, fostering its seamless operation
and sustained growth.

Figure 6.11 Admin

6.12 Supervisor Project

The project supervisor will oversee all aspects of a project from its
inception to completion. One of the key functions fulfilled by the project
supervisor is the hiring and training of employees. They must interview and
appoint qualified candidates to perform the crucial jobs to complete the
project. They must ensure that new recruits work in a manner conducive to
budget concerns. This can be accomplished by developing as well as
implementing training seminars. Employee performance management on a
periodic basis is also part of the project supervisor’s job. They oversee and
review employee performance, offer constructive feedback based on their
observations, and report findings to management if needed. Assembling the
input received from all levels, a project supervisor offers suggestions and
implements changes to products or services. The project supervisor is also
responsible for managing customer service issues by working closely with
account management teams to assess client needs. The project supervisor
must make sure that all requests logged by the customers and account teams
are completed in an accurate, timely and reasonable manner. To help the
customer understand how the product fits their needs and how to use it, the
project sup0ervisor could facilitate product training sessions. During these
sessions, these supervisors would receive feedback on product performance
and use this knowledge to formulate innovative solutions to improve product
functionality.
 Figure 6.12 supervisor project

6.13 Description

The documentation for the Online Cake Bakery System encapsulates the
comprehensive design, development, and implementation process of a sophisticated
digital platform aimed at revolutionizing the way customers engage with bakery
services online. Through meticulous planning, iterative development cycles, and
rigorous testing procedures, the system was meticulously crafted to offer users an
intuitive interface for browsing, customizing, and ordering a wide array of delectable
cakes and pastries. Leveraging modern web technologies, secure payment gateways,
and seamless integration with backend inventory management systems, the platform
ensures a seamless user experience from selection to delivery. Robust administrative
functionalities empower bakery staff to manage orders, track inventory, and analyze
sales data efficiently. Extensive documentation provides insights into system
architecture, database schema, API endpoints, and user workflows, facilitating future
enhancements and maintenance. With a focus on scalability, reliability, and security,
the Online Cake Bakery System represents a cutting-edge solution poised to redefine
the digital landscape of confectionery commerce.

6.14 Discussion of the Findings

In examining the findings of the Online Cake Bakery System, several key
insights emerge regarding its functionality and user experience. The analysis reveals a
robust platform capable of facilitating seamless online transactions for customers
seeking baked goods. One notable finding is the system's user-friendly interface,
which allows users to navigate through various options effortlessly, enhancing overall
accessibility. Additionally, the incorporation of diverse payment methods ensures
convenience for customers, thereby fostering higher satisfaction levels and
encouraging repeat business. Moreover, the system's efficient order processing
mechanism minimizes delays, contributing to timely deliveries and customer delight.
Furthermore, the integration of feedback mechanisms enables continuous
improvement, as customer suggestions are actively considered for enhancing service
quality. The findings also highlight the importance of backend management tools,
which streamline inventory control and optimize resource allocation for enhanced
operational efficiency. Overall, the findings underscore the Online Cake Bakery
System's effectiveness in meeting customer needs and its potential for sustained
success in the competitive online marketplace.
6.15 Limitations
In the documentation for the Online Cake Bakery System, several limitations and
challenges are identified that warrant consideration. Firstly, the system's reliance on
internet connectivity poses a potential barrier for users in areas with limited or
unstable internet access, potentially impeding their ability to utilize the platform
effectively. Secondly, while efforts have been made to ensure the security of user
data, the system may still be vulnerable to cyber threats such as hacking or data
breaches, necessitating ongoing vigilance and updates to maintain the integrity of
customer information. Additionally, the user interface and experience may not cater to
individuals with disabilities or those who are less technologically adept, highlighting
the importance of accessibility considerations in future iterations. Furthermore, the
scalability of the system may be limited by factors such as server capacity and
resource availability, potentially hindering its ability to accommodate a growing user
base or increased demand during peak periods. Finally, while the documentation aims
to provide comprehensive guidance for users and developers, there may be gaps or
ambiguities that could lead to confusion or misinterpretation, emphasizing the need
for clear and concise communication throughout the development and implementation
process.

6.16 Conclusion
In conclusion, the development of the Online Cake Bakery System has been a
rewarding journey, marked by meticulous planning, innovative design, and dedicated
implementation. Through this project, we aimed to streamline the process of ordering
customized cakes, thereby enhancing customer experience and optimizing operational
efficiency for bakeries. By harnessing the power of technology, we have created a
platform that seamlessly connects customers with bakeries, facilitating convenient
online ordering and delivery services. Throughout the development process, we
prioritized user-centric design principles, ensuring an intuitive interface and smooth
navigation for both customers and bakery owners. Moreover, by incorporating
features such as secure payment gateways and real-time order tracking, we have
endeavored to instill trust and reliability in our system. Looking ahead, we envision
continued refinement and expansion of the Online Cake Bakery System, leveraging
user feedback and emerging technologies to further enhance its capabilities and reach.
Ultimately, this project underscores our commitment to leveraging technology for the
betterment of businesses and the convenience of consumers in the realm of bakery
services.

6.17 Summary
The Online Cake Bakery System documentation encapsulates the comprehensive
design, development, and implementation of a sophisticated digital platform tailored
for the confectionery industry. This system seamlessly integrates cutting-edge
technologies to facilitate a user-friendly interface for customers to browse, select,
customize, and order delectable cakes online. Through meticulous planning and agile
methodology, the system encompasses features such as a dynamic catalog showcasing
an array of cake varieties, intuitive customization tools enabling users to personalize
their orders, secure payment gateways ensuring seamless transactions, and efficient
order management functionalities streamlining the entire process from placement to
delivery. Additionally, robust administrative modules empower bakery owners with
tools to manage inventory, track orders, analyze sales data, and enhance customer
engagement through targeted promotions and discounts. By leveraging the power of
digitalization, the Online Cake Bakery System revolutionizes the traditional bakery
experience, offering convenience, accessibility, and a delightful array of treats at the
fingertips of customers while empowering businesses with efficient operations and
enhanced market reach.

Chapter 7
FUTURE WORK
In envisioning the future trajectory of the Online Cake Bakery System, several
avenues for expansion and enhancement emerge, poised to elevate both user
experience and operational efficiency. One significant avenue for future work
involves the integration of advanced AI algorithms to personalize user interactions,
anticipate customer preferences, and streamline order management processes. By
leveraging machine learning techniques, the system can analyze past ordering
patterns, seasonal trends, and individual customer behaviors to offer tailored
recommendations and promotions, thereby fostering customer loyalty and increasing
sales. Furthermore, the implementation of real-time inventory tracking and predictive
analytics can optimize supply chain management, ensuring the availability of
ingredients and reducing wastage. Additionally, exploring the incorporation of
augmented reality (AR) technology could revolutionize the online shopping
experience by allowing customers to visualize cake designs in their own environments
before making a purchase, thereby enhancing confidence and satisfaction. Moreover,
expanding the platform's accessibility through the development of dedicated mobile
applications for various platforms can further broaden its reach and convenience for
users on the go. Collaborations with local delivery services or the establishment of
proprietary delivery infrastructure could also enhance the system's competitiveness by
offering faster and more reliable delivery options. Furthermore, continuous
refinement of the user interface and user experience design based on feedback and
usability studies can ensure intuitive navigation and seamless transactions. Lastly, as
the system scales, investing in robust cybersecurity measures and compliance with
data protection regulations will be imperative to safeguard customer information and
maintain trust. By embarking on these avenues of future work, the Online Cake
Bakery System can continue to evolve as a market leader, delighting customers and
stakeholders alike with its innovation and efficiency.
REFERENCES

1. https://open.lib.umn.edu/socialproblems/chapter/1-4-doing-research-on-
social-problems/
2. https://hohmannchris.wordpress.com/2014/05/06/constraint-vs-bottleneck/
3. https://www.visual-paradigm.com/guide/uml-unified-modeling-language/
what-is-sequence-diagram/
4. https://library.sacredheart.edu/c.php?
g=29803&p=185935#:~:text=Definition,a%20synthesis%20of%20key
%20points.
5. https://stackoverflow.com/questions/36701955/how-to-restore-the-menu-bar-
in-visual-studio-code
6. https://blog.papertrue.com/why-tech-organizations-need-editors/