=?ISO-8859-1?Q?=ABDomain_Model=BB_in_.NET=3F?=

Fowler, Evans, et.al. heavily promotes the use of a «Domain Model» for
applications with complex business rules.

As a .NET developer, however, you read design papers from Microsoft
promoting «Table Module» and typed DataSets. This pattern is also
supported by Visual Studio .NET.

I can't seem to find any mature and stable (large user base, proven
customer cases, and so forth) tool for model/domain-driven design.

Questions:
1. Is Fowler wrong? I.e. Microsofties are very good at producing
complex business rules with their DataSets and DataReaders.

2. Is Fowler right? I.e. applications with complex business rules
aren't inherently built with .NET.

Regards,
// Martin Rosén-Lidholm

It seems to me that MS has always been promoting the single thing fits
all idea. Maybe the reason why Table Module was chosen is historical -
it goes very well with the idea of two tier architecture where business
logic is either implemented by database or mixed with the GUI.

I think that Fowler was right and he also said that if the tool used
supports Table Module approach then it's probably easier to go that way.
That is also why there isn't any widely used Domain Model frameworks for
..NET. Building such framework would probably also require implementing
some additional layer for GUI mapping unless you want to develop your
own GUI components.

If one uses .NET then maybe easier to develop the GUI stuff whereas
managing business rules might be a bit more difficult. So each approach
has its strengths and weaknesses.

BR,
Urgo

Martin R-L wrote:
> Fowler, Evans, et.al. heavily promotes the use of a «Domain Model» for
> applications with complex business rules.
>
> As a .NET developer, however, you read design papers from Microsoft
> promoting «Table Module» and typed DataSets. This pattern is also
> supported by Visual Studio .NET.
>
> I can't seem to find any mature and stable (large user base, proven
> customer cases, and so forth) tool for model/domain-driven design.
>
> Questions:
> 1. Is Fowler wrong? I.e. Microsofties are very good at producing
> complex business rules with their DataSets and DataReaders.
>
> 2. Is Fowler right? I.e. applications with complex business rules
> aren't inherently built with .NET.
>
> Regards,
> // Martin Rosén-Lidholm

Martin, have you seen this project:

http://neo.codehaus.org/

Might be along the lines of what you were looking for. I'm a bit new to the
Domain Model but I found this while I was researching it. HTH.
_Matthew


"Urgo Ringo" <urgo.ringo@aqris.com> wrote in message
news:416e64b6$1_2@news.estpak.ee...
> It seems to me that MS has always been promoting the single thing fits
> all idea. Maybe the reason why Table Module was chosen is historical -
> it goes very well with the idea of two tier architecture where business
> logic is either implemented by database or mixed with the GUI.
>
> I think that Fowler was right and he also said that if the tool used
> supports Table Module approach then it's probably easier to go that way.
> That is also why there isn't any widely used Domain Model frameworks for
> .NET. Building such framework would probably also require implementing
> some additional layer for GUI mapping unless you want to develop your
> own GUI components.
>
> If one uses .NET then maybe easier to develop the GUI stuff whereas
> managing business rules might be a bit more difficult. So each approach
> has its strengths and weaknesses.
>
> BR,
> Urgo
>
> Martin R-L wrote:
> > Fowler, Evans, et.al. heavily promotes the use of a «Domain Model» for
> > applications with complex business rules.
> >
> > As a .NET developer, however, you read design papers from Microsoft
> > promoting «Table Module» and typed DataSets. This pattern is also
> > supported by Visual Studio .NET.
> >
> > I can't seem to find any mature and stable (large user base, proven
> > customer cases, and so forth) tool for model/domain-driven design.
> >
> > Questions:
> > 1. Is Fowler wrong? I.e. Microsofties are very good at producing
> > complex business rules with their DataSets and DataReaders.
> >
> > 2. Is Fowler right? I.e. applications with complex business rules
> > aren't inherently built with .NET.
> >
> > Regards,
> > // Martin Rosén-Lidholm