The objectives of the individual project (iP) is to learn/refresh the basics of,
- Java
- OOP
- IDEs
- Git and GitHub
- Project automation tools
- Code quality
The iP is very similar to the project you did in TIC2002 but with the following differences:
- Faster pace: You'll need to finish the project within 6 weeks.
- Better tools: You'll be using industry-strength tools more e.g., use an IDE instead of an online editor
- Higher rigor: You are expected to follow a more systematic process e.g., using Git and GitHub more.
- Higher bar: The code quality is expected to be higher and the functionality should be more robust e.g., required to follow some code quality guidelines.
If you didn't do well in the TIC2002 project, this is another chance for you to catch up and level up your skills in preparation for the team project that is coming up later.
If you did well in the TIC2002 project, use this as an opportunity to stretch yourself and improve your skills further e.g., go beyond the minimum requirements, try different design options
All skills you will learn in the iP will be useful in the team project (tP). Some of the iP code can even be adapted for the tP.
The more you do in the iP and farther you push beyond the minimal expectations, the easier it will be in your tP.
The iP is based on the generic project called Project Duke, the overview of which is given below.
The iP is to be done over the first half of the semester.
- Volatile requirements ahead!: Some requirements will only be released later (or could be changed along the way), to simulate how requirements of a project may not be available at the start or stay the same during the project.
- Requirements may differ between students!: Note that some requirements that are to be released later could be different from one student to another.