Jim Starkey wrote:

>The process that I believe leads to good design has these steps:
> 1. There is agreement on requirements. This is too often skipped.
> Without a clear understanding of requirements, there is no way to
> judge a prospective design.

later, Vlad Horsun wrote:

> >May be some examples will help ?
> >
> >
> >

Jim Starkey answered:

> Vlad, I hope my answer to Claudio answers some of your questions. As
> for examples, I'll be happy to do some, but I'm not there yet.

For what my humble opinion is worth, this is a very dangerous design
methodology.
The design MUST start from the EXAMPLE, many examples even, published
and well understood.
THEN from these examples the requirements can be extracted, and after
that, the whole process can advance. Whenever the disagreement arises,
each argument MUST be also illustrated with the concrete example,
written in code, not simple words.
Forget the concreteness -- and the discussion risks to became a duel
of wizards, each locked it his own ivory tower, throwing t-words at
another one.

Sorry, could not resist :-)