#cpe3c

On August 29, 2024, our group had a consultation session for our Software Design and Engineering course, specifically for Activity 3.4, which focuses on the implementation and the hardware and software requirements for our system. Two of my groupmates met with our instructor, Engr. Suasola, to review our progress. Following the consultation, we were advised to add images to the other categories of our hardware and software requirements.

My groupmates and I plan to discuss this addition, along with other necessary tasks, during our next meeting. We are aware that this is a challenging process, but we are committed to addressing all feedback and completing the requirements efficiently.

From Disappointment to Renewed Hope: Week 16

The anticipation was high as our team prepared for the final presentation of TrendTailor, our capstone project. Sir Carl had promised us an exemption from the final exam if our system met all the requirements. We were motivated and determined. However, on presentation day, we encountered a setback. We were only able to present the designer and client dashboards as we faced significant challenges with our MySQL database. Disappointment set in, but a message from Sir Carl brought a glimmer of hope. He informed us that we would still be exempted from the final exam and granted us another opportunity to present our completed system. It was a day of mixed emotions, a rollercoaster ride from initial disappointment to renewed hope and determination

From Disappointment to Renewed Hope: Week 16

The anticipation was high as our team prepared for the final presentation of TrendTailor, our capstone project. Sir Carl had promised us an exemption from the final exam if our system met all the requirements. We were motivated and determined. However, on presentation day, we encountered a setback. We were only able to present the designer and client dashboards as we faced significant challenges with our MySQL database. Disappointment set in, but a message from Sir Carl brought a glimmer of hope. He informed us that we would still be exempted from the final exam and granted us another opportunity to present our completed system. It was a day of mixed emotions, a rollercoaster ride from initial disappointment to renewed hope and determination.

Forever grateful, I will treasure our friendship sir. the best kaayo ka, Salute! we love youuu 🦋

The day of our final presentation for TrendTailor had arrived—a moment we had all been preparing for. Earlier, Sir Carl had encouraged us by stating that if our system met 100% of the requirements, we would be exempt from the final exam. This gave our team a boost of motivation. However, on presentation day, we could only showcase the designer and client dashboards, as we faced significant challenges with our database, which was built using MySQL.

Despite our struggles, a glimmer of hope emerged when Sir Carl informed us that we were exempt from the final exam and would be given another opportunity to present our system. The day was a whirlwind of emotions, but it ultimately ended on a positive note.

Today, our instructor facilitated a class discussion and pre-test on Topic 6: Software Reliability and Quality Management. This topic highlighted the importance of developing dependable software that meets user expectations by prioritizing reliability—ensuring consistent, error-free performance over time—and quality management, which planning, testing, and process improvement. After the discussion, we worked on case studies as part of our activity, where we identified software quality issues and proposed solutions to enhance reliability and performance. This provided us with practical insights into real-world applications. Following the activity, I continued working on the front end for our "TrendTailor" project.

Today, Sir Carl gave us another activity that really made us think. He started with a quick review of APIs—like how they work, endpoints, and why security is so important. After that, he gave us a group task where we had to figure out how to set up API endpoints for something like accessing secure medical records. It sounded intimidating at first, but once we got into it, it was actually pretty interesting.

In our group, we started by listing the steps, like creating a login endpoint, retrieving medical records, and managing patient data. We even drew a sequence diagram to show how everything connects—like how the user interacts with the app, and how the API communicates with the database. It was kind of fun, but also frustrating at times because we kept debating about what headers to use for authorization and how to handle errors. Sir Carl went around checking on us, and when we got stuck, he gave us tips to keep us moving forward.

Today, Sir Carl started the class by giving us a short seatwork to check if we had reviewed the course material on Topic 7: API. The topic covered the fundamentals of APIs, including their definition, importance, functionality, examples, and various types such as public, private, partner, and composite APIs. APIs act as bridges, allowing different software systems to share data and functions. For instance, they enable apps to connect with social media platforms, payment gateways, or weather services. Sir Carl thoroughly explained how APIs work, emphasizing their role in sending and receiving requests between systems. To reinforce our understanding, he also assigned a group activity where we analyzed real-world examples of APIs and discussed their applications in everyday technology.

by Sittie Janimah A. Disimban

Reflection. Journey. Apprecation.

After months of dedication and overcoming numerous challenges, today marks a major milestone for our capstone project: the final submission to Engr. Carl Suasola. This journey has truly been a rollercoaster ride—filled with moments of frustration, stress, and moments of triumph. Through it all, our determination and teamwork have carried us to this point.

Every moment was spent revising, debugging, and improving both the app and the accompanying papers. We worked late nights, making sure everything was as flawless as possible, with no detail overlooked. As the days passed, we could see our project evolve into something much more polished, and the sense of accomplishment grew with every fix.