Appearance
Use Cases
When you have worked on an industrial use case which exploits quantum algorithms for solving and improving one (or even multiple) subproblem(s) you can elaborate on it in this section. When creating a new use case and after entering its name, you should see 4 tabs at the top, whose contents are described below:
Details
Most of the important information of your use case must be noted here (otherwise you will not be able to publish your use case). The summary should contain a very short description of the use case, which will be displayed on the preview tile within the quantum service store. It is limited to 200 characters (less than a tweet!), so keep it simple! Anything that goes beyond that can be (and should be!) exhaustively described in the eponymous field "Description". Similar to the description of an algorithm, you can put all information regarding the use case (e.g. how to get from the initial problem statement to the corresponding mathematical subproblem, which can be mapped onto quantum hardware) in here.
For illustration purposes you can also add some pictures within "Sketches" and reference them within the description field. Also, you should add some application areas and industries, which might be relevant for the use case at hand
Authors
The Authors section allows you to properly attribute all contributors who worked on the use case. You can add both individual persons and organizations as authors to give appropriate credit and provide contact points for those interested in learning more about your work.
When adding authors, make sure to include all key contributors who played a significant role in developing, implementing, or documenting the use case. This helps establish credibility and enables the community to connect with the experts behind the use case for potential collaborations or inquiries.
Demos
For each use case, you have the option to create an interactive demo that allows users to experience and experiment with your quantum solution firsthand. Interactive demos provide a hands-on way for the community to understand how your use case works in practice, making complex quantum algorithms more accessible and tangible.
Demos can showcase the inputs, parameters, and outputs of your quantum application, enabling users to try different configurations and see real-time results. This interactive approach significantly enhances understanding and engagement with your use case.
For detailed information on how to create and configure demos, including technical requirements and best practices, please refer to the Demos documentation.
Sketches
The Sketches section enables you to upload visual materials such as diagrams, flowcharts, architecture diagrams, and other images that help illustrate your use case. Visual representations are often crucial for explaining complex quantum workflows, system architectures, or the mapping from classical problems to quantum formulations.
You can upload sketches directly to this section and then reference them within your use case description using Markdown image syntax. This allows you to create a rich, illustrated documentation that makes your use case more understandable and engaging for readers.
For more information on how to reference images in Markdown and use advanced formatting features, please refer to the Markdown documentation.
Relations
The Relations section is a powerful feature that allows you to establish connections between your use case and the underlying algorithms and services that implement it. By linking relevant algorithms and services to your use case, you create a comprehensive knowledge graph that helps users understand the complete technical solution.
These relationships provide valuable context by showing:
- Which quantum algorithms are applied to solve the problem
- Which services implement these algorithms and can be used to execute the solution
- How different components work together to address the use case
Establishing these relations makes it easier for the community to explore the technical implementation, discover reusable components, and understand the end-to-end solution architecture. This interconnected approach enhances discoverability and helps users navigate from high-level business problems to concrete technical implementations.

