why use business objects?
Also: unless/until we rewrite the old functionality to use the new business objects, we’ve got the same logic in multiple places. But I would say that if you have decent OO design skills (again, from a technical point of view) then your reuse of logic is very minimal. The other thing to consider is the orthogonality of presentation and business logic. If the business logic changes, you don’t want to have to search through twiddly bits of presentation code to determine what you have to change, and the same applies for changes to the presentation logic. Conversely the majority of changes to underlying data requires a change to both the business and presentation layers. Those changes are greater then if you have some of the logic together. Another thing I’m having a hard time justifying is the wasteful use of the database. A robust business object will pull in way more data than you need, and one of the major bottlenecks in today’s enterprise environments is the database.
