Quantum DevOps: Towards Reliable and Applicable NISQ Quantum Computing

Gheorghe-Pop, Ilie-Daniel; Tcholtchev, Nikolay; Ritter, Tom; Hauswirth, Manfred

doi:10.1109/gcwkshps50303.2020.9367411

Cited by 15 publications

(10 citation statements)

References 31 publications

(24 reference statements)

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…To do that, quantum DevOps is starting to emerge. In [39] the author propose a technique to regularly check the reliability of quantum computers. This reliability is the used to estimate if a given hardware will provide results of enough quality and to select the best fitting available hardware to run a quantum service.…”

Section: Related Workmentioning

confidence: 99%

Trials and Tribulations of Developing Hybrid Quantum-Classical Microservices Systems

Rojo,

Valencia,

Berrocal

et al. 2021

Preprint

View full text Add to dashboard Cite

Quantum computing holds great promise to solve to problems where classical computers cannot reach. To the point where it already arouses the interest of both scientific and industrial communities. Thus, it is expected that hybrid systems will start to appear where quantum software interacts with classical systems. Such coexistence can be fostered by service computing. Unfortunately, the way in which quantum code can be offered as a service still misses out on many of the potential benefits of service computing. This paper takes the traveling salesman problem, and tackles the challenge of giving it an implementation in the form of a quantum microservice. Then it is used to detect which of the benefits of service computing are lost in the process. The conclusions help to measure the distance between the current state of technology and the state that would be desirable in order to have a real quantum service engineering.

show abstract

Section: Related Workmentioning

confidence: 99%

Trials and Tribulations of Developing Hybrid Quantum-Classical Microservices Systems

Rojo,

Valencia,

Berrocal

et al. 2021

Preprint

View full text Add to dashboard Cite

show abstract

“…This includes, e.g., the packaging of the quantum application to ship it into the target environment, or its deployment [7]. The required concepts and tools differ from classical DevOps and have to be extended for the quantum computing domain [29]. Section 3.5 presents the operations lifecycle exhaustively.…”

Section: Quantum Workflow Lifecyclementioning

confidence: 99%

“…Quantum DevOps was proposed by Gheorghe-Pop et al [29], motivating the need to apply the DevOps paradigm in the quantum computing domain. Thereby, they analyze the different phases of the traditional DevOps process and extend them correspondingly.…”

Section: Related Workmentioning

confidence: 99%

“…Further, the various software artifacts also have to be managed, which is prepared and done in the (iv) operations lifecycle. Thereby, developers and operations personnel should be tightly integrated following the widely used DevOps paradigm [7,29] to enable fast and frequent releases [92]. This is especially important in the quantum computing domain with the rapid development of new quantum computers or software tools, which may require adapting the quantum applications regularly [81].…”

Section: Interwoven Lifecyclesmentioning

confidence: 99%

“…After specifying the topology model, the quantum application is packaged as a selfcontained archive [29,47]. Therefore, only a single entity including all dependencies has to be transferred into the target environment for the execution [89].…”

Section: Packagingmentioning

confidence: 99%

See 2 more Smart Citations

The Quantum software lifecycle

Weder

Barzen

Leymann

et al. 2020

Proceedings of the 1st ACM SIGSOFT International Workshop on Architectures and Paradigms for Engineering Quantum Software

View full text Add to dashboard Cite

With recent advances in the development of more powerful quantum computers, the research area of quantum software engineering is emerging, having the goal to provide concepts, principles, and guidelines to develop high-quality quantum applications. In classical software engineering, lifecycles are used to document the process of designing, implementing, maintaining, analyzing, and adapting software. Such lifecycles provide a common understanding of how to develop and operate an application, which is especially important due to the interdisciplinary nature of quantum computing. Since today's quantum applications are, in most cases, hybrid, consisting of quantum and classical programs, the lifecycle for quantum applications must involve the development of both kinds of programs. However, the existing lifecycles only target the development of quantum or classical programs in isolation. Additionally, the various programs must be orchestrated, e.g., using workflows. Thus, the development of quantum applications also incorporates the workflow lifecycle. In this chapter, we analyze the software artifacts usually comprising a quantum application and present their corresponding lifecycles. Furthermore, we identify the points of connection between the various lifecycles and integrate them into the overall quantum software development lifecycle. Therefore, the integrated lifecycle serves as a basis for the development and execution of hybrid quantum applications.

show abstract

Multicriteria decision‐making–based framework for implementing DevOps practices: A fuzzy best–worst approach

Kumar,

Nadeem,

Shameem

2023

J Software Evolu Process

View full text Add to dashboard Cite

Increasingly, software organizations are implementing DevOps culture to benefit from it in terms of continuous testing, delivery, improvement, and so forth. Implementing DevOps is difficult due to a lack of understanding about the practices and their effective application for its effective implementation. This paper aims to explore different DevOps practices that can be implemented in software organizations. The study involves conducting a systematic literature review (SLR) to identify DevOps implementation practices, followed by the utilization of the fuzzy best–worst method (FBWM) to establish a taxonomy or classification of software practices. We have used an SLR to investigate the practices, and subsequently, the survey method was followed to validate the identified practices. Moreover, the best–worst method (BWM) was considered to evaluate the significance and develop the taxonomy of the practices. The results of this study extracted 19 practices that have been identified in the SLR process. The identified factors are further classified into six core DevOps lifecycle phases. The results of the BWM approach are shown. The outcomes of the study conclude that the proposed taxonomy of the practices could help DevOps practitioners and researchers effectively implement them in software development organizations.

show abstract

Quantum DevOps: Towards Reliable and Applicable NISQ Quantum Computing

Cited by 15 publications

References 31 publications

Trials and Tribulations of Developing Hybrid Quantum-Classical Microservices Systems

Trials and Tribulations of Developing Hybrid Quantum-Classical Microservices Systems

The Quantum software lifecycle

Multicriteria decision‐making–based framework for implementing DevOps practices: A fuzzy best–worst approach

Contact Info

Product

Resources

About