A Real- time Research Project/Societal Related

Project Report
on
EVERLAST
AN ANNIVERSARY WEBSITE
submitted in partial fulfillment of the requirements for the award of the degree of

BACHELOR OF TECHNOLOGY

in

COMPUTER SCIENCE AND ENGINEERING

by

22WH1A05E3 Ms. G AKSHARA

22WH1A05G6 Ms. KHYYATI VEGIRAJU
22WH1A05G9 Ms. SRAVYA MAJETY
23WH1A0515 Ms. J AKSHAYA

Department of Computer Science & Engineering

BVRIT HYDERABAD
College of Engineering for Women
(UGC Autonomous Institution | Approved by AICTE | Affiliated to JNTUH)
(NAAC Accredited – A Grade | NBA Accredited B. Tech. (EEE, ECE, CSE and IT))
Bachupally, Hyderabad -500090

April, 2025
 BVRIT HYDERABAD
College of Engineering for Women
(UGC Autonomous Institution | Approved by AICTE | Affiliated to JNTUH)
(NAAC Accredited – A Grade | NBA Accredited B. Tech. (EEE, ECE, CSE and IT))
Bachupally, Hyderabad -500090

Department of Computer Science and Engineering

CERTIFICATE

This is to certify that the Real-time Research Project/Societal Related Project entitled
“Anniversary Website-Everlast” is a bonafide work carried out by Ms. G Akshara
(22WH1A05E3), Ms. Khyyati Vegiraju (22WH1A05G6), Ms. Sravya Majety (22WH1A05G9),
and Ms. J Akshaya (23WH1A0515) in partial fulfillment of the award of the B.Tech. degree in
Computer Science and Engineering, BVRIT Hyderabad College of Engineering for
Women, Bachupally, Hyderabad, affiliated to Jawaharlal Nehru Technological University
Hyderabad, Hyderabad under my guidance and supervision .The results embodied in the project
work have not been submitted to any other University or Institute for the award of any degree
or diploma.

Project Coordinator Head of Department

Ms. S.Vidyullatha, Dr. M Sree Vani,
Assistant Professor, Professor & HoD,
Department of CSE. Department of CSE.
 DECLARATION

We hereby declare that the work presented in this project entitled “Anniversary Website-
Everlast” submitted towards the completion of a Real-time Research Project/ Societal Related
Project Work in the II-II B.Tech., CSE at BVRIT Hyderabad College of Engineering for
Women, Hyderabad, is an authentic record of our original work.

Sign with Date:

Ms. G AKSHARA

(22WH1A05E3)

Sign with Date:

Ms. KHYYATI VEGIRAJU

(22WH1A05G6)

Sign with Date:

Ms. SRAVYA MAJETY

(22WH1A05G9)

Sign with Date:

Ms. J AKSHAYA

(23WH1A05I5)
 ACKNOWLEDGEMENT

We would like to express our sincere thanks to Dr. K V N Sunitha, Professor & Principal,
BVRIT HYDERABAD College of Engineering for Women, for her support by providing the
working facilities in the college.
Our sincere thanks and gratitude to Dr. M Sree Vani, Professor & HoD, Department of
CSE, BVRIT HYDERABAD College of Engineering for Women, for all timely support and
valuable suggestions during the period of our project.
We are extremely thankful to our Project Coordinator, Ms. S Vidyullatha Assistant
Professor, CSE, BVRIT HYDERABAD College of Engineering for Women, for her
constant guidance and encouragement throughout the project.
Finally, we would like to thank all Faculty and Staff of CSE department who helped us directly
or indirectly. Last but not least, we wish to acknowledge our Parents and Friends for giving
moral strength and constant encouragement.

Ms. G AKSHARA

(22WH1A05E3)

Ms. KHYYATI VEGIRAJU

(22WH1A05G6)

Ms. SRAVYA MAJETY

(22WH1A05G9)

Ms. J AKSHAYA

(23WH1A0515)
 ABSTRACT

Everlast: An Anniversary Website is an innovative e-commerce platform designed to enhance

the celebration of anniversaries by providing a wide range of customizable products and

services. This project focuses on creating a seamless and enjoyable user experience for

customers looking to commemorate their special moments with personalized gifts, event

planning, and exclusive anniversary-related offerings. The platform leverages advanced

technologies and intuitive design principles to offer an extensive catalog of products,

personalized keepsakes, and more. Customers can easily navigate the website, select items,

customize their orders, and arrange for delivery, ensuring a hassle-free and memorable

anniversary celebration.

This documentation provides a detailed overview of the website's development process,

highlighting key design and implementation strategies, user experience considerations, and

future enhancement plans. Everlast: An Anniversary Website stands as a testament to

innovation in the e-commerce sector, dedicated to making anniversary celebrations truly

unforgettable for couples and their loved ones.

 INDEX
S.No Topic Page No.

1 Introduction 1
1.1 Objectives 2
1.2 Existing System 5
1.3 Proposed System 7

2 Literature Survey 8

3 Methodology 15
3.1 Proposed Model/Architecture 17
3.2 Datasets 26
3.3 Algorithm(Title if any) 25
3.4 Performance Metrics 28

4 Results and Discussion 29

