Catalogue Search | MBRL
Are you sure you want to remove the book from the shelf?
{{itemTitle}}
72,033
result(s) for
"software Production"
Sort by:
Some Questions of the Innovative Development Methodology of the Software Production Quality Management System
The study proves the relevance of the problem of ensuring the innovative character of the development of software production quality management systems (QMS). The goal of the QMS is to ensure the sustainability of raising and maintaining a given level of software quality and achieving strategic competitive advantages of the software manufacturer as a whole. The authors present a description of existing concepts of various scientists of the world scale, and also describe in detail the conceptual apparatus of the problem. A schematic representation of the concept of \"innovative development of the quality management system of software production\" is demonstrated. The concept and principles of the paradigm and the mechanism of innovative development of the quality management system are considered. The original concept of the innovative potential of the development of the quality management system in the field of software development is original. A model of the potential of an enterprise operating in the field of software production is described, with reference to the quality management system. The uniqueness of the research consists in presenting the concept and structure of the formation of the organizational and economic mechanism for regulating the innovation potential of the QMS of software production.
Journal Article
Kubernetes Cluster for Automating Software Production Environment
Microservices, Continuous Integration and Delivery, Docker, DevOps, Infrastructure as Code—these are the current trends and buzzwords in the technological world of 2020. A popular tool which can facilitate the deployment and maintenance of microservices is Kubernetes. Kubernetes is a platform for running containerized applications, for example microservices. There are two main questions which answer was important for us: how to deploy Kubernetes itself and how to ensure that the deployment fulfils the needs of a production environment. Our research concentrates on the analysis and evaluation of Kubernetes cluster as the software production environment. However, firstly it is necessary to determine and evaluate the requirements of production environment. The paper presents the determination and analysis of such requirements and their evaluation in the case of Kubernetes cluster. Next, the paper compares two methods of deploying a Kubernetes cluster: kops and eksctl. Both of the methods concern the AWS cloud, which was chosen mainly because of its wide popularity and the range of provided services. Besides the two chosen methods of deployment, there are many more, including the DIY method and deploying on-premises.
Journal Article
Who makes open source code? The hybridisation of commercial and open source practices
While Free and Open Source (F/OSS) coding has traditionally been described as a separate commons linked to values of openness and sharing, recent research suggests an increasing integration of private corporations into F/OSS practices, blurring the boundaries between F/OSS and commodified coding. However, there is a dearth of empirical, and especially quantitative studies exploring this phenomenon. To address this gap, we model the power dynamics and infrastructural aspects of software production within GitHub, a central hub for F/OSS development, using a large-scale, directed network. Using various network statistics, we detect the ecosystem’s most impactful actors and find a nuanced picture of the influence of individuals, open source organizations, and private corporations in F/OSS practices. We find that the majority of public repositories on GitHub depend on a small core of specialized repositories and users. In accordance with expectations, individuals and open source organizations are more prevalent in this core of elite GitHub users, however, we also find a significant amount of private organizations with an indirect, yet consistent influence within GitHub. In addition, we find that directly influential individuals tend to facilitate sponsorship methods more often than indirectly or non-influential individuals. Our research highlights a hybridization of F/OSS and sheds light on the complex interplay between influence, power, and code production in the multi-language dependency ecosystem of GitHub.
Journal Article
Virtualization Costs: Benchmarking Containers and Virtual Machines Against Bare-Metal
DevOps advocates the usage of Virtualization Technologies (VT), such as Virtual Machines and Containers. However, it is complex to predict how the usage of a given VT will impact on the performance of an application. In this paper, we present a collection of reference benchmarks that developers can use to orient when looking for the best-performing VT w.r.t their application profile. To gather our benchmarks in a resource-wise comprehensive and comparable way, we introduce VTmark: a semi-automatic open-source suite that assembles off-the-shelf tools for benchmarking the different resources used by applications (CPU, RAM, etc.). After performing a survey of VTs in the market, we use VTmark to report the benchmarks of 6 of the most widely adopted and popular ones, namely Docker, KVM, Podman, VMWare Workstation, VirtualBox, and Xen. To validate the accuracy of our reference benchmarks, we show how they correlate with the profile performance of a production-grade application ported and deployed on the considered VTs. Beyond our immediate results, VTmark let us shed light on some contradicting findings in the related literature and, by releasing VTmark , we provide DevOps with an open-source, extendable tool to assess the (resource-wise) costs of VTs.
Journal Article
Software Product System Model: A Customer-Value Oriented, Adaptable, DevOps-Based Product Model
DevOps pipelines have brought notable advantages, such as fast and frequent software delivery to software production paradigms, but dynamically dealing with quality attributes desired by the customer employing a DevOps pipeline remains a challenge. This work aims to define the design of a systems thinking inspired model, called Software Product System Model (SPSM), applying a customer-value oriented, holistic approach for implementing quality requirements, and its application and evaluation in a large software house. The main features include dynamic control of quality gates, the parameters of which are driven by customer requirements and feedback from surveys. All of the inputs are collected in a product backlog and fed forward to the quality gates over the DevOps pipeline. SPSM was successfully deployed in a large software house extending a DevOps pipeline with an accompanying improvement of customer-value oriented key performance indicators for projects. In a 2-year-long case study, security and code quality were the main quality attributes, with the metrics on security vulnerabilities and unit test coverage. At the end of the 2020, the DevOps pipeline within SPSM provided a 69.50% decrease of security vulnerabilities of all software products, and a 29.43% increase in unit test coverage for the whole code base for increasing code quality. At the end of 2020, the project completion ratio was measured to be 99.50% and the Schedule Performance Index (SPI) was measured to be 99.78% as the average of 762 projects delivered. The flexibility of SPSM allowed the software house to adapt to changing customer expectations. A checklist is provided for the replicability of the model application.
Journal Article
Cost-Benefit Analysis of the Implementation of an Integrated Production Software in the Raw Materials Sector of A Pharmaceutical Industry
The pharmaceutical industry currently has computer systems that seek to optimize processes and allow the maximum performance of its resources through the use of computer tools. The objective of the work was to determine the costs and benefits of two different software in management of raw materials for the pharmaceutical industry. Methods: observational, descriptive, cross-sectional, study that compared ONDANET and SAP software in positive and negative costs inferred in the implementation of the tools and the benefits in terms of the profitability of the management of raw materials for the elaboration of pharmaceutical products. Results: it has been observed by using direct costs and benefits that the benefit-cost ratio of the SAP software implementation yielded a result of 15.37, whereas the ONDANET software presented a cost-benefit ratio of 0.05, which could have been demonstrated Conclusion: A widely favorable cost-benefit ratio was found for SAP Software compared to the previously used ONDANET Software, indicating that the new software used is profitable. It is desirable to periodically carry out this type of analysis to guarantee not only that the Pharmaceutical Industry has a greater profitability, without also being able to provide its products with continuity and at affordable prices for the population.
Journal Article
Applying Model-Driven Engineering to Stimulate the Adoption of DevOps Processes in Small and Medium-Sized Development Organizations
Microservice architecture (MSA) denotes an increasingly popular architectural style in which business capabilities are wrapped into autonomously developable and deployable software components called microservices. Microservice applications are developed by multiple DevOps teams each owning one or more services. In this article, we explore the state of how DevOps teams in small and medium-sized organizations (SMOs) cope with MSA and how they can be supported. We show through a secondary analysis of an exploratory interview study comprising six cases, that the organizational and technological complexity resulting from MSA poses particular challenges for small and medium-sized organizations (SMOs). We apply model-driven engineering to address these challenges. As results of the second analysis, we identify the challenge areas of building and maintaining a common architectural understanding, and dealing with deployment technologies. To support DevOps teams of SMOs in coping with these challenges, we present a model-driven workflow based on LEMMA—the Language Ecosystem for Modeling Microservice Architecture. To implement the workflow, we extend LEMMA with the functionality to (i) generate models from API documentation; (ii) reference remote models owned by other teams; (iii) generate deployment specifications; and (iv) generate a visual representation of the overall architecture. We validate the model-driven workflow and our extensions to LEMMA through a case study showing that the added functionality to LEMMA can bring efficiency gains for DevOps teams. To develop best practices for applying our workflow to maximize efficiency in SMOs, we plan to conduct more empirical research in the field in the future.
Journal Article
Sustainability Challenges of Phosphorus and Food: Solutions from Closing the Human Phosphorus Cycle
The Green Revolution has led to a threefold growth in food production in the last 50 to 75 years, hut increases in crop production have required a concurrent increase in the use of inorganic phosphorus as fertilizer. A sustainable phosphorus supply is not assured, though, and food production depends on mineral phosphorus supplies that are nonrenewable and are being depleted. Phosphorus is effectively a nonsubstitutable necessity for all life. Because mineral phosphorus deposits are not distributed evenly, future phosphorus scarcity may have national security implications. Some projections show economically viable mineral reserves becoming depleted within a few decades. Phosphorus-induced food shortages are therefore a possibility, particularly in developing countries where farmers are more vulnerable to volatile fertilizer prices. Sustainable solutions to such future challenges exist, and involve closing the loop on the human phosphorus cycle. We review the current state of knowledge about human phosphorus use and dependence and present examples of these sustainable solutions.
Journal Article
Closing the Feedback Loop in DevOps Through Autonomous Monitors in Operations
DevOps represent the tight connection between development and operations. To address challenges that arise on the borderline between development and operations, we conducted a study in collaboration with a Swedish company responsible for ticket management and sales in public transportation. The aim of our study was to explore and describe the existing DevOps environment, as well as to identify how the feedback from operations can be improved, specifically with respect to the alerts sent from system operations. Our study complies with the basic principles of the design science paradigm, such as understanding and improving design solutions in the specific areas of practice. Our diagnosis, based on qualitative data collected through interviews and observations, shows that alert flooding is a challenge in the feedback loop, i.e. too much signals from operations create noise in the feedback loop. Therefore, we design a solution to improve the alert management by optimizing when to raise alerts and accordingly introducing a new element in the feedback loop, a smart filter. Moreover, we implemented a prototype of the proposed solution design and showed that a tighter relation between operations and development can be achieved, using a hybrid method which combines rule-based and unsupervised machine learning for operations data analysis.
Journal Article