#CPE3C

[reysamoranos]

Consultation Frenzy: Week 3 Insights!

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.

[jeshuae]

CPE312 Software Design and Engineering

EduConnect: PIT Software Presentation

Week 10

October 24-25, 2024

ִֶָ𓂃 ࣪˖ ִֶָ🐇་༘࿐

Yesterday, we had our PIT software presentation scheduled during our Software Design and Engineering class. Leading up to the presentation, I felt a bit nervous because I hadn’t completed as many layout designs as I’d hoped. I realized I’d also forgotten to upload some files to GitHub. The night before, I was cramming to finish the system's layout and ended up staying up all night. I also felt some personal stress that affected my focus, so I decided to play some music to help me keep going and complete my work.

During our presentation, our leader gave a brief introduction to our system, called 'EduConnect.' This platform connects students with tutors, who can be other students or instructors. We showcased the main navigation functions, including signing in, creating accounts, the dashboard, subject room, searching for instructors, messaging, profiles, payments, and settings. We demonstrated the backend using Firebase, which handles account management like adding and deleting accounts directly through the database. We also shared some of the errors we encountered and how we planned to fix them. Our instructor provided valuable guidance and gave us feedback, which led to a promising score. He then advised us on areas to improve and asked us to present again the next day with the adjustments made.

Today, we returned to present our updated system to improve our score. Our leader, Tejano, made significant improvements to the backend, such as adding error handling for short passwords, handling invalid credentials, and optimizing the runtime. His leadership included regular updates and reminders, keeping our roles well-coordinated and helping me identify parts of the layout that needed fixing or adding. With his support, we were able to finish the presentation successfully. I’m grateful for his patience and dedication to the project, which motivated all of us to stay on track. We wrapped up the presentation and were relieved to have done our best.

ִֶָ𓂃 ࣪˖ ִֶָ🐇་༘࿐

[razhelleregoniel]

September 5, 2024 *ೃ༄

During the fourth week of Software Engineering and Design, we had an in-depth discussion about Software Design and its significance in system development. We also discussed about the different design patterns, and things to consider when programming the system design.

Furthermore, we were also grouped randomly for a collaborative task regarding the discussion. For our group, we were given a scenario about a designing a system for collaborative document editing. To us, it sounded similar to programs like Canva or Google Docs. For the activity, we defined the core functionalities of the system, recommended design patterns that fit the features of the system, and sketched an initial system design. Then, we were tasked to analyze the work of the opposite group and see whether their recommended design patterns worked for their system or if it didn't.

In conclusion, I have learned a lot about software design and its value to a system project, and I also learned more about collaborating with other people with limited time budget.

That's all for the fourth week! ✧ ˚ · .

[marian-claire-bacas]

August 15, 2024 - Software Design and Engineering Orientation Day

Week 1 Starting in August, I am officially a third-year college student studying at USTP CDO, and classes start in the third week. And the day to return to reality was last Thursday, August 15. That day marks not just the start of class or the return to school but also the orientation for the Software Design and Engineering course I am taking. So I got up early and started getting for school, despite the fact that our class starts at 12 noon. You may be asking why so early given that I live near the university, but you may be familiar with the tense, thrilling feeling in the night before our trip the next day, which makes it difficult to fall asleep. Yes, I felt the same nervousness that day or night before I went to bed, but for the opposite reason. I did not think I was ready to go back to school, and based on the name of the subject, it sounds like a rather scary one, so that's why I was nervous. Nevertheless, I have to do it. So I arrived at school, entered our classroom, and before we began, we were asked to introduce ourselves by stating our name, age, address, and favorite music (I went with Castles Crumbling by Taylor Swift). Following that, we talked about the course's objectives and requirements, including the grading system, and then we recited the student pledge together. That's basically what happened during our orientation. And, I hope that we finish this subject as well as we started it.

[chedilyn]

Week 13

On Week 13, we started with seatwork to test if we had read the given PDF, ensuring we were ready for the discussion ahead. After completing the exercise, our instructor took us through the main topic, explaining key concepts and answering any questions we had. Next, we moved into a group activity, where we collaborated to apply the lessons from the lecture. The activity challenged us to think critically and creatively as we worked together to solve problems.

[mercydacup]

Week 11.

Thursday, November 14, 2024

On that day, I wasn’t able to attend class because of a personal matter. However, I didn’t let the time go to waste—I decided to focus on working on our project instead. It felt like a practical way to stay productive and ensure I was still contributing, even though I couldn’t be present in class.

I’m hopeful that I’ll have the opportunity to either complete the activity I missed that day or find an alternative way to make up for it. Missing it felt like a setback, but I’m determined to catch up and ensure I stay on track. Whether it’s by taking the activity at a later date or completing an equivalent task, I want to demonstrate my willingness to take responsibility for my absence and remain fully engaged with the class or project requirements.

0 notes

[princess-velle-jaspe]

October 18-25, 2024 ♡

Week 11 was an intense week focused on studying and revising code for our PIT. We spent long hours refining both the frontend and backend, with attention to every detail to ensure everything worked smoothly. Sleep was scarce as we pushed to meet our goals, staying up late to tackle last-minute issues and fine-tune our work. Debugging became second nature, with constant testing and adjustments to polish the project. Despite the exhaustion, it was rewarding to see our code come together as we approached the final stages.

