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
FEATURE, TIP, TOOL MagicDraw/Cameo: You can drag-n-drop most applicable Stereotype types from the model browser onto an Element's symbol in a Diagram to apply it to that Element (does not work in all cases). Diagram, Element, symbol, Stereotype MagicDraw SysML, Cameo Systems Modeler, MagicDraw UML, drag-n-drop
FEATURE, TIP, TOOL MagicDraw/Cameo: You and can drag-n-drop the icon for most Diagram types from the model browser onto a symbol in a Diagram to make it the default hyperlink for that Element; clicking on that Element symbol will then open up that Diagram. Diagram, Element, symbol MagicDraw SysML, Cameo Systems Modeler, MagicDraw UML, hyperlink, drag-n-drop
DISPLAY, FEATURE, SETTINGS, TOOL MagicDraw/Cameo: You and can choose which Features, element properties, or tagged values of Stereotypes to show on most symbol compartment types Diagram, Element, symbol, compartment, element property, tagged value MagicDraw SysML, Cameo Systems Modeler, MagicDraw UML
ASSERTION, DISPLAY, SETTINGS, STYLE, TOOL ALL Model-Based Engineering: Just because you can't see a Feature or some other aspect of a SysML (or UML) Element in a tool on a symbol does NOT mean it does not exist in the underlying model (repository)! The model is not just what is DISPLAYED! Alf-1.1, fUML-1.3, fUML-1.4, SysML-1.6, SysML-1.7, SysMLv2, UML-2.5.1 Diagram, Element, symbol Webel Best Practice, MagicDraw SysML, Cameo Systems Modeler
ASSERTION, DISPLAY, TOOL Rule #1: A UML or SysML Element in a tool is NOT just an Element symbol in a diagram! A Note is not an Element (compare with a Comment). SysML-1.6, UML-2.5.1 Diagram, Element, symbol Webel Best Practice, MagicDraw SysML, Cameo Systems Modeler
TOOL MagicDraw/Cameo: Keep most elements out of the top-level of a project (i.e. not directly under the project Root). Have one top-level index/content/package diagram. Package, Model Webel Best Practice, MagicDraw SysML, Cameo Systems Modeler
DISPLAY, SETTINGS, STYLE, TOOL Webel: Recommend maintain a basic black-and-white style file for starting new projects. Webel course attendees have access to a basic Webel.stl file (or clone and tune the 'OMG SysML style'). Webel Best Practice, MagicDraw SysML, MagicDraw UML, Cameo Systems Modeler, Magic Model Analyst [Cameo Simulation Toolkit]
DISPLAY, SETTINGS, STYLE, TOOL Webel: MagicDraw/Cameo: First recommended display style settings and project option steps for every SysML (and UML) project. [Includes TIP: DO NOT show the Diagram Name in the optional Diagram Info adornment, show it on the Diagram frame only] Webel Best Practice, MagicDraw SysML, MagicDraw UML, Cameo Systems Modeler, Magic Model Analyst [Cameo Simulation Toolkit]
ISSUE UML-2.5.1 refers to 'isTestFirst' in 16.11.3.4 but to isTestedFirst in the attributes list for LoopNode under 16.14.30.4 Attributes UML-2.5.1 LoopNode, LoopNode::isTestedFirst
TIP Not every task in Activity Diagrams is well-suited to graphical modelling and LoopNode and ConditionalNode are notoriously fiddly to setup; consider using Action Language Helper (ALH) or Action Language for Foundational UML (Alf) LoopNode, ConditionalNode, StructuredActivityNode Alf, Action Language Helper, Cameo Systems Modeler, Magic Model Analyst [Cameo Simulation Toolkit]
CAVEAT Cameo Simulation Toolkit 19SP3 DOES NOT support 'setupPart' in LoopNode (because fUML does not) LoopNode, LoopNode::setupPart Magic Model Analyst [Cameo Simulation Toolkit], Cameo Systems Modeler
CONVENTION, NAMING, POLICY Webel: SysMLv1.x: AVOID (where possible) SysML Unit names that are the same as unit symbols. Unit names SHOULD start with a lower case Latin alpha letter. Custom Unit names should be a single lower case word or lowerCamelCase. SysML-1.6, SysML-1.7 ModelLibrary Unit Webel Best Practice, units, scientific unit system, ISO-80000, SysMLv1.x
ISSUE SysML-1.6: The provided/required Interfaces indicated in the spec version of D.19 for 'connector c1 in Figure D.19.' are not defined on the corresponding Block in Figure D.20 (known issue) SysML-1.6 Interface, InterfaceRealization, Usage, BehavioredClassifier::interfaceRealization
WARNING GOTCHA: Just because an InitialNode MAY have more than one outgoing ControlFlow and offers tokens on every outgoing ControlFlow does NOT mean that every outgoing edge takes a control token; InitialNode does NOT act like an implicit fork! InitialNode, implicit fork
DISPLAY, TIP In a SysML Activity Diagram a control flow may be notated with a dashed line and stick arrowhead; this helps distinguish a ControlFlow from an ObjectFlow symbol. SysML-1.6 ControlFlow SysML control flow notation, SysML Activity Diagram
ISSUE UML-2.5.1: Has an incorrect local Transition with same source and vertex in 'Figure 14.34 Local Transitions' UML-2.5.1 StateMatchine, State, Transition, TransitionKind::local, Transition::source, Vertex, Transition::target
ASSERTION The entry, doActivity, and effect Behaviors defined on a submachine State are specific that particular usage of its Submachine UML-2.5.1 State, State::/isSubmachineState, submachine, State::entry, State::doActivity, State::exit, State::submachine, State::containingStateMachine()
TOOL, WARNING MagicDraw/Cameo: GOTCHA: ‘entry’, ‘exit’, ‘doActivity’ are all subsets of ‘ownedElement’; to use an existing Activity without changing its owner you need to create a “wrapper” Activity. Beware the tool does not simply move your Activity! StateMachine, State, Activity, State::entry, State::exit, State::doActivity MagicDraw UML, MagicDraw SysML, Cameo Systems Modeler, Magic Model Analyst [Cameo Simulation Toolkit]
TIP The ActivityEdge, Transition, and Connector metaclasses do not extend (directly or indirectly) the Relationship metaclass (although the notations for them do indicate a kind of "relationship"). ActivityEdge, Transition, Connector, Relationship, DirectedRelationship
FEATURE, TOOL MagicDraw: Has an additional tool-specific notation and feature sometimes called "ball-and-socket dependency wiring" for use with provided and required Interfaces in Class Diagrams and some other definition-level diagrams. Class, BehavioredClassifier, Interface, required Interface, provided Interface, Usage, InterfaceRealization, BehavioredClassifier::interfaceRealization, ball-and-socket MagicDraw UML
CAVEAT While SysML does not officially include the UML Profile Diagram, in practice in the MagicDraw/Cameo tool it is often used (rather than a Package Diagram) to afford access to all profile element menus and to make it clear that it involves profile elements. Profile Diagram, Stereotype, Extension SysML Package Diagram MagicDraw SysML, Cameo Systems Modeler, SysML, Systems Modeling Language
FEATURE, TIP, TOOL, WARNING MagicDraw/Cameo: The context menu item 'Tools > Define Context-Specific Value' will only ever be available in an Internal Block Diagram on a part property symbol typed by a Block that has a value property! Block, initial values, initialValues compartment, context-specific values MagicDraw SysML, Cameo Systems Modeler
FEATURE, TIP, TOOL, WARNING MagicDraw/Cameo: The context menu item 'Tools > Define Context-Specific Value' will only be available UNTIL you have assigned one! Thereafter it does not appear anymore because the tool will have already created a tree of instances to carry the values. Block, initial values, initialValues compartment, context-specific values MagicDraw SysML, Cameo Systems Modeler
FEATURE, TIP, TOOL MagicDraw/Cameo: For context-specific values you do not have to deal with fiddly instances, you can edit the values directly in the 'initialValues' compartment! Enable 'Tools > Define Context Specific Initial Value' on a part whose Block has a value. Block, initial values, initialValues compartment, context-specific values MagicDraw SysML, Cameo Systems Modeler
POLICY Webel: A plain Dependency that is not stereotyped is always strictly timed-ordered; the supplier (target) must exist before the client (source). SysML-1.6, UML-2.5.1 Dependency, Dependency::supplier, Dependency::client, DirectedRelationship::/source, DirectedRelationship::/target
TIP You can use a ValueType to document how a value of a certain quantity kind should be measured (in a particular system, in a particular organisation, or according to an industry standard). SysML-1.6 ValueType, ValueType::quantityKind
CAVEAT, TOOL, WORKAROUND MagicDraw/Cameo: By default assumes custom units are both Unit and DerivedUnit and that quantity kinds are both QuantityKind and DerivedQuantityKind. Just remove the "Derived" variants if they don't apply and add the "Simple" variants. Unit, DerivedUnit, DerivedQuantityKind, QuantityKind, SimpleUnit, SimpleQuantityKind MagicDraw SysML, Cameo Systems Modeler
DISPLAY, ISSUE, TOOL MagicDraw/Cameo: The ordering of feature in a SysML IBD :features compartment may differ from that in its defining Block (and there are no corresponding display options for controlling sorting). Class, Property, compartment, attributes compartment Block, :values compartment, :parts compartment, :references compartment, parts compartment, values compartment, references compartment inheritance, MagicDraw SysML, MagicDraw UML, Cameo Systems Modeler
DISPLAY, ISSUE, TOOL MagicDraw/Cameo: BUG: Sometimes the 'Show Inherited' display feature does not work immediately on Class and Block compartments or SysML IBD :features compartments unless you toggle a compartment (close then re-open it). Class, Property, compartment, attributes compartment Block, :values compartment, :parts compartment, :references compartment, parts compartment, values compartment, references compartment, IBD :features compartments inheritance, MagicDraw SysML, MagicDraw UML, Cameo Systems Modeler
ASSERTION, WARNING Visual nesting of InstanceSpecification symbols has no meaning in the underlying model, only assignment to a Slot does! InstanceSpecification, instance MagicDraw SysML, Cameo Systems Modeler, MagicDraw UML
FEATURE, TIP, TOOL MagicDraw/Cameo: When you create an InstanceSpecification in a diagram it will a Select Classifier dialog. It is often faster to Cancel that and then just drag a Classifier onto the instance symbol from the diagram or model tree. instance, InstanceSpecification MagicDraw UML, MagicDraw SysML, Cameo Systems Modeler
DISPLAY, ISSUE, TOOL MagicDraw/Cameo: The display option 'Show Value Type Units' does not seem to work on the Slots of an InstanceSpecification in a BDD InstanceSpecification, Slot ValueType::unit, Unit, ValueType, value property MagicDraw SysML, Cameo Systems Modeler
FEATURE, TIP, TOOL MagicDraw/Cameo: In a BDD the diagram sidebar menu item for 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 Cameo Systems Modeler, MagicDraw SysML
CAVEAT, DISPLAY, NAMING, TOOL MagicDraw/Cameo v19SP3: The SysML 'properties' compartment of a ValueType is called 'attributes' like in UML2.5.1 for DataTypes [CLAIMED FIXED in v2021x] compartment, attributes compartment ValueType, properties compartment MagicDraw SysML, Cameo Systems Modeler
CAVEAT The SysML Complex "primitive" ValueType does in fact have substructure: realPart:Real and imaginaryPart:Real SysML-1.6 PrimitiveValueType, Complex, ValueType
TIP QUDV in SysML refers to: Quantity, Unit, Dimension, Value. It is strongly influenced by the International Vocabulary of Metrology (VIM). SysML-1.6 QuantityKind, ValueType::unit, Unit::quantityKind, ValueType, Unit scientific unit system, Systems Modeling Language, VIM3, SysML, ISO-80000
DISPLAY, FEATURE, TOOL MagicDraw/Cameo has many tool-specific Stereotype icons, most of which can be hidden in most diagrams using Stereotype and icon display options. icon, Stereotype:icon Cameo Systems Modeler, MagicDraw SysML
DISPLAY, FEATURE, TOOL MagicDraw/Cameo: If you want to show a Property or Port listed both in its corresponding compartment on a Class or Block symbol and as the end of an Association in the same diagram, set the display option Show Association Ends As Attributes/Ports to 'all' Class, Property, Association, Association::ownedEnd, Association::memberEnd, Association::navigableOwnedEnd, compartment, Port, Class Diagram Block, parts compartment, references compartment, values compartment, part property, reference property, value property, "standard" Port, SysML Block Definition Diagram MagicDraw UML, MagicDraw SysML, Cameo Systems Modeler, UML, Unified Modeling Language, SysML, Systems Modeling Language
TIP If instances of Blocks “communicate” with each other use an Association between them. Association Block Webel Best Practice
ASSERTION, TIP When dealing with required Interfaces you must use Usage (not Dependency) and it has dedicated "socket" notation. Usage, required Interface
TOOL, WORKAROUND MagicDraw/Cameo: If you can't find Usage on a particular diagram just use a Dependency then the refactor context menu item. Usage, Dependency MagicDraw UML, MagicDraw SysML, Cameo Systems Modeler
TIP Prefer not rename Properties when redefining unless indicating a clear change in role. Property::redefinedProperty, NamedElement::name Webel Best Practice
WARNING The difference between Dependency and Usage in UML is notoriously vague. SysML-1.6, UML-2.5.1 Dependency, Usage
FEATURE, TIP, TOOL MagicDraw/Cameo: You can set a Property as redefined/subsetted by another in a Class Diagram or BDD by dragging its label from an Association end onto the label of another Property on an Association end then choosing 'Set As Redefined/Subsetted Property' Class, Property, Property::redefinedProperty, Property::subsettedProperty Block MagicDraw SysML, MagicDraw UML, Cameo Systems Modeler
DISPLAY, OPTION, TOOL MagicDraw/Cameo: Has a symbol display option 'Show Inherited' applicable to (amongst others) Features of Class and Block symbols, Property symbols, and underlying Featured of Property symbols in SysML IBDs when using SysML Feature Compartments Class, Property Block Cameo Systems Modeler, MagicDraw UML, MagicDraw SysML, inheritance, multiple inheritance
POLICY, TIP Webel: SysML: Always consider including an abstract (sometimes intermediate) base Block in your domain modelling Generalization hierarchy. Classifier::isAbstract, Generalization Webel Best Practice
CONVENTION, NAMING If using "French style" post-adjective naming in English use a trailing underscore after the noun and before the adjective or qualifier: Vin_rouge, Cable_digital. Can be combined with TLA acronyms: Player_DVD. NamedElement::name, Class Block Webel Best Practice
NAMING, POLICY Use singular Property names, let the multiplicity indicate plurality. Property, NamedElement::name, MultiplicityElement, multiplicity
CAVEAT, DISPLAY, TOOL MagicDraw/Cameo: Does not show the “structure” label at the top of an internal structure compartment. internal structure compartment, compartment, label internal structure Cameo Systems Modeler, MD SysML
ASSERTION When domain modelling with SysML, Generalization, inheritance, and even multiple inheritance are not "evil" and can be used relatively freely. We are not doing code-oriented Decorator patterns - an implementation choice - we are doing domain modelling! Generalization inheritance, multiple inheritance
A common interpretation of composite Aggregation of a part property in SysML domain modelling is that if the owner Block is "destroyed" so is the child part property. Webel adopts these semantics always. AggregationKind::composite, AggregationKind, Property::aggregation Block, part property, MD:PartProperty Webel Best Practice
ASSERTION, TIP If an abstract Block or Class in a domain model has Associations to Blocks or Classes that are not also abstract, it's often a hint that you have not identified a correct abstraction layer. Association, Class, Classifier::isAbstract Block Webel Best Practice
ASSERTION, TIP SysML Blocks have lots of possible features and compartments, lots of capabilities, and are very powerful! But you don't have to use every aspect of a Block (or show every aspect in every diagram) at once on every project. Block Webel Best Practice
ISSUE, NAMING, TOOL MagicDraw/Cameo v19SP3: uses the Block compartment name 'signal receptions' instead of just 'receptions'. [CLAIMED FIXED in v2021x] SysML-1.6, SysML-1.7, UML-2.5.1 receptions compartment, Signal, Reception Cameo Systems Modeler, MagicDraw UML, MagicDraw SysML
TIP MagicDraw/Cameo: If you make a copy of the SYMBOL of an Element in a Diagram you have only copied the SYMBOL, it represents the same Element! If you make a copy of an Element in the model browser you have indeed made a unique new (distinct) Element! Element, symbol Cameo Systems Modeler, MagicDraw UML, MagicDraw SysML
ASSERTION, TIP MagicDraw/Cameo support for the SysML Parametric Diagram and ConstraintBlocks for equations and mathematics is excellent, and it integrates with powerful maths engines such as Mathematica. It CAN be used on industrial strength real-world projects. Constraint ConstraintBlock, constraint parameter, SysML Parametric Diagram mathematics, equation, Mathematica, Cameo Systems Modeler, MagicDraw SysML
ASSERTION, TIP The SysML Parametric Diagram and the ContraintBlock technology for equations and mathematics is clever, powerful, useful, and integrates well with the other model-based engineering aspects of SysML. Constraint ConstraintBlock, constraint parameter mathematics, equation
TIP In SysML, unless you MUST use a DataType or PrimitiveType from an existing ModelLibrary or Profile, you SHOULD probably be using a ValueType, Enumeration ValueType, or SysML PrimitiveValueType instead so that it integrates with the value system of SysML. DataType, PrimitiveType ValueType, PrimitiveValueType Webel Best Practice
ISSUE MagicDraw/Cameo 19SP3: Stakeholder: Has 'concern' NOT derived and /concernList derived; SysML-1.6 has /concern derived and concernList NOT derived. SysML-1.6 Stakeholder::/concern, Stakeholder::concernList MagicDraw SysML, Cameo Systems Modeler
FEATURE, TIP, TOOL MagicDraw/Cameo: You can set many fields in an Element's specification dialog just by dragging compatible elements from the model browser onto the value area of the field. Cameo Systems Modeler, MagicDraw SysML, MagicDraw UML, drag-n-drop
CAPABILITY, FEATURE, TOOL MagicDraw/Cameo: supports HTML hyperlinks directly on model elements, and they are launchable from model element symbols in diagrams. symbol, Element hyperlink, HTML, Cameo Systems Modeler, MagicDraw SysML, MagicDraw UML
CAPABILITY, FEATURE, TOOL MagicDraw/Cameo: supports HTML (including hyperlinks) in String based tagged value (Stereotype property) fields. Just activate HTML mode during tagged value editing. Stereotype, tagged value, stereotype Property hyperlink, HTML, Cameo Systems Modeler, MagicDraw SysML, MagicDraw UML
ASSERTION Webel Parsing Analysis (with strict traceability of all elicited model elements) can be used side-by-side with "freestyle" modelling with incremental benefit the more it is used. Webel Parsing Analysis, parsing analysis, WPA:«document», WPA:«pa», WPA:«snippet»
ASSERTION The Webel Parsing Analysis recipe promotes a clearly scoped modelling workflow. Webel Parsing Analysis, parsing analysis, WPA:«document», WPA:«snippet»
ASSERTION Even relatively informal elicitation of model elements using the SysML ElementGroup and a Parsing Analysis approach is extremely powerful. ElementGroup Webel Parsing Analysis, parsing analysis, WPA:«document», WPA:«snippet», WPA:«pa», systems engineering
ASSERTION Translating authoritative technical documents written in “natural” engineering language (snippet-by-snippet) into Webel Parsing Analysis diagrams creates consistent underlying systems models and can bridge easily to existing methodologies. Webel Parsing Analysis, parsing analysis, WPA:«document», WPA:«snippet», WPA:«pa», systems engineering
ASSERTION Humans work well with natural language: Many stakeholders – including those who are not necessarily familiar with UML or SysML modelling symbols and diagrams - benefit enormously from having plain text in diagrams side-by-side with graphics. Requirement Webel Parsing Analysis, parsing analysis, WPA:«document», WPA:«snippet»
ASSERTION Webel Parsing Analysis is a "meta-process" that can be applied to general domain source documents to elicit Requirements (and related model elements) or to a Requirements Specification itself as a special case of a domain source document! Requirement requirements engineering, Webel Parsing Analysis, parsing analysis, WPA:«document»
ASSERTION Not even the most experienced requirements engineers can easily state requirements perfectly in consistent requirements-friendly language first shot; requirements and constraints are often buried in the natural text of domain source documents. Requirement requirements engineering, Webel Parsing Analysis, parsing analysis
ISSUE, TOOL MagicDraw/Cameo: The apparent grouping of member elements under an ElementGroup node in the model tree can cause complications for searching and for the Cameo Collaborator exports. ElementGroup, ElementGroup::/member Cameo Collaborator, Cameo Systems Modeler, MagicDraw SysML
POLICY Webel Parsing Analysis: A Snippet (keyword «snippet») MUST always have exactly one domain 'source' Document (keyword «document»). Webel Parsing Analysis, parsing analysis, WPA:«document», WPA:«snippet», WPA:Snippet::source
POLICY Webel Parsing Analysis: A custom Document stereotype (keyword «document») extends the UML standard profile Document that extends Artifact (which is NOT in the UML4SysML intersection). Such a Document may act as the 'source' of a «snippet». Artifact, «document» Webel Parsing Analysis, parsing analysis, WPA:«document», WPA:«snippet», WPA:Snippet::source
POLICY Webel Parsing Analysis: Create a top-level 'source' or '0-source' Package/Model SEPARATE from your project model. All source «document» elements and «snippet» extracts and «pa» diagrams MUST be ultimately owned by that top-level Package/Model as ancestor! Package, Model Webel Parsing Analysis, parsing analysis, WPA:«pa», WPA:«document», WPA:«snippet»
POLICY, STYLE Webel «pa» Parsing Analysis Diagrams (PADs) are "scratchpads" used to elicit model elements traceably from text Snippets (extracts from source Documents). While BDDs are a good initial choice, most types of SysML diagram can be used as a «pa» diagram. Webel Parsing Analysis, parsing analysis, WPA:«pa»
TIP, TOOL Webel Parsing Analysis: If you are processing lots of text from one source «document» create a STUB «snippet» with that «document» set as 'source' and just make copies of it in the model browser as needed. Big time saver! Webel Parsing Analysis, WPA:«pa», WPA:«snippet», WPA:«document»
ASSERTION, DISPLAY, POLICY, SETTINGS, STYLE, TOOL Webel Parsing Analysis: If you wish to show a «snippet» comment symbol (with its body text) in a presentation diagram (that is NOT a «pa» diagram) remove the '/member' tagged value from display so the only visible tagged value is 'source'. ElementGroup::/member Webel Parsing Analysis, parsing analysis, WPA:«pa», WPA:Snippet::source
POLICY, STYLE Webel Parsing Analysis «pa» diagrams are NOT intended as final presentation diagrams! They serve merely to traceably elicit model elements, which may then be shown in other (typically much tidier) presentation diagrams elsewhere. Webel Parsing Analysis, parsing analysis, WPA:«pa»
CONVENTION, TIP Webel Parsing Analysis: typically the quoted extract text (body) of a «snippet» is a short phrase, a sentence, or a couple of short sentences (but not dozens of sentences). ElementGroup Webel Parsing Analysis, WPA:«snippet», parsing analysis
ASSERTION, CAVEAT The UML Artifact and its UML standard profile extensions such as «document» Document and «file» File are NOT included in UML4SysML. Artifact, «document», «file»
OPTION In Webel Parsing Analysis if you want to track elicited model elements that have not been explicitly mentioned in source text you can introduce Element-level custom tracking Stereotypes with the keywords «pa:implied» or «pa:assumed». Stereotype, custom Stereotype, «keyword», user defined Stereotype parsing analysis, Webel Parsing Analysis, WPA:«pa:implied», WPA:«pa:assumed»
TIP An ElementGroup comment symbol may appear on more than one diagram type and may collect different kinds of anchored annotatedElement members from more than diagram. Comment, Comment::annotatedElement, MD:anchor ElementGroup, ElementGroup::/member
TOOL In MagicDraw/Cameo the dashed line symbol from a UML Comment or SysMLv1.x ElementGroup to an annotatedElement is called an 'anchor'. Comment, Comment::annotatedElement, MD:anchor
TIP The grouping of member elements by an ElementGroup is denoted here "logical" in the sense that it does not "steal ownership" of member elements (as opposed to "physical" ownership of elements in the model) ElementGroup, ElementGroup::/member, ElementGroup::orderedMember logical grouping
TIP The Webel Parsing Analysis recipe for SysML1.x does not use the ElementGroup directly, it extends it as a user-defined Snippet stereotype with keyword «snippet» and with MagicDraw Customization. Stereotype, custom Stereotype, MD:Customization, user defined Stereotype, Comment ElementGroup Webel Parsing Analysis, WPA:«snippet»
OPTION The default display of all tagged values on the comment symbol for an ElementGroup can make diagrams cluttered, but you can extend it with a custom stereotype and customise the default visible tagged values. tagged value, stereotype Property, user defined Stereotype, Stereotype, custom Stereotype, MD:Customization ElementGroup, ElementGroup::name, ElementGroup::/size, ElementGroup::/criterion, ElementGroup::/member, ElementGroup::orderedMember
OPTION Do not feel obliged to use the 'name' property of an ElementGroup if you don't feel it adds value. ElementGroup, ElementGroup::name
FEATURE, TIP, TOOL MagicDraw/Cameo: Many table cells are interactive! You can, for example, edit the 'name' of elements. Most columns are also sortable. And you can navigate from element cells to elements in the model browser via context menu items. MagicDraw SysML, MagicDraw UML, Cameo Systems Modeler
DISPLAY, FEATURE, TOOL MagicDraw/Cameo: The default swimlanes in SysML Activity Diagrams are AllocateActivityPartition swimlanes with the «allocate» keyword applied. ActivityPartition, swimlane AllocateActivityPartition, behavior allocation, «allocate» functional allocation, Cameo Systems Modeler, MagicDraw SysML
TIP By all means use ActivityAllocatePartition swimlanes for CallBehaviorAction allocation in usage allocation mode, but use BDDs for your definition-level allocations with directly drawn «allocate» relationships between Activity and Block symbols. CallBehaviorAction, ActivityEdge::redefinedEdge AllocateActivityPartition, behavior allocation, Block, «block», «activity» functional allocation
TIP MagicDraw/Cameo: If you remove a CallBehaviorAction from an ActivityAllocatePartition swimlane any previously created allocations won't be removed, but you can delete them using the Allocations section of the Specification dialog of any relevant element. CallBehaviorAction, swimlane ActivityAllocatePartition
ISSUE SysML-1.6: The constraint that ''An Action appearing in an “AllocateActivityPartition” shall be the /client (from) end of an “allocate” dependency.' is not compatible with all Activity Diagram swimlane configurations. SysML-1.6 Dependency::client, Dependency::supplier AllocateActivityPartition
CAVEAT, FEATURE, TOOL, WARNING MagicDraw/Cameo: In SysML Activity Diagrams you can only set the allocation mode in to 'usage' or 'definition' for an entire AllocateActivityPartition group at once, not for individual AllocateActivityPartition columns or rows. Classifier, Property, Action, Activity AllocateActivityPartition, Allocate, behavior allocation, SysML Activity Diagram, part property, MD:PartProperty, Block MagicDraw SysML, Cameo Systems Modeler, functional allocation
FEATURE, TIP, TOOL MagicDraw/Cameo: The Allocate relationship is available on many element kinds on most SysML diagram types as a smart manipulator (click symbol once then look at right of symbol). Allocate, «allocate»
FEATURE, TIP, TOOL MagicDraw/Cameo: The Allocate relationship is available in all SysML diagram types under the Common sidebar menu group (but you can only use it to make allocations between elements that both appear in a given diagram). Allocate, «allocate»
FEATURE, TIP, TOOL MagicDraw/Cameo: You can allocate an Action to any NamedElement in the model via its specification box under the Allocations section by dragging and dropping an element (such as a part Property) from the model browser onto the Allocate To field. Action Allocate, part property, MD:PartProperty functional allocation, Cameo Systems Modeler, MagicDraw SysML
ISSUE, TOOL MagicDraw/Cameo 19SP3: The property path in callout does always correspond to the SysML spec examples. callout pathname dot notation MagicDraw SysML, Cameo Systems Modeler
CONVENTION, TIP Webel use editorial Sterotypes prefixed with ! and ? in and in CAPS in keywords such as: «!». «?», «!ERROR», «!ISSUE», «!CAUTION», «!WARNING», «!CAVEAT», etc. Stereotype Webel Best Practice
STYLE, TIP Associative BDDs are best used as staging diagrams for you the modeller (and SysML-fluent readers). IBDs usually make better presentations diagrams for a wider audience of general engineers and other stakeholders. SysML Internal Block Diagram, SysML Block Definition Diagram Webel Best Practice
CAPABILITY, TIP, TOOL MagicDraw/Cameo: Use a Customization to set the «keyword» on a custom Stereotype. Make sure to save, close, then re-open the project afterwards! Stereotype, «keyword», MD:Customization MagicDraw SysML, Cameo Systems Modeler
CAPABILITY, TIP, TOOL MagicDraw/Cameo: You can easily create your own extensions of Block to act as subjects of UseCases. The tool knows how to handle the rectangular ‘subject’ notation on Use Case Diagrams UseCase, UseCase::subject, MD:Customization, Stereotype Block, SysML Use Case Diagram MagicDraw SysML, Cameo Systems Modeler