SLIDE 1-2: INTRODUCTION
Qarisha:
We all know that animal shelters are doing meaningful, often life-saving
work—but behind the scenes, their systems can be outdated and
inefficient.
It’s like a constantly shifting puzzle—with new pieces added over time,
but without the right system in place, keeping those pieces all together is
a serious challenge.
SLIDE 3-6: PROBLEM
Randel:
Many shelters still rely on manual systems—paper forms, spreadsheets,
and phone calls—which slows everything down. A centralized digital
system is a necessary tool to remove these inefficiencies and help staff
work faster, with better outcomes for the animals.
SLIDE 7-9: OBJECTIVES
Cyduane:
We designed this system with clear goals in mind:
Organize animal profiles and health data – for better internal
management and more transparency for potential adopters.
Enable online registration and appointment scheduling – so
adopters can engage with the shelter from anywhere.
Maintain adoption and medical history logs – making it easy to
access complete, accurate records at any time.
SLIDE 10-13: CORE FUNCTIONS
Trishia:
There are three key user roles within the system:
Adopters can register, browse pets, schedule visits, and apply for
adoption online.
Shelter staff manage animal profiles, medical records, and adoption
status.
Admins oversee system activity, generate reports, and manage user
access.
DATABASE STRUCTURE
Cabi:
The system is powered by a well-structured relational database,
consisting of six main tables:
Adopters hold user profiles and contact details.
Animals contains pet data—species, breed, age, and status.
Appointments logs scheduled visits between adopters and animals.
Vaccinations and Medical History track each animal’s health
care. Adoptions finalizes the link between an adopter and their pet.
ERD
Cyduane:
Here’s how the ERD works in this system.
Each entity in the diagram represents a table in our database. So we
have entities like Adopters, Animals, Appointments, Vaccinations,
Medical History, and Adoptions.
Qarisha:
Each of these entities has a primary key—for example, adopter_id for
Adopters and animal_id for Animals and the relationships are managed
via foreign keys to ensure referential integrity across the system.
Here’s how those relationships work:
Trishia:
One Adopter can schedule multiple Appointments—so that’s a
one-to-many relationship.
Each Appointment links to one Animal, but each Animal can have
many appointments—again, one-to-many.
For medical data, each Animal can have multiple Vaccination and
Medical History records—also one-to-many.
The Adoptions table is where it all comes together: it connects one
Adopter with one or more Adoptions, forming an optional one-to-many
relationship— and since an animal can only be adopted once, or not at
all the rela
Randel:
This schema ensures normalized data, supports fast lookups, and allows
for clean joins across adoption workflows, health tracking, and user
interaction history.
CONCLUSION:
Cabi:
To wrap up, this system isn’t just a convenience—it’s a real solution to
real problems. This system saves time, reduces errors, and helps staff
focus on what matters—caring for animals and placing them in homes.
It’s a simple, effective solution that makes shelter work faster and more
organized. Thank you.