Untitled

[tito-ben]

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.

WEEEEKK - ELEBEN

[tito-ben]

Week - 16 = :(

Today was the big day—our final presentation for TrendTailor. Sir Carl told us that teams meeting 100% of the requirements would earn a perfect score, which pushed us to give it our all. We stayed up all night trying to finish both the app and the documentation. Early in the morning, we gathered at the 4th floor of the CEA building to make last-minute revisions and finalize everything.

When it was our turn, our leader introduced TrendTailor and its functionality, while I handled presenting the documentation. Unfortunately, luck wasn’t on our side this time. We fell short because we had to switch from MySQL to Firebase midway through the project, which forced us to start from scratch. Sir Carl pointed out some areas we needed to revise and encouraged us to fix everything and resubmit.

Even though things didn’t go perfectly, we learned a lot from the experience. It’s tough to miss the mark, but it’s also a reminder of how important it is to adapt to challenges. Hopefully, we can make the necessary improvements and bounce back.

*gabie nami nakauli kay olats:(((

[tito-ben]

WEEK 15 = leshgoooo!!!₧

Today marked our final meeting for our Software Design and Engineering class. Sir Carl gave us a quiz covering Topics 8 and 9, which focused on Data Mining and Visualization. Data Mining is about discovering meaningful patterns and insights within large datasets, while Data Visualization presents these findings in clear, easy-to-understand charts and graphics. After finishing the quiz, we gathered for a group photo with Sir Carl to commemorate our time in the class. Thank you, Sir Carl, for teaching and guiding us through these valuable lessons!

[tito-ben]

Week 13-14 = shakabrah

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.

Meanwhile, I've been working on our homepage and its functionality, and it’s been an engaging experience.

[tito-ben]

Week 12 - dis and acts

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.

[tito-ben]

WEEK 1 - I Can’t Believe I Missed the First Day of SDE. I’m So Sorry, Sir Carl 😭

The day did not go as expected and as a result, I wasn’t able to attend the first day of our class in Software Design and Engineering (SDE). Believe me, I did not want to begin the semester like this. I had planned on going, but things got messy, and I was late to the class, and it had already begun without me.

Honestly speaking, I don’t even have a valid alibi – it was one of those days when all went wrong. I don’t know, the bac ha bum was who was already raring to go that day, I missed out on thanks to… bad timing, I guess, or maybe my brain simply bailed on me that day. I tried to compose myself but was ready to sign in (or arrived) when clearly, the moment had passed. And I am regretting it right now. I dislike so much to miss anything crucial, especially the first day where everything that has to be done is detailed.

I am very much aware that attendance right from the word go is of utmost importance, and I truly didn’t opt to miss it. I would like to extend my shallow apologies, Sir Carl, for my absence today. I’ll make up for it – I will make sure that I will catch up with whatever I missed, and I will take the necessary steps to get ready for the class. Huhu, I swear this is the last time it will ever happen.

Looking forward to the next class, it is going to be nice, and I am going to be on the right course! 😅

[tito-ben]

Week 5: A Rollercoaster of a Day

Week 5

This day was… rough. I knew I had no time to sleep if I wanted to make it on time for my first quiz, which started at 7 AM sharp. So, instead of resting, I powered through the night to prepare. After the quiz, we had an online CPE311 class right after, followed by a group activity. Things were non-stop, and by the time we finally wrapped that up, it was lunchtime.

After eating, I thought I could catch a quick break. I managed to squeeze in a short nap before my Software Design and Engineering (SDE) class, which thankfully started at 1 PM instead of noon. But just as I was getting comfortable in class, the instructor announced we’d be having Part 2 of our quiz—totally unexpected. I hadn’t reviewed at all. As you can guess, I bombed that quiz, and the disappointment hit me hard.

And just when I thought the day couldn’t get worse… boom! Earthquake drill. Our entire class had to walk down from the seventh floor—and then, after the drill, climb all the way back up. Yes, stairs. From the ground floor to the seventh. Honestly, that was the worst part. I was running on barely an hour of sleep, my legs were on fire, and I still had that failed quiz gnawing at me.

By the end of the day, I just wanted to curl up in bed and forget everything. But instead, I carried this heavy feeling of self-reproach all the way home. It was one of those days where everything felt out of control—and man, I was so ready for it to end.

[tito-ben]

Week 3: Planning for Our TrendTailor Website

Week 3

The last week of August, which marked our third week in Software Design and Engineering, was an asynchronous class. Instead of a lecture, our instructor designated the day for consultation, giving us a chance to meet and address any questions about our projects. However, our group decided to use the time differently—we focused on making progress on our TrendTailor website and organizing for the upcoming first assignment.

Collaboration and Brainstorming

Since we were working remotely, we held a Google Meet to discuss the direction of our project. Our TrendTailor website aims to be a platform where users can customize their wardrobe, similar to how Shein operates, complete with an add-to-cart feature. During the meeting, we tackled some key decisions, including:

Choosing the right programming languages for the project.

Splitting the workload so everyone could contribute fairly.

Learning additional technical information that could help us move forward smoothly.

Making It Fair and Fun

We wanted to ensure the work was divided evenly, so we used a wheel of names to assign tasks—an easy and fun way to keep things balanced! Once we had our tasks sorted out, we decided to experiment with coding a basic webpage. That exercise was an eye-opener, as we quickly realized that building the TrendTailor site would be more complex than expected. It wouldn’t be a straightforward journey, but we were excited for the challenge ahead.

Final Thoughts

This asynchronous week gave us the time we needed to align our goals and responsibilities. Even though we didn’t have a formal consultation, the discussions and planning we did were productive. As we move forward with TrendTailor, I’m learning that communication and preparation are essential in a project like this. We’re ready to take on the next steps—challenges and all!

[tito-ben]

Week-2

Week 2: Building an Insulin Pump Control System

This week in class was both exciting and educational! Our task was to design an insulin pump control system—a challenging yet meaningful project. We started with research, diving into how insulin pumps work, their components, and the technology behind them. The main goal was to figure out how to build a control system and map out the flow of operations to determine if the design was practical and feasible.

Breaking Down the Process

Research and Understanding: We began by understanding the basics—what an insulin pump is, how it regulates blood glucose levels, and what components are involved, like sensors, controllers, and the insulin reservoir. This gave us a clear picture of the system’s complexity.

Creating the System Flow: After gathering the data, we started mapping the flow of the system. This involved creating a step-by-step process showing how the pump would operate—from receiving blood glucose readings to delivering the correct amount of insulin. We also discussed error handling to make sure the system can manage unexpected issues safely.

Feasibility Check: One of the most important parts of the activity was assessing whether the design was feasible—whether the system could realistically function with the components and methods we identified. This required teamwork, as we had to double-check everything to ensure nothing was overlooked.

What I Learned

This group project was a great experience because I learned the importance of collaboration. Working together made it easier to brainstorm, divide tasks, and find solutions. I realized that sharing the workload allowed us to finish quicker and come up with more creative ideas. It also helped that everyone in the group was engaged and contributed their strengths to the project.

Final Thoughts

Overall, I really enjoyed the activity. Not only did we successfully design a potential insulin pump control system, but we also learned how valuable teamwork is in technical tasks. When everyone works together, complicated projects become easier and even fun! This week was a reminder that engineering isn’t just about knowledge—it’s about working with others to bring ideas to life.

[tito-ben]

WEEK 4 - The walkout huehue

Yooo wazzup!!!

We started the discussion with software design with topics of design principles and patterns, software design methodologies, system implementation, implementation strategies: coding standards, modularization, code review, and refactoring, integration, and deployment. and some cool stuff we covered in our bout in SDE class principles, patterns, and how to actually build and deploy prototype software, that we will. It all came together when we worked on a group project to create a restaurant reservation system.

Now for the fun part—our group activity! We were tasked with designing a restaurant reservation system that allows customers to book tables online. We split into teams to handle different parts of the project: Pseudo Code: Drafting the logic of the system, System Design: Creating the overall structure and architecture, Front-End Design: Crafting the user interface and experience.

I was part of the front-end team, and it was so cool to see our ideas come to life. We brainstormed designs, created mockups, and built a user-friendly interface that made the reservation process smooth and intuitive. It was great to see our collective creativity and teamwork shine through in the final product.

Wrapping Up

This class was not just about learning theory but applying it in a real-world scenario. Designing the restaurant reservation system was a fantastic way to understand how software design principles and practices come together in a practical project. It was fun, engaging, and a great learning experience.

If you’re diving into software design, remember: it’s not just about writing code—it’s about crafting solutions that work seamlessly and efficiently.

Catch you later,

Tito-Ben^^