• Topic Area
  • Subfield
  • Topic

Best practi­ces (e.g. clean code, documentation)

A “best practice” in software develo­p­ment is a method or guide­line that has proven over time to lead to better, more relia­ble, and maintainable software than common alter­na­ti­ves in a given context. It is usually treated as a recom­men­ded standard for how software should be designed or how a team should work. There are best practi­ces regar­ding design, code quality, testing, documen­ta­tion, and deploy­ment. Examp­les for best practi­ces are, among others: rules for clean code (e.g. meaningful, descrip­tive names for varia­bles, reada­bility and consis­tent format­ting and struc­ture),  automa­ted testing, and regular code reviews to catch defects early and share knowledge.

Topics in the Subfield Quantum software engineering:

Select another topic within the subfield Quantum software engineering

Design patterns

A design pattern is an abstract descrip­tion of how a recur­ring problem within a…

Workflows

In the context of software, a workflow descri­bes the struc­tu­red sequence of activi­ties, whether manual or automa­ted, states, and transi­ti­ons through which…

Standar­diza­tion (Appli­ca­tion Programming Inter­faces, APIs)

Standar­diza­tion in software develo­p­ment and APIs… 

Testing, debug­ging, verification

Testing in software develo­p­ment is the syste­ma­tic process of execu­ting a program or system with the objec­tive of…

AI powered code generation

AI Powered Code Genera­tion in software develo­p­ment refers to the use of artifi­cial intel­li­gence models to…

Conti­nuous Develo­p­ment / Conti­nuous Integration

Conti­nuous develo­p­ment is an overar­ching approach in which code changes are conti­nuously imple­men­ted, integra­ted, tested, and…

High Level Programming Languages (e.g. QRISP)

A high level programming language such as Python or QRISP is highly abstrac­ted from machine code and allows develo­pers to work with…

Domain speci­fic programming languages (DSLs)

A domain speci­fic language (DSL) in software develo­p­ment is a programming language that is specia­li­zed for a parti­cu­lar appli­ca­tion domain, problem area, or class of tasks.

Hardware Speci­fic Programming Languages

In the context of quantum software enginee­ring, hardware speci­fic refers to…

Low Level Programming Languages (e.g. Qiskit)

High level and low level programming languages differ prima­rily in how closely they…

Software Develo­p­ment Kit (SDK)

A Software Develo­p­ment Kit (SDK) is a bundled collec­tion of tools, libra­ries, and documen­ta­tion that…

General Purpose Emula­tors (e.g. state vector, QASM, tensor networks)

A General Purpose Emula­tor in quantum compu­ting software develo­p­ment is a classi­cal software tool or simula­tor that…

Specia­li­zed Emula­tors (e.g. STIM, QRyd)

In high perfor­mance compu­ting (HPC), specia­li­zed emula­tors refer to emula­tion tools or platforms that…

Quantum high perfor­mance compu­ting integration

Quantum HPC integra­tion in quantum compu­ting software develo­p­ment refers to the…

Develo­p­ment Platform

In the context of quantum software enginee­ring, the term platform refers to the under­ly­ing environ­ment on which software is develo­ped, execu­ted, and opera­ted. It compri­ses a combi­na­tion of…

Services QaaS

Quantum as a Service (QaaS) is a cloud service model that provi­des location indepen­dent, on demand access to quantum compu­ting resour­ces, inclu­ding real quantum proces­sors, emula­tors, and develo­p­ment tools, via the internet.

Hybrid Cloud

A hybrid cloud in software develo­p­ment and cloud compu­ting descri­bes an archi­tec­ture in which appli­ca­ti­ons and data are distri­bu­ted across a combi­na­tion of private and public cloud environments.

Manage­ment and opera­tion of cloud quantum compu­ting (e.g. orchestra­tion, scheduling)

The term descri­bes how a cloud based quantum compu­ting (QC) environ­ment is opera­ted in practice: how jobs…

Partners