Content deleted Content added
m Open access bot: doi added to citation with #oabot. |
|||
Line 95:
<blockquote>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.</blockquote>
This viewpoint assumes that all end users are equally naive when it comes to understanding software, although Pliskin and Shoval argue this is not the case, that sophisticated end users are capable of end-user development.<ref>{{cite journal |first=Nava |last=Pliskin |author2=Shoval, Peretz |title=End-user prototyping: sophisticated users supporting system development |journal=ACM SIGMIS Database |volume=18 |issue=4 |pages=7–17|year=1987|doi=10.1145/1017816.1017817|s2cid=18183262 |doi-access=free }}</ref> However, compared with expert programmers, end-user programmers rarely have the time or interest in systematic and disciplined software engineering activities,<ref>{{Cite book|last1=Brandt|first1=Joel|last2=Guo|first2=Philip J.|last3=Lewenstein|first3=Joel|last4=Klemmer|first4=Scott R.|date=2008-01-01|title=Opportunistic Programming: How Rapid Ideation and Prototyping Occur in Practice|journal=Proceedings of the 4th International Workshop on End-user Software Engineering|series=WEUSE '08|___location=New York, NY, USA|publisher=ACM|pages=1–5|doi=10.1145/1370847.1370848|isbn=9781605580340|s2cid=17479074 }}</ref> which makes ensuring the quality of the software artifact produced by end-user development particularly challenging.
In response to this, the study of '''end-user software engineering''' has emerged. It is concerned with issues beyond end-user development, whereby end users become motivated to consider issues such as reusability, security and verifiability when developing their solutions.<ref>{{cite web |url=http://eusesconsortium.org/findings.php |title=End-User Software Engineering: Empirical Findings| publisher=End Users Shaping Effective Software Consortium | access-date=2008-05-28 }}</ref>
| |||