Icon class icon_class fas fa-quote-left icon_class_computed fas fa-quote-left Related content In general, the SysML DirectedFeature approach is more powerful and the notation is cleaner than UML provided/required Interfaces. Prefer SysML DirectedFeatures unless you have a really good reason to use Interfaces! Avoid mixing flow properties on the Type of a Port with directed features (operations and values); One distinguishes between "ports with flows" and "contract ports". Hybrid SUV example: provided/required DirectedFeatures (Block Definition Diagram) Hybrid SUV example: provided/required DirectedFeatures (Internal Definition Diagram) UML provided/required Interfaces vs SysML DirectedFeatures on Ports Conjugation in SysML-1.7 is Type-based: InterfaceBlock, ~InterfaceBlock, and DirectedFeature Source OMG Systems Modeling Language (SysML) 1.6 Copyright information About Object Management Group copyright in text extracts quoted from OMG specifications for educational purposes Snippet kind INFO SysML keywords DirectedFeature FeatureDirectionKind::provided FeatureDirectionKind::required FeatureDirectionKind::providedrequired FeatureDirectionKind Previous snippet Full quote A DirectedFeature indicates whether the feature is supported by the owning block (provided), or is to be supported by other blocks for the owning block to use (required), or both ... Next snippet (the owning block for features on types of proxy ports is the type of the block usage the proxy port is standing in for, which might be an internal part). Please visit now instead: SysML-1.7: 'A DirectedFeature indicates whether the feature is supported by the owning block (provided) for other connected blocks to use, or is to be supported by a connected block for the owning block to use (required), or both (providedRequired).' Related snippets The ~InterfaceBlock stereotype (shall be pronounced: "conjugated interface block") is a specialization of InterfaceBlock that has the same features as its original InterfaceBlock except that its DirectedFeatures and FlowProperties are reversed (conjugated Related snippets (backlinks) (the owning block for features on types of proxy ports is the type of the block usage the proxy port is standing in for, which might be an internal part). Using non-flow properties means to read or write them, and using behavioral features means to invoke them. Provided non-flow properties are read and written on the owning block, while required non-flow properties are read or written on an external block Provided behavioral features are invoked with the owning block as target, while required behavioral features are invoked with an external block as target (required). A DirectedFeature has the same notation as other non-flow properties and behavioral features with a feature direction prefix (prov | reqd | provreqd), which corresponds to one the FeatureDirectionKind literals “provided,” “required,” and “providedrequired Directed features can appear in compartments for the various kinds of properties and behavioral features. A DirectedFeature indicates whether the feature is supported by the owning block (provided) for other connected blocks to use, or is to be supported by a connected block for the owning block to use (required), or both (providedRequired). A providedRequired feature specifies a symmetric dependency between two connected blocks whereby a block’s internal use of such a feature is delegated to the connected block with the corresponding feature and conversely that block’s internal use of ... Visit also Visit also (backlinks) Flags
