what is meant business object in 3-tier architecture and what the use

Question

3.00/5 (2 votes)

See more:

ASP.NET

what is meant business object in 3-tier architecture and what the use?

Posted 25-Jun-12 3:41am

skpraveenkumar

Add a Solution

2 solutions

Solution 2

Most business application has 3 essential components.

1. Some data Store that will contain the business specific data.
2. Some business logic that will govern how to enter, retrieve and interpret the data in the data store.
3. A meaningful display of this information to the user.

so I can say we need three things -

1. Data Store
2. Data Access
3. Business Rules/Logic + Validations
4. Web pages to present it to user.

The store could be any database. rest three have to be implmented in order to have our application working.

Now we can put all this code into one big project and get the things to work, but that would lead to some problems.

1. High degree of coupling between modules with separate and dedicated functionality.
2. A small change would need the change in complete application and even recompiling in some cases.

So why not we design the system in such a way that all the modules in independent of each other. independent in terms of extensiblity i.e. change in one area will not need change in any other area. Secondly resusability i.e. if we design the modules independetly then each module can then be resued independently and finally the best part if i need to replace or enhance one area I dont have to redo the complete application. i will change only the required tier.

Now coming on how to do it, its simple. identify what falls in which category and have each tier implemented as a separate solution.

Here are two toy projects that will give you a very good idea on how things are done in n-tier architecture.

YaBlogEngine - A Tiny Blog Engine written in ASP.NET/C#[^]

YaMessaging - A simple e-mail like messaging application[^]

P.S. I hope this was helpful and informative for you. please let me know if you have any confusion and or question.

Posted 25-Jun-12 5:11am

Rahul Rajat Singh

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Prasad_Kulkarni · Accepted Answer · 2012-06-25T03:48:00

Business Object Layer consists of objects that represent business entities which always should be 100% independent of database used for data persistence.

Provides manager classes accessible from Presentation layer.

HttpHandlers.

My own Page base class.

More things go here..

The business layer is vital; in that, it validates the input conditions before calling a method from the data layer.
This ensures the data input is correct before proceeding, and can often ensure that the outputs are correct as well.
This validation of input is called business rules, meaning the rules that the business layer uses to make “judgments” about the data.

However, business rules don’t only apply to data validation; these rules apply to any calculations or any other action that takes place in the business layer. Normally, it’s best to put as much logic as possible in the business layer, which makes this logic reusable across applications.

One of the best reasons for reusing logic is that applications that start off small usually grow in functionality.
For instance, a company begins to develop a web site, and as they realize their business needs, they later decide to add a smart client application and windows service to supplement the web site. The business layer helps move logic to a central layer for “maximum reusability.”
Ref.: Introduction to 3-Tier Architecture[^]