Knowledge Agents: Maintenance 24.12

[obalandi]

Description

This issue is not aiming for new or extended functionalities, but assuring all changes are implemented, that are required to ensure the compatibility/interoperability with depending components.

The required changes are depending on the features changes of the depending components, selected during the upcoming PI Planning. The full extent of required changes can only be defined, after all other features requests are approved and finalized in the PI Planning.

The preliminary maintenance changes might include:

• Adaptation of changes of depending components (see Dependencies below)
• Adaptation of new sub-components of depending components
• Adaptation of changes to the ontologies
• Adaptation of new release guidelines for 24.12
• Solving upcoming security issues to fullfil acceptance criteria
• Additional maintenance to pass new quality gates
• Required enablers
• Depending on the selected feature changes of the PI Planning.

Business value

As this is not a feature, it does not provide direct business value, but cares for not losing existing business value, by making sure existing business applications will work with the updated components as well.

Test scenarios

The existing test scenarios shall be passed as expected, as the functional scope of the component is not changed.

Acceptance criteria

• Ensured compatibility with depending components based on integration/E2E tests
• Security issues are solved
• Quality Gate has to be passed
• Feature estimation not yet possible due to the dependency on the PI Planning.

Developer team

@drcgjung, @obalandi

Dependencies

Eclipse Dataspace Connector (EDC) Decentralized Digital Twin Registry (dDTR) Managed Identity Wallet (MIW) SLDT Ontologies models

[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? I am not sure if we can present it, because of the number of dependencies? Are they already discussed?

[obalandi]

@stephanbcbauer, we don't need to present it. It is just the maintenance of the Knowledge Agents. Adjustments are only made when there are changes in EDC and AAS. Since the last release, we also offer the AAS-Bridge solution. That's why these dependencies exist.