# Use Case Development

{% hint style="warning" %}
**Note:** This page is currently being updated to align with the DSSC Blueprint 3.0 as well as the iSHARE Framework 3.0. An updated version will be published soon.
{% endhint %}

The iSHARE Trust Framework describes[ three primary use cases](https://framework.ishare.eu/detailed-descriptions/functional/primary-use-cases), explaining the basic design and implementation of the Trust Framework:

* [Machine-to-machine service provision](https://framework.ishare.eu/detailed-descriptions/functional/primary-use-cases/1.-m2m-service-provision)
* [Human-to-machine service provision with identity info at the Service Provider](https://framework.ishare.eu/detailed-descriptions/functional/primary-use-cases/3.-h2m-service-provision-with-identity-info-at-the-ip/without-identity-broker)
* [Human-to-machine service provision with identity info at the Identity Provider](https://framework.ishare.eu/detailed-descriptions/functional/primary-use-cases/3.-h2m-service-provision-with-identity-info-at-the-ip/with-identity-broker)

The three primary use cases are supported by[ seven secondary use cases](https://framework.ishare.eu/detailed-descriptions/functional/secondary-use-cases).

A more practical description of the framework's functionality is provided in[ these four example use cases](https://framework.ishare.eu/use-cases).

{% hint style="info" %}
These use cases provide a generic overview of the functionality the framework provides. To get a more practical view of the provided functionality by this particular data space, it is suggested to provide real-life examples under this page that resonate with (potential) data space participants, including the relevant data products or services involved.
{% endhint %}

Similarly, DSSC also encourages you to build on this foundation by showcasing relevant, concrete use cases that resonate with your target ecosystem to make your own data space effective. These don’t need to be overly complex; even a small, well-designed pilot can spark interest and demonstrate the potential of data sharing. Strong use cases should show how they create value, whether economic, social, or environmental.

Use case development is an iterative process: (THE WORD "MONITOR" SHOULD BE UPDATED TO "TRACKING" IN IMPROVE CONTINUOUSLY (dssc changed this))

<figure><img src="https://3616791469-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FjHLUr2NWnUxvFTGYU4AT%2Fuploads%2FyLkNP9LfY7BaMBueJQwU%2FScreenshot%202025-11-07%20113046.png?alt=media&#x26;token=4ae0b0ff-00bf-459e-b4af-183e6a41ba66" alt=""><figcaption><p>Figure 4. Iterative Process for Use Case Development.</p></figcaption></figure>

{% hint style="info" %}

### The complete DSSC description is available [here](https://blueprint.dssc.eu/?pane=business\&intro=blueprint-in-the-broader-context\&f%5BblueprintVersion%5D=v3.0\&business=use-case-development#DataSpaceOfferings).&#x20;

{% endhint %}

Throughout this process, it is important to track progress and adjust use cases as needed, so they remain relevant and do not become outdated as participant needs, business context, and available offerings evolve. Keeping the principle of the iSHARE Framework at the centre: trust, clarity, and participant autonomy.&#x20;

Also, look for synergies and complementary efforts across the ecosystem. Strong use cases not only add value, but they also inspire others to join and scale the impact of your data space.

{% hint style="info" %}
Use Case Development connects closely with other building blocks:

* **Business Model:** Use cases create value and show how the data space helps participants.
* **Data  Space Offerings & Value Creation Services:** The available data and tools determine which use cases are possible.
* **Intermediaries & Operators:** They coordinate participants and manage use cases.
* **Regulatory Compliance:** Use cases must follow the law and regulations.
* **Contractual Framework:** Agreements set the rules for sharing data and providing services.
* **Data Models:** How data is structured affects which use cases can work.
  {% endhint %}

{% hint style="warning" %}
The guiding questions can help in the co-creation process and in defining this building block, so please see the next section.&#x20;
{% endhint %}
