-
Key: SYSML2-33
-
Status: open
-
Source: DEKonsult ( Mr. Hans Peter de Koning)
-
Summary:
Identify the implications of views on the model organization and how to mitigate circular dependencies.
Approaches to representing nested views
- Case 1: Specify view rendering for each element in the view (e.g., show nested parts as a tree view for some parts and interconnection view for others)
- Case 2: View exposes packages with views
- Case 3: View contains nested views
Example (representing nested parts tree). The default case is to apply the same rendering method to each element. In effect, the rendering method and filter is inherited by all elements in the view.
Case 1. Specify view rendering for each element in the view (e.g., show nested parts as a tree view for some parts and interconnection view for others)
Case 2. View exposes packages with views
Case 3. View contains nested views
-
Reported: SysML 2.0a1 — Wed, 26 Apr 2023 11:55 GMT
-
Updated: Wed, 10 Apr 2024 00:41 GMT
-
Attachments:
- nested-view-fig1.png 7 kB (image/png)
- nested-view-fig2.png 19 kB (image/png)
- nested-view-fig3.png 8 kB (image/png)
- nested-view-fig4.png 16 kB (image/png)
- nested-view-fig5.png 9 kB (image/png)
- nested-view-fig6.png 23 kB (image/png)
- nested-view-fig7.png 4 kB (image/png)
- nested-view-fig8.png 23 kB (image/png)
SYSML2 — Identify impact views on model organization
- Key: SYSML2-33
- OMG Task Force: Systems Modeling Language (SysML) 2.0 FTF