Marketplace Improvements

[ybidois]

Overview

Explain the topic in 2 sentences

Improve the Marketplace so customers can subscribe to apps and services easily

What's the benefit?

• Make it easier for customers to subscribe to apps or services
• Reduce complexity in listing an app or service on the marketplace

What are the Risks/Dependencies ?

Detailed explanation

• No dependency per se, but could consult BPDM regarding GR apps / services

Current implementation

Proposed improvements

• Improve UI/UX of marketplace
• Implement pricing schemes
• Implement multi-subscriptions for apps
• Improve subscription management for apps and services
• Harmonize Terms & Conditions for Service Marketplace

Feature Team

Contributor

• @Cofinity-UX
• @sophiepotyka
• @tfjanjua
• @ss-nikunj
• @saadanzari
• @Usmanfee
• @ybidois

Committer

• @oyo
• @ntruchsess
• @Phil91
• @evegufy

User Stories

• Harmonization and Enhancement of identifier types #605
• Ability for App or Service Provider to Decline the Subscription request portal-backend#1140
• Ability for App or Service Provider to Decline the Subscription request  portal-frontend#1371
• App/Service Release Process Form -> Agreements & Consents Step -> Translation portal-backend#937

Acceptance Criteria

• Criteria 1
• Criteria 2
• Criteria 3

Test Cases

Test Case 1

Steps

1. Do something
2. Click something
3. Add something

Expected Result

1. Expectation
2. Expectation
3. Expectation

Architectural Relevance

The following items are ensured (answer: yes) after this issue is implemented:

• This feature aligns with our current architectural guidelines
  • Data Sovereignty: All data sharing activities across company boundaries follow the Catena-X Regulatory Framework, in particular the Data Exchange Governance, and the Dataspace Protocol via a compliant Connector (like the tractusx-edc or similar, see Connector KIT)
    • CX-0010 Business Partner Number
    • CX-0013 Identity of Member Companies
    • CX-0018 Data Space Connectivity (EDC)
    • CX-0049 DID Document Schema
    • CX-0050 Framework Agreement Credential
    • CX-0149 Verified Company Identity
  • Interoperability: Digital Twins are used (compliant to the Digital Twin KIT and the Industry Core KIT)
    • CX-0001 EDC Discovery API
    • CX-0002 Digital Twins in Catena-X
    • CX-0018 Data Space Connectivity (EDC)
  • Data Format:
    • The data model is based on a published Semantic Model
• The impact on the overall system architecture has been assessed. The Feature does not require changes to the architecture or any existing standard? Please have a look here on the overarching architecture
• Potential risks or conflicts with existing architecture has been assessed

Justification: (Fill this out, if at least one of the checkboxes above cannot be ticked. Contact the Architecture Management Committee to get an approval for the justification)

Additional information

• I am aware that my request may not be developed if no developer can be found for it. I'll try to contribute a developer (bring your own developer)

[stephanbcbauer]

@obalandi not sure about this feature. Is it planned to present it in tomorrow's planning? It was never presented in a Refinement meeting. Did we miss something?

[stephanbcbauer]

Some hints from Release Management (@ther3sa) and Tractus-X Project Lead (@stephanbcbauer)

• Please add missing sections from the feature template, or fill them out
• Please add contributor and committer
• Please add assignee (overall responsible person who drives the feature)

[ybidois]

Updated with new template

[dorkabcox]

to be linked: eclipse-tractusx/portal-backend#937

[evegufy]

Committers:
@oyo
@ntruchsess
@Phil91
@evegufy

[MaximilianHauer]

added the request/proposal from @maximilianong to a story based on the email communication

• sig#815 - Improve the clarity on the app/service subscription process portal-frontend#1337

@dorkabcox / @Cofinity-UX fyi

[Cofinity-UX]

@ybidois @dorkabcox @MaximilianHauer in the proposed improvements of this ticket it says "Implement pricing schemes" – this has dependencies with sig#18, where offer is requested as default setting on app/service detail pages. To be defined if both scenarios will be implemented.