Webel's "super-relational" Note pages!

A Note is a short categorised statement, claim, policy, tip, or issue tracker Throughout this site, content is often related to supporting Notes, and each Note page links back to the content pages that reference it! The Note and Snippet concepts are very closely related and they support each other.
Look for "super-relational" Note page links at the bottom of most content pages!
Note kind Note Spec tag UML keywords SysML keywords Keywords
CAPABILITY, FEATURE, TOOL MagicDraw/Cameo: Supports embedding of one or more Diagrams in another via the Diagram Overview feature. Awesome! MagicDraw UML, MagicDraw SysML, Cameo Systems Modeler
ISSUE Webel vs SysML-1.6: There is no «port» stereotype keyword for Port or Property in UML-2.5.1 or SysML-1.6, it is introduced as a custom (user-defined) stereotype keyword here only to mimic the spec Figure 9-8. SysML-1.6 «keyword», Port SysML specification figure
ISSUE SysML-1.6: does not leverage redefinition of 'sp:Surface' on 'Figure 9-7: Usage example of proxy and full ports' (earlier versions of the spec did). And does not show direction of flows. SysML-1.6 Property::redefinedProperty SysML specification figure, FlowProperty
ISSUE SysML-1.6: 'Figure 9-6: Usage example of ports with provided and required features' does not expose any directed features. It would be more instructive if the ports on the diagram used the capability to show the underlying directed features of the blocks SysML-1.6 DirectedFeature
ISSUE SysML-1.6: Missing correct diagram for 'Figure 9-5: Item Flow Stereotype' SysML-1.6 ItemFlow
MagicDraw/Cameo 19SP3: Does not yet support AddFlowPropertyValueOnNestedPortAction AddStructuralFeatureValueAction AddFlowPropertyValueOnNestedPortAction Cameo Systems Modeler, MagicDraw SysML
ISSUE, TOOL MagicDraw/Cameo 19SP3: enumeration 'FeatureDirection' should be 'FeatureDirectionKind' (reflects known error in older SysML specification versions) FlowDirectionKind Cameo Systems Modeler, MagicDraw SysML
ISSUE MagicDraw/Cameo: the keyword for PropertySpecificType is «PropertySpecificType» not «pst» PropertySpecificType, «pst» Cameo Systems Modeler, MagicDraw SysML
ISSUE SysML-1.6: Figure 8-17: Multiplicity of rollBarBR should be [0] not [*] in 'Vehicle Model 2' SysML-1.6 multiplicity, Property::redefinedProperty SysML specification figure, Block, BoundReference
ISSUE SysML-1.6: Figure 8-17: EndPathMultiplicity is applied to 'rollBarBR' instead of 'lugBoltBR' of 'Vehicle Model 2' SysML-1.6 multiplicity, Property::redefinedProperty SysML specification figure, Block, BoundReference, EndPathMultiplicity
ISSUE SysML-1.6: Figure 8-17: Multiplicity of 'lugBoltBR' of 'Vehicle Model 1' should be [6] not [6..8] SysML-1.6 multiplicity, Property::redefinedProperty SysML specification figure, Block, BoundReference
ISSUE SysML-1.6: Figure 8-17: Multiplicity of 'rollBarBR' in 'Vehicle Model 1' should be [1] not [*] and it has no redefined type for the 'light roll bar' SysML-1.6 multiplicity, Property::redefinedProperty SysML specification figure, Block, BoundReference
ISSUE SysML-1.6: Figure 8-17: Multiplicity of 'cylinderBR' in 'Vehicle Model 1' should be [4] not [*] SysML-1.6 multiplicity, Property::redefinedProperty SysML specification figure, Block, BoundReference
A BindingConnector may optionally be indicated by an '=' sign or the keyword «equal» BindingConnector
NAMING, TOOL MagicDraw/Cameo: SysMLv1.x: ValueType naming: The ISO-80000 libraries use 'lower case' (sometimes with spaces for compound units and/or with [scaling] indicated in square brackets). ValueType, QuantityKind IEC80000, SI, MagicDraw SysML, Cameo Systems Modeler, ISO-80000, compound unit
NAMING, POLICY SysMLv1.x: ValueType naming: The Webel convention is 'UpperCamelCase' (a.k.a. PascalCase). ValueType, QuantityKind Webel Best Practice
CONVENTION, NAMING, POLICY Webel: SysMLv1.x: AVOID (where possible) ValueType names that are the same as the name of units or unit symbols Unit Webel Best Practice
ISSUE SysML-1.6: Use of ValueTypes named like units in Figure 8-12 and Figure 8-14 is inconsistent w.r.t. some other specification diagrams and examples (but not necessarily wrong) SysML-1.6 ValueType
ISSUE SysML-1.6: Typo: Figure 8-12 'diamter' should be 'diameter' SysML-1.6
TIP The UML multiplicity range notations '0..*' and '*' are completely equivalent UML-2.5.1 multiplicity, MultiplicityElement, MultiplicityElement::/lower, MultiplicityElement::/upper, LiteralUnlimitedNatural, *
CAVEAT, TOOL UML4SysML is a specification abstraction (concept) only, it does not find direct expression (such as via a namespace) in tools like MagicDraw/Cameo SysML-1.6 UML4SysML Cameo Systems Modeler, MagicDraw SysML
CAVEAT, DISPLAY, TOOL MagicDraw/Cameo: Does not seem to support showing a trailing colon ':' in labels of Properties or Connectors that are untyped OR are typed by anonymous Classes, Blocks, or Associations. (The notation is used in some SysML specification diagrams.) Property, label, Connector MD:PartProperty, part property, block property MagicDraw SysML, Cameo Systems Modeler
ISSUE SysML-1.6: Typo in figure name 'Figure 4-2: SysML Extension of UMLFigure' SysML-1.6 SysML specification figure
DISPLAY, STYLE, TIP Webel recommends (usually) display the header of a Package, Model, ModelLibrary, or Profile in the 'tab' (rather than 'top') Package, Model, ModelLibrary, Profile MagicDraw UML, MagicDraw SysML, Cameo Systems Modeler, Webel Best Practice
ISSUE SysML-1.6 Typo 'Acitivies' in Figure 4-3: SysML Package Structure SysML-1.6
TIP Place your SysML-1.6 ~InterfaceBlock conjugation under the 'original' InterfaceBlock (i.e. make the original the containment owner). ~InterfaceBlock, conjugation
CAPABILITY, FEATURE, TIP, TOOL MagicDraw/Cameo: You can edit context-specific values (initial values) directly in an IBD by using the context menu item Tools > Define Context Specific Initial Values on appropriate blocks; once activated you can edit the values directly like Slot values context-specific values, initial values, initialValues compartment, SysML Internal Block Diagram menu item
ISSUE SysML-1.6: Spec Figure D.41 refers to 'em:ElectricalMotor' inconsistent w.r.t. 'emg:ElectricalMotorGenerator' in D.18 and allocation tables. SysML-1.6 HSUV sample problem
ISSUE SysML-1.6: Spec Figure D.41 refers to 't:Transmission' not 'trsm:Transmission', inconsistent w.r.t. D.18 and allocation tables (with impact on some connector names). SysML-1.6 HSUV sample problem
ISSUE Some Connectors 'b-l' and 'i-l' shown in Figure D.17 are missing in spec Figure D.41, and some 'c-p' and 'bk-p' are named inconsistently w.r.t 'p-c' and 'p-bk' in D.17 SysML-1.6 HSUV sample problem
ISSUE SysML-1.6: Spec Figure D.41 refers to 'i:Interior' not 'i:InteriorSubsystem', inconsistent w.r.t. Figure D.16. SysML-1.6 HSUV sample problem
DISPLAY, FEATURE, TIP, TOOL MagicDraw/Cameo: To show the type of initialValues (context-specific values) use the display option Show Slot Type compartment, Slot context-specific values, initial values, initialValues compartment MagicDraw SysML, Cameo Systems Modeler
ASSERTION, NAMING, WARNING The SysML block compartment name 'initialValues' for what are really "context-specific values" is confusing - even completely misleading; please just think of them as 'contextValues' (and initial values as a special context case) SysML-1.6 Parameter::defaultValue, compartment initialValues compartment, contextValues compartment, context-specific values, initial values
ISSUE SysML-1.6: The allocation from ObjectNode 'driveCurrent' in Figure D.38 to itemFlow 'i1' on the Connector in Figure D.39 does not appear in the allocation table Figure D.40; Instead there is an allocation from an ObjectFlow 'o6' to the Connector 'epc-emg' SysML-1.6 ObjectNode, ObjectFlow, Connector HSUV sample problem, ItemFlow, Allocate, allocation, «allocate»
ISSUE, TOOL MagicDraw/Cameo: 19SP3: Callout of allocatedFrom on Connector vs ObjectFlow shows «decisionInputFlow» not «objectFlow» keyword Connector, callout, ObjectFlow, DecisionNode::decisionInputFlow Allocate, allocation, «allocate» MagicDraw SysML, Cameo Systems Modeler
ISSUE, TOOL MagicDraw/Cameo 19SP3: Can't callout from ItemFlow on Connector, the Note handle pulls from the Connector not the ItemFlow Connector, callout, Note, handle ItemFlow MagicDraw SysML, Cameo Systems Modeler
DISPLAY, TIP MagicDraw/Cameo: The display option Apply SysML Callout Style shows elements with their Metaclass or Stereotype keywords and no vendor-specific icons callout MagicDraw SysML, Cameo Systems Modeler, Systems Modeling Language, SysML
ISSUE, TIP, TOOL MagicDraw/Cameo: HOWTO redisplay the name and type of a SysML ItemFlow on a Connector if it vanishes (such as when the Connector is redrawn) Connector, InformationFlow, InformationFlow::conveyed, Classifier, NamedElement::name, Type ItemFlow, ItemFlow::itemProperty MagicDraw SysML, Cameo Systems Modeler
NAMING, VARIATION The Webel trail versions of the Activity Diagrams D.36 and D.38 use the name 'transMode' for the output Parameter and corresponding ActivityParameterNode (consistent with the spec figure D.38) NOT 'transMode_imported' (as in spec figure D.36) Parameter, ActivityParameterNode HSUV sample problem
CAVEAT, DISPLAY, ISSUE, TOOL MagicDraw/Cameo 19SP3: If Continuous or Discrete are applied to the underlying Parameter of an InputPin or an OutputPin the keywords «continuous» or «discrete» can't be displayed Parameter, Pin, InputPin, OutputPin Continuous, «continuous», Rate, «rate», Discrete, «discrete» MagicDraw SysML, Cameo Systems Modeler
ISSUE, STYLE In the Webel trail versions of the SysML-1.6 spec sample Figure D.38, the alignment of ObjectNode symbols over the ActivityParameterNode boundaries is completely contrived, please DO NOT mimic it; please use explicit Pins instead! SysML-1.6 elided Pin notation, ObjectNode HSUV sample problem, AllocateActivityPartition MagicDraw SysML, Cameo Systems Modeler
DISPLAY, FEATURE, TIP, TOOL MagicDraw/Cameo 19SP3: if Continuous or Discrete are applied to the Parameter of an ActivityParameterNode the keywords «continuous» or «discrete» can be optionally displayed on the ActivityParameterNode symbol ActivityParameterNode, Parameter Continuous, «continuous», Rate, «rate», Discrete, «discrete» MagicDraw SysML, Cameo Systems Modeler
DISPLAY, TOOL MagicDraw/Cameo: If the underlying Parameter of an InputPin or OutputPin on a CallBehaviorAction or CallOperationAction is set to streaming, the indicator {stream} optionally displays on the Pin Pin, InputPin, OutputPin, Activity, Parameter, Behavior::inputParameters(), Behavior::outputParameters(), Parameter::isStreaming SysML Activity Diagram MagicDraw SysML, Cameo Systems Modeler
ISSUE MagicDraw/Cameo 19SP3: Continuous and Discrete have metaclass [ActivityEdge, ObjectNode, Parameter] not just [ActivityEdge, Parameter] (via Rate), so may be applied directly to Pin and ActivityParameterNode ActivityEdge, Parameter, CallBehaviorAction, CallOperationAction, InputPin, OutputPin, Pin Continuous, «continuous», Rate, «rate» MagicDraw SysML, Cameo Systems Modeler
ISSUE SysML-1.6: Each «continuous» Parameter (of each corresponding ActivityParameterNode) in Figure D.36 and Figure D.38 should be set to be streaming, because the Continuous Stereotype has a Generalization to Rate SysML-1.6 Parameter::isStreaming, Parameter Continuous, «continuous», Rate, «rate»
ISSUE SysML-1.6: The spec version of Figure D.37 does not show the breakdown from the top-level Accelerate activity SysML-1.6 Activity
DISPLAY, ISSUE, TOOL, WARNING Webel recommends when using MagicDraw/Cameo: AVOID the "elided Pin" abstract ObjectNode notation on Activity Diagrams, use explicit Pins! Pin, ObjectNode MagicDraw UML, MagicDraw SysML, Cameo Systems Modeler
ISSUE, TOOL, WARNING MagicDraw/Cameo: DO NOT use the ObjectNode menu item on Activity Diagrams ever! Pin, ObjectNode, ObjectFlow, ActivityEdge MagicDraw UML, MagicDraw SysML, Cameo Systems Modeler
ISSUE, TOOL [BUG: FIXED]: MagicDraw/Cameo SP193: Offers the display option to show the name and type label inside a Pin symbol, but it does not seem to work. [FIXED since 2022xRefresh2] Pin Cameo Systems Modeler, MagicDraw UML, MagicDraw SysML
DISPLAY, TIP Prefer the Name Display Mode 'both' on CallBehaviorAction symbols (rather than 'Show Action Name', 'Show Behavior Name', or 'Show Both or Behavior Name') Action, Behavior, CallBehaviorAction Webel Best Practice, Cameo Systems Modeler, MagicDraw UML, MagicDraw SysML
ISSUE, TOOL MagicDraw/Cameo: ERROR: Incorrectly uses 2 ObjectFlow edges and a CentralBufferNode in place of "elided Pin notation" instead of an abstract ObjectNode symbol and 2 arrow symbols (that are supposed to represent together 2 Pins and 1 ObjectFlow edge) Activity, Action, Pin, ActivityEdge, ObjectFlow, ObjectNode, CentralBufferNode, elided Pin notation Cameo Systems Modeler, MagicDraw SysML, MagicDraw UML
CAVEAT, DISPLAY, STYLE MagicDraw/Cameo: Does not support ConstraintNote: Can't callout the Constraint of the ConstraintBlock of a constraint property into a Note on a Parametric Diagram (show on the constraint property symbol instead) Constraint ConstraintBlock, constraint property, ConstraintNote MagicDraw SysML, Cameo Systems Modeler
ISSUE SysML-1.6: Figure D.32 does not have 'incline' value property connected SysML-1.6 SysML specification figure, BindingConnector, value property
CONVENTION, NAMING, STYLE Avoid punctuation in Property names (except when used to "quote text"). You can usually avoid underscores in Property names (even if they are used in the Type name) if you can "Trust the Type"! Property Webel Best Practice
ISSUE SysML-1.6: Figure D.32 aggregation kind on 'delta-t' is inconsistent w.r.t. Figure D.26 SysML-1.6 AggregationKind SysML specification figure
CAPABILITY, FEATURE, STYLE, TIP TIP: UML/SysML: MagicDraw/Cameo: Consider showing the constraint parameter name and type label inside the small rectangular parameter symbol on SysML Parametric Diagrams. Dr Darren swears by it! PackageImport constraint parameter, MD:ConstraintParameter, SysML Parametric Diagram MagicDraw SysML, Cameo Systems Modeler, Webel Best Practice
ISSUE SysML-1.6: Figure D.31 has constraint parameter 'vc' on ':CapacityEquation', which is inconsistent w.r.t. parameters 'V1', 'V2', 'V3' and constraint {pcap=Sum(Vi)) shown in Figure D.26. SysML-1.6 constraint parameter, ConstraintBlock, «constraint»
CAVEAT, ISSUE, TIP, TOOL MagicDraw/Cameo 19SP3: Does not seem to directly support compartment for decomposition of Views as properties of Views (but one can create properties in an IBD and they will show in the 'attributes compartment') Property View MagicDraw SysML, Cameo Systems Modeler
CAPABILITY, TOOL MagicDraw/Cameo: Offers a customised Views and Viewpoints Diagram type with dedicated menus and some Viewpoint types. View, Viewpoint, Expose MagicDraw SysML, Cameo Systems Modeler
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 Expose, View, Viewpoint MagicDraw SysML, Cameo Systems Modeler
CAVEAT, ISSUE SysML-1.6: The spec sample diagrams D.27 has Expose relationships to ValueType, they should be to value properties. SysML-1.6 HSUV sample problem, View, Viewpoint
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. SysML-1.6 HSUV sample problem, View, Viewpoint
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) Expose
Prefer owner path indicators over Package containment operators (which are fragile). Element::owner, owner path display
NAMING, STYLE Webel: "Trust the Metaclass or Stereotype" of an Element to indicate what type of element it is (you don't have to repeat it in the name) NamedElement::name Webel Best Practice
NAMING Webel: SysML: You don't need to call every ConstraintBlock a 'SomethingEquation' NamedElement::name ConstraintBlock Webel Best Practice, mathematics, equation
ISSUE SysML-1.6: Figure D.25 has the type Fuel for both an in Port and an out Port on FuelTankAssembly (and it is not ideal to have same name as the Classifier that flows) SysML-1.6 Port HSUV sample problem, FlowProperty
CAPABILITY, FEATURE, TIP, TOOL 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 DirectedRelationship, DirectedRelationship::/source, DirectedRelationship::/target Cameo Systems Modeler, MagicDraw SysML, MagicDraw UML
ISSUE SysML-1.6: Need a Connector from fuel:Fuel to :FuelPump in 'Figure D.25 Detailed Internal Structure of Fuel Delivery Subsystem (Internal Block Diagram)' SysML-1.6
CONVENTION, NAMING Webel: DO NOT name the Type (Block or InterfaceBlock) of a Port with a flow the same as the name of the 'Stuff' that flows through it; use the Webel 'F_Stuff' convention! Port FlowProperty, InterfaceBlock, ~InterfaceBlock, Block Webel Best Practice
TOOL MagicDraw/Cameo: HOWTO Create a nested Property "shortcut" symbol with a dot property path in a Parametric Diagram or Internal Block Diagram Property multi-level property path, pathname dot notation, nested Property, "shortcut" MagicDraw SysML, Cameo Systems Modeler
ISSUE, NAMING SysML-1.6: Naming inconsistencies 'Figure D.24 is a parametric diagram showing how fuel flowrate is related to FuelDemand and FuelPressure value properties.' SysML-1.6 HSUV sample problem
ISSUE SysML-1.6: Typo: 'Binding connectors, as defined in Clause 8 are used' SysML-1.6
ISSUE SysML-1.6: Figure D.24 does not explicitly show «equal» keyword or '=' on BindingConnectors [suggest this might be good to show this notation on at least one HSUV sample diagram] SysML-1.6 BindingConnector, «equals»
DEPRECATION, ISSUE SysML-1.6: Figure D.23 has FuelFlow redundantly stereotyped by the DEPRECATED «flowSpecification» SysML-1.6 DEPRECATED:FlowSpecification
ISSUE SysML-1.6: The provided features are in fact not indicated on the spec version of Figure D.20 (this was addressed by OMG JIRA SYSML17-224 'Features that are not denoted as a DirectedFeature are implicitly provided features'') SysML-1.6
ISSUE SysML-1.6: References to 'ecu:PowerControlUnit' should be 'pcu:PowerControlUnit' SysML-1.6 HSUV sample problem, SysML specification figure
ISSUE SysML-1.6: Figure D.19: It's not clear why 'Port:~FuelTankFitting' (an ~InterfaceBlock conjugation port) does not match 'Port:ICEFuelFitting' SysML-1.6 Port HSUV sample problem, ~InterfaceBlock, conjugation
ISSUE, TOOL MagicDraw/Cameo 19SP3: Does not yet handle Feature-wise validation of provided/required DirectedFeature contracts (it only handles them at the level of entire Block types). Webel asserts the spec is inconsistent w.r.t. ProxyPort connection compatibility. Feature, BehavioralFeature, Reception, Operation, StructuralFeature, Property provided Feature, required Feature, DirectedFeature MagicDraw SysML, Cameo Systems Modeler
ASSERTION, WISHLIST SysMLv1.6 Provided/required DirectedFeature contracts for ProxyPorts SHOULD be satisfiable Feature-wise (including as subsets of Features) not necessarily just at the level of entire Blocks (types)! [See also the SysMLv1.7 spec changes.] SysML-1.6 Feature, BehavioralFeature, Reception, Operation, StructuralFeature, Property provided Feature, required Feature
ISSUE SysML-1.6: Figure D.19 has an unnecessary Comment with the name of the 'ctrl' Port SysML-1.6 HSUV sample problem
NAMING, POLICY DO NOT use spaces in Property names or Class/Block names! If you want to communicate familiar names of elements within an organisation use a custom stereotype and tagged values (such as 'aka')! NamedElement::name, Property, Class, Connector Block Webel Best Practice
CONVENTION, NAMING, STYLE FlowProperty naming. Use anonymous or just 'i' for in, 'o' for out, and 'io' for inout. "Trust the Type". For conjugation ~InterfaceBlock use 'o' for in, 'i' for out, and 'oi' for inout. FlowProperty, FlowDirectionKind, FlowDirectionKind::in, FlowDirectionKind::inout, FlowDirectionKind::out Webel Best Practice
CAPABILITY, FEATURE, STYLE, TIP TIP: MagicDraw/Cameo: Consider showing the Port name and type label inside the Port symbol! CAVEAT: This loses the direction indicators on Ports typed by Blocks with flow properties (but is fine if ItemFlows show the direction, or for "contract ports"). Port MagicDraw SysML, Cameo Systems Modeler, Webel Best Practice
MODELLING, STYLE 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. SysML-1.6, SysML-1.7 Port SysML Block Definition Diagram Webel Best Practice, SysMLv1, Systems Modeling Language, SysML
CAPABILITY, DISPLAY, TOOL The MagicDraw/Cameo feature "Enable Parts Compartments" really means "Enable SysML Compartments" Port Cameo Systems Modeler, MagicDraw SysML
CAPABILITY, DISPLAY, TOOL MagicDraw/Cameo: the (not so well named) "Enable Parts Compartment" feature on Ports is highly recommended and can make diagrams much easier to read. Port Cameo Systems Modeler, MagicDraw SysML
DISPLAY, STYLE SysML directed features displayed on Port symbols are often far clearer than UML-style provided/required Interface "ball (lollipop) and socket" notation SysML-1.6 provided Interface, required Interface, ball-and-socket, InterfaceRealization, Usage directed Feature
ASSERTION SysML: Typing a Port by an InterfaceBlock or ~InterfaceBlock does NOT imply that the Port is a ProxyPort (but ProxyPort must be typed by an InterfaceBlock or ~InterfaceBlock) SysML-1.6 Type, TypedElement, TypedElement::type InterfaceBlock, ~InterfaceBlock, ProxyPort, "standard" Port, FullPort
POLICY For Blocks and Interface blocks with one or more FlowProperty items, choose a direction convention and use it across one project. FlowProperty, FlowDirectionKind, FlowProperty::direction, FlowDirectionKind::in, FlowDirectionKind::out, Block, InterfaceBlock, ~InterfaceBlock
NAMING, POLICY DO NOT name ports with first letter capital (like 'Port'), DO NOT name ports 'port' (except for educational illustration), and DO NOT use port names that do not indicate a role. Port Webel Best Practice
ISSUE SysML-1.6: Figure D.19 Internal Structure of the Power Subsystem (Internal Block Diagram): Connector 'acl-ecu' and 'bkp-ecu' should be 'acl-pcu' and 'bkp-pcu' SysML-1.6 Connector HSUV sample problem, SysML Internal Block Diagram
CAPABILITY, FEATURE, TIP, TOOL In MagicDraw/Cameo an assigned stereotype of a Classifier that types an instance-like element (such as a part Property) "shines through" unless it has an instance-level stereotype assigned. This is sometimes called a "secondary stereotype". Diagram, Property, symbol, Stereotype part property MagicDraw UML, MagicDraw SysML, Cameo Systems Modeler, translucency, secondary stereotype, SysML, Systems Modeling Language, UML, Unified Modeling Language
CAPABILITY, FEATURE, TIP In MagicDraw/Cameo if the Type of a Property has a Composite Structure Diagram or Internal Block Diagram defined it will act as the default hyperlink target for the Property Diagram, Property, symbol part property MagicDraw UML, MagicDraw SysML, Cameo Systems Modeler
CAPABILITY, FEATURE, TIP In MagicDraw/Cameo one can just drag the IBD or BDD of a Block from the model browser onto parts that are typed by that Block to make them the default hyperlink target for that part (so one can just "open the parts up" recursively to navigate the system). Diagram, Property, symbol part property MagicDraw UML, MagicDraw SysML, Cameo Systems Modeler
ISSUE It's not clear that the «domain» block 'AutomotiveDomain' is the best choice of owner for BDD Figure D.16, the «system» block 'Hybrid SUV' might be better.
CAVEAT, DISPLAY, STYLE, WARNING MagicDraw/Cameo tool support for Association composition "trees" is not good, and they end up being fiddly to maintain (and they can also cause issues for InformationFlows). Avoid them! Association, InformationFlow Webel Best Practice, MagicDraw UML, MagicDraw SysML, Cameo Systems Modeler
DISPLAY, STYLE, TIP As an alternative to composition Association "trees" consider instead using symbol resize to visually "bracket" composed items (can however be a bit fiddly). Association Webel Best Practice
CAVEAT, DISPLAY, TOOL HSUV trail slide: Figure D.4: IBD: Could not show Connector typed by an anonymous Association as 'connectorName:' with trailing colon Association, Connector, Type HSUV sample problem Cameo Systems Modeler, MagicDraw SysML, MagicDraw UML, anonymous
ISSUE SysML-1.6: For the Connectors in Figure D.4 to be typed by the implied anonymous Associations need define them in Figure D.15 (or elsewhere) between 'HybridSUV' and: 'Driver', 'Maintainer', 'Passenger', 'Baggage', 'Environment'. SysML-1.6 Association, Connector, Type HSUV sample problem