Técnicas de control de flujo de datos de un cliente de streaming de vídeo escalable en el tiempo

En la actualidad, para la reproducción de un vídeo a través de Internet es necesario tener que parar el vídeo para darle tiempo para poder reproducir parte del vídeo sin tener que se pause. Con este proyecto fin de carrera lo que se quiere conseguir es dise ˜nar un servicio de streaming de vídeo escalable donde el cliente va a ver una reproducción de dicho vídeo acorde al ancho de banda que este disponga. El lenguaje implementado para conseguir esto ha sido C

Back analysis of intensive rock mass damage at the El Teniente mine

A three dimensional non-linear solution of stress, strain and energy distribution was developed to determine the deformation and damage on the extraction level and undercut level for comparison with observations during model calibration. Based on the plastic strain results (% rock mass damage), an Esmeralda scale damage was developed for its extraction evolution. By mean of this scale, the collapsed zones by periods were assessed in order to undertake the final phase of back analysis

DevOps Ontology - An ontology to support the understanding of DevOps in the academy and the software industry

Currently, the degree of knowledge about what DevOps really means and what it entails is still limited. This can result in an informal and even incorrect implementation in many cases. Although several proposals related to DevOps adoption can be found, confusion is not uncommon and terminology conflict between the proposals is still evident. This article proposes DevOps Ontology, a semi-formal ontology that proposes a generic, consistent, and clear language to enable the dissemination of information related to implementing DevOps in software development. The ontology presented in this article facilitates the understanding of DevOps by identifying the relationships between software process elements and the agile principles/values that may be related to them. The DevOps Ontology has been defined considering the following aspects: the REFSENO formalism that uses the representation in UML was used and the language OWL language using Prótegé and HermiT Reasoner to evaluate the consistency of its structure. Likewise, it was satisfactorily evaluated in three application cases: a theoretical validation; instantiation of the continuous integration and deployment practices proposed by the company GitLab. Furthermore, a mobile app was created to retrieve information from the DevOps Ontology using the SPARQL protocol and RDF language. The app also evaluated the Ontology’s proficiency in responding to knowledge-based questions using SPARQL. The results showed that DevOps Ontology is consistent, complete, and concise, i.e.: to say: the consistency could be observed in the ability to be able to infer knowledge from the ontology, ensuring that the ontology is complete by checking for any incompleteness and verifying that all necessary definitions and inferences are well-established. Additionally, the ontology was assessed for conciseness to ensure that it doesn't contain redundant or unnecessary definitions. Furthermore, it has the potential for improvement by incorporating new concepts and relationships as needed. The newly suggested ontology creates a set of terms that provide a systematic and structured approach to organizing the existing knowledge in the field. This helps to minimize the confusion, inconsistency, and heterogeneity of the terminologies and concepts in the area of interest

FQMaP: Towards a Framework Quantitative Management of Processes in Small Software Development Organizations

Software development organizations need to control and improve their practices, seeking to reduce variability when executing the necessary processes to elaborate software; therefore, these organizations implement improvement plans to identify factors that affect the processes. Quantitative Management deals with identification, tracing, and control of those incident factors, using data proactively to predict performance and the effect of possible changes in a process. Reference models in software processes development such as CMMI V2.0 and ISO/IEC 33061:2021 address Quantitative Management, but are aimed at big enterprises. Other models such as MoProSoft, COMPETISOFT, and MPS.BR are aimed at small enterprises, but do not include enough elements on Quantitative Management. Execution of a systematic literature review permitted searching for works on Quantitative Management intended for small software development enterprises, indicating necessary practices and how to perform them. This search showed that a proposal is not available that incorporates Quantitative Management practices for software processes aimed small software development enterprises. The referred aspects make it difficult to adopt a Quantitative Management culture within these organizations, it which has become a problem, consisting in that small software development enterprises that do not execute quantitative management practices will have difficulty identifying and focusing on the factors that impact the process performance and, therefore, on the results of their projects. This work sought to tackle this problem by proposing the “framework for quantitative management of processes in small software development organizations” (FQMaP), which allows incorporating practices and techniques that support Quantitative Management of software development processes in these kinds of enterprises. From the evaluation of FQMaP, carried out by following Focus Group technique guidelines, it can be demonstrated that it is a simple proposal and with elements that can serve a company to quantitatively manage software development processes. Also, it has clearly specified its components, showing that its structure is familiar with other process patterns, that would facilitate their interpretation

La formación de los bibliotecólogos y archivistas: aproximación a los modelos pedagógicos predominantes

This paper presents a theoretical and conceptual approach to the pedagogical models in higher education —models focused on teaching and learning and models focused on education— and points out the model of Technical Rationality as an ideal model to the curricular conditions of the careers reunited under the label of Documentation and Information Systems: Librarianship and Archivistics. The acknowledgment of the dynamic character of the technical rationality model allows the academic community to promote processes of reflection on curricular redesign and adaptability to the technical and technological changes that support professional work. In this context, the paper approaches the change and unification of criteria in the educative institutions responsible for the education of professionals of information and documentation. The objective is to consolidate a reflection on the pertinence of the above mentioned pedagogical currents for the education of librarians and archivists, as well as to perform an analysis of their professional profile according to contemporary theoretical conceptions based on pedagogical and epistemological considerations

DevOps model in practice: Applying a novel reference model to support and encourage the adoption of DevOps in a software development company as case study

DevOps has emerged as an approach to help organizations automate, cost optimization, increase profitability, improve the stability of the software development process and the responsiveness of organizations, and create a more agile development and release pipeline. However, its adoption, maintenance and evaluation continue to be a challenge for software organizations, due to the absence of solutions that formalize process elements in a detailed way, such as: practices, roles, artifacts, objectives, among others. This paper presents a DevOps Model, this model to support the adoption of DevOps, which provides a set of fundamental and complementary values, principles, dimensions, and practices. The practices suggest a set of items such as purpose, specific objectives and expected artifacts. The elements defined in proposed DevOps Model arise from the elements found in the studies analyzed through a systematic mapping study. Model evaluation was carried out through a software development company as case study. The results obtained have allowed the case study company to evaluate, diagnose and identify improvement opportunities to be carried out in the processes and projects where a DevOps-based approach is used, the above in a practical, useful, and adequate way that allows this type of companies and with a low use of resources, both economic investment and time. This is how the DevOps Model could guide professionals and organizations towards a better understanding of DevOps, in addition to minimizing the subjectivity and error of its interpretation, adoption and evaluation