You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As user
I want manufacturer name for an asset to have a clear name of the company to interact with
so that to access the bpdm API over EDC and could interact with the BPDM API in a data sov. manner.
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)
The text was updated successfully, but these errors were encountered:
Overview
Explain the topic in 2 sentences
What's the benefit?
What are the Risks/Dependencies ?
Detailed explanation
Current implementation
Proposed improvements
Feature Team
Contributor
Committer
User Story
As user
I want manufacturer name for an asset to have a clear name of the company to interact with
so that to access the bpdm API over EDC and could interact with the BPDM API in a data sov. manner.
Links
Hints / Details
NFR
[ ] Improving performance by using caching strategy for manufacturer information in the backend instead of lookup information on each asset
Acceptance Criterias
Test Cases
Test Case 1
Steps
Expected Result
Architectural Relevance
The following items are ensured (answer: yes) after this issue is implemented:
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
The text was updated successfully, but these errors were encountered: