Team meeting to discuss changes

We met this evening to go over how to best implement the changes required by our client without re-coding or having to change major parts of the software. And we were able to find a solution for the 2 main changes of making the hourly rate for the employees dependant on the employee, and also for making the payroll editable.

Unique hourlyRate

Firstly, we decided that creating an “hourlyRate” field in the “clsEmployee” class would do the job, and we could save this hourlyRate (per employee) to the clsRate object (that is aggregate of clsPayroll) field of the same name.

i.e., clsRate.hourlyRate = clsEmployee.hourlyRate

In this way, we only have to assign the hourlyRate value from clsEmployee while saving a payroll instead of clsRate. And the other claculations follow the same!

BEFORE

NOW

editPayroll

We will add a new method to the clsEmployee class, editEmployee(), so that if the month and year of a new payroll being added match, the user will be prompted to overwrite.

So basically, the structural changes come to only the clsEmployee class.

Renaming

We will change all captions on the windows, or in the VB project names to reflect the new name our client decided.

Year-to-date totals

We have to make an algorithm for this, and we also decided to clean up the code that calculates the yearly totals on the ledger class, and perhaps integrate it into the classes instead of having it as a GUI code. This will be the major work.