chariebelssss

[chariebelssss]

Weeks 10 & 11: A Rollercoaster of Growth and Achievement

Week 10 was all about exams! 📚 We pushed ourselves to the limit, revisiting everything we’ve learned so far in Software Design and Engineering. It wasn’t easy, but the thrill of overcoming challenges fueled us to give our best. Exams are always a test of not just knowledge but also perseverance, and we’re proud to have faced them head-on!

Week 11 marked an exciting shift as we focused on preparing for our PIT System Citizenshield Net Project. This project was a true test of our collaboration and technical skills. We worked tirelessly to ensure our system was functional, secure, and user-friendly. The hard work paid off, as we achieved 85 for the Frontend and an impressive 90 for the Backend! 🎉

This journey has been both challenging and rewarding. Every step, from brainstorming to implementation, reminded us of the art and science behind software engineering. Here’s to more milestones and continuous improvement as we grow together as a team and future engineers! 💻🚀"

#SDE

[chariebelssss]

Week 17 | 121724

Week 17 was filled with productive consultations and final preparations for our PIT (Project Implementation and Testing) presentation. During this time, we worked on making minor revisions to our system, particularly for the admin panel, which included improvements like filtering concerns, updating the user manual video, refining test cases, and finalizing Chapters 4 and 5 of our project.

The biggest surprise came when Sir Carl exempted all of us from the exam, a thoughtful gesture that relieved a lot of pressure. He even gave us an opportunity to meet today, December 21, 2024, to finalize everything. However, we encountered a minor setback—the door was closed, and we couldn’t meet as planned.

But, the good news is we will be back on January 3, 2025. This unexpected break gives us more time to revise our papers and correct any errors, so it’s not a big issue. We are grateful for Sir Carl's understanding and the chance to perfect our work before the final submission.

Overall, we’re thankful for Sir Carl’s support and patience throughout this semester. We look forward to seeing him again in the new year and finishing the course on a high note!

[chariebelssss]

Week 16 | 121224

Week 16 marked the end of our journey in Software Design and Engineering. We took Quiz 2, our last assessment for the course, wrapping up all the concepts we’ve learned over the semester. It was bittersweet, knowing it was our last meeting with Sir Carl, who left a significant impact on all of us.

After the quiz, Sir Carl shared a heartfelt message, encouraging us to continue striving for excellence and reminding us of the value of perseverance and teamwork. He even surprised us with bonuses, which made everyone cheer with gratitude. His generosity and kindness truly made the class feel special.

To commemorate the moment, we had a picture-taking session filled with smiles and laughter, capturing the bonds we’ve built over the past weeks. It was the perfect way to end a memorable semester, leaving us with lessons and memories we’ll carry forward in our academic journey.

[chariebelssss]

Week 14 & 15 | 120524

Week 14 brought us a much-needed pause with Wellness Week spanning three days. This break was an opportunity to recharge and reflect amidst the hustle of academic life. It highlighted the importance of prioritizing mental and physical health, a reminder that self-care is as crucial as academic achievement. Wellness activities encouraged relaxation and mindfulness, helping us return to our studies with renewed energy and focus.

After the rejuvenation of Wellness Week, Week 15 brought us into the intricate world of data mining. We discussed its origins, how incomplete data arises, and the role of data cleaning in ensuring meaningful analysis. Common causes of incomplete data include missing entries, human error, and system limitations, which can skew insights if not addressed.

Origins of Data Mining: Tracing its roots from statistics, artificial intelligence, and database systems.

Data Cleaning: Techniques to identify and fix errors, remove duplicates, and fill gaps for cleaner datasets.

Applications: The ability to uncover hidden patterns and predict outcomes using vast amounts of data.

We explored how Target Corporation uses data mining to understand customer behavior and tailor their services. By analyzing purchase patterns and preferences, they anticipate customer needs, recommend products, and even predict life events like pregnancies. This activity demonstrated the real-world implications of data mining, from business optimization to enhancing customer experiences.

