#CPE3C
Explore tagged Tumblr posts
Text
Week 11: Progress of the Manuscript and Consultation on System Development
by Sittie Janimah A. Disimban
Feedback. Documentation. Details.
This was packed with important milestones as we focused on completing Activity 3 for our Software Design and Engineering course. This activity involved creating a detailed tutorial video that demonstrates how to navigate the user manual and brochure of our developed system. The goal is to provide clear instructions on how users can interact with the system effectively. This is a key component of the user functional and usability testing process, as it allows us to gather feedback from users on the system’s ease of use and functionality. The tutorial video, along with a copy of the user manual, will be shared with our testers to guide them through the process and ensure they can make the most of the system’s features.
youtube
Additionally, this week, we had another consultation session with our instructor. The session was incredibly valuable as we discussed the overall progress of our system development, with a focus on refining the processes involved. We also went over the manuscript paper we’re working on, receiving feedback and suggestions to improve the quality of our work. This consultation allowed us to clarify any questions about Activity 3, and we were able to align our efforts with the expectations of the project.
Through this week’s activities, we gained a deeper understanding of how to effectively present our work to users and testers, ensuring that the system we’ve developed is user-friendly and functional. The consultations and the preparation for testing have set us on the right path for the next phase of the project, and we’re excited to move forward. This week has been essential for solidifying the documentation and preparing for the crucial testing phase, and we’re looking forward to seeing how our users will interact with the system.
2 notes
·
View notes
Text
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.
3 notes
·
View notes
Text
October 17, 2024 - Software Design and Engineering: Asynchronous Class
Week 10
Our major midterm examinations for this week concluded yesterday, but we still have one practical exam left, which is scheduled for October 29. I therefore took a one-day break from my studies for this day because it had been such a demanding and restless week. And I had planned to continue working on our PITs for two major subjects, one of which was SDE. So, yes, I slept and browsed all day because tomorrow and the following few days will be PIT time. I really don't have anything more to say than this because, well, nothing exciting ever happens when I'm at home. (Photo taken yesterday after exam, and it was my first time being on a rooftop in USTP.)
2 notes
·
View notes
Text
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.
ִֶָ𓂃 ࣪˖ ִֶָ🐇་༘࿐
2 notes
·
View notes
Text
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! ✧ ˚ · .
2 notes
·
View notes
Text
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.
0 notes
Text
Week 18!!!
On December 12, 2024, we took Quiz 2 finals for our Software Design and Engineering course, which covered Data Mining and Data Visualization. It proved to be a terrific challenge to test our knowledge as well as our ability to apply everything we had learnt over the term. The first section of the quiz focused on Data Mining, which tested our ability to recognize techniques such as clustering, classification, and association rules and grasp their real-world applications. The difficult concerns encouraged us to think critically about how such algorithms can extract important insights from enormous datasets.
The second component of the test focused on Data Visualization, which involved reading and analyzing data visualizations as well as determining the best approach to present different types of data. This portion taught me that sharing understanding is a critical component in any technical sector.
As I completed the quiz, I realized how Data Mining and Data Visualization interact with one another. Data visualization makes crucial insights more accessible and comprehensible. This connection demonstrated the holistic nature of everything we learnt in this course. As I completed the quiz, I realized how Data Mining and Data Visualization interact with one another. Data visualization makes crucial insights more accessible and comprehensible. This connection demonstrated the holistic nature of everything we learnt in this course.
1 note
·
View note
Text
Week 17!!!
FINAL FINAL PIT PRESENTATION
The week where it is a hit or a miss. Because of the amount of revisions I had to do as well as both my team's effort to fix some codes, it was almost a gamble for us. But despite all that, we strived and managed to finish all the said revisions and proceeded to do some finishing touches.
As we presented our software and manuscript, the hidden nervousness as well as the "laugh it off despite the panicking feeling" we were all on shambles (internally) as the presentation continues. Fortunately, we met Sir's expectations and gave us a small detail revision for us to then be finished with the project.
As we finished the project, we felt lightness as realizations now hit us that we are done and we did succeed in creating a software for our client in accordance with both us and their suggestions. After Sir approved our project, we left with ecstatic emotions as we leave the room.
This was a rollercoaster trip, I am Christian Anton S. Nobleza - Project Manager/Leader together with James Thelo S. Quilang UX/Web Design and Raniel Miro - UI/Graphics Design here we say thank you for the knowledge and the experience.
1 note
·
View note
Text
Week 12
Aight week 12 week twelve! So to give u a bit of context, Sir Carl assigned a short seatwork to check if we had reviewed the course material on Topic 7: APIs. The lesson introduced the basics of APIs, including their definition, significance, functionality, examples, and types, such as public, private, partner, and composite APIs. For instance, they enable apps to integrate with social media platforms, payment gateways, or weather services. Sir Carl also elaborated on how APIs facilitate communication by sending and receiving requests between systems.
Afterwards, we had a group activity where we simulated a patient securely accessing medical records via an API linked to a healthcare provider's electronic health record (EHR) system.
Oh yeah one more thing.. This dude pulled a funny attempt on putting a weird wallpaper on the google chrome and everyone go nuts with it and had a good time hahahahahaha
0 notes
Text
CPE312- Software Design and Engineering
Big Wrap Up
To start off this week was supposed to be our examination week, with all major subjects scheduled, including Software Design and Engineering (SDE). But get this; our professor presented the class with a proposition: any group that achieved 100% completion on their project would be exempted from the exam. Naturally, the entire class immediately dove into their laptops and papers.
But I felt more conflicted about managing my time between revising our project and preparing for other subjects. While I focused on working on our papers, the rest of the team did their own thing. I really thought that we wouldn't make it in time before the exam. Adding to the pressure, the SDE exam was scheduled for Wednesday, leaving us little time to spare.
The day before the exam, we practically did nothing but sit on our asses working on our projects on the 4th floor of the CEA building for the entire day. Hours passed, and the school grew darker and emptier as we waited for our turn to consult with our professor. We were seventh on the list of groups to present. After our turn, the professor gave us feedback, instructing us to work on chapters 4 and 5, the appendix, and the User Manual video.
But the biggest plot twist was when we received a text from our professor on our gc. Do you know what he said?
That’s right, I had dumped all of my textbook knowledge on a whim after hearing this. Just by reading this I felt an entire class of hopeless peeps jumping, screaming, crying, and vomiting of joy as they received this almost in the middle of the night. But this meant that we had to work twice as hard to hit 100% completion. For three days, we juggled project work and other examinations.
On Thursday, after finishing our morning exam, we returned to our project. For what felt like eight straight hours, we revised our papers and prepared for our final consultation. This time, our professor pointed out the remaining gaps.
By 7:00 PM, we finally went back to present our completed work. The presentation went smoothly, and by the end, our professor confirmed we had reached 100% completion. We were one of the few groups to finish early, and it felt incredible to know our hard work paid off.
Looking back, I’m immensely grateful. We made it through the semester as project managers and engineers. Thank you to everyone in CPE-3C who had been a huge help, and special thanks to Sir Carl Angelo Suasola for his guidance. May you continue to inspire other students with your resilience and patience as you pursue your master’s.
December 18-19, 2024
1 note
·
View note
Text
December 12, 2024 ♡
Topic 9: Data Visualization
Today marked the conclusion of our Software Design and Engineering class. We completed a quiz on Topics 8 and 9, focusing on Data Mining and Data Visualization—discovering patterns in data and conveying insights through visuals. Following the quiz, Sir Carl expressed his heartfelt gratitude, and we took a group photo to celebrate the semester. Thank you, Sir Carl, for an inspiring and educational experience!
1 note
·
View note
Text
Week 15: Intense Revision and Final Touches of the System Development
by Sittie Janimah A. Disimban
Reflection. Journey. Apprecation.
After months of dedication and overcoming numerous challenges, today marks a major milestone for our capstone project: the final submission to Engr. Carl Suasola. This journey has truly been a rollercoaster ride—filled with moments of frustration, stress, and moments of triumph. Through it all, our determination and teamwork have carried us to this point.
Every moment was spent revising, debugging, and improving both the app and the accompanying papers. We worked late nights, making sure everything was as flawless as possible, with no detail overlooked. As the days passed, we could see our project evolve into something much more polished, and the sense of accomplishment grew with every fix.
Finally, after days of tireless effort, Engr. Suasola gave his approval for our project. That moment of relief and pride was indescribable—a true reflection of the teamwork, persistence, and dedication we had invested in this capstone project. As we close this chapter, we are eager to take the next step in our academic journey: Technopreneurship in the upcoming semester. We are excited about the future of our project and the opportunity to transform it into something even more impactful. Armed with the lessons, challenges, and successes we’ve experienced so far, we are ready to continue growing and applying what we’ve learned to create something valuable and meaningful. This project not only helped us develop technical skills but also gave us a deeper understanding of what it takes to work as a team, overcome obstacles, and keep pushing forward. We look forward to seeing how our hard work continues to shape our future endeavors. Heartfelt appreciation to my team, John Kenneth Cabibil and Stinnely Dagooc. Thank you for welcoming me into your group. It was a pleasure working the digitzed log book system with you. 🤍
1 note
·
View note
Text
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.
2 notes
·
View notes
Text
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.
2 notes
·
View notes
Text
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.
ִֶָ𓂃 ࣪˖ ִֶָ🐇་༘࿐
#CPE3C#SDE#3rdYear#College#SoftwareDesign#JohnBrooke#SUS#ScalabilityUsageSystem#SoftwareTesting#QualityAssurance
2 notes
·
View notes
Text
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! .ೃ࿐
2 notes
·
View notes