English (United Kingdom)

https://curated-unify.zendy.io/wp-json/zendy-region/v1/featured_content/oa?rat=en

https://curated-unify.zendy.io/wp-json/zendy-region/v1/highlighted_journal/

Global: Zendy Plus annual

Presents the access of premium content as premium feature

Premium Content

Presents the keyphrase highlighting as premium feature

Keyphrase Highlighting

Presents the summarisation as premium feature

Summarisation

Insights

Presents the pdf analysis as premium feature

PDF Analysis

Presents the zaia usage as premium feature

ZAIA

Global: Zendy Tools annual

Global: Zendy Free Plan

Global: Zendy Tools monthly

Global: Zendy Plus monthly

This paper presents an investigation into why software engineers do not keep to the principle of separating business logic from display. The concept of method rationale is used to establish what is supposed to be achieved by following the principle. The resulting model is then contrasted with results from in-depth interviews with practicing engineers about what they want to achieve. The difference between what the principle advocates and what engineers consider beneficial holds the answer to why the principle of separating business logic from display is not maintained. The results suggest that many espoused benefits of the principle do not appeal to engineers in practice and the principle is tailored to make it more useful in particular contexts. Tailoring the principle also brought about other benefits, not explicated by the principle, thus reinforcing the idea that method tailoring is crucial to the successful enactment of information systems engineering methods.

Why Software Engineers Do Not Keep to the Principle of Separating Business Logic from Display: A Method Rationale Analysis