# Traceability and Cross-Layer Linking in SysML v2 Modeling (ESA Methodology)

**URL:** <https://forum.sensmetry.com/t/traceability-and-cross-layer-linking-in-sysml-v2-modeling-esa-methodology/248>\
**Category:** Questions / Help\
**Tags:** modeler, sysmlv2\
**Created:** [October 9, 2025, 7:10am UTC](https://forum.sensmetry.com/t/traceability-and-cross-layer-linking-in-sysml-v2-modeling-esa-methodology/248 "2025-10-09T07:10:05Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Susmitha\_Suresh](https://yyz2.discourse-cdn.com/flex008/user_avatar/forum.sensmetry.com/susmitha_suresh/32/131_2.png) [@Susmitha\_Suresh](https://forum.sensmetry.com/u/Susmitha_Suresh)\
**Post date:** [October 9, 2025, 7:10am UTC](https://forum.sensmetry.com/t/traceability-and-cross-layer-linking-in-sysml-v2-modeling-esa-methodology/248/1 "2025-10-09T07:10:05Z")

</div>

Hello,

I’m working on a project, that involves **SysML v2 modeling of a spacecraft subsystem** , and I’m following the **ESA SysML Solution Methodology** where the model is structured into distinct layers (Mission, System of Interest, Functional, Physical, Requirements, Verification, etc.).

My core challenge is **effectively linking and tracing information across these layers**.

**Specifically, how can I best represent the complete traceability chain within the SysML v2 model?** For example, I need to show:

1. How a **Mission Objective** is fulfilled by a specific **System Capability**.

2. How that Capability translates into a defined **Function**.

3. How that Function is ultimately **realized by the Physical Design** (components/structure).

4. And, crucially, which **Requirement** this entire chain satisfies.

**Is it possible to visually represent this traceability** (e.g., as a matrix, a graph, or a derived view) **and/or easily navigate through the model** (e.g., by clicking a requirement and tracing its fulfillment path down to the physical design, or vice versa)?

Any insights or best practices, particularly with respect to SysML v2’s new features or tool support in this context, would be greatly appreciated!

Reference: [https://indico.esa.int/event/386/contributions/6221/attachments/4264/6373/0935%20-%20esa%20mbse%20evolution%20from%20esa%20sysml%20toolbox%20to%20esa%20mbse%20solution.pdf](https://indico.esa.int/event/386/contributions/6221/attachments/4264/6373/0935%20-%20esa%20mbse%20evolution%20from%20esa%20sysml%20toolbox%20to%20esa%20mbse%20solution.pdf)

Thanks!

---

<div class="post-metadata">

**Author:** ![Simas\_Kaminskas](https://avatars.discourse-cdn.com/v4/letter/s/dbc845/32.png) [@Simas\_Kaminskas](https://forum.sensmetry.com/u/Simas_Kaminskas)\
**Post date:** [October 10, 2025, 8:30am UTC](https://forum.sensmetry.com/t/traceability-and-cross-layer-linking-in-sysml-v2-modeling-esa-methodology/248/2 "2025-10-10T08:30:27Z")

</div>

Hello Susmitha,

Thank you for you question.

You can try linking your information across different logic levels using `allocation` in SysML v2.  
You can find more information on this in the official SysML v2 documentation here: [SysML v2 documentation](https://github.com/Systems-Modeling/SysML-v2-Release/tree/master/doc)

To represent a specific requirement that satisfies the whole chain you can create a `requirement def` and then nest the `requirement` usage in the elements of this chain.

Once everything is connected you should be able to navigate your model easily by using references.

Best regards,  
Simas