alexguardaquivil619

[alexguardaquivil619]

Week 19: PIT Consultation and Final Stretch

Fine-Tuning for Success

On December 17, 2024, we had our Performance Innovative Task (PIT) Consultation, marking a pivotal moment in our Software Design and Engineering course. This consultation was dedicated to evaluating both the progress of our application and the draft of our manuscript. These components represent the culmination of our semester-long efforts and are essential to demonstrating the practical and theoretical knowledge we've acquired throughout the course.

During the consultation, we presented the current state of our application, highlighting its features and how it addresses the problem we set out to solve. The PIT provided valuable feedback, focusing on areas where we could improve, such as optimizing backend functionality and enhancing the user interface for better usability. While the comments revealed aspects that required refinement, they also affirmed the strides we had made in our development process. The session gave us a clear roadmap for achieving a polished, fully functional application.

We also received feedback on our manuscript, an equally critical deliverable. This document serves as a comprehensive record of our project, detailing our objectives, methodologies, and findings. The PIT emphasized the importance of aligning our results with our initial goals and improving the clarity of our technical descriptions. These insights will be instrumental in ensuring that our manuscript effectively conveys the depth and impact of our work, both technically and academically.

The next day, December 18, was scheduled to be our final exam. However, in a surprising yet motivating announcement, Engr. Suasola informed us that we would not need to take the exam. Instead, he set a new challenge: we had to achieve 100% implementation of our PIT. This decision underscored the importance of applying what we’ve learned in a tangible and meaningful way, prioritizing real-world execution over theoretical assessment. It felt both rewarding and challenging, as it pushed us to focus all our efforts on bringing our project to completion.

This unexpected shift was a reminder of the course's focus on practical learning and problem-solving. Rather than simply testing our knowledge, Engr. Suasola’s decision encouraged us to demonstrate our capabilities by delivering a fully functional application. It was both a relief and a responsibility, motivating us to channel our energy into meeting the requirements of our PIT with excellence.

[alexguardaquivil619]

Week 18: Quiz on Data Mining and Visualization

Practical Understanding

On December 10, 2024, we entered the final stretch of our Software Design and Engineering course with Quiz 2 Finals, covering Data Mining and Data Visualization. Having spent weeks exploring these topics, this quiz tested our ability to connect theoretical understanding with practical application. The timing felt perfect, as it gave us a chance to reflect on the semester’s lessons while gauging our growth in this subject area.

Data Mining was the first major topic in the quiz. It required us to identify techniques like clustering, classification, and association rules and explain their real-world relevance. These questions prompted us to think critically about the application of these methods in extracting insights from large datasets. The questions were challenging, but they also allowed us to realize how much we’ve learned about interpreting and utilizing data effectively.

The second focus of the quiz was Data Visualization, a topic that had been uploaded to USTeP before the finals. Visualization is the art of transforming raw data into impactful visual representations like graphs, charts, and dashboards. The quiz asked us to interpret data visualizations and identify the most appropriate methods for presenting different types of information. This part of the test emphasized the importance of communicating data-driven insights clearly and effectively, an essential skill in any technical field.

As I worked through the quiz, I realized how well the two topics complemented each other. Data mining provides the insights, while visualization ensures those insights are understandable and actionable. The synergy between these two disciplines was evident throughout the test, reinforcing the interconnected nature of our learning in this course.

Week 18 was a fulfilling experience. Although the quiz was challenging, it felt like the culmination of weeks of hard work. It was not just a test of knowledge but also a reflection of how much we’ve grown as problem solvers and critical thinkers. This week left me feeling both accomplished and excited to apply these concepts in future projects.

[alexguardaquivil619]

Week 17: Exploring Data Mining

Unearthing Insights

