>No, that isn't overloading, that is just different methods of one or more business objects. Overloading is where the same method name has more than one implementation depending on the parameters passed. It's also called polymorphism.
>
>Mike

Yep I used "overloading" for want of a better expression. What I was trying to determine was whether the one business object should handle all areas of the scheduling process eg. Working out how long a job will take, Slotting the job into dates, Reporting on various aspects of scheduling etc.

There are several "sub-processes" (another bad term but I hope you get my drift) within scheduling and should there be business objects handling each facet separately ?

Cheers,
Jamie