Download as pptx, pdf, or txt
Download as pptx, pdf, or txt
You are on page 1of 30

RECIPE FINDER

WEB APPLICATION
K S S E M Vish m i R a m o n a [ E 1 3 2 2 8 5 ]
S o f tw a r e E n g in e e r in g [ S e p ]
1. INTRODUCTION

2. BACKGROUND

3. WORK COMPLETED
OUTLINE 4. FURTHER WORK

5. PROGRESS REVIEW

6. REFERENCES
INTRODUCTION
 The Recipe Finder Web Application addresses the evolving
culinary landscape by offering a comprehensive platform that
integrates recipe discovery, meal planning, and ingredient
management to meet the growing demand for efficient and
personalized culinary solutions.
BACKGROUND
 The culinary landscape poses several challenges for individuals aiming
to efficiently organize and prepare meals. Factors such as time
constraints, dietary restrictions, ingredient availability, and the desire for
a variety of wholesome options can complicate meal planning. The
Recipe Finder Web Application is proposed as a solution to these
problems. By offering users an intuitive interface and a wide selection
of recipes tailored to their tastes and dietary requirements, this platform
seeks to simplify the process of finding, organizing, and cooking meals.
ESTIMATED BENEFITS AND
DRAWBACKS
 The deployment of the Recipe Finder web application presents both
potential benefits and drawbacks. Consumers stand to gain from more
effective meal planning, increased creativity in cooking, and easier access
to wholesome and delectable recipes. Additionally, by assisting users in
making better use of available ingredients and improving meal planning
skills, the application may also help reduce food waste. However,
challenges such as technological issues, user adoption barriers, and privacy
concerns could pose difficulties during implementation. Thus, it is
essential to develop a solution that minimizes potential negative effects
while maximizing benefits.
KEY FEATURES OF THE RECIPE FINDER WEB
APPLICATION
 Shopping List Generator
 Interactive Q&A Platform
 Food Journey Documentation
KNOWLEDGE GAPS AND FUTURE RESEARCH DIRECTIONS
 While the Recipe Finder web application offers many useful features, there
are areas of unanswered questions that require further research. Future
studies could focus on improving the shopping list generator, utilizing
machine learning techniques to anticipate user preferences, and examining
the impact of community-driven features on user participation and culinary
knowledge development.
 This literature review aims to highlight the potential of recipe finder
applications to revolutionize meal planning, cooking practices, and culinary
experiences by addressing current knowledge gaps and suggesting future
research directions.
WORK COMPLETED
 The development approach for the Recipe Finder Web
Application followed a structured and systematic process
tailored for solo development. This methodology emphasized
personal accountability, time management, and continuous self-
assessment. Regular progress checkpoints and self-reflection
were incorporated to ensure the project remained on track and
aligned with personal goals and objectives.
PROPOSED METHODOLOGY

 Structured and systematic development process tailored for solo development.


 Emphasized personal accountability, time management, and continuous self-assessment.
 Regular progress checkpoints and self-reflection to ensure project alignment with goals.
TECHNOLOGIES

 HTML, PHP, CSS, and MySQL utilized for development.


 Chosen for familiarity, adaptability, and fit for web application development.
 PHP and MySQL for backend functionality and data storage, HTML and CSS for frontend.
TECHNOLOGIES

 HTML, PHP, CSS, and MySQL utilized for development.


 Chosen for familiarity, adaptability, and fit for web application development.
 PHP and MySQL for backend functionality and data storage, HTML and CSS for frontend.
ARCHITECTURES

 Designed for scalability and modularity.


 Utilized conventional monolithic architecture with close frontend-backend integration.
 Simplified development and deployment processes.
DESIGN PATTERNS
 Used Observer, Factory method, and Singleton patterns to solve typical software design
problems.

TOOLS
 Visual Studio Code used for coding, debugging, and version management.
 Extensive capabilities and lightweight design make it ideal for developers
LIBRARIES

 Minimized external libraries to maintain code simplicity and reduce dependencies.


 Core technologies such as HTML, PHP, CSS, and MySQL provide sufficient functionality.
RESOURCES
Software Requirements

o Integrated Development Environment (IDE): Visual Studio Code

o Operating System: Windows 7 (64bit/32bit)

o Web Browsers: Firefox, Chrome

o Database Management: MySQL, XAMPP control panel

o Version Control: Git