On December 3, 2024, our Software Design and Engineering class focused on Data Mining, marking our exploration of a critical field in modern technology. Engr. Suasola introduced us to the topic by discussing its foundations, techniques, and real-world applications. Data mining, as he explained, involves extracting meaningful patterns from large datasets to aid in decision-making. This opened our eyes to its significance in industries such as marketing, healthcare, and business analytics. The lecture was engaging, blending theoretical concepts with practical examples of how companies harness data to drive their strategies.

After the lecture, we had a seatwork that allowed us to apply our newly acquired knowledge. The activity required us to analyze practical scenarios where data mining could be utilized effectively. Engr. Suasola designed it to make us think critically about how data transforms into actionable insights, reinforcing the principles we had just learned. I found the exercise helpful in cementing my understanding of how raw data can be processed into valuable knowledge that drives organizational decisions.

The day’s highlight was the group activity, where I worked with Crystal, Jessel, Gwen, Carl, Clarence, and Aljohn. We were given a case study about Target’s use of data mining in its marketing strategies. Target collects customer data to develop personalized discounts, creating a competitive edge in retaining customer loyalty. Our group analyzed how Target assigns Guest IDs to track purchases and predict customer behavior. We also discussed potential ethical issues, such as privacy concerns and data misuse, making the activity not only technical but also thought-provoking.

As a group, we had a lively discussion about the effectiveness of personalized marketing and the risks involved in using third-party data. One of the most intriguing aspects of the activity was debating how companies like Target can balance innovation with ethical responsibility. We also explored opportunities to improve marketing strategies through predictive analytics, envisioning how data mining could evolve in the coming years to meet the demands of a dynamic market. This experience highlighted the importance of both technical understanding and ethical awareness in implementing data-driven solutions.

Looking back, Week 17 was a meaningful learning experience. It showcased the transformative power of data mining in shaping business strategies and introduced us to the challenges of navigating its ethical boundaries. Working with my group reminded me of the value of teamwork in solving complex problems, and I gained a deeper appreciation for the role of data mining in today’s world.

[alexguardaquivil619]

Week 16: Quiz 1 Finals

Testing Knowledge on Software Reliability and APIs

Last November 26, 2024, our Software Design and Engineering class marked an important milestone as we took Quiz 1 for the Finals. This quiz covered two critical topics from our previous discussions: Topic 6: Software Reliability & Quality Management and Topic 7: APIs (Application Programming Interfaces). It was an opportunity to test our understanding of these essential concepts and their practical applications.

The quiz format was well-structured and required a thorough understanding of the material. From Topic 6, we were assessed on our knowledge of defect prevention, testing strategies, and maintaining software reliability. Questions delved into scenarios where we had to apply these principles to ensure a system’s quality over its lifecycle. Reflecting on the group activity about HealthTrack from week 14 helped me relate theoretical concepts to real-world examples.

From Topic 7, the quiz emphasized the core principles of APIs, such as their role in enabling system integration, the importance of secure API design, and how API requests and responses function in practice. The seatwork and group activity about securely accessing medical records through APIs during week 15 were invaluable in helping me navigate these questions. Designing a sequential diagram and identifying key API endpoints during the activity had provided a solid foundation for understanding how APIs work.

Although the quiz was challenging, it was also rewarding. It allowed me to gauge how well I had absorbed the lessons and identify areas for further improvement. Preparing for the quiz reinforced the importance of revisiting previous materials and engaging with practical examples to deepen understanding.

Overall, Quiz 1 was not just an assessment but a reminder of how far we have come in mastering complex software concepts. I am looking forward to building on these insights as we approach the final weeks of the course. Stay tuned for more updates and reflections in the coming weeks!

[alexguardaquivil619]

Week 15: APIs and Collaborative Problem Solving

Bridging Systems Through APIs and Teamwork

Last November 19, 2024, our Software Design and Engineering class took an exciting turn as Engr. Suasola introduced Topic 7: APIs (Application Programming Interfaces). APIs play a pivotal role in modern software development, acting as intermediaries that allow different software systems to communicate and share data seamlessly. Engr. Suasola’s lecture explained these concepts in detail, covering API functionality, security measures, and their importance in creating integrated and efficient software ecosystems. It became evident how APIs underpin many of the conveniences we enjoy in today’s interconnected digital world, such as mobile apps accessing online services or systems sharing information in real time.

