Mapping of Catena-X Consortia Quality Gate Artifacts to Graduation Process Artifacts

[kelaja]

Graduation Stage	Graduation Artifact	QGate Object	Summary	Description
Sandbox	Use Case	-	-	-
n.a. Prerequesite	-> GitHub Pull Request	Pull-Request	1 Week prior to QG Identify Version under Review	Pull request for KIT version under review must be placed min one week prior to your reserved Quality-Gate timeslot \ (to enable formal reviews by relevant BOs, BDAs, DevSecOps System Team) \ Example checkpoints: \ - Aligned basic navigation structure \ - Core naming schema for critical page like the Changelog \ - Links / references between Eclipse Tractus-X vs. Catena-X
n.a. Prerequesite	-> GitHub Discussion	BO-Approval	Approval for all Solution Acceptance Criteria	Product Manager / Business Owner confirms: \ All acceptance criteria met (as defined in PI documentation). Relevant evidence is available.
n.a. Prerequesite	-> GitHub Issue	Developer-Journey	Test and Approval of Developer Journey	"PREFERABLE \ \ Business Owner / Product Owner should conduct a case study with at least 1 provider (ideally outside) of the consortium to test the developer journey.
Incubating		Release-Notes	Provide change log page in KIT	Each KIT team must provide a KIT-specific release note / change log for developers \ \ +++ Note: Add non-software explanation +++
n.a. Prerequesite	-> GitHub Repo	Repository	KIT Repo in Tractus-X	A KIT must have an own repository in Eclipse Tractus-X. The naming of the repository must have a postfix "-kit" \ \ e.g., "traceability-kit"
Sandbox	Mission Vision	KIT-Vision-and-Mission	Vision and Mission Documents in Repository	Documentation must be available in Eclipse Tractus-X as part of the adoption view MD files.
Sandbox	Business Value	Business-Value	Business Value Documents in Repository	Documentation must be available in Eclipse Tractus-X as part of the adoption view MD files.
Incubating	Semantic Model	Semantic-Models	Semantic Model standards submitted and published	KIT Product Owner confirms: \ The KIT under review is compliant to all relevant Semantic Model Standards which are already published on the Association website. \ The content of upcoming Semantic Model Standardization Requests (STAN) has been reviewed and feedback was provided to the responsible PCA/BDA. \ \ Note: \ Please create and submit standards in time according to process and timeline > The standardization process: https://confluence.catena-x.net/display/CXSTAN/The+standardization+process
Incubating	Logic - Schema	Logic-Schema	Logic / Schema standards submitted and published	KIT Product Owner confirms: \ The KIT under review is compliant to all relevant Logic / Schema Standards which are already published on the Association website. \ The content of upcoming Logic / Schema Standardization Requests (STAN) has been reviewed and feedback was provided to the responsible PCA/BDA. \ \ Note: \ Please create and submit standards in time according to process and timeline > The standardization process: https://confluence.catena-x.net/display/CXSTAN/The+standardization+process
Incubating		Business-Processes	Business Process Documentation	Documentation must be available in Eclipse Tractus-X as part of the adoption view MD files.
Incubating	Architecture	Architecture (Adoption View)	Architecture Documentation	Documentation must be available in Eclipse Tractus-X as part of the adoption view MD files.
Incubating		Access-and-Usage-Policies	Access and Usage Policies Documentation	Mandatory if a use case needs access & usage policies. \ \ Documentation must be available in Eclipse Tractus-X as part of the adoption view MD files. \ \ Policies must contain: \ - a human-readable text (aligned with legal) \ - a technical policy that can be executed by the EDC
Incubating	Tutorials	Tutorials	Tutorials and Documenation	PREFERABLE \ \ Documentation must be available in Eclipse Tractus-X as part of the adoption view MD files.
Incubating	White-Paper	White-Paper	White Paper	PREFERABLE \ \ Documentation must be available in Eclipse Tractus-X as part of the adoption view MD files.
Incubating	API-Specification/Protocols	API	API Specification / Protocols	Documentation for the development view must be available in Eclipse Tractus-X as part of the development view MD files.
Incubating	Sample-Data	Sample-Data	Sample Data Available in Repository	Sample data must be available in Eclipse Tractus-X as part of the development view MD files.
Incubating	Reference-Implementation	Reference-Implementation	Reference Implementation	Mandatory, if reference implementation is provided \ \ A reference implementation must follow the FOSS release gates and must be available in the corresponding repository in the Eclipse Tractus-X project.
Incubating	Architecture	Architecture (Development View)	Development-View Architecture Documents in Repository	Mandatory (for Platform Domain / CX ART) \ \ Documentation must be available in Eclipse Tractus-X as part of the development view MD files.
Incubating	Quick-Setup-Guide	Quick-Setup-Guide-and-Deployment-Scripts	Quick Setup Guide and Deployment Scripts in Repository	Documentation for the operations view must be available in Eclipse Tractus-X as MD files. \ A reference implementation must be deployable via versioned and released HelmCharts with ArgoCD and as local deployment. In addition, a quick setup guide must be provided. \ - Quick Setup Guides \ - Deployment Scripts (e.g., local, helm charts, terraform)

[kelaja]

There are two Architecture Criteria which are from different Views. Do we really need both of them? Is this distinction really necessary?

[FaGru3n]

Hi @kelaja,
which one did you mean?

[FaGru3n]

personally i would integrate the approval from BO as a label or within the Pull-Request (BO reviewer) and if they approve the Pull-Request should be fine.