Decoupling Business Logic Layer from the User Interface Layer using C#
page 4 of 9
by Joydip Kanjilal
Average Rating: This article has not yet been rated.
Views (Total / Last 10 Days): 50942/ 77

The Architectural and Operational Objectives

This section discusses the architectural and the operational objectives of this framework.

Architectural Objectives

·         Isolate the common Execution Logic of an application from its Business Logic.

·         Facilitate architectural ease of use for different verticals/modules in the future.

·         Provision for converting the Business Logic Layer to Business Rules Engine in the future.

·         Ensure that the Business Logic Layer is an autonomous component. In the long run, this component can be replaced by XSLT or XML based files.

·         Enable other generic services like Security, Workflow, Messaging, etc. to make use of the this framework.

Operational Objectives

·         Ensure that consistent standards are maintained.

·         Minimize coding and reduce the development time.

View Entire Article

User Comments

No comments posted yet.

Community Advice: ASP | SQL | XML | Regular Expressions | Windows

©Copyright 1998-2024  |  Page Processed at 2024-06-23 9:13:46 PM  AspAlliance Recent Articles RSS Feed
About ASPAlliance | Newsgroups | Advertise | Authors | Email Lists | Feedback | Link To Us | Privacy | Search