To ensure we grasped the concepts, we began with a seatwork exercise focused on identifying API functions and understanding their roles in system integration. This activity served as an excellent opportunity to immediately apply the theoretical knowledge from the lecture, solidifying our understanding of how APIs function in real-world applications.

Following the seatwork, we engaged in a group activity based on a case scenario titled "Patient API Access Simulation: Securely Accessing Medical Records." This activity was particularly engaging because it combined technical knowledge with practical problem-solving. I was grouped with Mizzy, Gabriel, John Lord, Imee, Christian, Kert, and Crystal. Together, we tackled the scenario, which simulated the steps a patient might take to securely access their medical records via an API connected to a healthcare provider’s Electronic Health Record (EHR) system.

Collaborating with my group was a rewarding experience. Each member brought unique perspectives, whether it was technical insights or creative problem-solving approaches. This diversity of thought allowed us to brainstorm effective solutions, refine our sequential diagram, and address the discussion questions comprehensively.

Through this activity, I gained a deeper appreciation of how APIs facilitate seamless integration across systems, making them indispensable in today’s software landscape. I also realized the importance of teamwork in tackling complex problems—a skill that is as critical as technical expertise. This session emphasized how theoretical knowledge, paired with practical application, can lead to meaningful learning experiences.

Overall, this week’s activity deepened my understanding of APIs and their role in software development. I look forward to applying these concepts to future projects as we continue to learn and grow in this course.

Stay tuned for more updates as we progress further in Software Design and Engineering!

[alexguardaquivil619]

Week 14: Exploring Software Reliability & Quality Management

From Concepts to Collaboration in Ensuring Software Excellence

Last November 12, 2024, our Software Design and Engineering class with Engr. Suasola started with seatwork based on the previous topic he had posted in USTeP. This preliminary activity served as a quick recap and warm-up, ensuring that we were ready to dive into the topic.

The focus of our session was Topic 6: Software Reliability & Quality Management. Engr. Suasola introduced us to the principles and methodologies that ensure the reliability and quality of software systems. The discussion highlighted critical concepts like defect prevention, testing techniques, and maintaining software performance over time. I appreciated how Engr. Suasola emphasized the importance of these practices, especially in systems where errors could have significant consequences.

As is customary in our classes, the lecture transitioned into a hands-on group activity. This time, the case study was titled "Ensuring Quality and Reliability in HealthTrack: A Medical Records Management System." The scenario required us to analyze and propose strategies to maintain the quality and reliability of a software system handling sensitive medical data.

I was grouped with Novem, Reigns, John Lord, Aljohn, Christian, April, Josh, and Albert. Collaborating with my teammates was a great experience, as we exchanged ideas and debated the best approaches to ensure HealthTrack met the highest standards. The case study challenged us to apply theoretical knowledge to a practical situation, which deepened our understanding of the topic.

Overall, this session reinforced the critical role of software quality and reliability in ensuring user trust and system longevity. It was an eye-opening experience that underlined the intersection of technical expertise and user-centric thinking. Working on HealthTrack’s case study with my group also highlighted the value of teamwork in solving complex challenges.

I’m excited to carry forward the insights from this week into future projects and endeavors. Stay tuned for more reflections and lessons in the coming weeks!

[alexguardaquivil619]

Week 13: A Moment for Wellness

Embracing Balance: A Pause for Wellness and Renewal

This week in our Software Design and Engineering course, we took a step back from the usual hustle and bustle of academic life. Following Memorandum No. 239, s. 2024, we observed a wellness break—an initiative that underscores the importance of mental and physical well-being.

The wellness break provided a much-needed opportunity to recharge. With no classes scheduled, it was a chance to reflect on the past weeks' workload and accomplishments, and to prepare mentally and physically for the remaining challenges of the semester.