5 Conclusion & Future scope 30

6 References 32

i
 LIST OF FIGURES

S.NO Fig.No Fig.Name Page No.

1 2.2 Flow Chart 4
2 2.3 E-R Diagram 6
3 2.4 Sequential Diagram 9
4 5.1 Login Page 20
5 5.2 Sign Up Page 21
6 5.3 Available Locations Page 22
7 5.4 Home Page 22
8 5.5 Detailed view of Product 24
9 5.6 Dynamic Cart 25
10 5.7 Address Page 27
11 5.8 Personalize gifts page 28
12 5.9 Payment Page 30
13 5.10 Add Address Page 31

ii
 1 INTRODUCTION

Introduction

Everlast: An Anniversary Website is a comprehensive e-commerce solution

designed for personalized and memorable anniversary celebrations. Users can
effortlessly browse, personalize, and purchase a wide range of gifts and services.
The platform features a secure login page for account management and
personalized recommendations. Users can check delivery options based on
location to ensure timely service. The extensive product catalog includes
personalized keepsakes with detailed descriptions and high-quality images.
Personalization options such as engraving and custom messages allow users to
preview and customize gifts before adding them to the cart. The intuitive cart
interface and simplified address management ensure accurate delivery. A
dedicated personalization page offers tools for adding personal touches, and a
secure payment gateway supports multiple payment options for safe transactions.
Everlast utilizes HTML, CSS, and JavaScript for a responsive interface, with
database connections for managing user accounts, product details, orders, and
personalization options.

1.1 Objectives

The primary objectives of the Everlast are as follows:

• Streamlined Shopping Experience:

Provide a seamless and intuitive platform for users to browse, personalize, and purchase
anniversary gifts.

1
• Enhanced Personalization:

Offer a wide range of customization options to make each gift unique and special.

• Secure Transactions:

Ensure the security of user data and transactions through robust security measures.

• Reliable Delivery:

Provide accurate delivery options and ensure timely delivery of all orders.

• User-Centric Design:

Develop a user-friendly interface that caters to the distinct needs of all users, ensuring
ease of use and accessibility.

1.2 Methodology

The development of Everlast: An Anniversary Website involves a structured approach

combining user research, design iterations, and technical development to create an
engaging e-commerce experience.

User Research: Conduct online surveys and interviews to gather data on user
preferences for anniversary gifts and shopping behaviours and analyse data for trends.

Design Iterations: Create wireframes and prototypes, conduct usability testing, and
refine designs based on user feedback.

Technical Development: Use HTML, CSS, and JavaScript for a responsive interface.
Implement secure database connections and integrate a secure payment gateway.

2
 2 DESIGN

2.1 Introduction

The design phase of Everlast: An Anniversary Website involved a thorough approach to

meet user requirements and operational objectives. Key design principles included:

 User Interface (UI): Creating an intuitive and responsive interface

tailored to diverse user needs, ensuring ease of navigation and
accessibility of functions.
 Database Design: Developing a robust and scalable database architecture
to efficiently manage data related to products, user accounts, orders, and
personalization options.
 Security Measures: Implementing stringent security protocols to protect
sensitive user data from unauthorized access and cyber threats, ensuring
compliance with data privacy regulations.

2.2 Architecture Diagram

The architecture diagram illustrates the structural layout of Everlast: An Anniversary

Website, showcasing the integration of various components and their interactions.
Architectural diagrams help in understanding, designing, and communicating the
structure and functionality of a system. They provide a high-level view, making it easier
to see how different parts work together and identify potential issues or improvements.
Below is a simplified Architecture representation as follows:

3
Fig. 2.2 flow chart

4
This flowchart illustrates the user journey on Everlast: An Anniversary Website. The
process begins with the user accessing the website. If the user does not have an account,
they will be prompted to sign up and fill out a registration form. If the user already has
an account, they will proceed to the login page and enter their credentials. Once logged
in, the user can verify their account and access the product catalog. From there, they can
add products to their cart, enter

delivery address details, personalize the selected products, and proceed to the payment
page. After completing their activities, the user can log out, concluding the process.
Update any incorrect details. After you’ve finished using the portal, you can log out and
close the website.

2.3 E-R DIAGRAM

An E-R diagram, or Entity-Relationship diagram, is a visual representation of the

relationships between different data entities in a database. It helps to illustrate how data
is structured and how different entities (like customers, orders, products) are related to
each other.

In simple terms, it's like a map that shows how different pieces of data connect
andinteract within a system.

An Entity-Relationship (E-R) diagram is a tool used in database design to visually

depict the structure of a database. It consists of entities, relationships, and attributes:

1. Entities: These are objects or things in the real world that have distinct existence
and are represented by rectangles. For example, in a university database, entities
could be "Student," "Course," and "Professor."
2. Attributes: These are properties or characteristics of entities, represented by ovals.
For instance, the "Student" entity might have attributes like "StudentID," "Name,"
and "DateOfBirth."

5
 3. Relationships: These illustrate how entities are related to each other and are
represented by diamonds. For example, a "Student" entity might have a relationship
with a "Course" entity, which could be "enrolls in”.