[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.

[kurisuchan-nobureza]

Week 7!!

The last quiz of the midterm

The quiz went as expected, a surprise to some, an expectation-satisfied to others, everyone had their own perspectives on the quiz. The quiz consisted of an enumeration, identification, and an analysis which are different types and problems type off analysis. From Mccabe's cyclomatic complexity formula to System Usability Testing (SUS).

During the quiz, everyone had different strategies in order to answer the questions, many were having difficulties answering and some went smoothly.

In the end, everyone finished the quiz and were discussing the answers, the given quizzes served as preparation for the midterms, after all portions of it were used as questions on the exams.

[earlcagaanansde]

CPE312- Software Design and Engineering

PIT Presentation

This week we tried our hardest to cram, code and test our product EduConnect as it is to be presented in class on thursday. Our professor decided to use the remaining time of our class to showcase our PIT, after he was handing out our exam answer sheets. We were the third group to present our PIT and it went very well; we gave our professor a quick demo of signing up on a new account, showcased some features on the front-end, showed how the code works on the back-end, even tested out the accounts and deleting them in Firebase, and manipulating their data.

Our professor told us our PIT is merely 60% complete, which we didn't believe at first. But nevertheless we were satisfied with the outcome of this presentation. Hopefully by finals we are able to develop and implement our project into its full potential.

October 24, 2024

[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.

[reysamoranos]

Quiz 2 - Part 2 Experience: October 3, 2024

On October 3, 2023, we had part 2 of Quiz 2, as part 1 was held online. This time, I found it a bit more challenging. There were too many thoughts running through my mind during the quiz, which made it difficult to concentrate fully on the questions. Despite trying to stay focused, I struggled to give my best performance. It was a valuable reminder of the importance of mental clarity during exams, and I hope to manage my distractions better in the future.

[jeshuae]

CPE312 - Software Design and Engineering

Class Discussion + Group Activity

September 19, 2024

WEEK 6

ִֶָ𓂃 ࣪˖ ִֶָ🐇་༘࿐

Today, our instructor discussed about Software Testing and Quality Assurance. Although I was a bit sleepy during the lecture, I managed to catch a few important parts of the discussion. We learned about different testing methods like Black Box and White Box Testing, and John Brooke's System Usability System (SUS). Our instructor also discussed Regression Testing, which checks if changes in the software create new problems, and System Testing, which ensures that the whole program works properly before release.

After the lecture, we had our group activity where we analyzed UI (User Interface) problems. Our group included Sean Quincy Manquilimotan and Earl Cagaanan as note-takers, while John Raynier Tejano and I focused on discussing the issues in the UI design. We looked at problems users might face, like unclear layouts or confusing buttons, and tried to come up with ways to improve the overall experience.

We were also given another task involving John Brooke’s System Usability Scale (SUS). This scale helps measure how easy or hard it is to use a system by asking 10 questions. Each question is rated from 1 to 5, and after calculating the responses, we get a score that tells us how good the usability is. A higher score means better usability. To calculate it, you subtract 1 from the odd-numbered questions' answers, subtract the even-numbered questions' answers from 5, and then multiply the total by 2.5 to get a score out of 100.

For this task, Tejano worked on solving the SUS with responses from 3 participants through google forms and google spreadsheets, while I did it manually. We added up all the scores, divided them by 3 (since there were 3 participants), and this gave us the average score, showing how usable the system was overall.

I really enjoyed the activity because we worked as a team and made sure no one was left behind. Everyone’s opinions were welcomed, and we didn’t have any arguments. I hope that when we work on our EduConnect TutorHub software, we can use the same strategy we showed today—doing teamwork and everyone participates.

ִֶָ𓂃 ࣪˖ ִֶָ🐇་༘࿐

[razhelleregoniel]

August 29, 2024 ˖°࿐ •⁀➷

For the third week of Software Design and Engineering, the class was held asynchronously. However, it was also consultation hours, so some of our classmates took the opportunity to consult with Sir Carl regarding their manuscript and the required activity.

Our group, on the other hand, took the time to meet up virtually and discuss about the manuscript and the coding portion of the system, as well as the division of tasks. Because we were indecisive, we used an online picker wheel to decide which member was code which part of the system.

For the rest of the day and the week, we started on learning and coding some parts of our proposed system. That's all for the third week! .ೃ࿐

[marian-claire-bacas]

October 24, 2024 - Software Design and Engineering: PIT Presentation Time

Week 11

On this particular day, we had our performance innovative task presentation for two different subjects. I went to school at 9 AM on this particular day without getting any sleep at all because we still needed to assemble our prototype PIT. It was challenging because, when we installed our circuit inside our warehouse miniature, it wasn't working as it should, so we had some trial and error because of wiring issues, which took up too much of our time, and we still needed to get ready for our SDE system PIT presentation. We presented our SDE PIT at 4 p.m., then continued to work on our LCD PIT, which we presented at 6 p.m. We are relieved that we made it despite the hectic day that kept us up at night and prevented us from eating lunch. I was relieved that both of our presentations went well, so I went home to eat and go to bed early—this was the first time I had ever done so—and woke up at ten in the morning the next day. (Also, we forgot to take a picture after our SDE presentation because it was already at night and we were rushing for our next presentation. So I only had these T_T)

[chedilyn]

WEEK 12

On Week 12, we started the class with a seatwork activity to check our understanding of the provided PDF for our first finals topic. This quick exercise helped us recall key details and prepared us for the discussion that followed. Our instructor then introduced the topic, breaking it down with clear explanations and examples. To wrap up, we participated in a group activity, where we applied the concepts we learned, sparking meaningful discussions and teamwork among classmates.