Posts Tagged ‘DAL’

HELLO PEOPLE !!

Well this post is about layered architecture , which organize your project into 3 or more disjunvtive layers. 3 layered architecture is a very well know buzz word in the world of software development whether it web based or desktop based.

NEED OF LAYERED ARCHITECTURE:

1.    To make your application more understandable.

2.    Easy to maintain, easy to modify application and we can maintain good look of architecture.
3.    If we use this 3-Tier application we can maintain our application in consistency manner.
Basically 3-Tier architecture contains 3 layers
1.    Application Layer or Presentation Layer or User interface
2.    Business Access Layer(BALor Business Logic Layer(BLL)
3.    Data Access Layer(DAL)
Now lets understand these 3 layers and their working .
PRESENTATION LAYER .
 It is the Very first layer also called as user interface layer. Basically it is the layer on which end user works.
for example : Registration form , any home page of website.
Our Presentation Layer is the Web application, that will be exposed to the end user,The Web application includes Web Forms i.e. aspx pages, User Controls i.e. Ascx pages,

Scripts (client side java scripts), Styles (css and custom styles for styling the page), Master Page (.master extension, for providing common functionality to group of desired pages, Configuration Files like web.config and app.config etc.).

MulLayer2.jpg
BUSINESS LOGIC LAYER: For validating the data as per the rule for the business. It works as a real world object. All the functionality is defined in this class and used to display the details in the Presentation Layer. It is a bridge between Data Access layer and Presentation Layer. It reduces the validation check to the Database server. So Database does not get overloaded.
DATA ACCESS LAYER :
All code that is specific to the underlying data source – such as creating a connection to the database, issuing SELECT, INSERT, UPDATE, and DELETE commands, and so on – should be located in the DAL. The presentation layer should not contain any references to such data access code, but should instead make calls into the DAL for any and all data requests. Data Access Layers typically contain methods for accessing the underlying database data