Week 15 emphasized how data mining transforms raw information into actionable insights, a skill that’s becoming increasingly essential in the data-driven world.

[chariebelssss]

Week 13 | 112124

This week, we delved into the critical role of APIs and their connection to software reliability. APIs, or Application Programming Interfaces, are the bridges that allow different software systems to communicate. Ensuring reliability in APIs means guaranteeing seamless, secure, and consistent data exchange, especially in sensitive systems like healthcare.

Our seatwork revolved around understanding API structure, functionality, and how proper implementation impacts overall system reliability. This included studying error handling, response times, and adherence to standards like REST.

For our activity, we simulated secure patient API access. This involved designing a system to allow patients to retrieve their medical records without compromising privacy or data integrity. We applied authentication protocols, encrypted connections, and role-based access to maintain security.

These lessons reinforced the importance of secure and reliable APIs in building trust and ensuring efficiency in software systems.

[chariebelssss]

Week 12 | 111424

Week 12 of our academic journey brought a deep dive into the essential principles of 5S, software quality management, and their application in a real-world case study: HealthTrack, a Medical Records Management System. This activity emphasized how structured approaches can elevate the reliability and performance of software, especially in critical sectors like healthcare.

Originating from lean manufacturing, 5S is a workplace organization method focusing on efficiency, productivity, and safety. Here’s a brief recap of its components:

1. Sort (Seiri): Remove unnecessary items.

2. Set in Order (Seiton): Organize tools and materials for easy access.

3. Shine (Seiso): Maintain cleanliness to prevent clutter.

4. Standardize (Seiketsu): Establish consistent practices.

5. Sustain (Shitsuke): Ensure long-term adherence to these practices.

When applied to software development, 5S ensures that processes are clear, resources are optimized, and teams work in harmony.

Software quality management (SQM) plays a pivotal role in the lifecycle of any system. It encompasses three main components:

1. Quality Planning: Defining quality standards and benchmarks.

2. Quality Assurance (QA): Ensuring processes are followed to achieve these standards.

3. Quality Control (QC): Testing and validation to ensure the product meets user expectations.

In the case of HealthTrack, SQM principles ensured the software was not only functional but also reliable, secure, and user-friendly.

The case study revolved around HealthTrack, a system designed to manage medical records efficiently and securely. This is particularly crucial in healthcare, where errors or inefficiencies can have life-altering consequences.

This week’s activity underscored the importance of combining structured methodologies like 5S with rigorous software quality management practices. In the context of HealthTrack, these approaches ensured that the system was not only functional but also reliable and secure—a non-negotiable in the medical field.

Implemented robust QA processes, including automated and manual testing.

Focused on compliance with healthcare data regulations like HIPAA.

Integrated user feedback loops to ensure continuous improvement.

#CPE #SDE

[chariebelssss]

Week 9: PIT Consultation and Major Progress on Our System

October 24 yesterday, was a big week for us! We had our consultation for the Project-in-Progress (PIT), where our system needed to be at least 70% complete. Going into the consultation, our system was around 50% done, so we knew we had some catching up to do. But with focus and teamwork, we’ve made major strides and are now much closer to our goal.

After implementing changes and pushing our project forward, we returned today for our follow-up consultation. We’re thrilled to report that our system is now 90% complete on the front end and 85% complete on the back end! Engr. Carl was very supportive, acknowledging our progress and providing final pointers to help polish and refine our system further. His feedback was invaluable, and knowing that our hard work is recognized has motivated us even more.

Since the consultation, we’ve managed to push our project even further. Now, our system is 90 score on the front end and 85% score on the back end. This is a huge leap from where we started this week, and it’s all thanks to the team's hard work and the encouraging feedback we received. Seeing our system come together is incredibly motivating, and knowing that Engr. Carl appreciates our efforts keeps us driven.

