mariel-mae-mapiot

[mariel-mae-mapiot]

SOFTWARE DESIGN AND ENGINEERING WEEK 17 (December 16-21, 2024)

Week 17: The Final Push for Our PIT

This week was all about the Performance Innovative Task (PIT), and it was nothing short of intense. For a whole week, we had to go back and forth to school for consultations, revisions, and finalizing every detail of our project. The process was grueling; we’d consult with our instructor, get detailed feedback, and then rush to revise the paper or system as needed. It felt like a never-ending cycle of writing, correcting, and refining until everything was 100% perfect.

One of the biggest challenges was the long line for consultations. With three sections all working on their own PIT presentations, the waiting time sometimes felt like hours. Everyone was tired and stressed, but we knew we had to push through. Each comment from our instructor had to be addressed carefully—from small adjustments in the system to major changes in the manuscript. It was exhausting, but we were determined to complete everything on time.

I took on a lot of responsibility for the manuscript, focusing on parts like the user manual, appendices, and other sections. While it was overwhelming at times, I felt proud knowing that I contributed significantly to polishing our paper. Finally, on December 21, we were done. Everything was completed—the system was functional, and the manuscript was finalized. The sense of relief and accomplishment was indescribable. It was a tough journey, but we made it to the finish line.

[mariel-mae-mapiot]

SOFTWARE DESIGN AND ENGINEERING WEEK 16 (December 12, 2024)

In Week 16, we reached the final stretch of the semester. Our last Software Design and Engineering (SDE) class began with Quiz 2, but the day didn’t go as smoothly for me. After finishing an advanced final exam for another subject, DDC, at 7 AM, I spent the morning browsing on my phone instead of preparing for the quiz. Time flew by, and before I knew it, class was about to start. Realizing this, I quickly skimmed through Topics 8 and 9, trying to absorb as much as I could at the last minute.

During the quiz, I managed to answer some questions, but I wasn’t confident about most of my responses. Afterward, we had our final group activity, marking the last official day of our SDE class. To end the session on a meaningful note, we took a class photo with Sir Carl—a way to remember all the challenges and memories we shared throughout the semester.

Looking back, it’s hard to believe how quickly time passed. SDE was a mix of laughter, stress, and sleepless nights, but it also taught us perseverance. While it was bittersweet to conclude the subject, the journey wasn’t over yet, as the Performance Innovative Task (PIT) presentation awaited us.

[mariel-mae-mapiot]

SOFTWARE DESIGN AND ENGINEERING WEEK 14-15 (November 25-December 7, 2024)

In Weeks 14 and 15, our schedule was a mix of wellness and academics. Week 14 coincided with Wellness Week, which meant no classes for three days. During this time, I focused on troubleshooting an issue with running my PHP files on a localhost. After several attempts, I finally managed to get the files to work, but it was a challenging process that took up most of my week. Reflecting on that period, I didn’t document much, so it feels like the days passed in a blur.

Week 15 brought us back to class with Topic 8: Data Mining. Sir Carl started the session with a quick seatwork, followed by a lecture on how businesses use data mining for strategies like marketing. Unfortunately, I was so exhausted from the previous weeks that I ended up completely dozing off during the discussion. I only woke up when the group activity was assigned. Our task was to analyze how Target uses data mining to improve their marketing strategies. Despite my earlier lapse, working with the group helped me grasp the practical applications of data mining, making the topic feel more relevant and engaging.

[mariel-mae-mapiot]

SOFTWARE DESIGN AND ENGINEERING WEEK 13 (November 18-23, 2024)

In Week 13, we explored Application Programming Interfaces (APIs), starting with a quick seatwork to test our knowledge of the topic. Honestly, I wasn’t sure if I answered everything correctly, but it was a good way to get us thinking. Sir Carl then explained how APIs work as connectors that let different apps and systems communicate. He covered the basics, including the types of APIs—public, private, partner, and composite—and how they send and receive requests. It was fascinating to realize how much we rely on APIs in everyday life, from logging into apps using social media accounts to checking weather updates or making online payments.

After the discussion, we were grouped for an activity to apply what we learned. Our group was assigned the "Patient API Simulation: Securely Accessing Medical Records," which each of us in the group contributed ideas. Working together made the task more manageable, and it helped us better understand how APIs function in real-world scenarios.

