> Straight forward "rule-systems", ala mycin, are great at what is best called
> "diagnoi/// diagnosis". Design is quite a different kind of problem. Its
> "constructive" rather than "analytric". The possible paradigm of generating
> all possible solutions and evaluating them to find the best one is simply
> to time-consuming to be a meaningful approach. So the "rul-e-checking"
> approach is not satisfactory iether.
I'm agree, but remember that a rule system could be used also as a proposal
system: you can connect some concepts with a set of parameters. Based on the
actual parameters (for example: user requests) you can give a choice between
what you have precedently coded.
Of course, you can't be creative at all in this context, and this is not what
I'm trying to project.
> I think that there is some sort of methodology that may lay between based
> on a strong version of generate a prototype - find out what's wrong with it,
> make another, and do it over. A protyping scheme.
This is the scheme proposed by Gero, who talks about design prototypes scheme.
It's an attractive point of view.
> I am currently reading _ Creativity in Invention and Design_ by
> Subrata Dasgupta, Cambridge Press. It is the strongest analysis of
> computational design that I have seen to date and I suggest to anyone
> interested in the subject. Maybe, we can discuss it here on the DESIGN-L
> if enough people are interested.
I'm interested about it. What are major topics?
Bye, Giuliano
PS: please, include your email address in your messages.
--
Piergiuliano Bossi
e-mail: bossi@xxxxxxxxxxxxxxxxxx
fidonet: 2:331/308.8
> "diagnoi/// diagnosis". Design is quite a different kind of problem. Its
> "constructive" rather than "analytric". The possible paradigm of generating
> all possible solutions and evaluating them to find the best one is simply
> to time-consuming to be a meaningful approach. So the "rul-e-checking"
> approach is not satisfactory iether.
I'm agree, but remember that a rule system could be used also as a proposal
system: you can connect some concepts with a set of parameters. Based on the
actual parameters (for example: user requests) you can give a choice between
what you have precedently coded.
Of course, you can't be creative at all in this context, and this is not what
I'm trying to project.
> I think that there is some sort of methodology that may lay between based
> on a strong version of generate a prototype - find out what's wrong with it,
> make another, and do it over. A protyping scheme.
This is the scheme proposed by Gero, who talks about design prototypes scheme.
It's an attractive point of view.
> I am currently reading _ Creativity in Invention and Design_ by
> Subrata Dasgupta, Cambridge Press. It is the strongest analysis of
> computational design that I have seen to date and I suggest to anyone
> interested in the subject. Maybe, we can discuss it here on the DESIGN-L
> if enough people are interested.
I'm interested about it. What are major topics?
Bye, Giuliano
PS: please, include your email address in your messages.
--
Piergiuliano Bossi
e-mail: bossi@xxxxxxxxxxxxxxxxxx
fidonet: 2:331/308.8