Refactoring the code to encompass the various school/college entities #2
Description
The project currently handles Basic college and student info with no persistence .
For future proofing and the possibility of switching to a GUI , proper class hierarchies should be implemented. Proper persistence is a requirement for that.
Possible steps:
- Extend the type of attendance records to include staff. Interfaces can come in handy especially for dependency injection
- Basic persistence for school/college info. Nothing fancy I am just lazy to enter details every time I run the app to test something XD. It's possible to use CSV files for this