avalon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stepanossov, Kirill" <kstep...@lehman.com>
Subject RE: [PROPOSAL] lifecycle release
Date Mon, 17 Mar 2003 14:54:20 GMT
Sorry for interfering with your discussion but for the sake of Avalon well
being
here are a few articles which Avalon team may be find interesting to read. 
http://swt.cs.tu-berlin.de/~ron/diplom/node46.html#SECTION006800000000000000
00
http://st-www.cs.uiuc.edu/users/droberts/evolve.html

Just a fragment
//-------------------------------------------------------------------
While initial designs may be acceptable for single applications, the ability
to generalize for many applications can only come by actually building the
applications and determining which abstractions are being reused across the
applications. Generalizing from a single application rarely happens. It is
much easier to generalize from two applications, but it is still difficult.
The general rule is: build an application, build a second application that
is slightly different from the first, and finally build a third application
that is even more different than the first two. Provided that all of the
applications fall within the problem domain, common abstractions will become
apparent. 

Your framework won't be done after three applications. You can expect it to
continue to evolve. However, it should be useful and you can use it to
gather more examples. Just don't acquire too many users initially the
framework will change! 

There are two approaches to developing these applications. In the first
approach, the applications are developed in sequence by a single team. This
allows the team to begin reusing design insight immediately at the possible
expense of narrowness. In the second approach, the applications are
developed in parallel by separate teams. This approach allows for diversity
and different points of view at the expense of the time it will take to
unify these applications in the future. 

Some people have built a particular kind of application many times, so they
might be able to design a framework without first building an example. They
are not counterexamples, they just built their examples before they decided
to start the framework. 
//-------------------------------------------------------------------
Kirill

------------------------------------------------------------------------------
This message is intended only for the personal and confidential use of the designated recipient(s)
named above.  If you are not the intended recipient of this message you are hereby notified
that any review, dissemination, distribution or copying of this message is strictly prohibited.
 This communication is for information purposes only and should not be regarded as an offer
to sell or as a solicitation of an offer to buy any financial product, an official confirmation
of any transaction, or as an official statement of Lehman Brothers.  Email transmission cannot
be guaranteed to be secure or error-free.  Therefore, we do not represent that this information
is complete or accurate and it should not be relied upon as such.  All information is subject
to change without notice.



---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org


Mime
View raw message