Abstract
End-user Service Composition (EUSC) is defined as service composition where the person who creates the composite service also uses it. We derived requirements for EUSC tools using a custom method based on the scenario-based requirements analysis method. Ten participants were given scenarios, a demonstrator application and examples of EUSC tools before being interviewed. Analysing their responses, we elicited 139 requirements across topics including service “types” (e.g. pervasive services), composition flow (i.e. control/data flow) and the use of templates in composition. This is the first published work to have used a robust requirements analysis method in EUSC, adapted specifically to take account of prior work on EUSC. Some of our requirements validate those found in prior research or current EUSC tools but many are unique to our findings. The requirements found in this work inform and inspire the development of future EUSC tools, and the methodology is easily adapted for application in other domains.
Highlights
Service Composition (SC), when aimed at endusers, is a relatively young area, and this is reflected in the small amount of work that has been done on deriving requirements for tools to support end-users in performingSC
We argue that End-user Service Composition (EUSC) and the technologies that underpin it can benefit from active investigation of what end-users require from composition
The work reported here has two main contributions: 1. The creation of a comprehensive set of 139 requirements for EUSC tools, which we have demonstrated to be valid
Summary
This work focuses on SC by end-users, with no explicit restriction on the technologies that underpin the overall composition process. We argue that EUSC and the technologies that underpin it can benefit from active investigation of what end-users require from composition. There are two main views on the life cycle for EUSC, the first of which splits it into four stages [6]. Service request—the user requests the composition that she wants to create [6] This is relevant only in automated SC); 2. To be truly dynamic, this life cycle needs to make some provision for adapting the composite service once it has been created
Sign-in/Register to view highlights & summary Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a callDisclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
