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

[razhelleregoniel]

August 15, 2024 ˖°࿐ •⁀➷

After weeks of bed-rotting and scrolling past hundreds of Tiktok videos over the summer, it's officially academic season once again! Or at least for us, Computer Engineering students.

For the first day of Software Design and Engineering class, headed by our dearest instructor, Engr. Carl Angelo Suasola, we had a brief introduction to each other, including our favorite song (mine was: how deep? by Tai Verdes). Besides that, we were also introduced to the course syllabus & content, course requirements, and a quick recap to the grading system.

In summary, it was a chill and fun first day of the course. I got introduced to new people and what to expect on SDE, and got to meet my friends again after the summer break.

Here's to hoping for a fun and promising semester!

*ੈ✩‧₊˚

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

On August 19, 2024, we didn’t conduct regular classes. Instead, the time was set aside for project consultations. However, we were unable to meet with our instructor that day, so we managed to consult on September 20, 2024. During the consultation, our instructor reviewed our choice of hardware and software tools, advising us on the best options to ensure compatibility and functionality. He suggested some revisions to our initial plans, which helped clarify our approach

[ldebs]

Week 5!!!!

September 19, 2024. Today, our professor asks us if we ever advance study about the pdf he sent to us. He told us to have advance reading about it. When he asked us. I was nervous cause i didn't read it. So, I kept quiet about it. Until our professor asks us who didn't read it and I was embarrassed but I raised my hand. And so we started our discussion. It was easy to understand since our professor was not relying by the ppt. I learned about test cases, test script, testability. Although i got prior knowledge about those, it was still a nice review. And he tackled about verification and validation. which is very easy to absorb since he was using real life scenario. Basically verification is a step by step process and validation is how you see it as a whole. He also tackled about the testing activites, debugging and etc. After discussing everything, we did our group activities. It was fun. To find, where the problems of the given scenarion and stuffs. It was quite challenging but i had fun today.

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

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

[kurisuchan-nobureza]

Week 5 of the SDE class!

During this time, the students are partaking their 2nd part on the first quiz. The quiz began on an identification test and followed by an analysis in which the students are given a situation where they are needed to connect specific aspects of the given analysis and create a new function to the given function.

Most of the students were able to answer several questions yet some had a hard time answering as well (including me). During the quiz, we encountered an earthquake drill which paused the quiz-taking and had to "evacuate". Afterwards, the quiz then began after the drill.

[earlcagaanansde]

CPE312- Software Design and Engineering

Day 2: First Topic Class

Now we actually have started our first lesson in Software Design and Engineering, which is about the introduction to software engineering.

Frankly speaking, this was going to be my first career choice before I even went to Senior High. But researched about this and I found out they don't offer this particular major here, atleast in Mindanao.

Bummer.

Anyways the discussion went pretty well. But the thing that took my interest my most was the subtopic about different Software Development Tools. Mainly because I know some of us had already tried alot of these before in our previous subjects. I am really interested in programming, then my eyes lit up a bit as I was writing this because I realized I hadn't have much time to experiment on my own. I would say that my skill in coding became stagnant.

After the discussion we also had a group activity with my classmates. We were tasked to review and analyze our chosen paper; ours was about a wilderness weather station. It was really hard to to this under an hour as we needed to create our presentation on Canvas. We split up the work and I was the one who tried to find the Software engineering principles applied in that paper. An hour later, we presented our amateur at best, half-baked presentation with only a single representative to report. I would say ours went very well even there were missing panels in that Canvas project.

We were also tasked by our instructor to record our progress through another software. For our group, we used Trello as our software. I'm still still getting the hang of it. Hopefully I could master all the different software required for our project since I'm left with a challenging task as a back-end developer

August 22, 2024

[sittiejanimahdisimban]

Week 4: First Consultation with Digitized System

by Sittie Janimah A. Disimban

Start-Up. Consultation. Progress.

