Although there are a wide variety of End-User Programming environments, it
is not clear to me how design is tackled by the EUP approach.
'Traditional' programming makes a distinction between the design stage and
the development stage, but no such distinction is apparent in EUP, the user
presumably being expected to design and code the system in a single
notation. While I can see benefits in this (e.g. shortening the
develop-compile-execute loop), I can also see problems arising from the
amount of information and the scale of the task the end-user must deal with
in a single envronment. This would seem to limit the scale of systems that
can be developed through EUP and later comprehension of what the system is
intended to do. Would anyone like to comment?
Cheers,
Pete
------------------------------------------------------------------------
Peter Hornsby,
Department of Computer Science
Loughborough University,
Loughborough,
Leicestershire,UK EMAIL:[EMAIL PROTECTED]
LE11 3TU. Tel: +44 (0)1509 222799
Fax: +44 (0)1509 211586
"The whole problem with the world is that fools and fanatics are always
so certain of themselves, and wiser people so full of doubts."
--Bertrand Russell
------------------------------------------------------------------------