4. Cardinality: This shows the numerical relationship between entities. For example, a
single student can enroll in multiple courses (one-to-many relationship), or a course can
have many students enrolled in it (many-to-one relationship).

By using an E-R diagram, you can easily see how different pieces of data fit together,
ensuring that the database is well-organized and accurately reflects the real-world
relationships between data. This makes it easier for database designers and developers
to understand the system and create an efficient database structure

Fig. 2.3 E-R Diagram

6
In an Entity-Relationship (E-R) diagram, several symbols are commonly used to
represent the various components of the diagram. Here are the most used symbols:

Rectangle: Represents an entity. An entity is an object or concept about which data is

stored. For example, "Student," "Course," and "Teacher" are entities.

Oval: Represents an attribute. An attribute is a property or characteristic of an entity.

For example, "StudentID," "Name," and "DateOfBirth" are attributes of the "Student"
entity

Diamond: Represents a relationship. A relationship shows how two entities are related
to each other. For example, an "enrolls in" relationship between "Student" and
"Course."

Line: Connects attributes to entities and entities to relationships. It indicates the

association between different components of the E-R diagram

Double Oval: Represents a multi-valued attribute, which can have multiple values. For
example, a "PhoneNumbers" attribute might store more than one phone number for a
person.

Dashed Oval: Represents a derived attribute, which can be derived from other
attributes. For example, "Age" can be derived from "DateOfBirth."

Double Rectangle: Represents a weak entity, which depends on another entity for its
existence. For example, a "Dependent" entity might depend on an "Employee" entity.

Double Diamond: Represents an identifying relationship, which links a weak entity to

its owning entity. This is used to show that the weak entity cannot exist without the
strong entity

Ellipses: In some variations, attributes can be represented by ellipses instead of ovals.

7
2.4 SEQUENTIAL DIAGRAM

A sequence diagram is a type of interaction diagram in Unified Modeling Language (UML)

that shows how objects interact in a particular sequence to achieve a specific goal or outcome.
It is particularly useful for understanding and documenting the dynamic behavior of a system
by visualizing the flow of messages, events, and interactions between various components over
time. A sequence diagram is a type of chart used to show how different parts of a system
interact over time. It helps visualize the order in which events happen and how objects or
people (actors) communicate with each other to perform a function.

Here's a simple breakdown:

1. Lifeline: A vertical line that represents an object or person involved in the interaction.
2. Actors: People or external systems that interact with the system, shown as stick figures.
3. Messages: Arrows that show the communication between objects or actors. They
indicate who is sending and receiving information.
4. Activation Bar: A thin rectangle on the lifeline that shows when an object is doing
something.
5. Fragments: Boxes that show special conditions like loops or choices (like if-else
statements).

Sequence diagrams are useful because they show the step-by-step process of how a task is
completed, making it easier to understand and communicate how a system works.

8
 Fig. 2.4 SEQUENTIAL DIAGRAM

This sequence diagram illustrates the interactions between a user and three
systems: the Account System, the Producer System, and the Payment System.
User Login:
 User logs in with userId and password.
 Account System validates credentials and confirms success to the user.
Viewing Products:
 User requests to view products.
 Account System requests product list from Producer System.
 Producer System sends product list back, which is displayed to the user.
Making a Payment:
 User initiates payment with payment details.
 Account System sends payment details to Payment System.
 Payment System processes the payment and confirms success.
 Account System confirms payment success to the user.

9
 3 TECHNOLOGY STACK

3.1 INTRODUCTION

The Everlast: An Anniversary Website is developed using a modern and efficient

technology stack to deliver a personalized and smooth e-commerce experience. The
front- end is created with HTML, CSS, and JavaScript to ensure a responsive and
interactive user interface. For the back-end, we utilize Spring Tool Suite with a
connection to MySQL for robust database management, enabling efficient handling of
user data, product details, and order histories. SQL Workbench is used for database
interactions and management. Secure online payments are integrated using reliable
payment gateway APIs, and the entire application is hosted on cloud platforms to
guarantee high availability, scalability, and security.

3.2 SOFTWARE REQUIREMENTS

Operating System: An operating system (OS) is the software that manages computer
hardware and software resources and provides common services for computer
programs. It acts as an intermediary between users and the computer hardware, enabling
applications to run efficiently and ensuring that different software and hardware
components can communicate effectively.
We have used Windows, macOS, or Linux (Ubuntu, CentOS) in our project.
Web Server: A web server is software that hosts websites and delivers web content to
users' browsers over the internet. It listens for incoming requests from client browsers,
retrieves and processes requested files (like HTML, images, or scripts) from storage,
and sends them back to the client. Web servers also manage security protocols, handle
sessions, and log access for administrative purposes.
We have used Apache Tomcat server 8.5 version in our project.

10
Database: A database is an organized collection of structured data stored electronically
in a computer system. It allows data to be easily accessed, managed, and updated.
Databases use tables to store related information, with each table consisting of rows (records)
and columns (fields) that define specific data types and relationships. They are fundamental for
storing and retrieving large amounts of information efficiently, supporting various applications
from websites to enterprise systems. MySQL is an open-source relational database management
system (RDBMS) that uses structured query language (SQL) to manage and manipulate data. It
is known for its speed, reliability, and ease of use, making it popular for web applications and
small to medium-sized databases. MySQL supports multiple storage engines, transactions, and
various data types, offering flexibility for different application needs.
We have used MySQL(Structured query language) in our project.

