Benefits of seperation of UI and BL

[dayv2005]

For my own personal understanding, i not the best when it comes to application architecture, what are some main reasoning why you want to separate The User interface with the business logic?

What are the pros to this and what's some good practicing with this?

 

[RKR]

For my own personal understanding, i not the best when it comes to application architecture, what are some main reasoning why you want to separate The User interface with the business logic?

What are the pros to this and what's some good practicing with this?

One simpel reason why you wish to seperate UI from BL is that you do not always want to have the same UI. Maybe you want to have a simple Progress 4GL UI, or a more advanced .NET UI. Some customers prefer character based UI on UNIX. Or you want to expose parts of your application on the internet.

When you have seperated BL from UI it is all possible without rewriting you BL for every platform. The BL is your actual application and contains the functionality. With a good design you can implement any UI with a minimum of work because you do not have to think about the functionality of your application.

 

[FrancoisL]

It also a good way to reduce redundancy of code. Different windows can call the same procedure instead of having the same code copied in both UI.
Changes become easier since the business logic only need to be changed at one place for all your UI. It will make your application more flexible .

 

[tamhas]

You might want to go here http://www.psdn.com/library/kbcategory.jspa?categoryID=54 and click on the new in the last 30 days link in the What's New box on the upper right. There are a series of 12 new "Definitions" of components or layers in the OERA and this includes a discussion of value.