I used this time to catch up on rest, revisit my personal goals, and engage in activities that bring me joy. Whether it was spending time with family, indulging in hobbies, or simply taking long walks to clear my mind, the wellness break reminded me of the importance of balance in life.

As the semester progresses, it's easy to get caught up in deadlines and projects. This break served as a gentle nudge to prioritize self-care and reminded us that productivity and creativity flourish when we are well-rested and centered.

Now, with a refreshed mindset, I am ready to tackle the weeks ahead with renewed energy and focus. Here’s to finishing the semester strong!

[alexguardaquivil619]

Week 12: SUS Activity

No in-person class

This week in our Software Design and Engineering course, we had a slightly different setup as there was no in-person session with our instructor, Engr. Suasola. However, we were given an engaging task to complete and submit by 5 PM on October 29. The focus of this activity was the System Usability Scale (SUS), a crucial tool in quality assurance for assessing the usability of a system.

The activity required us to delve into the principles and application of the SUS. This exercise not only helped us understand the importance of usability in software development but also emphasized the value of user feedback in ensuring system quality. By analyzing hypothetical scenarios or applying the SUS to our projects, we gained insights into how this simple yet effective scale can highlight areas for improvement.

Through this task, I appreciated how systematic evaluations like the SUS can bridge the gap between developers and end-users. The ability to quantify usability and derive actionable insights is an invaluable skill for any software engineer.

This week reminded me of the importance of ensuring that a system is not just functional but also user-friendly. I’m looking forward to integrating this knowledge into our ongoing projects and refining our designs to meet higher usability standards.

[alexguardaquivil619]

Week 11: Project Consultation and Progress Update

Advancing Toward Completion with Engr. Suasola's Feedback

Last October 22, 2024, we had a crucial consultation with Engr. Suasola to review the progress on our application, both frontend and backend. Our goal was to reach 70% completion before presenting, and the feedback from Engr. Suasola helped guide our next step toward refinement.

During the consultation, we showcased the current state of our application. The frontend and backend had come a long way, with core features and structure well on their way. We discussed design choices, implementation strategies, and some of the challenges we encountered along way. Engr. Suasola's feedback highlighted both strengths and areas for improvement, especially in terms of user experience and backend logic.

Post-consultation, our frontend reached 85% completion, with most of the UI and functionality in place. On the backend, we advanced to 80%, ensuring most of the core functions were up and running. Both sections still require additional polishing and testing, but reaching these milestones felt like a significant achievement after weeks of steady progress.

Engr. Suasola’s feedback gave us valuable direction, helping us see where to prioritize further development and testing. For the frontend, we’ll focus on optimizing the UI and improving user flow, while on the backend, additional work on database integration and performance tuning is needed. This consultation clarified the final steps and motivated us to push for a polished and fully functional application.

As we approach the final stages of our project, I’m excited to see all the pieces come together. With a clear roadmap, the next goal is to reach 100% completion, ensuring both the frontend and backend meet our standards. Week 11 has been pivotal in refining our application, and I look forward to seeing the finished product in the coming weeks.

[alexguardaquivil619]

Week 10: Midterm Exam in Software Design and Engineering

Testing Knowledge and Skills Through the Midtern Assessment

This week marked our midterm exam on October 14, a pivotal point in our Software Design and Engineering course, After the previous week's dedicated focus on Topic 4 and system requirements, I approached the exam feeling ready to demonstate my understanding and apply the concepts we've studied.

The exam thoroughly covered core aspects of software design, with an emphasis. The questions tested both my grasp on fundamental principles and my ability to understand it, such as in requirement specifications, system modeling, and design patterns. Each section encouraged a deeper look at how well we could connect theory to real world applications.

Completing the midterm provided me with key insights into my strenghts and areas that need more focus. While I felt confident about some concepts, there are aspects of system structuring and design I plan to revisit. This feedback is especially useful as I look forward to advancing my project with these improvements in mind.

