Hybrid SUV example: provided/required DirectedFeatures (Block Definition Diagram)

Gallery
Tutorial
TRAIL: Webel's ultimate guide to Systems Modeling Language (v1) with MagicDraw/Cameo
Section
09:04: Ports and contracts
UML keywords
Port
SysML keywords
DirectedFeature
HSUV sample problem
DirectedFeature::featureDirection
FeatureDirectionKind
FeatureDirectionKind::provided
FeatureDirectionKind::required
InterfaceBlock
~InterfaceBlock
Slide kind
SysML Block Definition Diagram (BDD)
Now we explore a DirectedFeature example from the Hybrid SUV sample problem.
Click on the image to view it full size
We want to be able to make a specific connection between the compatible ports typed by an InterfaceBlock ICE and a conjugate ~InterfaceBlock ~ICE in an IBD, as shown next .
Up next
Hybrid SUV example: provided/required DirectedFeatures (Internal Definition Diagram)
Notes
[MODELLING, STYLE]{RECOMMENDED} Webel: SysMLv1: Prefer not show Port symbols on the boundary of Block symbols in BDDs, just list them in compartments. One can't connect them in a BDD anyway. Recommend only show Port symbols in IBDs.
[NAMING, POLICY]{STRICT} For SysML Blocks and InterfaceBlocks used to type Ports with contracts use the naming convention 'I_UpperCamelCase' [may be combined with acronymn conventions]
[ASSERTION, TIP] SysMLv1: You can't make connections in BDDs, only in IBDs. A BDD shows where connections MAY be made (as indicated by Associations), an IBD shows where specific connections HAVE been made in a specific context!
Snippets (quotes/extracts)
  [SysML-1.6] [SysML1.6: PREFER SysML1.7] 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 ...
  [SysML-1.6] Directed features can appear in compartments for the various kinds of properties and behavioral features.
  [SysML-1.7] 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
Related slides (includes other tutorials)
Figure D.18 - Defining Structure of Power Subsystem (PowerSubsystem Breakdown)
Figure D.19 - Internal Structure of the Power Subsystem (Internal Block Diagram)
Figure D.20 - Blocks Typing Ports in the Power Subsystem (ICE Port Type Definitions)
Figure D.23 - Elaborating Definition of Fuel Flow (Power Subsystem Fuel Flow Definition)
Related slides (backlinks, includes other tutorials)
Conjugation in SysML-1.7 is Type-based: InterfaceBlock, ~InterfaceBlock, and DirectedFeature
Visit also
Visit also (backlinks)