Reusability and discovery models in software systems: a systematic literature review.

Abstract

Software Engineering principles and practices promote the reuse of existing elements to maximize the performance of development and maintenance processes. The core concepts of reusability are aligned with the FAIR (Findability, Accessibility, Interoperability, and Reusability) principles. From our perspective, FAIR principles are not only related to data in a software system, because there are other resources and parts of a system that are related to data indirectly or require data schemas and models for their description and management. Examples of these resources are services, business logic processes, contracts, security policies, architectures, components, deployment resources, execution rules, or interaction alternatives, among other possible examples. Actually, any resource in a system may need to be discovered either internally by a subprocess, or externally by any client that might be interested in finding, accessing, interoperating, or reusing it. This paper addresses a systematic literature review to analyze the current principles, paradigms, and technologies that can be applied to enable discovering and reusing mechanisms in modern software systems, and how traditional and outdated approaches have been adapted to support present issues. From this analysis, we outlined the challenges and open research lines that can be addressed to achieve a suitable reuse strategy.

Analysis, Evaluation and Reusability of Virtual Laboratory Software Based on Conceptual Modeling and Conformance Checking

“…Part of this analysis aims to clarify what has already been implemented and how to adapt software that already exist under the constraints of the new domain. SE aims to reuse as many previously developed software artifacts as possible, since software reuse can provide a better means of SE [40,41]. Furthermore, software reusability can be seen as a new approach for SE, leading to less development time, high-quality results, a reduction in software maintainability, less effort for developers and cost-effective solutions [42].…”