Now that the midterm is behind us, I'm expected to apply what I've learned to our project work. With renewed focus and practical experience from the exam, I'm ready to tackle the next phase of development in our course.

[alexguardaquivil619]

Week 9: Focusing on Topic 4 and System Requirements

Building Toward the Midterm: Key Readings and Project Milestones

This week marked a different approach in our Software Design and Engineering journey as we took on the challenge of independent study. With Engr. Suasola's announcement last October 8, 2024 that we wouldn't have a meeting, we were encouraged to dive deeper into Topic 4, a key part of our upcoming midterm exam, and to focus on progressing with 70% of our system requirements.

The readings this week in Topic 4 presented a great opportunity to reinforce foundational concepts that are integral to our understanding and application of software design. Engr. Suasola's guidance to focus on this topic suggested its importance, likely containing critical theories and methodologies that will directly relate to the challenges and questions in our midterm.

Taking the time to carefully read and understand these materials has helped me think about how these principles will impact not only our exam preparation but also the development of our systems. It was rewarding to take the time to break down each concept, reinforcing my grasp on software requirements, system modeling, and design patterns.

In addition to our readings, we were also tasked with advancing to 70% of our system requirements. This was valuable checkpoint that pushed me to take stock of the current state of my project. Defining clear requirements has been both challenging and enlightening, as it brings into focus the essential features and functionality that the system must achieve.

While we aimed to reach the 70% milestone, this week's work revealed areas in our project that could use more refinement. Through this independent study time, we identified several core functions and specifications that we needed to flesh out further. This checkpoint allowed us to make informed adjustments and prioritize what remains to be done.

With our midterm exam around the corner, Week 9 served as a strategic pause, giving me time to solidify my understanding and ensure we're building a strong foundation for the project requirements. These independent tasks, though initially daunting, are crucial for developing the skills and discipline necessary in real-world software design work.

I look forward to how these efforts will come together as we continue developing our projects and preparing for the midterm exam.

[alexguardaquivil619]

Week 8: Quiz Quiz Quiz

Another week of deliberation of learnings.

Last October 1, 2024 as we welcome the month of October we are also welcomed by our quiz 2 prepared by Engr. Suasola. The quiz has 3 parts, Enumeration, Identification and of course Analysis. The quiz was easy if you really read and understand the topic 3. It is always a nerve wracking moment for me whenever i take a quiz because it is where I can also assess myself if I do well or not.

The enumeration part for me was quite bothering because I forgot most of the answers to the question and it is so frustrating trying to remember it HAHAHA

The identification is always the part where I'm always having a second thoughts and ending up leaving it blank ):

and lastly, the analysis part. I guess I tried my best to explain my answers about the given situations.

again! cramming rarely works! I guess i need to remind myself that over and over again.

[alexguardaquivil619]

Week 7: Preparing for Upcoming Challenges in Software Design and Engineering

No in-person class, but the work continues!

This week marked an unexpected shift in our schedule as Engr. Suasola had to attend to an important matter, which means that we didn't have our usual in-person session. While it was a bit strange not to have our fact-to-face interaction, the week was far from being a break. Engr. Suasola ensured we stayed on course by leaving us with several tasks to focus on.

We were already introduced to Topic 3, which builds on the concepts we've covered so far in Software Design and Engineering. The materials provided gave us plenty to dive into. I'm expecting this topic to be crucial as we move forward, especially considering how it aligns with the design principles we've been learning throughout the course.

In addition to Topic 3, Engr. Suasola announced that Quiz 2 is scheduled for next week. This quiz will likely test our understanding of the recent topics, including those we've covered in the last few weeks. With this in mind, it's essential to revisit the notes, lectures, and exercises from previous classes to ensure I'm well-prepared for the challenge.

