[1045] Improve export to properly handle named SuccessionAsUsage

Bug: #1045
Signed-off-by: Arthur Daussy <arthur.daussy@obeo.fr>

Author: adaussy

CHANGELOG.adoc

@@ -31,6 +31,7 @@ A new dra & drop tool is available on the diagram, allowing moving `Satisfy Requ
 - https://github.com/eclipse-syson/syson/issues/1024[#1024] [diagrams] Allow `Usage` and `Definition` graphical node labels to be wrapped to handle long names more easily.
 - https://github.com/eclipse-syson/syson/issues/1030[#1030] [metamodel] `ConnectorAsUsage.getSourceFeature` and `ConnectorAsUsage.getTargetFeature` should redefine `Relationship.source` and `Relationship.target` features
 - https://github.com/eclipse-syson/syson/issues/1042[#1042] [import] Improve textual import of `SuccessionAsUsage` which define a new target action directly after the 'then' keyword.
+- https://github.com/eclipse-syson/syson/issues/1045[#1045] [export] Improve textual export by properly handle named `SuccessionAsUsage`.
 
 === New features
 

backend/application/syson-application/src/test/java/org/eclipse/syson/application/export/ImportExportTests.java

@@ -55,6 +55,19 @@ public void setUp() {
         this.checker = new SysmlImportExportChecker(this.sysmlLoader, this.editingDomainFactory, this.exporter, this.sysMLEditingContextProcessor);
     }
 
+    @Test
+    @DisplayName("Given a named SuccessionAsUsage, when importing and exporting the model, then the exported text file should be the same as the imported one.")
+    public void checkNamedSuccessionAsUsageInActionDefinitionTest() throws IOException {
+        var input = """
+                action def A4 {
+                    action a1;
+                    action a2;
+                    succession s1 first a1 then a2;
+                }""";
+
+        this.checker.check(input, input);
+    }
+
     @Test
     @DisplayName("Given a SuccessionAsUsage with an implicit source feature, when importing and exporting the model, then the exported text file should be the same as the imported one.")
     public void checkSuccessionAsUsageImplicitSourceTest() throws IOException {

backend/application/syson-sysml-export/src/main/java/org/eclipse/syson/sysml/export/SysMLElementSerializer.java

@@ -359,7 +359,7 @@ public String caseSuccessionAsUsage(SuccessionAsUsage successionAsUsage) {
         this.appendUsageDeclaration(declarationBuilder, successionAsUsage);
 
         if (!declarationBuilder.isEmpty()) {
-            builder.appendWithSpaceIfNeeded(declarationBuilder.toString());
+            builder.appendWithSpaceIfNeeded("succession ").append(declarationBuilder.toString());
         }
 
         List<EndFeatureMembership> endFeatureMemberships = successionAsUsage.getFeatureMembership().stream()
@@ -416,7 +416,7 @@ private boolean isSourceFeaturePreviousDefinedFeature(SuccessionAsUsage successi
 
     /**
      * Checks if the source feature define force the given {@link EndFeatureMembership} is implicit or not
-     * 
+     *
      * @param endFeatureMembership
      *            the element to test
      * @return <code>true</code> if the given EndFeatureMembership represent an implicit feature

doc/content/modules/user-manual/pages/release-notes/2025.4.0.adoc

@@ -54,12 +54,22 @@ image::release-notes-gv-satisfy-requirement-usage.png[Satisfy Requirement Usage
 For example importing the following SysML file would now create a valid semantic model:
 
 ```
- action def ActionDef1 {
+action def ActionDef1 {
     first start;
     then action a1;
     then action a2;
 }
 ```
+- Improve textual export of `SuccessionAsUsage` by properly handle its _name_.
+For example exporting a model of an `ActionDefinition` containing two `ActionUsages` and a named `SuccessionAsUsage` would produce the following file:
+
+```
+action def ActionDef1 {
+    action a1;
+    action a2;
+    succession s1 first a1 then a2;
+}
+```
 
 == Dependency update