a co worker ad I are having a Philosophical debate about how far to carry granularity in application design. Any thoughts would be appreciated.
Here is a scenario:
If we are making an application that tracks Employees within a company, we are in agreement that we could/should have a class called employee that defines employee information. The thoght is then we can always make a collection of employees that would then be a department.
In defining the Employee Data we have come to realize that we should probobly inherit from a class called Person as all employees are people and then we can also use our person class in the future for an Applicant tracking database. All is well. Now for the debate.
Should We make a base class called person that contains person type information and does all of the validating for name , address, social security etc.
should we go farther and makebase classes for things like Address, Name, Social Security and then include those in the class person, and then in the employee etc.
Please add any thoughts or comments there are a few fermented malt beverages invoved on this one.