This article is within the scope of WikiProject Computer science, a collaborative effort to improve the coverage of Computer science related articles on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.
I would like to propose an external link to the following End-User Development Discussion Forum, which is now listed on the EUSES Resource page. This is an open forum for discussion of end-user development ideas, papers, strategies, tools, etc. It is a new forum that is not yet linked from the master site at zipxap.com, but will be eventually. DISCLOSURE: I run this forum. If you deem value in the link then please add it. Ktpenrose (talk) 16:06, 14 September 2009 (UTC)
I have added a link to the EUSES home page, where your forum is the most recent item of news. I hope that will help attract contributions. - Pointillist (talk) 18:24, 14 September 2009 (UTC)
Yeah, EUSES is a great resource. Ktpenrose (talk) 17:49, 21 September 2009 (UTC)
I think this article deals more with who will make the end-user-application, as opposed to how the application will be made. When I look at the examples given for EUD's, I find they use spreadsheet and visual programming paradigm's.
Maybe the more useful distinction is that this is a software development paradigm. This means that this is a way of gathering software requirements, a way to make software more flexible by including EUD, or a collection of paradigm's and tools that are easy to use by non-programmers. I think it's not a programming paradigm by itself.
Are there any sources indicating that this is a programming paradigm? Azede Chukwu—Preceding undated comment added 11:26, 18 March 2012 (UTC).
Not just who will make the application, but EUD explicitly deals with how the application will be made. There are techniques described in the linked reference books to create semi-automatic code from examples, to create programming languages that are adequate to non-technical people and to make repetitive tasks easier (i.e. "programming", not just gathering requirements). Those are not presently described in detail but are the meat of the discipline. I'm not sure how you differenciate "programming paradigm" and "software development paradigm" though. I suppose you could call EUD a collection of programming paradigms, since several different paradigms fall under this umbrella (see ). Diego (talk) 12:11, 18 March 2012 (UTC)