A rational design process: How and why to fake it
IEEE Transactions on Software Engineering
Design patterns: elements of reusable object-oriented software
Design patterns: elements of reusable object-oriented software
Design patterns for object-oriented software development
Design patterns for object-oriented software development
On the criteria to be used in decomposing systems into modules
Communications of the ACM
Pocket PC development in the enterprise: mobile solutions with Visual Basic and .NET
Pocket PC development in the enterprise: mobile solutions with Visual Basic and .NET
Understanding and Evaluating Methodologies: NIMSAD, a Systematic Framework
Understanding and Evaluating Methodologies: NIMSAD, a Systematic Framework
Java 2 Web Developer Certification Study Guide
Java 2 Web Developer Certification Study Guide
Explaining Software Developer Acceptance of Methodologies: A Comparison of Five Theoretical Models
IEEE Transactions on Software Engineering
Joint Elicitation of Problems: Important Aspects of Change Analysis
Proceedings of the IFIP WG8.2 Working Group on Information Systems Development: Human, Social, and Organizational Aspects: Human, Organizational, and Social Dimensions of Information Systems Development
Java Frameworks and Components
Java Frameworks and Components
Enforcing strict model-view separation in template engines
Proceedings of the 13th international conference on World Wide Web
Teaching inter-object design patterns to freshmen
Proceedings of the 36th SIGCSE technical symposium on Computer science education
Hi-index | 0.00 |
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.