Re: Decouple SQL queries from class in OOP design
- From: "scott frye" <scottf3095@xxxxxxx>
- Date: 6 Dec 2005 07:35:01 -0800
>>Robert C. Martin wrote:
>
>>> A huge amount of effort goes into mapping business data into
>>> presentation formats. This mapping is not a business rule, per se;
>>> but is still complicated and important code that needs to be written.
>>> It should be separate from the business rules.
>>
>>The dividing line between such is rather blurry in practice.
>
> It often seems blurry. It is a goal of software design to sharpen the
> focus and discover the true separation between business rules and
> presentation rules.
.... AND....
>
> The point is that separations like this are a major objective of
> software design, and in particular of Object Oriented software design.
>
I agree with the the concept but the wording is too far reaching.
"A goal" of software design is to provide easily manintainable code
that scales well. "A technique" to do this, used by OO software
design, is to sharpen the distinction between business rules and
presentation rules.
Scottf3095@xxxxxxx
-------------------------------------------------
Panton in temperantia , comprehendo temperantia.
-unknown
-------------------------------------------------
.
- Follow-Ups:
- Re: Decouple SQL queries from class in OOP design
- From: topmind
- Re: Decouple SQL queries from class in OOP design
- From: Thomas Gagne
- Re: Decouple SQL queries from class in OOP design
- References:
- Re: Decouple SQL queries from class in OOP design
- From: Robert C . Martin
- Re: Decouple SQL queries from class in OOP design
- Prev by Date: Re: Different group of opertions as a separate class?? OOAD
- Next by Date: Re: Decouple SQL queries from class in OOP design
- Previous by thread: Re: Decouple SQL queries from class in OOP design
- Next by thread: Re: Decouple SQL queries from class in OOP design
- Index(es):
Relevant Pages
|
Loading