This blog is all about my journey through CS-348 Software Process Management. Throughout the semester, I’ll be sharing my thoughts on what I’m learning, connecting class concepts to real-world examples, and exploring how effective process management can make software development a breeze. I’m excited to use this blog as a chance to practice clear communication … Read more
This blog has been created as part of my work in CS-343: Software Construction, Design, and Architecture at Worcester State University. Over the course of the semester, I will be sharing my reflections, insights, and experiences as I learn more about software engineering practices, design principles, and professional development.
The goal of this blog is not only to document my progress but also to connect what we learn in class to real-world applications in the field of computer science. I look forward to engaging with the wider community through my posts and learning from others in the course.
Stay tuned for upcoming posts on software architecture, design patterns, testing, and professional growth.
This blog dives into CS-343, exploring how to design, build, and maintain software that actually works in the real world. I’ll examine key software design principles, architectural patterns, and construction techniques that ensure programs are reliable, efficient, and maintainable. Along the way, I’ll analyze practical approaches to solving common challenges in software development, including debugging, testing, and refactoring, while exploring tools and technologies that support modern software construction.
Join me as I explore the art and science of turning ideas into usable programs. Through this blog, I’ll share insights on best practices, real-world applications, and strategies for creating software that meets both technical requirements and user needs. I’ll document my learning journey, reflect on lessons from hands-on projects, and track my growth as a Computer Science student as I deepen my understanding of software design, architecture, and engineering.
This is my first blog post for CS343 for section two! I am excited to learn software construction techniques, design, and how to maintain a software. Hope to have a great class!
In the Computer Science track at Worcester State, and as a prerequisite to this course, students have to take a Database Design course that teaches SQL. Because of this, before this course, when databases were mentioned, it typically invoked thoughts and memories of SQL queries and database management using the SQL language. However now, the project being made works with the use of MongoDB, a NoSQL database management system. This made me curious about the differences between managing databases with and without SQL and when it is smarter to use each.
I watched a video called, “Which is Better? SQL vs NoSQL”. The key point I took away is that SQL is a relational database whereas NoSQL, such as MongoDB, is a document database. The key differences being that relational databases store information in tables with keys whereas document databases store information in documents with JSON data. One main benefit of a document database such as MongoDB is that it is much easier to store unstructured data. This adds flexibility at the expense of being able to use simple commands such as JOIN which can be used in SQL.
Another core advantage of NoSQL databases is that they can handle having multiple people connected to them at the same time. SQL databases on the other hand do not manage this well. This fact gave a lot of clarity as to the usefulness of using MongoDB over something like MySQL for the purposes of Thea’s Pantry.
The video also mentions that NoSQL databases are better at scaling across different servers which can be useful if we need to write information across multiple platforms and in many places.
Overall, from what I understand, SQL tends to be stronger for performing more in depth and informative queries on a set of data, at the expense of requiring the data to be organized and consistently formatted. NoSQL, on the other hand, does not have the inherent ability for users to submit queries on the data but it allows for lack of format and consistency and that leniency provides more flexibility for data storage.
The ultimate conclusion was that both SQL and NoSQL databases are powerful in the hands of the right user. While they each have their strengths and weaknesses, they are similar enough to allow users to perform most of the same tasks on either one and that allows developers the freedom to choose the database that they are more comfortable using for the purposes of any project.
Hello everyone, my name is Sean Wang and this will be my blog for CS-343 this semester! I’m very excited to learn more in this course, and I will be sharing it through my blog! I hope everyone has a great semester!
Hi everyone this blog is going to be where I post my finding and developments in my career in computer science with a focus on cybersecurity as that’s the niche that I’m most interested in. This blog will cover everything to exploited vulnerabilities to threat actor trends in the industry. My experience is that I have a Security plus certification and a active cybersecurity engineering internship at barracuda networks where I have contributed to creating and updating detection rules and methods.
This is my blog, A Bostonians Blog. I couldn’t think of a better name than this but this blog is my personal space to share insights, experiences, and discoveries as I progress through my coursework, particularly focusing on Computer science at Worcester State University.