Perhaps the most significant update this week was the upload of the PIT (Performance Innovative Task) criteria in our manuscript. The criteria outline what we need to focus on for the next phase of our project, which has been evolving steadily over the past weeks. With these guidelines in place, We can refine the sections we've been working on, making sure that our project aligns with the expected standards. It's great opportunity to enhance the quality of my submission and ensure that it meets the expectations laid out by Engr. Suasola.

Although we didn't have an in-person session, it's clear that there's still a lot of work to be done. This week served as a reminder that even when circumstances change, the learning and preparation never stop. I'll be focusing on thoroughly understanding Topic 4, reviewing for the quiz, and refining our project based on the new PIT criteria. Week 7 may not have gone as originally planned, but it's certainly been productive in its own way!

[alexguardaquivil619]

Week 6: No Rebus Puzzle, Topic 3 and Consultation

Key Testing Methods, QA Practices, and Project Progress

Last August 17, 2024, no rebus puzzle to start off the session this time, but the subject matter was just as engaging. Our focus was on ensuring that software not only works but also meets high standards of reliability and usability. Testing is at the heart of this process, and our discussion began with two main types of testing Black Box Testing and White Box Testing. The Black Box Testing is all about functionality and the White Box Testing digs into the internal workings of the software. Both approaches have their strenghts, and a balanced combination helps ensure robust software. we also tackled about the regession testing, which is crucial after making changes to a software system, keeping this process efficient is where test automation comes in. Automating tests saves time and reduce human error. It's especially useful when projects grow larger, and more functionality needs to be tested repeatedly. We also discussed about Quality Assurance practices. QA isn't just about testing—it's a holistic approach to maintaining software quality throughout its development lifecycle. This includes adhering to coding standards, conducting peer reviews, and tracking issues as early as possible.

One of the highlights of the session is seen in the photos above, it was learning about User Acceptance Testing (UAT), particularly John Brook's Method. This method focuses on measuring the usability of software not only functions correctly but is also intuitive and easy to use.

Of course, after our discussion we are group into 6 groups and I am teamed up with Apus, Calalin, Diaz, Gonzales and Mahinay. We have our assessment or class activity every after our discussion. Engr. Suasola showed us 5 items on what to improved about the given UI and for the last item it was where we applied the John Brooke's Method and I am the one who was tasked to do that part. As a group, I can say that we did pretty well and everyone contributed to the answers we came up with.

Ending the class with a groufie with Engr. Suasola <3

Earlier, today, August 20, 2024, we had a consultation with Engr. Suasola regarding the revisions from our last consulation. the citation of the Appendix in the Requirements Gathering section was approved! However, we still have a few tweaks to make, specifically in our Data Normalization. During the consulation, we were also reminded of our deliverables before midterm and were informed that our presentation after midterm will be crucial in demonstration our progress. It's a lot to work on, but we're on the right track!

It's clear that testing and quality assurance are more than just final steps in the software development process. They are continuous efforts that start early and are vital to delivering a successful product. I found the exploration of different testing methods enlightening, and it deepened my understanding of how comprehensive testing strategies lead to higher-quality software.

With our project work moving forward, it's a busy but rewarding time in SDE. We're to refine our revisions and prepare for what's next!

[alexguardaquivil619]

Week 5: From Questions to Insights

How a simple quiz taught me the importance of preparation, analysis, and critical thinking in software design and engineering.

Last September 10, 2024, at around 6pm, we faced what every student both dreads and expects, a quiz. The format was a mixture of multiple choice, identification, and alayzation questions, and I can confidently say it wasn't a walk in the park, at least for me.

The multiple choice questions were fairly manageable. I mean, you at least get to guess when you're unsure, right? But then came the identification part, and that's when things got tricky. There's just so much information in the lessons, and trying to absorb everything all at once felt overwhelming. This is where my lack of preparation hit me hard. To be honest, I hadn't studied enough for that particular topic, and it showed. I struggle to recall the concepts and terms we had covered, and that's definitely a lesson learned when they say preparation is key, they really mean it.

