Skip to content

Commit b4acbbf

Browse files
add link
1 parent 030a6f1 commit b4acbbf

2 files changed

Lines changed: 3 additions & 1 deletion

File tree

process/folder_templates/platform/features/feature_name/architecture/index.rst

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,7 @@ Feature Architecture
1818
====================
1919

2020
.. note::
21-
The complete feature architecture template as shown here is intended to document the idea about the architecture of a feature (if needed) when a CR is created. After the CR is granted, it is moved and further detailed / maintained in the module where the feature resides. See `module template documentation <https://eclipse-score.github.io/module_template/main/>`__. Only the logical interfaces remains in the feature architecture platform documentation, as they are relevant for the overall platform architecture. The detailed architecture of the feature is documented in the module documentation, and the logical interfaces are linked from there to the platform documentation. This is to avoid that the platform documentation becomes too detailed and hard to maintain, while still providing the necessary information about the feature architecture in the platform documentation. In the reference integration of the platform the full feature architecture including the implementation of the features and its components becomes visible in the platform documentation.
21+
The complete feature architecture template as shown here is intended to document the idea about the architecture of a feature (if needed) when a CR is created. After the CR is granted, it is moved and further detailed / maintained in the module where the feature resides. See `module template documentation <https://eclipse-score.github.io/module_template/main/>`__. Only the logical interfaces remains in the feature architecture platform documentation, as they are relevant for the overall platform architecture. The detailed architecture of the feature is documented in the module documentation, and the logical interfaces are linked from there to the platform documentation. This is to avoid that the platform documentation becomes too detailed and hard to maintain, while still providing the necessary information about the feature architecture in the platform documentation. Depending from the project it might be that in the reference integration of the platform the full feature architecture including the implementation of the features and its components becomes visible in the platform documentation. See :ref:`Deployment example <deployment_example>`.
2222

2323
.. document:: [Your Feature Name] Architecture
2424
:id: doc__feature_name_architecture

process/general_concepts/score_building_blocks_concept.rst

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -133,6 +133,8 @@ developed as safety element out of context (SEooC).
133133
Deployment example
134134
++++++++++++++++++
135135

136+
.. _`deployment_example`:
137+
136138
The following figure is an example how the meta model may deployed on several repositories.
137139
The project main repository has the information about the platform and the features.
138140
These include stakeholder requirements, platform architecture, safety/security analysis

0 commit comments

Comments
 (0)