Presentation logic

From Wikipedia, the free encyclopedia

Separation of business logic from presentation logic is an important concern for software development.[1]

One major rationale behind "effective separation" is the need for maximum flexibility in the code and resources dedicated to the presentation logic.[2] Client demands, changing customer preferences and desire to present a "fresh face" for pre-existing content often result in the need to dramatically modify the public appearance of web content while disrupting the underlying infrastructure as little as possible.

The distinction between "presentation" (front end) and "business logic" (infrastructure) is usually an important one, because:

  • the presentation source code language may differ from other code assets;
  • the production process for the application may require the work to be done at separate times and locations;
  • different workers have different skill sets, and presentation skills do not always coincide with skills for coding business logic;
  • code assets are easier to maintain and more readable when disparate components are kept separate and loosely coupled;[2]

[edit] Footnotes

  1. ^ Parr, Terence John (2004). Enforcing strict model-view separation in template engines. Proceedings of the 13th international conference on World Wide Web. 1-58113-844-X. 
  2. ^ a b Paragon Corporation (2003-07-19). Separation of Business Logic from Presentation Logic in Web Applications.
 This article is uncategorized.
Please categorize this article to list it with similar articles. (May 2008)