The analyzation part, though, was where I tried to shine. I put in all my effort, really analyzing the problem step by step. But as the quiz went on, I couldn't shake the feeling that maybe my best wasn't good enough. You know that classic moment where you give it your all but still feel unsude? Yeah, that was me. Looking back, it was still a good exercise, even if things didn't turn out perfectly. HAHAHAHA!

In the end, this quiz reminded me that cramming rarely works (as if I didn't know that already). But most importantly, it pushed me to understand that true learning in Software Design and Engineering isn't just about memorization, it's about being able to think critically and apply concepts effectively. Lesson learned, for real this time!

[alexguardaquivil619]

Week 4: Software Design and Consultation

Intense assessment activity done after discussion and project manuscript revisions.

A captivating view outside the laboratory before our class with Engr. Suasola.

On September 3, 2024. As always, Engr. Suasola began class with something that challenged us, posting a rebus puzzle that required critical thinking to solve. Afterward, he smoothly transitioned into discussing Topic 2 of the week, which contained valuable information. His ability to balance fun with serious learning keeps the class energized and focused.

As soon as the lecture ended, it was time to apply what we had learned. Engr. Suasola gave us an in-class assessment task where we needed to demonstrate our understanding through a project. I am teamed up with Nambatac, Daohog, Ochia, Jabla, Sandigan, Escobio, and Mendoza, and we formed Group 2. We were ready to tackle the assessment.

The task given to us was no small feat. The task was to design a system for collaborative document editing, allowing multiple users to simultaneously edit the same document. We had to define core functionalities, recommend design patterns, and sketch an initial system design. Google Docs served as a major inspiration, we discussed how we could use its strengths while introducing fresh ideas into our design.

This required us to think critically about how the system would work, the features it needed, and potential technical challenges.

We had to define key features like real-time syncing, version control, and user permissions, then choose the appropriate design patterns.

Beyond focusing on our own project, Engr. Suasola gave us another valuable task: observing the systems developed by other groups, each working on a different scenario. This broadened our perspective, giving us a chance to see how others approached their design problems. We carefully noted what worked, what didn’t, and where improvements could be made. This exercise pushed us to think critically about our own design.

During the presentation, Mr. Daohog took the lead for our group. He confidently explained the main features of our system, guiding the audience through our thought process. He provided a step-by-step breakdown of the pseudocode so everyone could understand how the system would work. During the Q&A, the other group asked, "What makes your system different from Google Docs?" It was a thought-provoking moment that made us reflect on the uniqueness of our design.

To wrap up the week, on September 6, 2024, we met with Engr. Suasola to discuss our project management manuscript. This consultation was crucial as it provided us with detailed feedback and guidance on how to improve the project. His insights helped us refine our approach and get a clearer picture of our overall progress, keeping us on track for the final submission.

This week was filled with valuable lessons, collaborative efforts, and insightful feedback from Engr. Suasola. From engaging in stimulating activities like the rebus puzzle to working on a complex system design and receiving critical guidance during the consultation, the experience not only enhanced our technical skills but also encouraged teamwork, creativity, and critical thinking. It was a truly enriching journey that set the stage for continued growth and success in our project.

[alexguardaquivil619]

Week 3: A Break from Classes, But Not from Progress

Making the Most of Week 3: Celebrations, Health Breaks, and Manuscript Revisions

This week, we did not have any sessions with Engr. Suasola due to us making way for some university-wide events. On August 27, we had a health break that was observed university-wide; on August 28, we celebrated the Feast Day of St. Augustine, who is the Patron Saint of the City. Not having our regular classes does not hinder me from my groupmates and I in maximizing our time. We focused on revising our paper, getting the remarks corrected, and making necessary improvements. We also started doing Activity 1 pertaining to the Implementation of the project in our paper. Though we are not able to consult with Engr. Suasola in Week 3, we did make a substantial portion of it independently so we could preempt ourselves for the coming tasks and make sure that our work will not be stalling.