In the “Configure the artefact transformation pipeline“ business process, the Development Team Configures the model2owl transformation script on the release/X.Y.Z branch of the OP/epo-conceptual-model repository in order for model2owl to correctly transform the conceptual model of the new release. The Development Team may need to make additional adjustments to the configuration files during the “preparing SDS version release” stage if needed (due to a bug for example). As a result of this business process, the SDS Generation Configuration business object is created. ->>>>>>> de79c6bae97441da0ed761ee579c417faeb97376
+In the “Configure the artefact transformation pipeline“ business process, the Development Team Configures the model2owl transformation script on the release/X.Y.Z branch of the OP/epo-conceptual-model repository in order for model2owl to correctly transform the conceptual model of the new release. The Development Team may need to make additional adjustments to the configuration files during the “preparing SDS version release” stage if needed (due to a bug for example). As a result of this business process, the SDS Generation Configuration business object is created.
In the "Collect subject relevant material" business process, the ePO Working Group starts to meet on a weekly basis in order to develop the new ePO release. In the first meetings the Working Group collects and analyses relevant material to the new ePO release such as reports, sample data, and PEPPOL specifications. All the resulting files from this process are stored on a drive in OP’s Internal sharepoint. As a result of this business process, the “ORSD Supplementary Material” business object is created.
@@ -345,9 +338,11 @@Business vi
In the "ORSD consolidation" business process, The Development team integrates the feedback from the working group into the ORSD Word document and transcribes the document into an [1] Asciidoc page placed in the release branch on the ePO-docs] repository. This Process may be revisited from the “Preparing Semantic Data Specification” Stage, if an inconsistency was discovered during the review of the formal artefacts.
-
-== Application and Technology view
+
In the "ORSD consolidation" business process, The Development team integrates the feedback from the working group into the ORSD Word document and transcribes the document into an [1] Asciidoc page placed in the release branch on the ePO-docs] repository. This Process may be revisited from the “Preparing Semantic Data Specification” Stage, if an inconsistency was discovered during the review of the formal artefacts.
== Application and Technology view
Application and Technology view
+The concise diagram for the Requirements Gathering Stage that describes all the artefacts involved in this stage using business (yellow), application (blue) and technology (green) layers is depicted in the figure below. The Github Repositories branches that are used for this stage are also depicted as orange rectangles for reference purposes.