This lesson opened my eyes to how crucial APIs are in making technology seamless and efficient. They’re the invisible tools that keep so many of the apps and systems we use running smoothly. Week 13 was not just informative but also a reminder to appreciate the technology we often take for granted.

[mariel-mae-mapiot]

SOFTWARE DESIGN AND ENGINEERING WEEK 12 (November 11-16, 2024)

In Week 12, we had a class discussion and a short pre-test with Sir Carl on Topic 6: Software Reliability and Quality Management. This topic emphasizes making software dependable, ensuring it functions as expected, and maintaining high-quality standards. Software reliability refers to the software's ability to perform correctly over time without errors or failures, even under varying conditions. Meanwhile, quality management focuses on planning, monitoring, and improving the development process to ensure the final product meets user needs and expectations.

We also did an activity related to this topic, where we analyzed case studies. Our task was to identify quality issues in the software and suggest improvements to enhance its reliability and performance. This activity allowed us to apply what we learned, connecting the theoretical concepts to practical, real-world scenarios.

From the case study, we discussed strategies to improve Health Tracks reliability, such as enhancing data integrity, optimizing server performance, and implementing regular security audits. Suggested QA strategies included regression testing, beta testing, and code reviews to identify and resolve issues early. Scaling the system using cloud-based solutions and microservices architecture was also emphasized for better reliability during peak usage. Lastly, we highlighted the integration of security into QA processes through continuous testing, penetration testing, and secure coding practices. These solutions connected the theoretical aspects of software reliability and quality management with practical, real-world applications, providing valuable insights for improving system performance.

[mariel-mae-mapiot]

SOFTWARE DESIGN AND ENGINEERING WEEK 11 (November 5-9, 2024)

Week 11 was different from our usual schedule. Instead of regular classes, Sir Carl sent us a screenshot of our activity for the week. This gave us the flexibility to manage our time and work on our own. I used this opportunity to continue developing the front-end of our system project, focusing on creating categories like school appliances, uniforms, and food.

I also spent the week organizing some activities and thinking what to do on the testing of our system when it is not yet done. I also fix some problems on my laptop to run php files. This week felt productive, and it was satisfying to see the project slowly coming together.

[mariel-mae-mapiot]

SOFTWARE DESIGN AND ENGINEERING WEEK 10 (October 22-27, 2024)

Week 10 was a roller coaster of emotions! My team and I worked nonstop on our website system project, pushing hard to get everything ready for our Midterm PIT presentation. Each night was sleepless, filled with debugging, testing, and last-minute changes. The pressure was intense, and there were plenty of breakdowns, nonstop crying, and moments where it felt like we’d never get it done in time.

But despite all the stress and challenges, we made it to the presentation day! After showing our hard work to the class, there was an incredible feeling of relief and happiness. All the sleepless nights and hard work paid off, and I couldn’t have felt prouder of what we accomplished as a team. This week reminded me just how tough, yet rewarding, these projects can be.

Unfortunately, I didn't have any photos during and after the presentation.

[mariel-mae-mapiot]

SOFTWARE DESIGN AND ENGINEERING WEEK 9 (October 14-19, 2024)

Weeks 9 was one of the busiest week I’ve had this semester! In Week 9, I focused on studying for midterm exams in my minor subjects. I spent late nights trying to understand all the materials, making sure I didn’t miss any important details. Then for midterm exams in my major subjects. These exams were challenging, and I had to put in even more time reviewing.

After the exams, even though I was tired, I went right back to working on our system project. My group and I planned to make progress on the backend, but I ran into an issue with my laptop while running phpMyAdmin in Laragon. It was frustrating, but I’m working on a solution so we can keep moving forward with our project.

[mariel-mae-mapiot]

SOFTWARE DESIGN AND ENGINEERING WEEK 8 (October 7-12, 2024)

On October 3, we had our Quiz 2 Part 2 in a face-to-face setup, which was a refreshing change. It was a challenging quiz, and unfortunately, I didn’t get any photos from that day.

Then on October 5, we had a follow-up Quiz 2 Part 1, this time online. We used USTEP website that day and had a problem. I thought my quiz was not submitted but luckily it was submitted on time. It felt a bit different, but the questions really tested our understanding of the material.

[mariel-mae-mapiot]

SOFTWARE DESIGN AND ENGINEERING WEEK 7 (October 1-5, 2024)

We had a day off from class but our instructor left an activity for us to do. My group and I took advantage of the free time to continue developing the front-end of our system project. We focused on refining the interface to make it as user-friendly and effective as possible.

