Figure D.27 - Establishing a Performance View of the User Model (Package Diagram)

Gallery
Tutorial
TRAIL: The SysML-1.6 Hybrid SUV sample and specification diagrams in MagicDraw/Cameo (with annotations) [UNDERGOING UPDATE to SysML1.7]
Section
Section: SysML-1.6: HSUV sample
SysML keywords
View
Viewpoint
SysML Package Diagram
Stakeholder
Slide kind
SysML Package Diagram
Click on the image to view it full size
SysML-1.6: The View and Viewpoint spec sample diagrams D.27, D.28, D.29 and D.30 have multiple known issues; the trail versions here on this site are only placeholders until new spec versions are available once SysML-1.7 is released.
A quick list for D.27:
SysML-1.6: The spec sample diagrams D.27 has Expose relationships to ValueType, they should be to value properties.
D.27 Customer has 1 concern listed; D.28 has 2
The View Hybrid SUV Performance should be Performance View for consistency with Figure D.3
Inconsistent ownership of elements by the top-level Package
Package name Hybrid SUV Model is inconsistent w.r.t. Figure D.3
The View name Hybrid SUV Performance is inconsistent w.r.t. Figure D.3
The View name SUV Functional View is inconsistent w.r.t. Figure D.3
Yes, there are a lot of Expose relationships. Consider these alternatives:
Showing lots of Expose relationships can be unwieldy! Consider instead just showing them in a compartment once they have been created (then remove the relationships visually from the diagram)
MagicDraw/Cameo: you can make relationships between elements that are not visible in one diagram using the Relations section of the specification dialog for an element
Can't find the Expose relationship in a Package Diagram?
MagicDraw/Cameo: To access the Expose relationship use a View and Viewpoints Diagram (non-normative) or create a Dependency in a Package Diagram then use: Refactor > Convert To > Expose
MagicDraw/Cameo: Offers a customised Views and Viewpoints Diagram type with dedicated menus and some Viewpoint types.
Up next
Figure D.28 - Defining Requirements and VnV viewpoints (Package Diagram)
Notes
[CAVEAT, ISSUE] SysML-1.6: The spec sample diagrams D.27 has Expose relationships to ValueType, they should be to value properties.
[CAVEAT, ISSUE] SysML-1.6: The View and Viewpoint spec sample diagrams D.27, D.28, D.29 and D.30 have multiple known issues; the trail versions here on this site are only placeholders until new spec versions are available once SysML-1.7 is released.
[DISPLAY, TIP, TOOL] Showing lots of Expose relationships can be unwieldy! Consider instead just showing them in a compartment once they have been created (then remove the relationships visually from the diagram)
[TIP, TOOL] MagicDraw/Cameo: To access the Expose relationship use a View and Viewpoints Diagram (non-normative) or create a Dependency in a Package Diagram then use: Refactor > Convert To > Expose
[CAPABILITY, TOOL] MagicDraw/Cameo: Offers a customised Views and Viewpoints Diagram type with dedicated menus and some Viewpoint types.
Snippets (quotes/extracts)
  [SysML-1.6] Figure D.27 shows the user-defined Performance Viewpoint, and the elements that populate the HSUV specific PerformanceView. The PerformanceView itself may contain a number of diagrams depicting the elements it contains.
  [SysML-1.6] A stakeholder represents a role, group, or individual who has concerns that will be addressed by the View of the model.
  [SysML-1.6] A Stakeholder stereotype can only be applied to UML::Actor or UML::Class which are not a UML::Association.
  [SysML-1.6] The expose relationship relates a view to one or more model elements. Each model element is an access point to initiate the query.
  [SysML-1.6] The view and the model elements related to the view are passed to the constructor when it is invoked. The method describes how the exposed elements are navigated to extract the desired information.
Related slides (includes other tutorials)
Related slides (backlinks, includes other tutorials)
SysML View and Viewpoint - metamodel
View and Viewpoint example with «Create» method
Visit also
Visit also (backlinks)