After a week of starting the process, adjusting to getting to know each other, and showing commitment to contributing toward the success of our system, we finally had the courage to set up a consultation with our professor. During this meeting, several crucial topics were discussed, including our strengths and weaknesses. Our professor focused on the main objectives of our system, ensuring that the start-up could proceed with testing in our next meeting.

Digitized Log Book Mobile Application.

The purpose of this project is to develop a user-friendly tool for small-scale market store owners to efficiently record sales data, manage inventory, analyze customer behavior, and enhance data security. The application offers functionalities including easy data entry, inventory management, reporting, analytics, data security, and offline functionality. By providing these features, the Digitized Log Book aims to improve operational efficiency, provide valuable insights, and contribute to the success of small-scale market stores.

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

[maryannremolado]

Long Week No See!

09.05.24. During our third face-to-face session in SDE, Engr. Suasola discussed software design, covering its patterns, principles, methodologies, and implementation. I learned valuable techniques that we can apply to our system project, and it was exciting to see how creative and problem-solving the role of a software designer can be. At the end of the lecture, we were grouped into four teams and given a task, but some groups, including mine, didn’t complete it successfully. Despite that, I appreciated learning how important it is to be flexible, think critically, and collaborate as a software designer or computer engineer.

[reysamoranos]

System Design: Week 4 – Stepping Up!

During our Software Design class on September 5, 2024, Engr. Suasola emphasized implementation strategies as one of the topics he discussed. As our group prepares to build upon the functional system from the system prototype we created last semester, these strategies will be crucial for ensuring a successful outcome. By adopting coding standards and modularization techniques, we can enhance code consistency, readability, and maintainability. Coding standards will guide our team in writing code that adheres to best practices, making collaboration easier and reducing errors. Modularization will allow us to break down our system into smaller, self-contained components, improving scalability, testability, and reusability.

After the discussion, we participated in a group activity where we were tasked with describing the primary features and components of an e-learning platform, selecting appropriate design patterns, and drafting initial pseudocode and design. Although we faced challenges in completing the task within the limited time, the experience taught me the value of teamwork and working efficiently under pressure.

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

September 12, 2024 - Software Design and Engineering: Quiz Part II

Week 5

For this day, I went to school with no sleep at all because I focused on reviewing for the DDC quiz and didn't realize it was already morning, and I have no time to prepare for school if I go to sleep because our first subject quiz begins at 7 AM. Then, following our first subject, we had an online CPE311 class, and then we had to do a group task. After that, we made our way downstairs for lunch. Afterwards, I took the time to catch up on some sleep before our next class, SDE, which started at 1 PM instead of 12 NN. And shortly as our SDE class began, the instructor announced that we would be having our quiz part 2 that day. Since I was unaware of this and could not review our lessons in advance, I did so poorly on the quiz. I was really disappointed in myself that day. On top of that, there was also a little earthquake drill during class, which required us to go downstairs from the seventh floor and then use the stairs to go back up. STAIRS. 7TH FLOOR. I know. It was the worst. I slept for barely an hour that day, and I had to go up to the seventh floor. Anyway, we finished our quiz, and I went right home, flooded with self-reproach.

[chedilyn]

Week 6

On September 19, 2024, our instructor gave a discussion, and afterward, we had a group activity. Our teacher shared their screen, showing a GUI design with various symbols and elements, and our task was to identify any inconsistencies in the design. It became interesting as we had to carefully observe the layout, spot the misplaced or missing symbols, and then redraw the corrected version. Each group worked together, discussing how to improve the design, making sure everything aligned properly.

[ldebs]

Week 4!!!!

September 12, 2024. Our professor was quiet. It was because he's still mad at us. Since last meeting, he was mad at us. So, we started our quiz. Before that we took the part 1 quiz online. When the day's come to our face to face. We were confuse and startled because there might be a continuation to our quiz since it says part 1. But since our professor didn't announce anything, I didn't study. When our professor said we will start the quiz. I was nervous cause I barely remember what's the last topic is. So, as the quiz goes on, I answered only a few of them. mostly my paper was blank. and after the quiz, we joked around. It was a good thing since it was the first step that will help us all to be in good terms. Lesson learned: dili awayon si sir.