RESOURCES
Hardware Requirements
Computer Specifications: Intel Core 2 Duo (2.4 GHz), 2 GB RAM, 500 GB Hard Disk, Intel
775 Motherboard, 1 GB VGA, Power Supply 1kv.
Internet Connection: Wi-Fi connection with a 30 GB package (1mbps), Patch cable, Router
ARCHITECTURE
DIAGRAM
SYSTEM FLOW
DIAGRAM
USE CASE
DIAGRAM
ER DIAGRAM
FURTHER WORK
System Development: Several modules within the Recipe Finder web application are still
under construction, each with intended functional and non-functional features:
User Authentication Module
Functional Features:
User registration and login functionality.
Password management for account details and password reset.
Non-Functional Features:
Security measures to prevent unauthorized access.
FURTHER WORK
System Development
Recipe Management Module
Functional Features:
CRUD activities for recipes.
Categorization and tagging for better organization.

Non-Functional Features:
Performance optimization for handling a high volume of data.
Scalability considerations for future growth.

Search and Filtering Module


Functional Features:
Search functionality with advanced filtering options.

Non-Functional Features:
Speed and responsiveness in producing search results.
Accuracy in prioritizing relevant results.
FURTHER WORK
System Development
Recipe Management Module
Functional Features:
CRUD activities for recipes.
Categorization and tagging for better organization.

Non-Functional Features:
Performance optimization for handling a high volume of data.
Scalability considerations for future growth.

Search and Filtering Module


Functional Features:
Search functionality with advanced filtering options.

Non-Functional Features:
Speed and responsiveness in producing search results.
Accuracy in prioritizing relevant results.
FURTHER WORK
Shopping List Module
Functional Features:
Shopping list management with ingredient integration.

Non-Functional Features:
Cross-device synchronization for user convenience.
Usability of the interface for effective maintenance.
TEST PLAN
A comprehensive test plan will be implemented to ensure the reliability, functionality, and performance
of the Recipe Finder web application:
Unit Testing: Employing white-box and black-box testing techniques to evaluate individual functions
and methods.
Integration Testing: Utilizing top-down and bottom-up integration testing to verify interactions
between integrated modules.
System Testing: Conducting functional, usability, performance, and security testing to validate overall
functionality.
Acceptance Testing: Involving stakeholders and end-users in user acceptance testing to ensure the
application meets expectations.
WORK
BREAKDOWN
STRUCTURE
INITIAL
GANTT
CHART
REALISTIC ASSESSMENT OF CURRENT POSITION
 The project has encountered delays, primarily due to an error in MySQL within the
XAMPP environment. This issue required immediate attention and diverted focus towards
backend development to address database-related challenges. The resolution process for
the MySQL error has been more time-consuming than anticipated, involving meticulous
debugging and troubleshooting. Consequently, the time allocated for backend development
extended beyond the planned duration, impacting subsequent project stages. Additionally,
the complexity of backend development tasks contributed to the delay, requiring
comprehensive coding, testing, and refinement. Unforeseen challenges necessitated
adjustments to the project schedule, reflecting the reality of software development.
REVISED
GANTT
CHART
REFERENCES
FAO, 2011. Global Food Losses and Food Waste – Extent, Causes and Prevention. [Online]
Available at: https://www.fao.org/sustainable-food-value-chains/library/details/en/c/266053/

Guenther, P. M. et al., 2013. Update of the Healthy Eating Index: HEI-2010. [Online]
Available at: https://pubmed.ncbi.nlm.nih.gov/23415502/

Laing, B. Y., Mangione, C. M. & Tseng, C.-H., 2014. Effectiveness of a Smartphone Application for Weight Loss
Compared With Usual Care in Overweight Primary Care Patients. [Online]
Available at: https://www.acpjournals.org/doi/full/10.7326/M13-3005

Racle, J. & Gfeller, D., 2020. EPIC: A Tool to Estimate the Proportions of Different Cell Types from Bulk Gene
Expression Data. [Online]
Available at: https://link.springer.com/protocol/10.1007/978-1-0716-0327-7_17

Wang, X. et al., 2015. Recipe recognition with large multimodal food dataset. [Online]
Available at: https://ieeexplore.ieee.org/abstract/document/7169757

Weiss, S. M., Indurkhya, N. & Zhang, T., 2015. Fundamentals of Predictive Text Mining. [Online]
Available at: https://link.springer.com/book/10.1007/978-1-4471-6750-1

You might also like