Laurence Dave Ebalang

[ldebs]

WEEK 19!!!

On December 17, 2024, the Software Design and Engineering group held a PIT Consultation, during which the application and a draft of their text were presented to the panel. This meeting allowed the team to present their work and obtain input on topics such as optimizing back-end operations, improving User Interface design, and making technical statements more clear in terms of outlining their findings in accordance with the original project objectives.

The session comments provided crucial insight into how much progress had been made and what needed to be improved. While some difficulties arose that required attention, the session validated the team's progress and gave a clear path for developing both the application and the manuscript. This assistance was critical to the project's success and meeting deadlines for final submission.

On December 18, Engineer. Suasola made an unexpected announcement, he exempted us in the final exam and urged us to focus on attaining 100% execution of their PIT. This shift from theoretical assessment to practical application motivated the team to put their knowledge into practice, focusing on problem solving and hands-on work. It was a compelling but challenging move that drove us to fully commit to completing our assignment effectively.

[ldebs]

Week 18!!!

On December 12, 2024, we took Quiz 2 finals for our Software Design and Engineering course, which covered Data Mining and Data Visualization. It proved to be a terrific challenge to test our knowledge as well as our ability to apply everything we had learnt over the term. The first section of the quiz focused on Data Mining, which tested our ability to recognize techniques such as clustering, classification, and association rules and grasp their real-world applications. The difficult concerns encouraged us to think critically about how such algorithms can extract important insights from enormous datasets.

The second component of the test focused on Data Visualization, which involved reading and analyzing data visualizations as well as determining the best approach to present different types of data. This portion taught me that sharing understanding is a critical component in any technical sector.

As I completed the quiz, I realized how Data Mining and Data Visualization interact with one another. Data visualization makes crucial insights more accessible and comprehensible. This connection demonstrated the holistic nature of everything we learnt in this course. As I completed the quiz, I realized how Data Mining and Data Visualization interact with one another. Data visualization makes crucial insights more accessible and comprehensible. This connection demonstrated the holistic nature of everything we learnt in this course.

[ldebs]

Week 17!!

On December 5, 2024, our Software Design and Engineering class explored the interesting area of Data Mining. Engr. Suasola discussed the major concepts, methodologies, and practical applications of the field. Data mining is a concept that involves extracting meaningful patterns from large information in order to support business choices in fields such as marketing, healthcare, and business analytics. The professor mixed academic techniques with practical examples to explain how businesses use data to establish their plans.

Following the talk, we participated in a seatwork exercise that required us to think critically about circumstances where data mining could be used effectively. This project helped us understand how raw data may be turned into useful insights. The highlight of the day was a group activity about Target's use of data mining for targeted marketing. Our group talked about how Target records customer behavior and the ethical issues surrounding privacy and data use.

Our conversations also included the balance between innovation and ethical responsibility in data mining, as well as the potential of predictive analytics to improve marketing strategies. Overall, this experience demonstrated how technical knowledge and ethical awareness are inextricably linked when using data to influence decisions.

Week 17 was highly informative, demonstrating how data mining can be quite transformational while also reminding us that ethical procedures are difficult to sustain. Group work also emphasized the value of collaboration and expanded my understanding of the function of data mining in driving corporate strategies.

[ldebs]

Week 16!!!!

On November 28, 2024, we finally reached a crucial milestone in our Software Design and Engineering class: we took Quiz 1 for the Finals. In this quiz, we dealt with two crucial topics: software reliability and quality management (Topic 6), and APIs (Topic 7). The quiz was an overall test that required us to apply academic knowledge to practical applications. The quiz covered defect prevention, testing methodologies, and software reliability from Topic 6, as well as API integration, secure design, and request-response mechanics from Topic 7. Revisiting activities such as the HealthTrack case study and the API group project was extremely beneficial in addressing these issues. While tough, the quiz demonstrated how much we had learned and identified areas for development.

It highlighted the need of studying the subject and applying principles to real-world experiences. It will be interesting to observe how all of these insights affect our strategy as we approach the end of this course.

P.S. I forgot to take picture T_T

[ldebs]

Week 15!!

On November 19, 2024, our Software Design and Engineering class covered a fascinating topic: APIs. Engr. Suasola explained how APIs serve as mediators, allowing various software systems to communicate and share data seamlessly. His talk focused on API functionality, security measures, and their role in developing integrated and efficient software ecosystems, emphasizing their significance in today's interconnected digital world.

