[PURIS FOSS] Maintenance & Bug Fixing

[tom-rm-meyer-ISST]

Overview

Explain the topic in 2 sentences

Currently the application has several open bugs that should be fixed.

What's the benefit?

Bring the PURIS FOSS Reference Implementation into a shape that support adoption.

What are the Risks/Dependencies ?

Detailed explanation

No maintenance has been done in 24.12. Bugfixes and maintenance are open.

Current implementation

See 24.08 Release

Proposed improvements

Feature Team

Contributor

• @ReneSchroederLJ

Committer

• @tom-rm-meyer-ISST

User Stories

• See open bugs (to be refined)
• Dependency updates (EDC, DTR)
• Improve test coverage

Acceptance Criteria

• Bugs are fixed
• Test Coverage is at least 50% in Frontend and Backend

Test Cases

Smoketests - all tests of R24.08

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]

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

• Status currently in Inbox. ⇾ Only features with status backlog are considered in open planning
• Please add missing sections from the feature template, or fill them out
• Please add assignee (overall responsible person who drives the feature)