Logical SoI not considered in System Usecase

[MarkusAndres]

[userdoc/Functional Domain/System Use Case Viewpoint.md](../blob/main/src/userdoc/Functional Domain/System Use Case Viewpoint.md)

The system use case has no direct linkage to the logical SOI this has to be added. Additionally to allow dealing with use cases on different hierachical levels. An as well inside a system process it is not clear how the logical SoI can be involved via system use case.

[haarer]

Am 28. April 2025 22:49:06 MESZ schrieb MaRk ***@***.***>:

MarkusAndres created an issue (GfSE/SAF-Specification#112) [userdoc/Functional Domain/System Use Case Viewpoint.md](../blob/main/src/userdoc/Functional Domain/System Use Case Viewpoint.md) The system use case has no direct linkage to the logical SOI this has to be added. Additionally to allow dealing with use cases on different hierachical levels. An as well inside a system process it is not clear how the logical SoI can be involved via system use case. -- Reply to this email directly or view it on GitHub: #112 You are receiving this because you are subscribed to this thread. Message ID: ***@***.***>

In my opinion the relationship ist well defined, but it might be non obvious to users. While there is no direct relation, the SOI is tied to the use case, because the SOI is part of the context. And the context is tied to the use case. Any relation binding the system to the use case would have to be derived strictly from those facts. In order to make it directly visible, in a profile implementation the relationship could be computed by a derived property on the use case stereotype.

…

-- Gruß, Alexander

[parkaneric]

Implement as derived property for use cases. Profil implementation depending on particular tool (restrictions).

[haarer]

propose to close this