Week 5:

 

 Part One: Set Your Educational Goals





 

Part Two: Possible Capstone Ideas (30 minutes)

After viewing at least 3 presentations of Capstone, list three possible capstone projects you might choose to do at the end of your study. These sample project ideas which you may or may not pursue.

 It would be fun to use a Raspberry Pi to read inputs from sensors in a parking garage and have app let you know available spaces for parking.  Each parking space would have a sensor to see if a parking space has been taken and it would rely on that information back to a database.  A user could log into the account, and it would display the availability of parking space. It would be very good application to have in a big city to help find parking places.

A home improvement application, that lets homeowners upload large projects and have license contractors bid on the project. If the project is small like a hole in a drywall also allow handymen to apply for small projects. It would be a win-win for home homeowners to allow for price shopping and for contractors to find work. There can be reviews left on the project completed by the contractors and contractors can leave feedback on the homeowner.  

A pet water bowl, that refill itself automatically and has an app that lets you know when the main water tank is nearly empty.

 

 

Part Three: Keep Up With Your Learning Journal (30 minutes)

This week I learned what to expect for the capstone project. I looked at some of the project video presentations the past students had done, and it seems overwhelming. I hope to do as good as a job on my capstone project when the time comes. We also looked at logical fallacies and loaded words. We are constantly bombarded with those things daily. This week I got to be the team leader and I enjoyed it. My team takes turns every week as team leader. We discussed choosing three topics by this Sunday.

Comments

Post a Comment

Popular posts from this blog

CST438 Software Engineering: Week 8 (Final week)

 One of the most important things I learned is that software engineering is about much more than just writing code. While coding is a big part, there's a strong emphasis on documentation, understanding client needs, and getting continuous feedback. It’s about designing systems so others can easily improve them and applying principles like "low coupling and high cohesion" to keep things modular and maintainable.      Another key lesson was understanding the entire development process from end to end. This was the first time I worked with both the front end and back end together, fully grasping the HTTP protocol (including how methods like POST work), how JSON is used, and how the front end communicates with the back end. Seeing how everything fits from database interactions to deploying the app online—gave me a fascinating glimpse into the full workflow and a lot of practical experience.      Another important lesson was learning how to work as part of ...
Read more

CST438 Software Engineering: Week 1

What did you expect a course in Software Engineering would cover? I expected it to cover how to build applications from the ground up and the design behind application development. I thought we would look at other things we’ve been learning in this program, like database management, front end development, and back end work, and then put it all together into one complete project. After completing week 1, how has your opinion changed? Well, I never really thought much about keeping an application’s design maintainable for future improvements or changes. There is a lot more that goes into software engineering than just simple programming. It is  about planning ahead, documenting your work, checking for errors, and testing properly to avoid issues later. I’ve also realized software engineering looks at the big picture it is not just about coding and design but about how software impacts people and how teams work together to build it. Developers need to stay motivated, think critical...
Read more

CST370 Week 5

Hello everyone,  This week we studied binary‑tree traversals preorder, inorder, and postorder but I kept mixing them up. I finally got it when I attended TA office hours, and it clicked. Walking through Quick Sort step by step helped me see how the Decrease and Conquer approach works by breaking problems into smaller chunks. Then we looked at Kahn’s algorithm, and watching it remove nodes with no incoming edges reminded me of picking a pivot in Quick Sort. Seeing these patterns repeat helped me realize that many algorithms work by simplifying things piece by piece. 
Read more