Backend Development: Backend development refers to building and maintaining the server-
side logic of web applications. It involves writing code that interacts with databases, manages
user authentication, handles requests from the front-end, and ensures the application's
functionality and performance.
We have used Java Servlets and Java Server Pages(JSP) in our project.
JSP stands for Java Server Pages. It is a technology used for developing dynamic web pages
based on Java programming language. JSP allows developers to embed Java code with
pages,which is executed on the server side to generate dynamic content that can be sent to the
client's web browser.

Frontend Development: Frontend development involves creating and implementing the

visible parts of a website or web application that users interact with directly. It focuses on
building the user interface (UI) and user experience (UX), using languages like HTML for
structure, CSS for styling, and JavaScript for interactive elements. Frontend developers work to
ensure the site or app is visually appealing, responsive, and functional across different devices
and browsers, while collaborating closely with backend developers to integrate server-side
logic and APIs.

11
HTML, or Hypertext Markup Language, is the standard language used to create and structure
content on web pages. It consists of a series of elements or tags that define the different parts of
a webpage, such as headings, paragraphs, images, links, and forms. HTML tags are enclosed in
angle brackets (< >) and are used to format text, embed multimedia, create lists, and define the
overall structure and layout of web documents
Browsers interpret HTML to display content to users, forming the foundation of how
information is presented and accessed on the World Wide Web.

CSS, or Cascading Style Sheets, is a language used to define the presentation and appearance
of HTML elements on web pages. It controls the layout, colors, fonts, and styling of content,
separating the design from the structure and content defined by HTML. CSS allows developers
to create consistent and visually appealing web pages, enhancing user experience by
customizing the look and feel across different devices and screen sizes. It works by applying
rules or styles to HTML elements, using selectors to target specific elements and classes for
reusable styles.
We have used HTML5, CSS3, JavaScript in our project.

Development Environment: We have used Spring Tool Suite in our project.

Spring Tool Suite (STS) is an Eclipse-based development environment customized for
building Spring applications. STS integrates seamlessly with popular build tools like Maven
and Gradle and provides powerful debugging and testing capabilities. It also includes features
like live information about running Spring applications, a comprehensive set of code templates,
and deep integration with the Spring ecosystem, making it an ideal IDE for developers working
on Spring projects. The intuitive interface and extensive documentation make STS a valuable
tool for both beginners and experienced developers in the Spring framework.

3.2 HARDWARE REQUIREMENTS

Processor: A processor, also known as a central processing unit (CPU), is the brain of a
computer that executes instructions from software programs. It performs arithmetic, logic,
input/output operations, and controls the overall operation of the computer. Processors come in
various types and speeds, influencing the computer's performance and capability to handle
12
tasks efficiently.
We have used Multi-core processor (e.g., Intel Core i5/i7 or AMD Ryzen 5/7) in our project.

13
Memory: Memory in computing refers to electronic components used to store data and
instructions temporarily or permanently. It includes primary storage like RAM (Random
Access Memory) for fast access to currently running programs and secondary storage like hard
drives or SSDs for long-term data storage. Memory size and speed affect a computer's
performance and its ability to handle multiple tasks simultaneously.
We have used Minimum 8 GB RAM, recommended 16 GB or more in our project.

Storage: Storage in computing refers to devices or systems used to hold data permanently or
semi-permanently, even when the computer is powered off. It includes hard disk drives
(HDDs), solid-state drives (SSDs), and other storage mediums like optical discs and flash
drives. Storage capacity and speed vary across different types of storage devices, influencing
data access and retrieval times. We have used SSD with at least 256 GB capacity in our project.

Network: A network is a collection of computers and devices interconnected to share

resources, information, and services. It allows communication and data exchange between
devices using wired or wireless connections. Networks can be local (LAN) within a limited
area, wide (WAN) spanning across larger geographical areas, or global (Internet) connecting
networks worldwide. We have used Reliable internet connection in our project.

Peripherals: Peripherals are external devices connected to a computer that expand its
functionality or provide input/output capabilities. Examples include keyboards, mice, printers,
scanners, monitors, and external storage devices like USB drives. Peripherals enable users to
interact with and utilize the computer system for various tasks beyond basic processing.
We have used Standard keyboard and mouse, Additional monitors for extended workspace in
our project.

3.4 PACKAGS AND MODULES

Packages and modules refer to units of organized code in software development that serve
different purposes:

14
 1. Packages: In programming languages like Java and Python, packages are collections of
related classes and resources bundled together. They help organize code into
namespaces, making it easier to manage and reuse components across different parts of
a program or between different programs. Packages often encapsulate functionality,
providing a way to structure and modularize code for better maintainability and
scalability.
2. Modules: Modules are similar concepts but are more generalized across various
programming languages. They encapsulate a set of related functions, variables, and
classes into a single unit. Modules help in organizing code, reducing complexity, and
promoting code reusability. In languages like Python, modules are files with Python
code that can be imported into other Python scripts to provide additional functionality
or resources.

