Improvements and workflow enhancement

Description

This milestone is about making sure that there are no bugs causing the system to break. It involves looking through the code and removing any redundant code that is not needed. It also involves refactoring the code structure into an appropriate one hence avoiding spaghetti code.

Functional requirements:

1. There should be no code that is not being used unless it is a comment to enable others to understand how the code works.
2. There should be no known bug in the system that has not been fixed early.
3. The code structure should have low coupling and no spaghetti dependencies.

Non-Functional requirements:

1. The system should work smoothly without crashing
2. There should be very little or no bugs encountered in the system.

Example

After finishing writing codes, team members think of improving the structure and removing redundant codes. Some comments should be deleted because they don't provide any good explanation about the implementation. There might be some unnecessary notations, unused imports that should be removed as well.For improving the structure of the code there might some decisions regarding splitting the classes into different packages, so in this case all the relevant classes be in the same package for enhancement of functionality.