https://training-course-material.com/index.php?action=history&feed=atom&title=SysML_Package_DiagramSysML Package Diagram - Revision history2026-04-12T22:54:02ZRevision history for this page on the wikiMediaWiki 1.45.1https://training-course-material.com/index.php?title=SysML_Package_Diagram&diff=65280&oldid=prevFstachecki: /* Stakeholder, View and Viewpoint⌘ */2018-02-12T10:44:35Z<p><span class="autocomment">Stakeholder, View and Viewpoint⌘</span></p>
<p><b>New page</b></p><div>[[Category:SysML]]<br />
[[Category:private]]<br />
<br />
==SysML Package Diagram⌘==<br />
<!--<br />
===Named Element, Namespace⌘===<br />
*Named Element represents an element that '''may''' have a name and a visibility<br />
*Namespace is a named element that can own other named elements <br />
* Each named element may be owned by at most one namespace<br />
* Namespace provides a container for named elements<br />
* All the members of a '''namespace''' are distinguishable within it<br />
--><br />
===Package⌘===<br />
[[File:ClipCapIt-170907-112706.PNG]]<br />
* A Package is used to group elements, and provides a namespace for the grouped elements.<br />
* All the members of a namespace are '''distinguishable''' within it. A Packageable Element is a model element that may be owned directly by a Package.<br />
* The visibility of a packaged element (private or public) may be used to specify which elements can be imported into another package (default public)<br />
* A qualified name syntax:<br />
package name::element name<br />
====Package nesting⌘====<br />
[[File:ClipCapIt-160105-205328.PNG]]<br />
* Packages support package hierarchies.<br />
<br />
===Package relationship⌘===<br />
[[File:ClipCapIt-141024-152524.PNG]]<br />
* Some elements from package B depends on some elements from package A<br />
<br />
===Package Import, Access⌘===<br />
[[File:PackageImportAccess.png]]<br />
<br />
A package import is defined as a directed relationship that identifies a source package whose members are to be imported by a target<br />
namespace.<br />
<br />
Two types:<br />
* «import» for a '''public''' package import<br />
** transitive: if A imports B and B imports C then A indirectly imports C<br />
* «access» for a '''private''' package import<br />
** intransitive (elements are imported as private members of the target package)<br />
<br />
====Package Import Example 1⌘====<br />
[[File:PackageImportExample.png]]<br />
* elements in Types are imported to ShoppingCart, and then further imported to WebShop<br />
* elements of Auxiliary are only accessed from ShoppingCart, and cannot be referenced from WebShop<br />
====Package Import Example 2⌘====<br />
[[File:ClipCapIt-141024-161742.PNG]]<br />
<br />
===Model⌘===<br />
[[File:ClipCapIt-141024-154505.PNG]]<br />
* A Model is a description of a system - not only software and hardware but organizations and processes.<br />
* It describes the system from a certain viewpoint, for a certain category of stakeholders, and at a certain level of abstraction.<br />
* A Model is a Package.<br />
===Package diagram example⌘===<br />
[[File:ClipCapIt-160722-102822.PNG]]<br />
===Stakeholder, View and Viewpoint⌘===<br />
[[File:ClipCapIt-160725-103704.PNG]]<br />
* A '''stakeholder''' represents a role, group, or individual who has concerns that will be addressed by the View of the model.<br />
* A '''view''' is a representation of the system from defined viewpoint.<br />
* The '''viewpoint''' describes the point of view of a set of stakeholders, specifies conventions and rules for constructing and using a view.<br />
<!--<br />
• Viewpoint represents the stakeholder perspective<br />
• View conforms to a particular viewpoint<br />
– Imports model elements from multiple packages<br />
– Can represent a model query based on query criteria<br />
• View and Viewpoint consistent with IEEE 1471 definitions<br />
--><br />
====View and Viewpoint example⌘====<br />
[[File:ClipCapIt-160721-161651.PNG]]</div>Fstachecki