I also went to school to take care of a few other important matters. It was a productive day, and we made solid progress on our project despite the unexpected break from class.

[mariel-mae-mapiot]

SOFTWARE DESIGN AND ENGINEERING WEEK 6 (September 23-30, 2024)

TOPIC 3: SOFTWARE TESTING AND QUALITY

This week we had a discussion about the topic 3 which is software testing and quality.  

Software testing is the process of evaluating software to ensure that it meets the required specifications and functions correctly. It involves running the program with specific inputs and analyzing whether it behaves as expected. If any unexpected behavior is identified, the conditions are noted for future debugging and correction.

After the discussion we had a group activity. An activity where our group mates are our group during the PM course last semester. It was quite challenging and it requires speed in analyzing and identifying the error and solution of a given problem which is a picture. We also used and solved John Brooke’s Technique which made me enjoy it more.

Remember! 

While testing cannot eliminate all defects, it remains an essential part of the software development process. Through structured testing techniques, automation, and quality assurance practices, developers can deliver reliable and functional software to users.

TODAY’S ACTIVITY WAS FUN AND IT'S A WRAP!!!

[mariel-mae-mapiot]

SOFTWARE ENGINEERING AND DESIGN (SDE) (September 9-14, 2024)

WEEK 5: Software Design and Engineering Midterm Quiz 1

As part of our midterm quiz in Software Engineering and Design, we tackled different types of questions, including multiple choice, enumeration, identification, and analysis. This quiz tested our understanding of key concepts we’ve been learning.

Multiple Choice Section

This section challenged us with shuffled questions.

Enumeration Section

In the enumeration part, was simply related to software design.

Identification Section

In this section, we had to identify someone's full name.

Analysis Section

The analysis questions were more in-depth, asking us to determine the specific pattern of a scenario and to draw. We also had to define, explain, and differentiate.

Overall, this quiz gave us a comprehensive review of software design principles. I found the analysis section the most challenging, but it was a good exercise in applying theory to practice.

[mariel-mae-mapiot]

SOFTWARE DESIGN AND ENGINEERING WEEK 4 (September 5, 2024)

TOPIC 2: Software Design

Software design transforms user requirements into a format that programmers can easily use to build software. It takes the client’s needs from the Software Requirement Specification (SRS) and turns them into something that can be implemented with code. This is the first step in the Software Development Life Cycle (SDLC), where the focus shifts from the problem to creating a solution.

Key Principles of Software Design

Problem Partitioning: Dividing the problem into smaller parts makes software easier to understand, develop, test, modify, and maintain.

Abstraction: Allows designers to focus on the bigger picture without getting bogged down by details, simplifying complex systems.

These principles help reduce complexity, minimize errors, and create flexible, maintainable software.

Those are the things I think I’ve learned much about and then we also had an impromptu group activity. 

[mariel-mae-mapiot]

SOFTWARE DESIGN AND ENGINEERING WEEK 3 (August 29, 2024)

Last week there was no face to face class and my group decided to have a meeting for us to start the front end of our project. We decided to discuss it in a google meet.

We divided the workloads using a spin the wheel to be fair for each of us. After dividing the parts, we discuss and talk more about our project.

[mariel-mae-mapiot]

SOFTWARE DESIGN AND ENGINEERING WEEK 2 (August 22, 2024)

Last August 22, 2024 we had our first formal class and had discussed Topic 1.

What is Software Engineering?

Software engineering is both a science and an art, combining rigorous methodologies with creativity and problem-solving skills. Whether developing a simple program or a complex product, the principles of abstraction and decomposition are key to managing complexity and ensuring success. The evolution of software engineering has moved from unstructured, exploratory programming to a structured, systematic discipline that is essential for building reliable, maintainable, and efficient software.

That day was a wrap and had so much fun because of an impromptu group activity. The hassle was absolutely there and the struggles of each group. But in the end we all made it and enjoyed the activity.

[mariel-mae-mapiot]

SOFTWARE DESIGN AND ENGINEERING WEEK 1 (August 15, 2024)

Hi! I’m Mariel and this will be my first ever blog. These pictures were taken last August 15, 2024. Our first face to face class for the course Software Design and Engineering (SDE). During that time our instructor Engr. Carl Suasola orients us about the class syllabus, grading system and also the class rules. The orientation was fun, that's why I only took a few pictures. Stay tuned for my next blog!! Thank you.