DevOps is a very trendy term these days in the software development companies (SDC), term that emerges as a possible solution to finally reach an acceleration and a rise of productivity expected with the appearance of agile development approaches, but that until now had not materialized, through automation practices, continuous integration, continuous build, and continuous deployment. This paper aims to show current knowledge about the process of adopting DevOps in SDC through a systematic mapping of the literature. However, the results obtained show that there is little detailed information regarding activities, tasks, roles, and other important process elements for the adoption of DevOps. Similarly, it has been concluded that there is no a unified terminology, therefore, it is important to standardize it to simplify the understanding and application of DevOps. Furthermore, this paper shows the preview of the framework that it is being developed for the adoption of DevOps in the SDC.

No abstract

JVM-based processors used in embedded systems are often scaled back versions of the standard JVM which do not support the full set of Java bytecodes and native methods assumed by a JVM. As a result, code bases such as Java libraries must be migrated in order make them suitable for execution on the embedded JVM-based processor. This paper describes Monarch, a high-assurance Java-to-java (J2j) source code migrator that we are developing to assist such code migrations.

No abstract

Static analysis and software manipulation tools are frequently rule-based and draw on a variety of software models in order to achieve their goals. Program transformation languages provide traversal and matching capabilities that are aligned with the core functionality of rule-based systems. Therefore, transformation systems should be considered as candidates for implementing static analysis and manipulation tools. An issue associated with this approach is that transformation systems predominantly operate on syntactic models (abstract/concrete trees) of software. To effectively support indepth analysis, it is beneficial to integrate the syntactic models used by transformation systems with one or more semantic models.This paper describes a system, called GPS-Traverse, that establishes a link between syntactic and semantic models of Java software. These models are central to a transformationbased Java source code analysis and manipulation system we are developing called Sextant. Within Sextant, GPS-Traverse provides a coordinate system that is accessible during transformation. These coordinates enable the semantic model to be queried in a context-sensitive fashion during the course of transformation.