Re: What is this model technique called

"Jarson" <jarson_at_nospam.com> wrote in message news:0%8Ga.14000$Gm4.1127160_at_news20.bellglobal.com...
> Another good
> example is BestBuy.com's site that allows you to compare product
> specifications for products of the same class. BestBuy gets either new
> product types or new specification attributes every week.
>
> In both examples, there will be some very common attributes that should be
> modeled classically. However, there will be attributes (such as viewable
> size, refresh rate, watts per channel, gigabytes, printing speed, etc.) that
> will change very frequently as new products are created or the way they are
> described changes. ...
>
> I understand that this type of design can be very dangerous and there is a
> real risk of it infecting the rest of the design. But then in some cases
> the alternative requires constant change to the data model.

I hear you, but I think in this case the issue is that we don't have techniques that allow for constant change to the data model. If a high rate of change in the model was accomplished easily, then this would be a non-issue.

Marshall Received on Wed Jun 18 2003 - 06:27:29 CEST