Both packages and modules are fundamental concepts in software development that promote
modular programming practices, making codebases more manageable, scalable, and
maintainable.

1. Spring Boot (Opinionated framework for building production-ready Spring applications)

2. Hibernate (Object-relational mapping framework)
3. Spring Security (Authentication and access-control framework)
4. JUnit (Testing framework for Java)
5. Apache Tomcat (Web server and servlet container)
6. Bootstrap (Front-end component library)
7. jQuery (JavaScript library for DOM manipulation and AJAX)
8. Popper.js (Dependency for Bootstrap tooltips, popovers, and dropdowns)

14
 4 IMPLEMENTATION

4.1 INTRODUCTION

Implementing Everlast: An Anniversary Website involves creating a comprehensive e-

commerce platform dedicated to providing a personalized shopping experience for anniversary
gifts. The implementation leverages modern web technologies to ensure a seamless user
experience, from browsing products to secure online payments. Key features include user
registration and login, product personalization, delivery verification, and efficient order
management. The aim is to build a robust, user-friendly platform that simplifies the process of
selecting and purchasing unique anniversary gifts, ensuring customer satisfaction and
operational efficiency.

4.2 TEST-CASES

Test cases are detailed instructions or scenarios designed to verify specific functionalities or
aspects of a software application. They are written based on requirements and specifications to
ensure that the software behaves as expected under various conditions. Each test case typically
includes inputs, expected outputs, and steps to execute, along with any preconditions or
assumptions necessary for the test. Test cases help testers systematically validate whether the
software meets quality standards, identifies defects or discrepancies, and ensures that all
aspects of the application are thoroughly tested before deployment.

->If JSP is not retrieving parameters properly, there could be several reasons for this issue:

1. Incorrect Parameter Names: Ensure that the parameter names used in the JSP match
exactly with the names sent from the previous request (e.g., from a form submission or
URL query string).
2. Encoding Issues: Check if there are encoding issues causing parameter values not to
be interpreted correctly.

Use appropriate character encoding settings (request.setCharacterEncoding("UTF-8") for

UTF-8 encoding, for example) before retrieving parameters

15
 3. Encoding Issues: Check if there are encoding issues causing parameter values not to be
interpreted correctly. Use appropriate character encoding settings
(request.setCharacterEncoding("UTF-8") for UTF-8 encoding, for example) before
retrieving parameters.
4. Scope of Parameters: Ensure that parameters are being sent and retrieved within the
correct scope. Parameters can be passed through request attributes (request.setAttribute)
or session attributes (session.setAttribute) depending on their scope and lifecycle
requirements.
5. Request Forwarding or Redirection: If parameters are lost during a request
forwarding or redirection, ensure that request attributes or session attributes are properly
used to pass parameters between different components (like servlets forwarding to JSP).
6. Servlet Container Configuration: Check the servlet container (like Tomcat)
configuration to ensure that it handles parameter parsing correctly and that there are no
server-side configuration issues causing parameter retrieval problems.

->A 404 error typically indicates that the resource or page you are trying to access could not be
found on the server. This error is not directly related to database connection issues but rather to
the web server not being able to locate the specified URL or resource.

Here are some steps to troubleshoot and resolve a 404 error when creating a database
connection in your web application:

1. Check URL and Configuration: Ensure that the URL or path specified in your web
application for database connection is correct and matches the configuration in your
code. Verify the JDBC URL, database name, username, password, and other connection
parameters are accurate.
2. Database Server Availability: Ensure that the database server (e.g., MySQL,
PostgreSQL) is running and accessible from the server where your web application is
deployed. Test the database connection separately using database management tools or
command line utilities to confirm connectivity.

16
 3. Servlet Mapping and URL Patterns: If you are using servlets or JSPs to handle
database operations, verify that the servlet mapping or URL patterns in your web.xml or
annotated configuration (@WebServlet) are correctly set up. Incorrect mappings can lead
to 404 errors when accessing servlets or JSPs.
4. Check Server Logs: Review the server logs (e.g., Tomcat logs, Apache logs) for any
specific error messages or exceptions related to the 404 error. Logs can provide insights
into what resource or URL is not being found by the server.
5. File and Directory Permissions: Ensure that the files and directories required for your
web application, including configuration files (web.xml, context.xml), are deployed
correctly and have appropriate read/write permissions.

->If you're encountering an issue where you cannot start or deploy your web application because
Tomcat server is already running, here are a few steps to resolve the situation:

1. Check Running Processes:

