A Systematic Literature Review on Service Description Methods

Abstract

Abstract. [Context and Motivation]As a result of recent trends in enhancing Service Oriented Requirement Engineering activities, a number of service description methods have been proposed for describing services. The availability of different service description methods can give developers a range of options to choose from so that they can have an appropriate description method that fits best their services. [Question/problem] But there is neither holistic information on service description methods nor a clear understanding of the strengths and weaknesses of each service description method. The aim of this paper is to identify problems of service descriptions that have been researched so far, and the techniques or methods available to tackle these problems. [Principle ideas/results] Thus, to gather this relevant information available in the literature, a systematic review was conducted. A total of 191 articles were examined, of which 24 articles focus on service description related concepts. The results show that, despite the recent efforts in describing the nonfunctional requirements of services through approaches like semantic annotations and policy attachments, there is still a lot to do in enhancing the description of quality aspects of services. Furthermore, this study reveals that a negligible effort is given to the description of consumer oriented services.[Contribution] This paper identifies and analyzes the current service description methods that exist in the literature and explains the pros and cons inherent to these methods

Empirical research methodologies and studies in Requirements Engineering: How far did we come?

“…Table 3 also shows that the following topics are addressed in two studies each: user participation, stakeholder identification, goal-oriented RE, and requirements elicitation while all other topics were addressed in only one study each. (Herrmann & Daneva, 2008;Pitangueira et al, 2013;Rinkelevic et al, 2013;Pergher & Rossi, 2013) 4 Requirements specification techniques/notations (Teka et al, 2012;Da Silva et al, 2011;Condori-Fernandez et al, 2009;Amyot & Mussbacher, 2011) 4 Security requirements (Iankoulova & Daneva, 2012;Souag et al, 2012;Mellado, 2009;Goudarzi et al, 2013;) M a n u s c r i p t Creativity techniques for RE (Saha et al, 2012;Lemos et al, 2012;Nguyen, 2009) 3 User participation and client involvement (Bano & Zowghi, 2013;Abelein & Paech, 2013) 2 Stakeholder identification (Pecheco & Garcia, 2012;Cala & Ivan, 2008) 2 Goal-oriented RE frameworks (Ghanavati et al, 2011;Horkoff et al, 2014) 2 Requirements triage and selection (Khurumet et al, 2012) 2 Requirements elicitation techniques (Davis et al, 2006;Ouhbi et al, 2013) 2 Requirements analysis techniques (Yue et al, 2011;Aguilar et al, 2010) 2 Automated requirements elicitation techniques (Meth et al, 2013) 1 Requirements modelling and analysis techniques for self-adaptive systems (Yang et al, 2014) 1 Tracing techniques (Torkar et al, 2012) 1 Generation of requirements specification from SE models (Nicolas & Toral, 2009) (Yang et al, 2014), cloud systems in two reviews (Mellado, 2009;Iankoulova & Daneva, 2012), service-...…”

A Review of Requirement Engineering Issues and Challenges in Various Software Development Methods

“…But WSDL fails in including and describing NFR [53] [54]. Moreover, SOA projects are based on business processes and their transformation is based on composition of services and not on use cases.…”

“…Once services are in operation, handling changes at the SLA level is difficult to implement because one has to involve customer and change the rules, policies and protocols for using and composing the services [53][55].…”