1,721,063 research outputs found
Supporting the semi-automatic semantic annotation of web services: A systematic literature review
No full textContext Semantically annotating web services is gaining more attention as an important aspect to support the automatic matchmaking and composition of web services. Therefore, the support of well-known and agreed ontologies and tools for the semantical annotation of web services is becoming a key concern to help the diffusion of semantic web services. Objective The objective of this systematic literature review is to summarize the current state-of-the-art for supporting the semantical annotation of web services by providing answers to a set of research questions. Method The review follows a predefined procedure that involves automatically searching well-known digital libraries. As a result, a total of 35 primary studies were identified as relevant. A manual search led to the identification of 9 additional primary studies that were not reported during the automatic search of the digital libraries. Required information was extracted from these 44 studies against the selected research questions and finally reported. Results Our systematic literature review identified some approaches available for semantically annotating functional and non-functional aspects of web services. However, many of the approaches are either not validated or the validation done lacks credibility. Conclusion We believe that a substantial amount of work remains to be done to improve the current state of research in the area of supporting semantic web services
Design and Experimentation of a Distributed Information Retrieval-Hybrid Architecture in Cloud IoT Data Centers
No full textOSS-TMM: Guidelines for improving the testing process of open source software
No full textOpen Source Software (OSS) products do not usually follow traditional software engineering development paradigms. Specifically, testing activities in OSS development may be quite different from those carried out in Closed Source Software (CSS) development. As testing and verification require a good deal of resources in OSS, it is necessary to have ways to assess and improve OSS testing processes. This paper provides a set of testing guidelines and issues that OSS developers can use to decide which testing techniques make most sense for their OSS products. This paper 1) provides a checklist that helps OSS developers identify the most useful testing techniques according to the main characteristics of their products, and 2) outlines a proposal for a method that helps assess the maturity of OSS testing processes. The method is a proposal of a Maturity Model for testing processes (called OSS-TMM). To show its usefulness, the authors apply the method to seven real-life projects. Specifically, the authors apply the method to BusyBox, Apache Httpd, and Eclipse Test and Performance Tools Platform to show how the checklist supports and guides the testing process of these OSS products
A Study on the Difficulty of Accounting for Data Elaboration in Functional Size Measures
No full textThe most popular Functional Size Measurement methods adopt a concept of “functionality” that is based
mainly on the data involved in functions and data movements. Functional size measures are often used as a basis for estimating the effort required for software development. However, Functional Size Measurement does not take directly
into consideration the amount of data processing involved in a process, even though it is well-known that development effort does depend on the amount of data processing code to be written. Thus, it is interesting to investigate to what extent the most popular functional size measures represent the data processing features of requirements and, consequently, the amount of data processing code to be written. To this end, we consider three applications that provide similar functionality, but require different amounts of data processing. These applications are then measured via a few Functional Size Measurement methods and traditional size measures (such as Lines of Code). A comparison of the obtained measures shows that differences among the applications are best represented by differences in Lines of Code. It is likely that the actual size of an application that requires substantial amounts of data processing is not fully represented by functional size measures. In summary, the paper shows that not taking into account data processing dramatically limits the expressiveness of the functional size measures. Practitioners that use size measures for effort estimation should complement functional size measures with measures that quantify data processing, to obtain precise effort estimates
A systematic review on the functional testing of semantic web services
No full textSemantic web services are gaining more attention as an important element of the emerging semantic web. Therefore, testing semantic web services is becoming a key concern as an essential quality assurance measure. The objective of this systematic literature review is to summarize the current state of the art of functional testing of semantic web services by providing answers to a set of research questions. The review follows a predefined procedure that involves automatically searching 5 well-known digital libraries. After applying the selection criteria to the results, a total of 34 studies were identified as relevant. Required information was extracted from the studies and summarized. Our systematic literature review identified some approaches available for deriving test cases from the specifications of semantic web services. However, many of the approaches are either not validated or the validation done lacks credibility. We believe that a substantial amount of work remains to be done to improve the current state of research in the area of testing semantic web services
Towards Probabilistic Models to Predict Availability, Accessibility and Successability of Web Services
No full textWeb Services are gaining increasing attention as programming components and so is their quality. The external qualities of Web Services (i.e., qualities that are perceived by their users) such as the OASIS sub-quality factors Availability, Accessibility, and Successability can only be measured at late stages after the deployment and the provisioning of the Web Service. This may necessitate expensive rework if the targeted levels of qualities are not satisfactorily met. A reliable prediction of the values of the external qualities at early phases during development may totally remove the need for reworking and hence save valuable resources. In this paper, we describe an approach for building and empirically evaluating probabilistic prediction models for the Web Services external sub-quality factors Availability, Accessibility, and Successability based on internal static and dynamic quality measures (e.g., Cyclomatic Complexity and Distinct Method Invocations). A methodology was established that involves the collection of a set of predefined quality measures and then performing regression analysis to identify any correlation between them and the above mentioned external qualities. For this purpose, a framework for data collection and evaluation was designed, implemented and tested. The results of the preliminary evaluation of the framework showed that it is feasible to collect all the data points necessary for the regression analysis and model building activities. We are currently working towards adding about 18 more Web Services to our testbed in order to carry out a wider controlled experiment and then to build possibly accurate probabilistic prediction models for Availability, Accessibility, and Successability
Test-and-Adapt: An approach for improving service interchangeability
No full textService-oriented applications do not fully benefit from standard APIs yet, and many applications fail to use interchangeably all the services that implement a standard service API. This article presents an approach to develop adaptation strategies that improve service interchangeability for service-oriented applications based on standard APIs. In our approach, an adaptation strategy consists of sets of parametric adaptation plans (called test-and-adapt plans), which execute test cases to reveal the occurrence of interchangeability problems, and activate runtime adaptors according to the test results. Throughout this article, we formalize the structure of the parametric test-and-adapt plans and of their execution semantics, present an algorithm for identifying correct execution orders through sets of test-and-adapt plans, provide empirical evidence of the occurrence of interchangeability problems for sample applications and services, and discuss the effectiveness of the approach in terms of avoided failures, runtime overheads and development costs
AI Chatbots in Political Campaigns: A Practical Experience in the EU’s 2024 Parliament Elections
No full text
- …
