Service-oriented Requirements Engineering Research Articles

Joint Impact of Agents and Services in Enhancing Software Requirements Engineering

Requirements engineering (RE) is a significant aspect of system development stages in generating reliable software (SW). Despite RE’s decisive impact on project success, SW systems still fail since there is a perplexity in sorting out requirements correctly. Researchers have tried several paradigms to deal with the specified challenges, such as agent-oriented RE (AORE), model-based RE, and service-oriented RE (SORE). By investigating the limitations of the independent use of these paradigms, this research sets an objective that proposes a framework which integrates the two paradigms (agent and service) on top of social media to enhance the SW RE processes. Thus, the research addresses challenges in gathering adequate requirements, detecting alignment between business requirements and SW products, prioritizing requirements, and recommending innovative ideas. The research has mainly adopted an empirical research methodology for SW engineering. Accordingly, two distinct expert groups have been formed based on their previous experience in AORE and SORE, respectively. The experts have been selected from enterprises and academic institutions, and they participated in our case study. After performing the necessary assessment based on specified criteria, those experts in the first group have reported that CASCRE (Collaboration of Agents and Services for Crowd-based Requirements Engineering) with a score of 93.7% is found to be better than that of AORE with a score of 88.7%. Moreover, experts in the second group have declared that CASCRE, with a score of 92.3%, is better than SORE, with a score of 83.7%. In both cases, improvements have been observed, which reveals that the synergy of the CASCRE features has a better impact on the RE process than utilizing individual approaches. Moreover, in order to demonstrate the applicability of CASCRE, feedback has been gathered from a focused crowd of local pharmaceuticals using a mini-prototype. Accordingly, 250 requirements related comments have been gathered from the discussion forum, and 1400 keywords were generated. Then, after performing a sentiment analysis using NLP algorithms, the result was demonstrated to experts. Therefore, 93% of gurus strongly agreed on the applicability of CASCRE in real projects.

Requirements Engineering in Cloud and Service-Oriented Systems: A Systematic Mapping Study

The domain of Cloud and Service-oriented requirements engineering (SORE) focuses on modelling, specifying, and analysing requirements to enable software development in a service-oriented manner. Even though Cloud and SORE has received increasing attention over the past decade, there is no clear view of the current state of knowledge. Our goal is to gain insights into the current status of Cloud and SORE research published to date. To this end, we conducted a systematic mapping study to develop a map to classify relevant literature published between 2007 and 2018. Out of the 326 studies that were examined, we selected 24 studies as primary studies. The resulting map provides an overview of the existing work on Cloud and SORE and makes it possible to identify gaps and plan and position future research. Our findings suggest that Cloud and SORE as a research context needs specific attention. More evaluation and validation research is needed to better understand the implementation and impact of the various solutions (e.g. frameworks, tools) that are proposed in the Cloud and SORE context.

What makes service oriented requirements engineering challenging? A qualitative study

The focus of Service Oriented Software Development (SOSD) is to develop software by integrating reusable services to lower the required cost, time and effort of development and increase reusability, agility, quality and customer satisfaction. It has been recognised in the literature that SOSD faces various challenges especially in requirements engineering (RE). The objective of this study is to investigate these challenges of Service Oriented RE (SORE) from practitioners' perspectives in order to gain a deeper understanding of the related issues and to reveal potential gaps between research and practice in SORE. They present a qualitative study of the challenges and issues in SORE. The data were collected by conducting interviews with practitioners working in IT companies in Sydney, who have had substantial experience with service oriented software projects. The authors findings reveal that most of the challenges of SORE are similar to those that are faced during RE in traditional or component-based software development. According to the practitioners, the research and practice has made some advances in the technical direction but the human related issues in SORE have not been addressed adequately.

Issues in IT Service-Oriented Requirements Engineering

Corporate information technology (IT) management is increasingly service-oriented, offering continuous evaluation and improvement of application, communication, delivery and support services to internal and external customers. Service-oriented requirements engineering (SoRE) plays a significant role in identifying and specifying service requirements, formally defined through service-level agreements (SLAs). However, the new frameworks and approaches emerging to guide these developments have not yet addressed how requirements for such services can be effectively developed, nor identified the diverse issues involved. We report a case study of a web services team development of requirements for an internal Service Desk service. The study revealed five main issues of concern when developing service provider requirements: service roles, responsibilities and accountability; service performance metrics; resolution of conflicting stakeholder service requirements; customer acceptance of service change; and service provider team structure. This study suggests that in the new IT services era, new techniques and approaches are needed for eliciting and determining provider and customer requirements that involve key stakeholder groups equitably and more closely negotiate the sometimes-conflicting provider and customer needs.