jjeroch
commented
8 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
zygokaktus
nicoprow
Description
I as a BPDM sharing member want to have the functionality to mark a business partner (BPNL, BPNA or BPNS) as the successor or predecessor of another business partner (BPNL, BPNA or BPNS). This is relevant in case of mergers, acquisitions, etc.
The BPDM data model must be enhanced with a possibility for relating a business partner successor to a business partner predecessor, or the other way round. Example: Company A is sold to Company B. The legal name of company A is dissolved but it is still relevant for former customers regarding e.g. warranty claims. Therefor there is a strong need to preserve the information about Company A and the linkage to Company B as legal successor and also vice versa (predecessor).
As this information is currently not available in Catena-X network there must be a concept worked out on how to provide this. This concept must also reflect the aspects of data ownership (e.g. regarding maintenance of sites) as well as the impact for linked data objects (like dissolving existing relations between BPNL/S/A), an and requirement for components and functionalities:
Outlook for further activities based on this concept (if not already covered in the points above) for Release 24.12:
Technical realization of concept.
Impact for technical components (to be validated in the course of the concept work)
• BPDM Gate and Pool API • Portal
Additional information