Week 6

 Part 1: Help Your Teammates to Develop Capstone Ideas

1. It would be fun to use a Raspberry Pi to read inputs from sensors in a parking garage and have an 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 a very good application to have in a big city to help find parking places.

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

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

4. Smart Waste Management System: Develop an IoT-based system to monitor urban waste levels and optimize collection routes, reducing overflow and improving efficiency.

5. Augmented Reality Navigation for Visually Impaired: Create AR-based navigation for the visually impaired, offering real-time audio and tactile feedback to guide them through urban environments.

6. Biometric Vehicle Authentication: Introduce biometric authentication in vehicles using fingerprint or iris scanners to enhance security and personalize settings for different drivers.

7. A smart recipe recommender which recommends recipes base on ingredients at home.

8. A language learning application

I really think the app that lets homeowners place project up for bidding would be a fun and exciting to make.



Part 2: Keep Up With Your Learning Journal

This week we looked at how to write a resume. It was helpful information that I will apply to my future resumes. A resume needs to be short, about one page, since job recruiters do not have time to read lengthy resumes.  In addition, a resume needs to be formatted nicely and easy to look at, meaning 12 size font and the organization of the information should flow logically. Finally, a resume should be mistake free and with relevant information to the job that is being applied to. We also looked at cover letters, though I had never used one, I would be using one now in the future applications. I learned that a cover letter gives you an opportunity to introduce yourself and explain more about yourself to a potential employer. 

We also learned about handling conflicts within a team. How to use active listening skills to make someone heard when they are having an issue. It's important to not escalate a conflict but at the same time there is a limit when some is being excessively argumentative or really causing an issue. At that point express what that person is making us feel and pointing out what they are doing objectively. Well, asserting what we feel to come up with a solution. I also refreshed myself on Java programing. It would be nice to start writing programs again. 

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