Today’s consultation was a great reminder of how crucial feedback, teamwork, and determination are in achieving our goals. With Engr. Carl’s encouragement and our commitment to making steady progress, we’re excited to push through to full completion. We’re confident that, with a few final adjustments, our system will be ready to deliver the functionality and experience we envisioned.

Thanks to Engr. Carl’s guidance and the team’s dedication, we’re closer than ever to the finish line—and ready to tackle these final steps with enthusiasm!

[chariebelssss]

Week 8: Diving into Testing and Understanding SUS Scores

Last October 3, 2024 marked an important milestone in our journey—we tackled Quiz 2, which centered on the concepts of testing and usability assessment through the SUS (System Usability Scale) score.

The quiz gave us an opportunity to test our understanding of core testing methodologies, usability principles, and how we assess systems effectively. It was a chance to apply what we've learned so far, reinforcing our knowledge of best practices in creating and evaluating user-friendly, functional systems.

Quiz 2 highlighted areas we’re strong in and areas where we can grow, especially in mastering SUS interpretations and various testing methodologies. Moving forward, we’re ready to use these skills to build and refine systems that are not only functional but also enjoyable for users. Let’s keep pushing forward with our learning, building on these foundations, and sharing insights with each other as we continue our journey.

[chariebelssss]

Week 7: Asynchronous Learning: Continuing the Momentum

While we're taking a brief pause for the CEA General Assembly, let's keep the momentum of our learning going! This means we can work at our own pace, but we encourage each other to stay engaged and on track.

To make the most of those time, we use it as an opportunity to reflect on what we've learned so far and reinforce those skills that we’re still working on. Each of us set an individual goals—whether it’s reviewing past materials, experimenting with new techniques, or even diving into topics that spark our curiosity but may not be part of the official curriculum. Those flexible period is also a perfect time for peer learning and collaboration, as we can share insights, offer support, and build on each other’s strengths.

Together, we keep each other motivated by sharing our small victories, discussing challenges openly, and helping one another find solutions. Reflecting on our progress and celebrating each milestone, no matter how small, will keep us focused and motivated.

#CPE #SDE

[chariebelssss]

Week 6: Diving Deeper into Software Testing, and SUS Score

Last August 21, 2024 we delve into the world of software design and testing. We explore how collaboration can help identify errors and calculate the System Usability Scale (SUS) average.

I learned that Black Box Testing focuses on external behavior, doesn't require knowledge of internal code, and often used for functional testing. White Box Testing focuses on internal structure, requires knowledge of programming languages, often used for unit testing and code coverage analysis.

I also learned that effective teamwork is important in identifying errors during the software development process. By combining diverse perspectives and expertise, teams can uncover issues that might be overlooked by individuals working alone.

Lastly, the System Usability Scale (SUS) is a widely used questionnaire to measure the perceived ease of use and usefulness of a product or system. Calculating the SUS average involves collecting data from multiple users and analyzing the results.

#CPE #SDE

[chariebelssss]

WEEK 5: Shaken Not Stirred: A Week of Quizzes and Earthquakes

091224

On September 12, 2024, was quite the rollercoaster! We had our Part 2 quiz, which was already challenging enough, but then an earthquake drill threw a wrench in our plans. Talk about a unique test-taking experience!

The multiple-choice questions were definitely intriguing. They required careful analysis and understanding of the concepts we'd covered. The identification questions were even more challenging, as we had to not only identify the terms but also provide detailed explanations.

While the earthquake drill was a bit unexpected, it was a good reminder of the importance of preparedness. It also added an interesting element of stress to our quiz-taking experience.

The essay and diagram portion of the quiz was the most challenging. It required us to think creatively and come up with innovative solutions. It was a great opportunity to apply our knowledge and demonstrate our understanding of the concepts.

