2010 Eighth IEEE European Conference on Web Services 2010
DOI: 10.1109/ecows.2010.17
|View full text |Cite
|
Sign up to set email alerts
|

Service Composition for Non-programmers: Prospects, Problems, and Design Recommendations

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
3
1
1

Citation Types

4
41
0

Year Published

2011
2011
2022
2022

Publication Types

Select...
8
1

Relationship

1
8

Authors

Journals

citations
Cited by 41 publications
(45 citation statements)
references
References 15 publications
4
41
0
Order By: Relevance
“…Given different mashup scenarios, surprisingly, participants quickly understood that components had to be linked together so that information could flow between components thus making the necessary connections. The lack of this understanding and ability is a well-acknowledged problem evidenced in several other user studies of EUD tools [Namoun et al 2010b]. Our observations indicate that the key to solve this problem is: (i) to alleviate users from specifying data mappings by adopting a by-reference data passing paradigm and (ii) the purposeful design of the Web services to be mashed up.…”
Section: Domain-specific Mashupsmentioning
confidence: 90%
See 1 more Smart Citation
“…Given different mashup scenarios, surprisingly, participants quickly understood that components had to be linked together so that information could flow between components thus making the necessary connections. The lack of this understanding and ability is a well-acknowledged problem evidenced in several other user studies of EUD tools [Namoun et al 2010b]. Our observations indicate that the key to solve this problem is: (i) to alleviate users from specifying data mappings by adopting a by-reference data passing paradigm and (ii) the purposeful design of the Web services to be mashed up.…”
Section: Domain-specific Mashupsmentioning
confidence: 90%
“…One of the lessons we learned in this context is that mashup tools (including our own) are too technical for end-users and, as a consequence, end-users are not able to: (i) understand what exactly they can do with the tool and (ii) how to do it. This observation is backed by Namoun et al [2010b], who performed a set of user studies to understand how end-users perceive mashups and concluded that they generally lack an understanding of what, for instance, Web services are, and of how these can be integrated to form new logics (e.g., via data or control flows). Yet, they also identified a positive attitude of end-users toward these new kinds of software development tools and the necessary curiosity to start "playing" with them, which we consider a necessary requirement for our work.…”
Section: Introductionmentioning
confidence: 99%
“…The main problem of these tools, according to a recent study conducted by Namoun et. al., is the fact that the wiring paradigm is difficult to understand by non-programmers [25].…”
Section: Overview Of Existing Eup Approaches For Mashupsmentioning
confidence: 99%
“…Among the simplification approaches, the business process management and service computing communities have focused on abstracting process development and service composition into activities, as well as control and data flows. However, these are still challenging tasks even for expert developers [1,2]. Traditional reuse approaches, in the form of program libraries, services, or templates (such as generics in Java or process templates in workflows) have targeted developers rather than end-users.…”
Section: Introductionmentioning
confidence: 99%