doc:user flows in Release 23.09 decentralized architecture

[ma3u]

Description

This draw.io user flows describes the interactions between the Tractus-X components in the new release 23.09. The the data space components evolves from centralized to federated and decentralised characteristics. This makes the data spaces more resilient, sovereign and scalable, but in the other hand it's harder to discover and control the components in a global network.

BPMN diagram:

0. Onboarding a new participant (draw.io Scenario 0)

Sequence diagrams:

1. Inital Registration of a data provider (draw.io Scenario 1)
2. Provision Digital Twin (draw.io Scenario 2)
3. Discover and Request Digital Twin (draw.io Scenario 3)

The Eclipse Tractus-X documentation Digital Twin KIT discovery sequence diagram describes scenario 3.

We want to discuss this user flows with the Catena-X participants. In the next step we will deliver a mark-down documentation and link these diagrams.

Please use draw.io https://app.diagrams.net and open these GitHub files, if you have access rights to the repos.

Please leave your comments to the PR.

[jjeroch]

Looking into this PR this week - we will need to move this PR into the other repos soon. But first of all will review the content :)

[Sebastian-Wurm]

Thanks for the diagrams... File extension of onboarding-registration should be "drawio", instead of "draw.io".

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
No Duplication information

[jjeroch]

@ma3u please find my feedback below:
Inital Registration of a data provider (draw.io Scenario 1)

• I dont like the naming "Initial Registration" => actually this chart shows 2 topics
  • For CX Members in the role of an data provider: the digital twin registration process (btw have a look at my images below - created them last week and would personally prefer those more....eventhrough it not draw.io)
  • For CSP-B/CSP-A: the discovery finder registration process
• The step to register at the OSP need to get changed
  • the connector registration is not a OSP service; its a CSP-A/B service
  • the company needs to register the connector; not the OSP
  • I strongly suggest to take out the company registration from this chart - this should get separated - otherwise its confusing

Onboarding a new participant (draw.io Scenario 4)

• I suggest to change the title 'Initial IDP Registration' is wrong; its the 'CX Member Registration Process'
• the "IDP" section is wrong - its quite a lot now to document this - but it needs updates - lets do this next week
• remove "BPN Discovery" from the section 'Portal Registration' - the lookup is not on the BPN Discovery; its done via the Golden Record
• Its not clear why the process of the registration stops after the "look-up" of the BPNL
• 'request DID' to be removed
• MIW process needs to get removed from this section as well => I miss the coverage of the actual approval process - did you check the portal documentation for this? Its quite detailed in the asset repo
• in the section "Onboarding process":
  • I think there is a spelling mistake - first box is saying "app request" while this is actually the "registration process"
  • "Create BPNL Record" => this is only needed if there is no BPN existing yet, can you please update your image
  • "Use Case Document" and "Use Case Credential" to be removed - this is a complete different process
  • "Participant Credential" is currently only stored in the portal; not in the holder wallet
  • "Compliance Credential" is currently only stored in the portal; not in the holder wallet
  • "Send Email with technical user to customer" needs to get removed; thats wrongly placed

[florianrusch-zf]

@thomas-henn I guess this belongs to your team, right?

[tunacicek]

@florianrusch-zf not really belong to the sldt team. As @jjeroch mentioned, it would make sense to move the PR to other repository.

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
No Duplication information

[tuncaytunc-zf]

Here is my feedback for Provision Digital Twin (draw.io Scenario 2)

After creating the Digital Twin, you have to register an asset. I would change the interaction order to:

Provider App --- create Asset -----> EDC Provider
Provider App -- create policy (access, usage) --> EDC Provider
Provider App -- create contract offer --> EDC Provider

When you create a contract offer you need to refer the a policy, that's why it should be after creating the policy.

[arnoweiss]

@ma3u - do you think that the Digital Twin Kit could be a suitable new home for this content?

[ma3u]

Arno:

For the Data Discovery screnarios we could add to the Digital Twin KIT: @thomas-henn What do you think?

Which Repo / KIT is the right for the on-boarding BPMN 2.0 flow?

[Sebastian-Wurm]

I am particularly interested in the onboarding / registration flow. Are there any plans to update / correct this as per Julia's Feedback?

[arnoweiss]

Arno:

For the Data Discovery screnarios we could add to the Digital Twin KIT: @thomas-henn What do you think?

Which Repo / KIT is the right for the on-boarding BPMN 2.0 flow?

Data discovery scenarios are (I think comprehensively) covered here [1]. @ma3u - if you have suggestions, feature requests or the like, feel free to open a ticket in [2]

[1] https://eclipse-tractusx.github.io/docs-kits/next/kits/Digital%20Twin%20Kit/Software%20Development%20View/dt-kit-interaction-patterns
[2] https://github.com/[eclipse-tractusx/eclipse-tractusx.github.io](https://github.com/eclipse-tractusx/eclipse-tractusx.github.io)