1. First, verify if Tomcat is indeed running. You can check this by opening Task
Manager (on Windows) or using commands like ps (on Unix-based systems) to
list running processes.
2. Look for processes named java or specifically catalina (Tomcat's executable) to
confirm if Tomcat is running.
2. Stop Tomcat:
1. If Tomcat is running, you need to stop it before you can start a new instance or
deploy your web application.
2. On Windows, you can stop Tomcat by using the Tomcat Monitor application (if
installed) or by stopping the service from Services (search for services.msc in
Start menu).
3. On Unix-based systems, you can stop Tomcat by using the shutdown.sh script
located in the Tomcat bin directory (./shutdown.sh).
3. Kill the Process:
1. If you cannot stop Tomcat through normal means (e.g., if it's unresponsive or
not stopping), you may need to kill the Java process directly.

17
 4. Deploy Your Application:
1. Once Tomcat is restarted and running, deploy your web application by copying
the WAR file or the exploded directory structure to Tomcat's webapps directory.
5. Deploy Your Application:
1. Once Tomcat is restarted and running, deploy your web application by copying
the WAR file or the exploded directory structure to Tomcat's webapps directory.

->The "HTTP Status 404 - Not Found" error typically indicates that the server could not find the
requested resource (in this case, the servlet) at the specified URL. Here are some steps to
troubleshoot and resolve this issue:

Check Servlet Mapping:

 Ensure that the servlet is correctly mapped in your web.xml deployment descriptor or
using annotations (@WebServlet) if you are using Servlet 3.0+ specification.
 Servlet Class and Package:
o Verify that the servlet class (com.example.MyServlet in the example) is
correctly defined and located in the specified package.
o Check for any typos or discrepancies in the servlet class name or package that
could prevent the servlet from being found.
 Context Path:
o If you are deploying your application with a context path (e.g.,
http://localhost:8080/myapp/), make sure that the servlet URL includes the
correct context path.
o For example, if your servlet is mapped to /myServlet, the full URL might be
http://localhost:8080/myapp/myServlet.
 Server Restart:
o After making changes to servlet mappings or configurations (web.xml or
annotations), restart your servlet container (Tomcat, for example) to ensure that
changes are applied correctly.
 Deployment Issues:
o Check the deployment of your application (war file or exploded directory
structure) to ensure that the servlet class files are correctly packaged and
deployed in the servlet container.

By systematically checking these aspects and ensuring that servlet mappings and configurations are
correct, you should be able to resolve the HTTP Status 404 error and access your servlet
successfully.

18
4.3 TESTING

Testing in Everlast : An Anniversary Website would involve various aspects to ensure the
functionality, reliability, and usability of the educational portal. Here are some key areas where
testing would be crucial:

1. Unit Testing: Verify individual components like modules, classes, or functions to

ensure they perform as expected. This ensures that each part of the system works
correctly in isolation.
2. Integration Testing: Test how different components work together as a group. This
includes testing interactions between modules, database integration, and API
interactions within the portal.
3. System Testing: Validate the entire system as a whole. This includes testing user flows,
navigation, functionality across different browsers and devices, and ensuring that all
features and functionalities of Everlast : An Anniversary website work seamlessly
together.
4. User Acceptance Testing (UAT): Involve end-users (students, faculty, administrators)
to test the portal in a real-world environment. This helps identify usability issues, gather
feedback, and ensure the portal meets user expectations and requirements.
5. Performance Testing: Evaluate how Everlast : An Anniversary website performs under
various load conditions. This includes stress testing to determine its stability and
responsiveness under peak loads, ensuring it can handle multiple users simultaneously
without performance degradation.
6. Security Testing: Assess the portal's security measures to identify vulnerabilities and
ensure data protection. This includes testing for authentication mechanisms, data
encryption, access controls, and protection against common security threats like SQL
injection and cross-site scripting (XSS).
7. Regression Testing: Ensure that recent code changes or updates do not adversely affect
existing functionalities. This involves retesting previously tested features to confirm
they still work correctly after modifications.

19
 8. Accessibility Testing: Verify that Everlast : An Anniversary website complies with
accessibility standards (such as WCAG) to ensure it is usable by individuals with
disabilities. Test features like keyboard navigation, screen reader compatibility, and
color contrast.

Fig.5.1 login page

The Everlast : Anniversary website login page includes:

Login Section:

 Email ID: A text input field where users enter their email address.
 Password: A text input field where users enter their password.
 Continue Button: A button labeled "Continue" that users click to submit their login
credentials.

Registration Link:

 At the bottom, there's a link for users who don't have an account, prompting them to
"Register here."

20
 Fig.5.2 Sign Up Page

The Everlast : Anniversary website signup page includes:

Sign Up Section:

 Email ID: A text input field where users enter their email address.
 Your Name: A text input field where users enter their name.
 Password: A text input field where users enter their password.
 Sign Up Button: A button labeled "Sign Up" that users click to submit their sign up
credentials and move to the login page.

Server-Side Processing:

1. Form Submission:
o The server receives the form data via a POST request.
o The data includes the email, name, and password entered by the user.
2. Database Connection:
o The server connects to the database where user details are stored.
o The connection is usually established using a database driver (e.g., JDBC for Java,
PDO for PHP).
3. Data Insertion:
o The server checks if the email already exists in the database to prevent
duplicate registrations.
o If the email is unique, the server inserts the new user's details into the database.
o Passwords are typically hashed before storage for security purposes.

21
 Fig.5.3 Available Locations Page

This page enables us to view and track different locations where the restaurant is
available and helps us to know whether that location is for delivery or not.

Fig. 5.4 Home page

The image is a screenshot of an e-commerce webpage from a website called "EverLast" that
specializes in selling gifts, flowers, and cakes. Here’s a breakdown of the key elements in the
image:

22
 1. Website Header:
o The top left has the "EverLast" logo with the tagline "Forever reasons for
forever ties."
o A search bar allows users to search for gifts, flowers, and cakes.
o There are navigation links for "Help," "Currency - INR," "Corporate Gifts,"
"Partner With Us," "Track Order," and icons for user account and shopping
cart.
2. Main Menu:
o Below the header, there's a menu with categories: Home, Birthday, Combos,
Anniversary, Express, Cakes, Flowers, Plants, Gifts, Personalised Gifts,
Chocolates, Combos, Birthday, and Occasions.
3. 2 Hour Delivery Gifts Section:
o This section showcases cakes available for 2-hour delivery.
4. Sort and Filter Options:
o Users can sort the products by "Name," "Price: Low to High," and "Price:
High to Low."
o They can also filter the products by delivery date.
5. Product Listings:
o Chocolate Truffle Cake: Priced at ₹500.00.
o Red Velvet Cake: Priced at ₹650.00.
o Photo Cake: Priced at ₹950.00.
o Black Forest Cake: Priced at ₹1100.00.

Each product listing includes an image of the cake, the name of the cake, and its price. The
interface is designed to help customers quickly find and purchase cakes for delivery within a
short timeframe.

23
 Fig.5.5 Detailed view of Product

The image is a screenshot from the "EverLast" website, showing the product page for a
"Chocolate Truffle Cake." Here’s a detailed explanation of the elements on this page:

1. Website Header:
o Same as the previous screenshot, with the "EverLast" logo, search bar, and
navigation links for "Help," "Currency - INR," "Corporate Gifts," "Partner With
Us," "Track Order," user account, and shopping cart.
2. Main Menu:
o Categories include Home, Birthday, Combos, Anniversary, Express, Cakes,
Flowers, Plants, Gifts, Personalised Gifts, Chocolates, Combos, Birthday, and
Occasions.
3. Product Information Section:
o Product Name: "Chocolate Truffle Cake"
o Price: Discounted price ₹579 from the original price of ₹699 (17% off)
o Available Offers:
 Up to ₹750 Cashback on paying via Mobikwik
 Use Coupon Code: TRYWINN1 to get 20% off
 Use Coupon Code: WIN50 to get ₹50 off

24
 4. Product Image:
o Large image of the Chocolate Truffle Cake, with smaller thumbnails on the left
showing different angles or variations of the cake.
5. Delivery Check and Add to Cart:
o Option to enter the pincode to check delivery availability.
o Green "ADD TO CART" button for purchasing the cake.
o A countdown timer indicating 06:39:29 hours left for today's delivery.
6. Additional Information:
o Below the main product section (partially visible), there is likely more
information about the product description, specifications, and possibly customer
reviews.

This page is designed to provide detailed information about the selected product, offer discounts
and promotions, and allow the user to add the product to their cart for purchase. The delivery
check ensures that customers can confirm the availability of delivery services to their location
before making a purchase.

Fig.5.6 Dynamic cart

25
This image appears to be a screenshot of a shopping cart from an e-commerce website. Here’s a
detailed breakdown of the different elements visible in the image:
1. Product in Cart:
o Product Name: Chocolate Truffle Cake
o Price: Rs 579.00
o Option to Remove: There is a "Remove" button to delete this item from
the cart.
2. Cart Summary:
o Total Amount: Rs 579.00
o Proceed to Payment Button: There is a green button labeled "Proceed
to Payment" for moving to the payment stage of the checkout process.
3. Additional Product Section:
o Partially visible, suggesting there may be more products or product
details below the visible section.
4. Discount/Cashback Offers:
o Text mentions cashback offers when paying via Mobikwik, with promo
codes provided:
 Code "TRYWINNI" for 20% off
 Code "WINS50" to get Rs 50 off
5. Navigation/Menu Options:
o A blue button labeled "Menu" is visible on the right side, which likely brings
up the website's navigation menu.
o Other navigation options such as "Corporate Gifts", "Partner With Us",
"Track Order", "Sign In", and "Cart" are visible at the top of the screen.
This layout is typical for an online shopping platform, showing the items in the cart, pricing,
and options to proceed to payment or modify the cart. The website might be focused on selling
cakes and other related products, as inferred from the product and discount offers.

26
 Fig. 5.7 Address page

The image is a screenshot of the "Shipping Address" page on the "EverLast" website, part of

the checkout process for purchasing a product. Here’s a detailed breakdown of the elements on

this page:

1. Website Header:

o The "EverLast" logo is present in the top left corner.

2. Checkout Progress Bar:

o The progress bar at the top indicates the steps in the checkout process:

1. Cart (completed)

2. Address (current step)

3. Personalize

27
 3. Shipping Address Form:

o Recipient Name: Field to enter the name of the person receiving the package.

o Phone Number: Field to enter the recipient's contact number

o Address: Field to enter the recipient's address.

o City: Field to enter the city of the recipient.

o State: Field to enter the state of the recipient.

o Zip Code: Field to enter the postal code of the recipient.

o Address Type: Options to select the type of address: Home, Office, or Other.

This page is designed to collect the necessary shipping information for delivering the product to the

recipient. It ensures that the delivery details are accurate and allows the user to specify the type

of address for appropriate handling and delivery of the package

Fig.5.8 Personalize gifts page

28
This image shows a "Personalize Your Gift" page from the EverLast website, which appears to

be part of the checkout process. Here's a detailed breakdown of the different elements visible

on this page:

1. Progress Bar:

o The top of the page shows a progress bar with four steps: Cart, Address,

Personalize, and Payment. The current step highlighted is "Personalize" (step

3).

2. Form Fields:

o Delivery Date and Time: A field to select the delivery date and time for the

gift.

o Occasion: Options to specify the occasion, such as Birthday, Anniversary, or

Other.

o Personal Message: A text box to enter a personal message that will

accompany the gift.

3. Sender Information:

o Name: A field to enter the sender's name.

o Phone Number: A field to enter the sender's phone number.

o Hide Sender Information: A checkbox to hide the sender's information if

the sender wishes to remain anonymous.

4. Button:

o Continue to Payment: A green button at the bottom to proceed to the next

step, which is the Payment step.

29
 5. Logo and Branding:

o The top left corner displays the EverLast logo with the tagline "Make Special

Moments Even More Special."

This page is designed to collect information necessary to customize the gift, making it suitable for

specific occasions and adding a personal touch before proceeding to the payment stage.

Fig. 5.9 Payment page

This image shows a "Payment" page from the Winni website, which is part of the checkout
process. Here’s a detailed breakdown of the different elements visible on this page:
1. Progress Bar:
o The top of the page shows a progress bar with four steps: Cart,
Address, Personalize, and Payment. The current step highlighted is
"Payment"
2. Payment Method Options:
o A row of buttons to select different payment methods:
 Credit Card
 Debit Card
 Net Banking
 UPI

30
 Cash on Delivery

30
 3. Payment Instructions:
o A section on the left with the instruction "Please select a payment method
to proceed," guiding users to choose a payment option from the above list.
4. Delivery Address:
o A section on the right displaying saved delivery addresses:
 Address 1: 123 Main Street, City, State - 12345, Country
 Address 2: 456 Elm Street, Another City, State - 67890, Country
o An option to "Add New Address" if the user wants to enter a different
delivery address.
o The total amount to be paid is Rs 1579.
5. Logo and Branding:
o The top left corner displays the Winni logo with the tagline
"Celebrate Relations."
This page is designed to allow users to select their preferred payment method and confirm the
delivery address before finalizing the purchase. The inclusion of multiple payment options
provides flexibility for the user, and the address section ensures that the product is sent to the
correct location.

Fig 5.10. Add address page

31
This page allows users to add the address they wish the product to be delivered.

Fig. 5.11 Payment successful page

This image shows an order confirmation message. It includes the order number, date, delivery
address, total amount, and estimated delivery time. There is also a button to continue shopping.
It appears to be a confirmation for an online order. The image features a small illustration of
a delivery person on a scooter delivering packages, emphasizing the nature of the confirmation.

32
5 CONCLUSION AND FUTURE SCOPE

5.1 CONCLUSION

In conclusion, the Everlast anniversary website project successfully integrates a range of

features designed to automate and optimize various administrative, academic, and
communication processes within the engineering college. By meticulously replicating the core
functionalities, such as user authentication, academic data management, and online payment
systems, the website ensures a seamless and efficient experience for all users, including
students, faculty, and administrators. Emphasizing robust security measures and user-friendly
interfaces, the Everlast platform not only mirrors the original website's efficiency but also
introduces modern technologies to enhance performance and reliability. This initiative
highlights the commitment to providing a technologically advanced digital platform that meets
the evolving needs of the college community, ultimately contributing to an improved and more
effective educational management system.

5.2 Future Scope for Everlast: Anniversary Website

Future enhancements for the Everlast anniversary website could focus on incorporating AI-
driven analytics to provide predictive insights into various aspects such as user behavior and
resource allocation. Enhancing mobile compatibility and improving the user interface design
for better accessibility and usability will also be key priorities. Additionally, exploring the use
of blockchain technology for secure verification of academic credentials and expanding
collaboration tools to support remote learning and virtual events will further enrich the
platform's capabilities. These advancements aim to keep the Everlast website at the forefront of
educational technology, ensuring it continues to meet the dynamic needs of its users and
enhances the overall operational efficiency and user satisfaction.

33
 6 REFERENCES

 Oracle. (n.d.). JDBC Developer's Guide. Retrieved from

https://docs.oracle.com/en/database/oracle/oracle-database/19/jjdbc/index.html
 Oracle. (n.d.). Java SE Documentation. Retrieved from https://docs.oracle.com/javase/8/docs/
 Oracle. (n.d.). Java EE Documentation. Retrieved from https://javaee.github.io/tutorial/
 W3C. (n.d.). HTML & CSS Standards. Retrieved
from
https://www.w3.org/standards/webdesign/htmlcss
 Oracle. (n.d.). MySQL Documentation. Retrieved from https://dev.mysql.com/doc/
 Duckett, J. (2011). HTML and CSS: Design and Build Websites. John Wiley & Sons.
 Nixon, R. (2012). Learning PHP, MySQL, JavaScript, and CSS: A Step-by-Step Guide to
Creating Dynamic Websites. O'Reilly Media.
 Winni. (n.d.). Online Cake and Flower Delivery. Retrieved from https://www.winni.in/

34