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
ASSERTION, TIP The «Subsystem» stereotype for UML Components has nothing to do with the non-normative SysML «subsystem» stereotype for Blocks Component, «Subsystem» Block, «subsystem»
PROPOSAL Dr Darren of Webel has always opposed the exclusion of the obviously useful UML Artifact from SysML (but in MagicDraw and Cameo you can sneak it in anyway). After all, systems engineers do use documents quite a bit. Artifact document-driven engineering
ASSERTION The SysML non-normative extended requirements are NOT offered as the ultimate set of requirements categories or requirements fields, but they are highly usable and can be easily adapted. SysML-1.6 AbstractRequirement, Requirement, ExtendedRequirement, VerificationMethodKind, RiskKind, «extendedRequirement», «functionalRequirement», «interfaceRequirement», «performanceRequirement», «physicalRequirement», «designConstraint»
TIP, TOOL MagicDraw/Cameo: Learn how to effectively use and customise the powerful table, matrix, and relation map diagrams and how to create custom queries, implied relations, and custom properties. It will open up a whole new world of enjoyable power modelling! Cameo Systems Modeler, MagicDraw UML, MagicDraw SysML
CAPABILITY, FEATURE, TOOL MagicDraw/Cameo can parse the 'text' field of some mathematical Requirements and populate the constraint (and also then the constraint parameters) of a ConstraintBlock that refines a Requirement (your mileage varies). Constraint Requirement, ConstraintBlock, constraint parameter, Refine mathematics, equation
CONVENTION, FEATURE, TIP, TOOL MagicDraw/Cameo: The default 'Implied Satisfy' relation will claim a Requirement is satisfied by any direct composite aggregation parent Block or composite aggregation ancestor Block of a part property Satisfy, Block, part property MagicDraw SysML, Cameo Systems Modeler, MagicDraw implied relationships, dependency matrix
DISPLAY, FEATURE, TIP, WARNING MagicDraw/Cameo: In a Dependency Matrix the mode 'Show Element = All' can lead to very large matrices (but it enables you to interactively create relationships for elements that don't yet have any). MagicDraw SysML, MagicDraw UML, MagicDraw implied relationships, Cameo Systems Modeler, dependency matrix
PROPOSAL Webel has suggested primary/replica as an alternative to master/slave terminology for the SysML Copy relationship in future SysML versions SysML-1.6 AbstractRequirement::/master, Copy, Requirement
TIP, TOOL MagicDraw/Cameo does not explictly support tracking of satisfaction and verification of composite/compound requirements, but the "implied relations" facility can help. Satisfy, Verify, AbstractRequirement::/satisfiedBy, AbstractRequirement::/verifiedBy MagicDraw implied relationships, MagicDraw SysML, Cameo Systems Modeler
PROPOSAL Webel has suggested that SysMLv2 should support verification of each individual claim of more than one Element helping to Satisfy a Requirement. SysML-1.6 SysMLv2, Requirement, Satisfy, Verify, TestCase, «testCase» requirements engineering, test engineering
CONVENTION, NAMING, POLICY The name of a «testCase» Behavior may be verbose and may use natural language, but should always start with a Capital letter. Behavior, Activity, Interaction, NamedElement, NamedElement::name TestCase, «testCase» Webel Best Practice
CAPABILITY, DISPLAY, FEATURE, TIP MagicDraw/Cameo: A Requirement may appear on many kinds of such as a Block Definition Diagram or Package Diagram, not just a Requirement Diagram Requirement, AbstractRequirement, SysML Requirements Diagram, SysML Block Definition Diagram, SysML Package Diagram Cameo Systems Modeler, MagicDraw SysML
ISSUE MagicDraw/Cameo 19SP3: uses PascalCase instead of lowerCamelCase on some SysML compartment names MagicDraw SysML, Cameo Systems Modeler
ISSUE SysML-1.6: AbstractRequirement: direction of /tracedTo wrong in Attributes description AbstractRequirement, AbstractRequirement::/tracedTo
NAMING, STYLE Webel has a proposal for clearly revealing anonymous typed elements in SysML callouts and on derived Properties from operation queries. NamedElement::name, Type, TypedElement, TypedElement::type block property, value property, part property, AbstractRequirement::/satisfiedBy, AbstractRequirement::/tracedTo, Satisfy, Trace
NAMING, STYLE SysML: Non-anonymous (concise please) block property names and port names may help a little in tracing participation of properties and ports in requirements relationships and play nicely with current SysML callout style. Short role indicators are best! NamedElement::name block property, value property, part property, AbstractRequirement::/satisfiedBy, AbstractRequirement::/tracedTo, Satisfy, Trace
ASSERTION, TIP The OMG SysML language deliberately does not aim to restrict users and tools to one strict systems engineering methodology; it provides flexible capabilities and options for use by many model-based systems engineering methodologies and tools. systems engineering, Model-Based Systems Engineering, requirements engineering, SysML, Systems Modeling Language
CAPABILITY, FEATURE, TOOL Magicdraw/Cameo has a powerful "implied relation" facility for use in query tables, dependency matrices, and as element properties Relationship, DirectedRelationship dependency matrix, MagicDraw implied relationships, MagicDraw SysML, Cameo Systems Modeler, MagicDraw UML
TIP When satisfying a Requirement with a Block, you need to ask whether the Block (all instances) satisfies the Requirement or whether only a particular usage of the Block (such as a part property) Satisfies the Requirement! Satisfy, Block, Requirement, part property MagicDraw implied relationships, Webel Best Practice
COMPLICATION In SysML more than one NamedElement can help Satisfy a single Requirement (which presents challenges for verifying satisfaction of Requirements). This is a conceptual challenge for requirements engineering in general, not just SysML! SysML-1.6 NamedElement Satisfy, Satisfy::getSatisfies(in ref), AbstractRequirement::/satisfiedBy, AbstractRequirement, Requirement requirements engineering, test engineering
DISPLAY, TIP, TOOL MagicDraw/Cameo: If a particular symbol for a tool does not support compartments for the requirements relationships 'refines', 'satisfies', 'tracedFrom' and 'verifies' use a callout into a Note instead compartment Requirement, Refine, Satisfy, Trace, Verify requirements engineering, Cameo Systems Modeler, MagicDraw SysML
TIP In UML and SysML a '/' forward slash prefix before a Property name indicates that it is derived from other elements in the model. SysML-1.6, UML-2.5.1 Property::isDerivedUnion, Property::isDerived
TOOL, WARNING MagicDraw/Cameo: If you must use the Documentation field in the specification dialog for a Requirement element DO NOT use it to state the Requirement because that is WET not DRY. Instead just use the Requirement 'name' and/or the 'text'. NamedElement::name Requirement, AbstractRequirement::text
ISSUE SysML-1.6: Refers to both 'composite requirements' and 'compound requirements' (clearly as identical concepts) SysML-1.6 composite (compound) requirement, Requirement
DISPLAY The ProxyPort «proxy» and FullPort «full» stereotype keywords can quickly lead to clutter in diagrams. The SysML Revision Task Force is working on some new concise notational indicators on the Port rectangle symbol itself. Stereotype, «keyword» ProxyPort, «proxy», FullPort, «full» SysML, Systems Modeling Language
ASSERTION A FlowProperty need not have 'composite' AggregationKind, it can be 'shared' or 'none'. (The MagicDraw/Cameo default is 'none'). SysML-1.6 AggregationKind, AggregationKind::composite, AggregationKind::none, AggregationKind::shared FlowProperty Cameo Systems Modeler, MagicDraw SysML
ISSUE, TOOL MagicDraw/Cameo 19SP3: Validation of required and provided Interfaces proxied between a ProxyPort and a part with a compatible contract fails SysML-1.6 required Interface, provided Interface, InterfaceRealization, Usage, part ProxyPort, part property contract, Cameo Systems Modeler, MagicDraw SysML
ISSUE, TOOL MagicDraw/Cameo 19SP3: Does not yet handle Property-wise Type compatibility validation of FlowProperty contracts (it only handles them at the level of entire Block types). Webel asserts the spec is inconsistent w.r.t. ProxyPort connection compatibility. provided Feature, required Feature, DirectedFeature MagicDraw SysML, Cameo Systems Modeler
ASSERTION SysML directional FlowProperty contracts for ProxyPorts SHOULD be satisfiable Property-wise (including as subsets of Properties) not necessarily just at the level of entire Blocks! SysML-1.6 FlowProperty, FlowProperty::direction, FlowDirectionKind
ISSUE SysML-1.6: InterfaceBlock: OCL in constraint 2_no_part is missing FlowProperty check (for FlowProperty of a valid type other than ValueType). SysML-1.6 InterfaceBlock, SysML-1.6, FlowProperty
ASSERTION Typing a "standard" Port by an InterfaceBlock or ~InterfaceBlock IS allowed AND can be useful; typing a FullPort by an InterfaceBlock or ~InterfaceBlock is formally allowed but not so useful, because it would have no parts or behaviors to do anything. Port "standard" Port, FullPort, InterfaceBlock, ~InterfaceBlock
CONVENTION, MODELLING, NAMING, TIP Webel: If you must name your Ports or Pins, name them simply 'i', 'o', or 'io' to indicate direction UNLESS you have to indicate a special role like 'iRole', 'oAuxiliary'. DO NOT use Port or Pin names like 'input', 'output', etc. SysML-1.6, SysML-1.7 Port, Pin, NamedElement::name Webel Best Practice
CAVEAT, DISPLAY, TOOL, WARNING MagicDraw/Cameo: Using the display option to show labels inside Port rectangle symbols or to use SysML compartments on Port symbols hides any flow direction indicators. Port FlowProperty Cameo Systems Modeler, MagicDraw SysML
TIP, TOOL MagicDraw/Cameo: HOWTO get back an InformationFlow or ItemFlow when it vanishes from a redrawn Connector. Use the 'Show Realised Item Flows' and 'Realize All Item Flows' smart manipulators! InformationFlow, InformationFlow::conveyed ItemFlow MagicDraw UML, MagicDraw SysML, Cameo Systems Modeler
NAMING, POLICY, STYLE "Trust the Port or Pin Type!" - Often the name of the Type of an anonymous Port or Pin is completely sufficient to indicate its role, unless a clear indication of its direction or unique role is required. NamedElement::name, Property, InstanceSpecification, Port Webel Best Practice
DISPLAY, MODELLING, NAMING, STYLE UML/SysML: In Internal Block Diagrams: Consider hiding the name of a named Port or Property in a Diagram if its Type is sufficient to indicate its role. SysML-1.6, SysML-1.7, UML-2.5.1 NamedElement::name, Property, Port "standard" Port, ProxyPort, FullPort, SysML Internal Block Diagram Webel Best Practice, SysML, Systems Modeling Language, UML, Unified Modeling Language
CONVENTION, STYLE In most Webel examples, the default is chosen to be 'out' if there is a single FlowProperty, so a Port with the type applied will act as a source. If an InterfaceBlock is used, then a Port typed by the conjugating ~InterfaceBlock will act as a sink. Webel Best Practice
TIP A SysML Enumeration is a UML Enumeration with ValueType applied (so properties typed by it will list as value properties in the 'values' compartment on a Block) SysML-1.6 Enumeration SysML Enumeration, ValueType, value property
TOOL In MagicDraw SysML or Cameo Systems Modeler if you drag a Classifier onto an Association or Connector, it will in fact create a SysML ItemFlow not a UML InformationFlow InformationFlow, InformationFlow::conveyed ItemFlow MagicDraw SysML, Cameo Systems Modeler
ISSUE, TOOL MagicDraw UML/SysML/Cameo 19SP3: Sometimes on application of a named Association as the Type of a Connector that already has an InformationFlow (or ItemFlow) applied, the direction of the InformationFlow (or ItemFlow) indicator swaps. InformationFlow, InformationFlow::conveyed, Connector Association, ItemFlow MagicDraw SysML, Cameo Systems Modeler, MD SysML
DISPLAY, NAMING, WARNING The UML InformationFlow notation and the SysML ItemFlow notation can sometimes clash with the notation of named Associations and named and typed Connectors InformationFlow, InformationFlow::conveyed ItemFlow, ItemFlow::itemProperty
ISSUE, WARNING In SysML the NOW DEPRECATED (since SysML-1.6) direct UML Port conjugation does not work consistently with SysML DirectedFeature and SysML FlowProperty on nested ports! SysML-1.6 Port::isConjugated, Port
TIP If you are using Blocks (not InterfaceBlocks) to Type your Ports just use "manual" feature-by feature direction inversion to achieve type conjugation (and you can even use a ~ tilde prefix) Port, TypedElement, TypedElement::type conjugation, Block
TIP MagicDraw/Cameo: You can easily find all elements a Stereotype has been applied to via the Stereotype's specification dialog. Stereotype MagicDraw UML, MagicDraw SysML, Cameo Systems Modeler
TOOL, WARNING MagicDraw/Cameo 19SP3 still supports the DEPRECATED UML Port conjugation (but it is recommended here that you DO NOT use it, even though there might be future migration for such directly conjugated Ports). Port, Port::isConjugated InterfaceBlock, ~InterfaceBlock, conjugation MagicDraw SysML, Cameo Systems Modeler
WARNING Until tool support for ~InterfaceBlock comes you have to make a decision: (1) Bake your own «~InterfaceBlock» then deal with clashes when tool support comes; (2) stick with the DEPRECATED UML conjugation (not nested-port friendly) and await migration. SysML-1.6 Port::isConjugated InterfaceBlock, ~InterfaceBlock, conjugation
DEPRECATION Although the older SysML FlowPort is strictly deprecated, the term "ports with flows" is often used for a Port typed by a block with a FlowProperty. The expression "flow port" is best avoided to prevent confusion. SysML-1.6 DEPRECATED:FlowPort, port with flows
POLICY 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". FlowProperty, DirectedFeature, InterfaceBlock, ~InterfaceBlock Webel Best Practice
DISPLAY, TIP, TOOL MagicDraw/Cameo: Stereotypes should be created/managed in UML Profile Diagrams and owned by Profile packages, but Stereotypes and Metaclasses can be displayed on UML Class Diagrams and SysML Block Definition Diagrams Stereotype, metaclass
TIP 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! SysML-1.6 provided Interface, required Interface, ball-and-socket, lollipop DirectedFeature, FeatureDirectionKind::provided, FeatureDirectionKind::required, FeatureDirectionKind::providedrequired Webel Best Practice
DISPLAY, STYLE, WARNING Provided/required Interface "lollipop" and "socket" (a.k.a. ball-and-socket) notation can quickly lead to clutter in UML Composite Structure Diagrams and SysML Internal Block Diagrams. SysML provided/required DirectedFeature notation is cleaner. Port, lollipop, ball-and-socket DirectedFeature, FeatureDirectionKind::provided, FeatureDirectionKind::required, FeatureDirectionKind::providedrequired
DISPLAY, STYLE, WARNING [HISTORICAL] ISSUE: UML: MagicDraw UML: Showing Port labels (name and type) inside Port rectangle symbols does not always work well with provided/required Interface "lollipop" and "socket" (a.k.a. ball-and-socket) notation Port, lollipop, ball-and-socket
CAVEAT, TOOL [HISTORICAL] MagicDraw/Cameo 19SP3: Does NOT yet support ~InterfaceBlock [NOW SUPPORTED in 2024x Golden] SysML-1.6, SysML-1.7 Port InterfaceBlock, ~InterfaceBlock, conjugation
WARNING The mechanism for conjugated Ports has been changed in SysML 1.6, it now conjugates the Type! If you are using an InterfaceBlock to type a Port you can conjugate that 'original' on another Port by typing it with an ~InterfaceBlock. SysML-1.6 Port InterfaceBlock, ~InterfaceBlock, conjugation
ASSERTION, TIP You can't make connections in BDDs, only in IBDs. A BDD shows where connections may be made, an IBD shows where specific connections have been made in a specific context! Connector, Port SysML Block Definition Diagram, SysML Internal Block Diagram
ASSERTION, ISSUE SysML-1.6: Needs a constraint on ~InterfaceBlock making the implied inversion of provided/required Interfaces explicit SysML-1.6 Interface, InterfaceRealization, Usage InterfaceBlock, ~InterfaceBlock, ~InterfaceBlock::original
ISSUE SysML-1.6: reference to 'Figure 17-1' should be 'Figure 16-7' SysML-1.6 SysML specification figure
CAPABILITY, DISPLAY, FEATURE, OPTION, TIP, TOOL MagicDraw/Cameo: To callout the element properties of Diagram's context Element into a Note in that Diagram use the context menu item Represent Diagram Context on the Note! SysML-1.6 Diagram, element property, callout, Note MagicDraw UML, MagicDraw SysML, Cameo Systems Modeler
ISSUE, NAMING SysML-1.6: Stereotype keyword consistency: «testCase» in Figure 16-6, «TestCase» in Figure 16-7 SysML-1.6 «keyword», Stereotype TestCase
TIP The SysML Copy relationship can be used to "import" Requirements from an existing read-only library into a new project context. Copy, Requirement Systems Modeling Language, systems engineering, Model-Based Systems Engineering
CAVEAT, TOOL MagicDraw/Cameo: Does not copy identical text from a supplier Requirement to a client Requirement on application of the Copy relationship (but DOES offer to fix it when the validation engine warning fires). Requirement, Copy validation engine, Cameo Systems Modeler, MagicDraw SysML
ISSUE SysML-1.6: Typo: Constraint name: Copy::1_source_and_ta[r]get_are_requirements SysML-1.6 Copy
DISPLAY, ISSUE, STYLE SysML-1.6: double-callout into one Note from 2 part Property symbols in 'Figure 16.4: Requirement satisfaction in an internal block diagram' is not tool friendly SysML-1.6 callout SysML specification figure
ISSUE SysML-1.6: in 'Figure 16-3: Links between requirements and design' on block BrakeSystem the part 'r:BrakeLine' should probably be 'r:RearBrake' SysML-1.6 SysML specification figure, part property, Block
DISPLAY, QUESTION, STYLE, TOOL MagicDraw/Cameo: How disable icons in requirement relationship compartments and tagged values compartment on Requirement symbol? tagged value, compartment DeriveReqt, Requirement, AbstractRequirement::/derived, AbstractRequirement::/refinedBy, Refine
ISSUE SysML-1.6: 'Figure 16-2: Requirements Derivation' indeed shows DeriveReqt but spec text refers to it only as 'an example of a compound requirement' SysML-1.6 SysML specification figure, AbstractRequirement::text, composite (compound) requirement
ISSUE SysML-1.6: text on Requirement 'Test and procedure conditions' is mangled in 'Figure 16-2: Requirements Derivation' (was OK in SysML-1.5) [and also on Figure 16-6] SysML-1.6 SysML specification figure, AbstractRequirement::text
NAMING, TOOL MagicDraw/Cameo: By implementation the name of some Stereotype attributes and operations is UpperCase instead of lowerCase like in the UML and SysML specs attribute, Stereotype, Property, Operation MagicDraw SysML, MagicDraw UML, Cameo Systems Modeler
DISPLAY, ISSUE, STYLE SysML-1.6: Consistency: either show the [metaclass] on all Stereotype symbols in profile diagrams or on none SysML-1.6 Stereotype, metaclass
ISSUE SysML-1.6: The spec 'Figure 15-8: Example of Structural Allocation' has an IBD for Block1, which only makes sense if 'Abstract Reference' and 'Concrete Example' are meant to be part Properties (not Blocks) SysML specification figure, Block, part property
ISSUE SysML-1.6: In 'Figure 15-7: Example of flow allocation from ObjectNode to FlowProperty' there are allocations from an Actions (usage level) to Blocks (definition level) SysML-1.6 SysML specification figure, Block, SysML Block Definition Diagram, allocation, behavior allocation
ISSUE SysML-1.6: In 'Figure 15-7: Example of flow allocation from ObjectNode to FlowProperty' it does not make sense naming the BDD 'Block0' if that Block is not shown in the diagram SysML-1.6 SysML specification figure, Block, SysML Block Definition Diagram
ISSUE SysML-1.6: The 'Figure 15-7: Example of flow allocation from ObjectNode to FlowProperty' does not show the allocatedFrom for 'action2' on Block7 SysML-1.6 Allocate, SysML specification figure
ISSUE SysML-1.6: The 'Figure 15-7: Example of flow allocation from ObjectNode to FlowProperty' does not allocate to any FlowProperty SysML-1.6 FlowProperty, Allocate, SysML specification figure
CAPABILITY, FEATURE, TOOL MagicDraw/Cameo: One can choose between 'usage' level or 'definition' level allocation modes on AllocateActivityPartition swimlanes. The setting always applies to all AllocateActivityPartition items in one Activity Diagram at once. swimlane Allocate, behavior allocation, AllocateActivityPartition functional allocation
POLICY, WARNING AVOID "mixed" functional (behavioral) allocation levels! DO NOT Allocate from Usage level (Action) to Definition level (Block) or from Definition level (Activity) to usage level (part Property) - even if formally permitted in SysML. Behavior, Action, Activity Allocate, behavior allocation, Block, part property, MD:PartProperty Webel Best Practice, functional allocation
CAVEAT, ISSUE, STYLE MagicDraw/Cameo does not seem to offer the display option Apply SysML Callout Style on CentralBufferNode callout, CentralBufferNode SysML callout style MagicDraw SysML, Cameo Systems Modeler
ISSUE SysML-1.6: Figure 15-5 does not show 'flow allocation of ObjectFlow .. alternatively to an ItemFlow', Figure 15-6 does. SysML-1.6 ObjectFlow SysML specification figure, ItemFlow
NAMING, POLICY Use of 'this-that' with a hyphen in Connector names is admissable (where 'this' and 'that' indicate Connector ends or their types) Connector Webel Best Practice
NAMING, POLICY, WARNING DO NOT use Connector names that are identical to the names of the Associations that type them! Type, NamedElement::name, Association, Connector Webel Best Practice
ISSUE SysML-1.6: text concerning Figure 15-4 says 'allocation of Actions to Parts are depicted in Figure 15-4' then has an allocation from a part to Activity6. SysML-1.6
ISSUE SysML-1.6: text concerning Figure 15-4 'The allocation to Activity6'; the allocation is FROM Activity6. SysML-1.6
NAMING, POLICY, WARNING DO NOT use Property names that are identical to the names of the Classifier (Class, DataType, Block, ValueType) that type them! Type, Classifier, Class, DataType, NamedElement::name Block, ValueType Webel Best Practice
CAVEAT, ISSUE MagicDraw/Cameo: DOES NOT support the Namespace compartment on Block MagicDraw SysML, Cameo Systems Modeler
ISSUE MagicDraw/Cameo 19SP3: can't assign Statemachine submachine as principal of AdjunctProperty via validation warning dialog (confirmed bug). WORKAROUND: Set principal using the specification dialog. AdjunctProperty, AdjunctProperty::principal MagicDraw SysML, Cameo Systems Modeler
ISSUE SysML-1.6 Typo: There is no "hybridSUV" Lifeline in Figure D.9 - there is 'vehicleInContext:HybridSUV' SysML-1.6
ISSUE SysML-1.6: An additional ControlFlow is required into the DecisionNode of 'Figure 11-12: Continuous system example 3' and the existing ObjectFlow with Brake Pressure must become a decisionInputFlow SysML-1.6 DecisionNode, DecisionNode::decisionInput, DecisionNode::decisionInputFlow
ISSUE SysML-1.6: Edge for [else] in 'Figure 11-11: Continuous system example 2' should be an ObjectFlow not a ControlFlow SysML-1.6
ISSUE MagicDraw/Cameo 19SP3: Can't seem to show {control} notation on control Pin Pin::isControl, ObjectNode::isControlType, control Pin MagicDraw SysML, Cameo Systems Modeler, MagicDraw UML
ISSUE MagicDraw/Cameo: Has ControlValue not ControlValueKind (due to known SysML spec issue) ControlValueKind Cameo Systems Modeler, MagicDraw SysML
ISSUE SysML-1.6: Multiple references to ControlValue should be ControlValueKind (known issue) SysML-1.6 ControlValueKind
ISSUE Claim: The ControlValue input to Monitor Traction without a Pin is invalid in 'Figure 11-10: Continuous system example 1' and multiple issues with ControlOperator Pin::isControl, ObjectNode::isControlType, elided Pin notation, ObjectFlow, control Pin ControlOperator, control parameter, ControlValueKind, ControlValueKind::enable, ControlValueKind::disable
ISSUE, TOOL MagicDraw/Cameo: Uses the lowerCase keyword «valueType», the SysML spec has «ValueType» in some sample figures SysML-1.6 «keyword», Stereotype ValueType
ISSUE MagicDraw/SysML 19SP3: does not support ObjectNode notation shown in SysML-1.6 in Figure 11-6 and Figure 11-7 because does not support ObjectNode notation properly MagicDraw SysML, Cameo Systems Modeler
MagicDraw/Cameo: to use SysML-style control flow notation with a dashed line and stick arrowhead set the Diagram Style display option SysML Control Flow Style to true (enabled) notation, ControlFlow SysML control flow notation, SysML Activity Diagram diagram style
DISPLAY, TIP, TOOL MagicDraw/Cameo: For the "rake" symbol to show on a CallBehaviorAction typed by a Behavior you must have the Show Rake Icon display option on AND the Behavior must have a Diagram (such as an Activity Diagram) rake icon, CallBehaviorAction, Behavior, Activity Cameo Systems Modeler, MagicDraw SysML, MagicDraw UML
ISSUE SysML-1.6: Reference to 'in the decomposition from Figure 9-17' should be '...Figure 9-16' SysML-1.6 SysML specification figure
FEATURE, TIP, TOOL MagicDraw/Cameo: HOWTO get a ConnectorProperty to show with a dashed line to its Connector in an IBD
ISSUE SysML-1.6: Reference to 'House 2' for Figure 9-11 is inconsistent. Should probably just be 'House'. SysML-1.6 SysML specification figure
ISSUE SysML-1.6: reference to 'association between Spigot and Faucet Inlet in Figure 9-11' should say 'Figure 9-8' SysML-1.6 SysML specification figure