#3rdyear

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

Today was the big day—our final presentation for EduConnect TutorHub. Sir Carl told us that if we met 100% of the requirements, we’d get a perfect score, which motivated us to stay up all night finishing both the app and the paperwork. Early this morning, we gathered at the 4th floor of the CEA building to revise and finalize everything. When it was our turn, our leader introduced the app and its functionality, while I presented the documentation. After the presentation, Sir Carl pointed out some needed revisions, so we planned to fix everything and return the next day.

Later that night, Sir Carl messaged our group chat and announced that we were exempted from the finals exam as long as we submitted all requirements within the week. We were so happy—thank you, Sir Carl!

The next day, we worked hard to complete everything. Our leader prepared screenshots for white-box and black-box testing, another teammate edited the user manual brochure and tutorial video, and I updated Chapter 4 to show the app’s 100% success rate. In Chapter 5, we concluded that the app is fully functional and ready for deployment, with recommendations for future improvements. We also tested its performance on multiple devices, showing that it worked smoothly without errors.

For the System Usability Scale (SUS), Sir Carl asked us to survey more respondents to ensure accurate results. We immediately conducted surveys with classmates and managed to get a 90+ SUS score, earning an A+ rating with the best imaginable ranking. After all the revisions and the final presentation, Sir Carl gave us a perfect 100%. We were relieved and proud to have completed everything on time and secured exam exemption.

This project had its challenges—stressful moments, arguments, and sleepless nights—but we pulled through as a team. I’m grateful to Sir Carl for his guidance, which helped turn our ideas into reality. This feels like a huge milestone for me as a 3rd-year Computer Engineering student. With that, we, the team of EduConnect TutorHub, are signing off. Good night!

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

Today was our last day of 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 Data Visualization. Data Mining involves finding useful patterns and insights hidden in large amounts of data, while Data Visualization helps us present these findings in simple, clear pictures or charts that are easy to understand. After the quiz, we took a group photo with Sir Carl as a keepsake of our time together. Thank you, Sir Carl, for guiding us through these lessons!

For our application, Edu Connect Tutor, we asked Sir Carl about improving our user manual. He showed us how to fit it into a brochure layout and make it simpler, so it will be perfect when we create our video guide. We also talked about the functional testing forms, which help check if our app meets all the requirements and works as intended. Our team leader discussed some problems with our backend, and Sir Carl suggested methods to fix errors and improve the system’s performance. Overall, we are almost finished with our project and hope to have it completely ready soon.

Until our next journey!

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

Today, Sir Carl started our class with a quiz that covered some of the key topics we’ve tackled in the past few weeks, like software reliability, quality management, ISO standards, and API basics. These topics helped us understand how to make software better and more reliable. After the quiz, he gave a short discussion about data mining, explaining how companies use data to understand their customers, predict what they might want, and improve their services. It’s fascinating to see how data plays such a big role in business decisions. We then had a 10-item seatwork to test what we learned, and afterward, we worked in groups on the Target Market Activity. This activity focused on using data mining techniques to come up with strategies for understanding and targeting customers in a business setting.

This will be our last class before the finals, which are just around the corner. I really hope I can do well on the exams and that the questions will be clear and based on the lessons we’ve covered. I also want to thank Sir Carl for being so understanding, especially with our late submissions and system issues.

On a side note, we’ve made a lot of updates to our EduConnect system. We added a "Log Out" button using a three-line menu for quick access. The "Create Subject" feature is now a pop-up instead of a separate file, making it more user-friendly. In the tutee’s class stream, we added a "Messages" button so they can easily contact their tutors, likely through Messenger. We also cleaned up the profile section by removing unnecessary features like the bio, which frees up more space for the subject cards. Lastly, for the payment system, we added a feature where users can click on a subject to view payment details in a pop-up. There’s still a lot to improve, but we’re getting closer to creating something we can be proud of.

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

Today, Sir Carl gave us a short seatwork to check if we had read the course material on Topic 7: API. The topic covered the basics of APIs, including what they are, why they are important, how they work, examples of APIs, and the different types, such as public, private, partner, and composite APIs. APIs are like bridges that allow different software to share data and functions. For example, they enable apps to connect to social media, payment systems, or weather services. Sir Carl explained how APIs work, focusing on their role in sending and receiving requests between systems.

After the discussion, we had a group activity where we simulated how a patient could securely access medical records through an API connected to a healthcare provider's electronic health record (EHR) system. Our task was to identify API endpoints, define HTTP methods, specify parameters and headers, and address security measures to ensure only the right data was retrieved. We also created a sequential diagram of the process and discussed challenges like preventing unauthorized access and designing a secure system. Once we submitted the activity, our class was dismissed early.

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

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

Last week, we had a class discussion and a short pre-test with Sir Carl about Topic 6: Software Reliability and Quality Management. This topic focuses on ensuring that software is dependable, works as expected, and meets high standards of quality. Software reliability refers to the ability of the software to function correctly over time without errors or failures, even under different conditions. On the other hand, quality management involves planning, monitoring, and improving the development process to ensure that the final product meets user needs and expectations. This includes activities such as testing, debugging, and following industry standards. We also had an activity related to the topic, where we were given case studies to analyze. Our task was to identify issues in the software's quality and suggest improvements to enhance its reliability and performance, helping us apply what we learned in real-world scenarios.

And for the update this week, I fixed some minor issues in the application because Expo Go was updated, which caused some UI design errors. I'm still confused about how to move the payment button to the payment section. Two days ago, I planned to code, but there was no internet in our area, and I still have many UI designs to finish. Today, I’m working faster so we can start focusing on our activities.

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

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

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.

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

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

Last week, we had our midterm exams and reviewed topics for subjects. After finishing exams in minor subjects, I used some time to make quick updates to our system's code.

With only a short time left to study for major subjects, I focused on the layout. I adjusted the borders and added some icons to improve the layout and added small and useful features for better and easy access for the app.

(This is just my small update in the system.)

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