Week 5 was a memorable one, filled with both challenges and opportunities for growth. The earthquake drill added an unexpected element of excitement to our quiz-taking experience, and the quiz itself was a great test of our understanding of the material. I'm looking forward to seeing what the rest of the semester has in store.

#CPE #SDE

[chariebelssss]

WEEK 4: A Week of Software Design and System Implementation

090524

Last September 5, 2024 was a tornado of software design concepts. From exploring the fundamentals to diving into specific patterns and system implementation, we've covered a lot of ground. We explored the different levels of software design, from architectural design to detailed design. Understanding these levels helps us break down complex systems into manageable components. We discussed various design patterns, such as Singleton, Factory, and Observer. These patterns provide reusable solutions to common design problems, helping us write more efficient and maintainable code.

Engr. Carl's scenario was a real test of our problem-solving skills. We had to suggest a suitable patterns to handle reservations, scheduling, and customer notifications, and to develop a design of the system. It was a challenging task considering the lack of power, but it also forced us to think creatively and come up with innovative solutions.

Working together on the scenario was a great opportunity to learn from each other and collaborate effectively.

#CPE #SDE

[chariebelssss]

082924 | CPE312 Software Design and Engineering | 12:00 - 3:00 PM

WEEK 3

On August 29, 2024, we present our initial progress of our CitizenShield Net Project to Engr. Carl. My team had been diligently working on the front-end design, focusing on important components of login, sign up, and the homepage. The anticipation was palpable as we prepared to showcase our efforts and seek valuable guidance from our mentor.

The consultation with Engr. Carl provided us with invaluable insights and feedback. While we were pleased with the progress we had made, it became evident that there were areas where our project could be enhanced. The suggestions offered by Engr. Carl were instrumental in identifying potential areas for improvement and ensuring that our project aligns with the highest standards of quality and functionality.

Looking ahead, our team is eager to apply the lessons learned from last week's consultation to our ongoing development efforts. We are confident that by incorporating the feedback and continuing to work collaboratively, we will be able to deliver a project that not only meets but exceeds our initial expectations.

#SDE #CPE

[chariebelssss]

082224 | CPE312 Software Design and Engineering | 12:00 - 3:00 PM

WEEK 2: Diving Deeper into Software Design and Engineering

Earlier, we really got into the the bottom line of what engineering is all about. One of the key takeaways was understanding that software engineering is both an art and a science which is a beautiful blend that requires creativity and logic.

We look into the emergence of software engineering and the evolution of techniques over time. It was fascinating to see how outdated programmers used the "build and fix" method, and how those early techniques have evolved into the highly developed processes we use today. We also dig into the Software Development Life Cycle (SDLC) and the waterfall model, laying a solid foundation for what's to come.

The highlight of today's session was a 30 minutes case study challenge Engr. Carl gave us. We got the "Galaxy Mining Company LTD" and we need to analyze the company's background, objectives of the system, services offered by the system, challenges faced, software engineering principles applied and the conclusion. We had just 30 minutes to analyze the case, to prepare a PPT, and 5 minutes to report it. It was intense but incredibly fun!

Overall, the discussions were interactive and full of energy. We all laughed, shared some sweet smiles, and truly enjoyed the collaborative spirit of the class.

As we continue this journey, I’m reminded of a quote: "Alone we can do so little; together we can do so much." by Helen Keller. It's teamwork that makes the dream work, and today proved that we’re all in this together!

#CPE #SDE

[chariebelssss]

081524 | CPE312 Software Design and Engineering | 12:00 - 3:00 PM

WEEK 1: A Fun Start to Software Design and Engineering Journey!

On August 15, 2024 we had our first class and it was such an interactive first class. The session kicked off with everyone introducing themselves and how interactive the orientation was. Instead of just going over the syllabus, our instructor made sure we were all engaged and having fun. I'm looking forward to dive deeper into the word of software design and engineering.

Stay tuned as I share more about our projects, learnings, and everything else along the way!

#CPE #SDE