jjeroch
commented
7 months ago Attention @rybtim : Upcoming PI Planning Preparation
As we gear up for the forthcoming PI Planning session, it is crucial that all features under consideration align with our established Feature Quality Standards and Definition of Done (DoD) guidelines. To ensure your feature is thoroughly prepared and stands a strong chance of being prioritized, please provide comprehensive documentation that includes the following components:
- Feature Summary: An executive overview that encapsulates the essence and objectives of the feature.
- Change Description:
- High-Level Overview: A succinct synopsis of the proposed changes and their overarching impact.
- Detailed Analysis: An in-depth exploration of the specific alterations, including a clear exposition of the anticipated impact on existing systems.
- Impacted Components: A list identifying all system components that will be affected by the feature implementation, accompanied by a brief explanation of the nature of the impact.
- Acceptance Criteria: A set of clearly defined conditions that must be met for the feature to be considered complete and acceptable.
- Test Scenarios: A detailed outline of test cases that cover all functional paths of the feature to ensure robust validation and verification.
- Risks/Dependencies
Please note that any feature submissions lacking these essential elements will not be eligible for consideration in the upcoming PI Planning. It is imperative that your documentation is both thorough and precise to facilitate a smooth and effective planning process.
Please let me know in case you have any questions
Grand-Thibault
rybtim
stephanbcbauer
JulianStoll
maximilianong
zygokaktus
Overview
This feature aims to introduce enhanced search functionality for Business Partners in the CX network. It improves the current available options for identifying Business Partners in different scenarios like e.g., within the CX-onboarding process. The benefit of the new functionality is that a member can search for a business partner based on several characteristics and receives the latest information out of the network.
Explain the topic in 2 sentences
Enhance business partner management by adding further options for searching for Business Partners in the CX Pool. The goal is to identify Business Partners which are already known in the CX network based on new search criteria which will be established in the scope of this feature.
What's the benefit?
The benefit of this functionality is that a member can search for a business partner based on several characteristics and receives the latest information out of the network.
What are the Risks/Dependencies/Restrictions ?
Dependencies: Technical implementation of enhanced search criteria in the portal must be foreseen in a future release.
Restrictions: As this is a base functionality and designed to use the CX Data-Pool as source, it is important that no data ownership rights/rules are violated. The privacy classification of the single fields is described below. It is mandatory that there is no visible link between the data set and the original sharing member.
The Scope of this feature is focussing on the CX-Pool; functionality can be enhanced for the gate API at a later stage.
Detailed explanation
Current implementation
Currently, the search function for Business Partners allows only search by name / name parts and Business Partner Number (BPN). No other search criteria are supported. It is also limited to onboarded CX members and does not contain BP which are shared by CX members Reference : https://github.com/eclipse-tractusx/bpdm/blob/main/docs/api/gate.yaml https://github.com/eclipse-tractusx/bpdm/blob/main/docs/api/pool.yaml
Proposed improvements
The search can be conducted via the following fields:
A combination of search criteria must be possible
The following information shall be shown for a found record:
Display Results: There should be the functionality of filtering the search results:
Feature Team
Contributor
Committer
User Stories
Acceptance Criteria
Test Cases
Test Case 1
Search by address data.
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