remove concrete project from architecture

Author: RolandJentschETAS

process/process_areas/architecture_design/architecture_concept.rst

@@ -175,7 +175,7 @@ On the feature level only *logical interfaces* shall be displayed. This means th
 SW Module View
 ==============
 
-A SW Module in S-CORE represents a outcome of an component or a set of components realizing a feature and all belonging parts of CI build tool. It serves only as a container (or package) which can include components. It is not meant to be an architectural element which includes that no requirements can be allocated to it.
+A SW Module represents a outcome of an component or a set of components realizing a feature and all belonging parts of CI build tool. It serves only as a container (or package) which can include components. It is not meant to be an architectural element which includes that no requirements can be allocated to it.
 
 On this level also a view shall be defined which is called *Module View*. It represents the allocation of components into modules and displays the dependencies between the single modules. In this view also cyclic dependencies between modules can be identified.
 
@@ -196,7 +196,7 @@ Component View
 Static View
 -----------
 
-The second viewpoint is named as *component architecture* and describes the implementation of the functionalities in a white-box view of the platform. It describes the structural decomposition of the *SW components* into *lower level* SW components. In the S-CORE project this viewpoint provides more detailed information concerning the respective interfaces of a component. If a SW component interacts with a different component it is also included via a *use* relationship in the diagram. An example of the *component architecture* is displayed here:
+The second viewpoint is named as *component architecture* and describes the implementation of the functionalities in a white-box view of the platform. It describes the structural decomposition of the *SW components* into *lower level* SW components. In the projects this viewpoint provides more detailed information concerning the respective interfaces of a component. If a SW component interacts with a different component it is also included via a *use* relationship in the diagram. An example of the *component architecture* is displayed here:
 
 .. comp_arc_sta:: Component 2
    :id: comp_arc_sta__example_feature__archdes_component_2

process/process_areas/architecture_design/guidance/architecture_inspection_checklist.rst

@@ -27,7 +27,7 @@ Purpose
 -------
 
 The purpose of the software architecture checklist is to ensure that the design meets the criteria and quality as
-defined per S-CORE processes and guidelines for feature and component architectural design elements.
+defined per project processes and guidelines for feature and component architectural design elements.
 It helps to check the compliance with requirements, identify errors or inconsistencies, and ensure adherence to best
 practices.
 The checklist guides evaluation of the architecture design, identifies potential problems, and aids in