Are you familiar with the arguments for separating presentation and content? Broadly speaking the logic behind the presentation is called display logic, and the special rules about content (eg that a payment for the full amount of an invoice closes that invoice) are called business rules. This despite the fact that the company actually decides both sets of rules, and that it can be hard to clearly draw the line between the two.
The reason for drawing this distinction is exactly so that presentation and content stay separate. Which separation is good software engineering for a number of reasons, several of which become particularly obvious when multiple ways of presenting the same data exist. (eg A web application and a desktop application.) Or alternately if the same basic presentation is used to present many different kinds of content. (I have a reporting application that definitely fits the latter description.)
In reply to Re: Display logic is driven by business rules IMHO
by tilly
in thread Display logic is driven by business rules IMHO
by metaperl
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |