Project Analysis

In the NumQuest project, I did well in creating the main parts of the game, especially the feedback system for user guesses. I made sure the game correctly marked digits as green, yellow, or grey based on the guess. This was important for players to understand how close they were to the correct answer. My strength in using inheritance and exceptions to handle errors and generate the secret number also helped the project succeed. I approached the project in a logical and organized way, which kept me on track.

Through this project, I learned a lot about object-oriented programming, particularly how inheritance works and how to handle exceptions for input validation. These are concepts I had worked with before but got to apply more deeply this time. I also got better at breaking down complex tasks into smaller steps, making the project more manageable.

In terms of skills I revisited, I worked more on handling user input and giving feedback. This was something I had done in earlier projects, but NumQuest gave me the chance to improve it. I also got better at creating UML diagrams to plan out the project before coding, which helped me visualize the structure of the game.

What went well was that I met the project deadlines and delivered a functional game. However, there was room for improvement in how I handled input errors. In future projects, I’ll focus on making the error handling even more thorough to catch all possible mistakes. I also saw an opportunity to make the code more modular and reusable, which would make it easier to work on future projects.

This project connects to others where I’ve developed games or interactive systems. The skills I learned in NumQuest, like handling user input and feedback, will be useful in future projects where I need to make similar systems.