#petconnect

This week marked an important step in our research journey. We presented both our Pet Connect system interface and the current draft of our manuscript during our partial defense. It was a great opportunity to show the progress we’ve made so far and gather valuable insights from our instructors.

During the session, we demonstrated how the Graphical User Interface (GUI) works, highlighting key features, how users can move through the system, and how each part supports our goal of helping pet owners and veterinarians connect more easily. We were glad to receive positive feedback on the flow and structure of the design, as well as suggestions on how to make the interface even clearer and more consistent.

On the academic side, we also walked through our manuscript, explaining the research behind our system, how we planned and built it, and the steps we took to get where we are now. This part helped us better understand the importance of being clear and detailed in both our writing and explanations.

The feedback we received from sir Earl and gave us a clearer direction moving forward. We’re now working as a team to apply their suggestions, refining both the system and the manuscript to make sure everything is aligned and well-prepared for the final submission of our paper.

We’re proud of how far we’ve come and even more motivated to keep improving. One step at a time, we’re getting closer to completing Pet Connect!

This week, our team finally got the chance to meet in person to work on the graphical user interface (GUI) for our research project. Being together helped a lot, we were able to share our ideas more clearly, give quick feedback, and make real-time changes using Figma. It was much easier to solve problems and improve our design when we were all in the same room.

During the week, we also had another oral recitation with Sir Earl where we shared what we’ve done so far. He asked questions that made us think more deeply about our work and gave us advice on how to improve it. His feedback helped us see things from a new perspective and motivated us to keep pushing forward with better ideas.

This week reminded us how powerful good communication and teamwork can be. With stronger designs, better understanding, and fresh motivation, we’re ready to keep moving forward!

This week, our team started working on something exciting, the Graphical User Interface (GUI) for our research project. After taking a short break and finishing our oral recitation with Sir Earl, we were ready to bring our ideas to life and begin building what users will actually see and use.

We started by asking ourselves: What should our system look like? What features are most important for users? From there, we made a plan. Each of us had a role, some worked on the design (like buttons, menus, and layout), while others focused on the coding side to make things function properly. We met often to share ideas, fix issues, and help each other out.

By the end of the week, we had a working version of our interface, a big step forward! It was really satisfying to see our hard work turn into something real on the screen. We’re still improving it, but this was a great start.

After taking a break for Holy Week, we came back to our research project feeling refreshed and ready to continue. This week, we had an important face-to-face oral recitation with Sir Earl, where we discussed what we learned from Modules 7, 8, and 9.

We started with Entity Relationship Diagrams (ERDs). These are like maps that show how data is connected in a database, what kinds of information we’re storing, and how they relate to each other. Understanding ERDs helps us design better systems.

Then, we talked about Database Normalization. This is a method used to organize data in a way that avoids duplication and makes everything more efficient. By following certain steps (called normal forms), we make sure each piece of information is stored only once and in the right place. This helps keep the database clean, easy to update, and less likely to have errors.

Lastly, we looked at the Data Dictionary, which is like a guidebook for the database. It explains what each piece of data means, its type, and how it fits into the system. This is helpful for both developers and users.

The recitation with Sir Earl was challenging, but it helped us understand these topics better. It also showed us where we need to keep improving. We’re now more prepared and excited to apply what we’ve learned to improve our project.

This week, we dove into revising our Pet Connect research after receiving detailed feedback from our instructor and it truly shifted our perspective. Rather than seeing the comments as a checklist of things to fix, we viewed them as a guide for deeper thinking. We revisited our analysis, questioned our methodology, and asked ourselves: Are we really telling the full story our data holds? These discussions led us to refine our arguments and improve both the clarity and impact of our presentation.

Through this process, we realized that feedback isn’t just about correction, it’s about growth. It pushed us to think more critically, communicate more clearly, and take ownership of our work in a new way. What once felt like a challenge became a turning point in strengthening both our project and our confidence as researchers.