To solidify our understanding, we began with a seatwork activity aimed at discovering API functions and their integration roles. Following that, a group activity based on a case scenario simulated secure access to medical records via an API. My colleagues and I examined the situation, produced solutions, and gained real knowledge of API applications and secure integration methodologies.

This week's lesson focused on the role APIs play in modern software, as well as the need of teamwork in addressing complicated challenges. The academic knowledge combined with hands-on experience provided me with a comprehensive understanding of how APIs enable seamless system interaction. I'm looking forward to applying these techniques to future projects as we progress through this course.

[ldebs]

Week 14!!!

On November 13, 2024, our Software Design and Engineering course with Engr. Suasola began with a recap task based on the previous topic covered on USTeP. It served as a warm-up for the day's discussion about software reliability and quality management.

The lecture concentrated on important ideas and approaches for assuring the dependability and quality of software. Engr. Suasola covered subjects such as defect avoidance, testing procedures, and performance maintenance, all of which he emphasized as critical to developing trustworthy and robust systems. We also conducted a joint case study to investigate ways for controlling software quality and reliability.

This session brought to my attention the importance of integrating technical expertise with user-centered approaches. It underlined the importance of software dependability and quality in ensuring the system's long-term viability and user trust. The ideas obtained from this debate are invaluable and will inform my approach to future initiatives.

[ldebs]

Week 13!!!

Embracing Wellness: A Time to Recharge

This week, in our Software Design and Engineering course, we had a wellness break in accordance with Memorandum No. 239. 2024, in pursuit of mental and physical health. Since courses were suspended, it became an opportunity to take a break, reflect on our success, and prepare for the difficulties that lay ahead. This break allowed me to recuperate, review my own goals, and engage in activities that I enjoyed, such as spending time with loved ones, hobbies, or simply unwinding.

This wellness break has reminded me that in order to maintain long-term productivity and creativity, a balance is required. This break provides for self-care and renews a sense of equilibrium in the midst of the semester's demands. Refreshed and invigorated, I am ready to tackle the remaining weeks with focus and resolve to finish the semester strong.

[ldebs]

Week 12!!!!

This week in our Software Design and Engineering class, we did not have an in-person session with Engr. Suasola. We were instead assigned a fascinating exercise connected to the System Usability Scale, a critical instrument in understanding system usability, which was to be submitted by 5 p.m. on October 31st. Because it is all about SUS, the assignment required us to understand the principles and applications of how they connect to the role of quality assurance in software testing.

This exercise demonstrated how SUS bridges the gap between developers and end-users by providing a framework for usability evaluation. We also discussed how, by evaluating hypothetical scenarios or just applying SUS to our own projects, we may identify potential usability difficulties and improve specific usability areas. It has demonstrated the importance of leveraging user feedback to improve the intuitive design of systems and apps.

I've always believed that was an important lesson in how software engineers should consider users rather than just functionality. The capacity to test usability and use the results to make changes leads to better-designed systems. The SUS provides a useful framework for methodically assessing and improving usability. This week emphasized the significance of developing systems that promote usability and functionality. As we continue to work on our projects, I'm enthusiastic to apply what we've learned to improve our designs and the overall user experience. It serves as a reminder that successful software is not only productive, but also user-friendly and pleasurable.

[ldebs]

Week 11!!!!

Making Progress with the Help of Engineer. Suasola

We had a consultation with Engineer. Suasola on October 22, 2024. We presented our project and evaluated its progress at 70% completion to find areas for improvement. We presented the frontend and backend, with an emphasis on significant features, design ideas, strategies, and implementation issues. Engr. Suasola's ideas highlighted user experience and backend optimization as topics for development. Following consultation, the frontend was 85% complete, with most UI elements and functions completed. The backend has reached 90% completion; it is virtually fully functional. Further refinement and testing are currently underway to ensure seamless functioning. We're focused on the front-end UI, improving the user experience, and increasing backend performance based on feedback. With a clear plan, we intend to achieve 100% completion in the following weeks, delivering a polished and fully usable application.

[ldebs]

Week 6!!!!

October 3, 2024. It was a hectic day for me. There's a lot of activities going on. I was tired all day long. Not only this day. But this week. Our midterms is coming close and quizzes and activities and PIT are stacking all together. Im really drained that week. So, We had a quiz this day. I studied but not detailed. That's why im not confident on my answers on this quiz. Im not sure if its correct or wrong. There's a lot of things that I forgot. My mind went blank after seeing the quiz. Even though I tried my best to answer what I can. It would be a lie if I say that I'm not disappointed. But there's a part of me that feels relief after taking the quiz.

