Learn about Webel IT's new SysMLv2/MBSE Workshop Seminar course!
VIDEO: The Webel SysMLv2/MBSE course has landed! Take a quick tour!
Webel now has a SysMLv2 Online Self-Study course with self-test Quizzes!

Section: SysML-1.6 specification diagrams: 09 Ports and Flows

Icon class
icon_class
far fa-bookmark
icon_class_computed
far fa-bookmark
Tutorial
TRAIL: The SysML-1.6 Hybrid SUV sample and specification diagrams in MagicDraw/Cameo (with annotations) [UNDERGOING UPDATE to SysML1.7]
Start section here
Figure 9-1: Port Stereotypes

Slides in this section

If you want to navigate the entire section including the additional explanatory text click on the title link of the first slide to view the full slide page, then use the next links to move through the slide pages. If you just want to view the slide images only in sequence, click on any slide to view it larger in a viewer, then click again to move through each slide in this tutorial trail section.
Figure 9-1: Port Stereotypes
Figure 9-2: Stereotypes for Actions on Nested Ports
Figure 9-3: Stereotypes for Property Value Change Events
Figure 9-4: Provided and Required Features
Figure 9-5: Item Flow Stereotype
Figure 9-6: Usage example of ports with provided and required features
Figure 9-7: Usage example of proxy and full ports
Figure 9-8: Water Delivery association block
Figure 9-9: Internal structure of Water Delivery association block
Figure 9-10: Two views of Water Delivery connector within House block
Figure 9-11: Specializations of Water Client in house example
Figure 9-12: Plumbing association block
Figure 9-13: Internal structure of Plumbing association block
Figure 9-14: Water Delivery association block with internal Plumbing connector
Figure 9-15: Usage example of item flows in internal block diagrams
Figure 9-16: Usage example of item flow decomposition
Figure 9-17: Usage example of item flow decomposition
Next trail section
Section: SysML-1.6 specification diagrams: 10 ConstraintBlocks
SysMLv1: A 'part property' in SysMLv1 does not formally include 'port' (which is considered a special kind of property), even though the Port metaclass in UML2 extends Property and a 'port' may have 'composite' aggregation and be typed by a Block.
Webel: SysML1.7: Port contract matching is Feature-based, not Type-based. There's nothing particularly magical or special about use of an ~InterfaceBlock on a "conjugating" SysML Port, it's just a convenient way of managing one-to-one Feature matching!