In any case, all listed papers have two limitations. First, users cannot undertake
anything but a straightforward design by themselves because they do not know how
to set forth their requirements and needs as components and would not be able to find
the right components. Second, users cannot extend the functionality of a component or solution without resorting to low-level programming, for which they are not qualified.
Both limitations lead to the same problem: end users are unable to enact a software
development lifecycle, progressing naturally from requirements to a gradually more
detailed composite design with increasingly lower-level components until they manage
to build their final solution. This goal calls for EUSE, which, for Web end users concerned
with the composite creation ofWeb applications, should define specific activities
within the software lifecycle and specifications for a support tool to guide users through
this lifecycle.