[ldebs]

Week 5!!!!

September 19, 2024. Today, our professor asks us if we ever advance study about the pdf he sent to us. He told us to have advance reading about it. When he asked us. I was nervous cause i didn't read it. So, I kept quiet about it. Until our professor asks us who didn't read it and I was embarrassed but I raised my hand. And so we started our discussion. It was easy to understand since our professor was not relying by the ppt. I learned about test cases, test script, testability. Although i got prior knowledge about those, it was still a nice review. And he tackled about verification and validation. which is very easy to absorb since he was using real life scenario. Basically verification is a step by step process and validation is how you see it as a whole. He also tackled about the testing activites, debugging and etc. After discussing everything, we did our group activities. It was fun. To find, where the problems of the given scenarion and stuffs. It was quite challenging but i had fun today.

[ldebs]

Week 4!!!!

September 12, 2024. Our professor was quiet. It was because he's still mad at us. Since last meeting, he was mad at us. So, we started our quiz. Before that we took the part 1 quiz online. When the day's come to our face to face. We were confuse and startled because there might be a continuation to our quiz since it says part 1. But since our professor didn't announce anything, I didn't study. When our professor said we will start the quiz. I was nervous cause I barely remember what's the last topic is. So, as the quiz goes on, I answered only a few of them. mostly my paper was blank. and after the quiz, we joked around. It was a good thing since it was the first step that will help us all to be in good terms. Lesson learned: dili awayon si sir.

[ldebs]

Week 3!!!!

September 5, 2024. We started our class normally. Our professor was doing great and he was in a good mood. So, we started our class talking about our past lessons. Which is about the relationship of science and arts in our course and proceed on the new topic about software design. We talked about the objectives of software design which is correctness, completeness, efficiency, flexibility, consistency, and maintainability. We learned about the principles of software designs, patterns of software design, and methodologies of software design. Then we started our group activities which will happen every end of our discussion. Each group is given a scenario and we will tackle about it. So, we got the scenario 3, which is collaborative document editing. It's like a google docs. and when we're going to report about it our professor was kinda irritated on us. Maybe because we were not listening to him while explaining. I'm sorry sir, we didn't mean to do that.

PS. Sorry for late upload. I was kinda busy.

[ldebs]

Official day for starting the course SDE. Week 2.

August 22, 2024. This mark as our official class in course SDE. The class started in quiet mode. Our professor was kinda bad mood or maybe he is not feeling well because he was wearing face mask. As the class started our professors presents the ppt and asked some questions. And im proud of my self that I answered one of his question. The question was like which one is more important in software engineering arts or science. I answered both and explained why. Basically my answer was, Both, because we need artistic skills to envision our project and we need science to actualize it. After that we continued the class and he tackled about the evolution of software design techniques. as you can see in the picture above. and finished the discusion.

Since we finished our class early and there's still time left. Our professor gave us something to do in our papers and start working on it as it is to be passed next week. and after that we did some group activities. We were give a scenario and make a ppt about it. we work together and luckily the person who was chosen to report was listening to us tackling on how to take this scenario. He reported well. It's not perfect but he did his best.

That's it for today's blog and see you next week!!!

[ldebs]

SUBJECT ORIENTATION FOR SDE!!! WISH ME LUCK ON MY JOURNEY.

I was late at uploading but here was the first day of our course in SDE. It was in August 15, 2024. This is where my first journey as a Computer Engineering in USTP in a course SDE begins. This marks our official first day of class.

It was the first day of our class. I was excited to the point that i woke up early than I usually do. but of course as a student i only woke up early but i didn't prepare early. I was taking my time and realize that its almost time for our class and I prepared in a rush. Luckily, I got there on time since our professor was kinda running late for a few minutes. I think he did that on purpose so that he can gives time to people who were running late like me. but still there was still some people who are late.

So, we started our Orientation with some games to know each other more. We introduced ourselves one by one. It was easy going because we already knew our professor since he was our professor last semester. The orientation runs smoothly as possible. I was kinda shocked since our professor was speaking Tagalog and I'm not used to it. He is also not used to it so there was some pause cause he didn't know what to say next and my classmate made fun of him. Long story short. It was a fun day and I hope that this will continue in finals. I hope that I can learn and apply it in real life.