Perpetual Beta
Perpetual beta" and the following principle lightweight
models"capture organizational issues related to the software
development that only indirectly in
uence the user. How-ever, they are listed here since they capture parts of what
denes the Web 2.0 and they have an eect on the e-learning
researcher.
In contrast to traditional software, Web 2.0 applications
are no longer released in version-based software packages,
one version at a time, but are constantly rened and im-proved. Changes to services happen gradually, there is no
Google 1.2. This is facilitated by the ability of Web appli-cations to track the user's interaction with the service and