Content deleted Content added
Pointillist (talk | contribs) →Cost-Benefit Modelling of End User Development: create section with summary of Manchester 2005 study, plus reference |
Pointillist (talk | contribs) →Other Aspects of End-user development: add section with summary of EUSE model, with reference |
||
Line 35:
* Usability of applications produced
* Overall quality of the applications produced.
==Other Aspects of End-user development==
Commentators have been concerned that end users do not understand how to test and secure their applications - "It’s simply unfathomable that we could expect security... from the vast majority of software applications out there when they’re written with little, if any, knowledge of generally accepted good practices such as specifying before coding, systematic testing, and so on.... How many X for Complete Idiots (where “X” is your favorite programming
language) books are out there? I was initially amused by this trend, but recently I’ve become uneasy thinking about where these dabblers are applying
their newfound knowledge."<ref>{{cite web |url=http://eecs.oregonstate.edu/EUSES |title= The Dangers of End-User Programming |last=Harrison |first=Warren |work=IEEE Software |accessdate=2008-05-28 }}</ref>
In response to this '''End User Software Engineering''' (EUSE) has been defined as a higher level of EUD, whereby end users become motivated to consider security and verifiability when developing their solutions.<ref>{{cite web |url=http://eusesconsortium.org/findings.php |title=End-User Software Engineering: Empirical Findings|accessdate=2008=05-28 }}</ref>
== See also ==
| |||