Answers are grounded in this paper and cite their sources.
Context: Hybrid quantum--classical software systems face extensive variability and dynamically changing operational conditions, including shifts in backend availability, queue latency, noise, cost, and provider constraints. These changes complicate the selection and maintenance of suitable configurations during operation.Problem: Software Product Line approaches have demonstrated their usefulness for addressing quantum-aware variability, particularly by capturing configuration alternatives and dependencies. However, most existing approaches manage variability primarily at design time, offering limited support for assessing and enacting runtime reconfigurations in response to changing operational conditions.Proposal: This paper proposes QUASAR (QUantum Adaptive Software ARchitecture), a Dynamic Software Product Line architecture for runtime self-adaptation in hybrid quantum--classical software systems. QUASAR integrates four artifacts into a MAPE-K feedback loop: a Runtime Decision Catalog, Runtime Information Catalog, Decision--Information Matrix, and Runtime Variability Model. An LLM-supportedreasoner generates candidate adaptations, while deterministic guardrails validate variability constraints, execution compatibility, and applicable policies before enactment.Results: A proof-of-concept examines backend rebinding, execution-parameter adjustment, and hybrid quantum--classical capability activation or bypass. Across 42 controlled executions, 10 (23.8\%) contained LLM-generated candidates violating implemented variability constraints; all were blocked before enactment. The prototype records auditable adaptation traces and reports 1.5--3~sadaptation latency, consistent with coarse-grained software orchestration.Implications: QUASAR provides preliminary evidence that a bounded subset of the proposed architecture can combine model-based variability management, LLM-supported planning, and deterministic validation for runtime adaptation in hybrid quantum–classical software systems.
No takes yet. Share an insight, caveat, or question.
Sepúlveda et al. (2026) studied this question.
Synapse has enriched 8 closely related papers on similar clinical questions. Consider them for comparative context: