#ScalabilityUsageSystem

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

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