Cameo Systems Modeler

Topic outline for 3-day & 4-day overview course versions: Model-based systems engineering with the OMG's Systems Modeling Language (SysML®) and the SysML Plugin for MagicDraw® and Cameo™

Keywords

Keywords

• course
• training
• seminar
• workshop
• education
• SysML
• Systems Modeling Language
• Model-Based Systems Engineering
• MBSE
• systems engineering
• systems
• graphical engineering
• requirements analysis
• requirements engineering
• MagicDraw SysML
• Cameo Systems Modeler
• Magic Model Analyst [Cameo Simulation Toolkit]

This topic outline accompanies this course:

Course: Model-based systems engineering with the OMG's Systems Modeling Language® and the SysML Plugin for MagicDraw® and Cameo™ (CATIA Magic)

---

IMPORTANT: If some of your prospective course attendees have minimal or no prior experience with the SysML language or the MagicDraw/Cameo tools, we strongly recommend that you request

MagicDraw/Cameo: HOWTO turn off verbose context information in SysML-style diagram frames

MagicDraw/Cameo: You can control how or whether applied Sterotypes are displayed on most Element symbols using the 'Show Stereotypes' display option (and in some cases this affects how the entire symbol is displayed).

MagicDraw/Cameo: You can assign values to 'tagged values' of Stereotypes via the Tags section in the specification dialog. Make sure you have one of the 'On Shape' or 'In Compartment' Show Tagged Values display options enabled.

MagicDraw/Cameo: You can assign or un-assign one or more Stereotypes to one or more selected Elements at once using the 'Stereotype' context menu item

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).

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.

MagicDraw/Cameo: You and can choose which Features, element properties, or tagged values of Stereotypes to show on most symbol compartment types

Just because you can't see a Feature or some other aspect of a UML or SysML Element in a tool on a symbol does NOT mean it does not exist in the underlying model (repository)!

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).

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.

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: First recommended style and project option steps for every UML and SysML project in MagicDraw/Cameo.

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)

Cameo Simulation Toolkit 19SP3 DOES NOT support 'setupPart' in LoopNode (because fUML does not)

Starting an Action that has a ValuePin - LIMITED SUPPORT

Gallery

Tutorial

TRAIL: Webel's ultimate guide to Systems Modeling Language with MagicDraw/Cameo

Section

01:04: UML Behavior: Activities quick start

Slide kind

UML Activity Diagram

Starting an Action that has a ControlPin

Gallery

Tutorial

TRAIL: Webel's ultimate guide to Systems Modeling Language with MagicDraw/Cameo

Section

01:04: UML Behavior: Activities quick start

Slide kind

UML Activity Diagram

Starting an Action that has an InputPin with multiplicity

Gallery

Tutorial

TRAIL: Webel's ultimate guide to Systems Modeling Language with MagicDraw/Cameo

Section

01:04: UML Behavior: Activities quick start

Slide kind

UML Activity Diagram

Starting an Action that has an InputPin

Gallery

Tutorial

TRAIL: Webel's ultimate guide to Systems Modeling Language with MagicDraw/Cameo

Section

01:04: UML Behavior: Activities quick start

Slide kind

UML Activity Diagram

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!

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.

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!

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.

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.

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.

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).

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).

Visual nesting of InstanceSpecification symbols has no meaning in the underlying model, only assignment to a Slot does!

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.

MagicDraw/Cameo: The display option 'Show Value Type Units' does not seem to work on the Slots of an InstanceSpecification in a BDD

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).

MagicDraw/Cameo v19SP3: The SysML 'properties' compartment of a ValueType is called 'attributes' like in UML2.5.1 for DataTypes [CLAIMED FIXED in v2021x]

MagicDraw/Cameo has many tool-specific Stereotype icons, most of which can be hidden in most diagrams using Stereotype and icon display options.

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'

MagicDraw/Cameo: If you can't find Usage on a particular diagram just use a Dependency then the refactor context menu item.

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'

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

MagicDraw/Cameo: Does not show the “structure” label at the top of an internal structure compartment.

MagicDraw/Cameo v19SP3: uses the Block compartment name 'signal receptions' instead of just 'receptions'. [CLAIMED FIXED in v2021x]

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!

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.

MagicDraw/Cameo 19SP3: Stakeholder: Has 'concern' NOT derived and /concernList derived; SysML-1.6 has /concern derived and concernList NOT derived.

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.

MagicDraw/Cameo: supports HTML hyperlinks directly on model elements, and they are launchable from model element symbols in diagrams.

MagicDraw/Cameo: supports HTML (including hyperlinks) in String based tagged value (Stereotype property) fields. Just activate HTML mode during tagged value editing.

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.

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/Cameo: The default swimlanes in SysML Activity Diagrams are AllocateActivityPartition swimlanes with the «allocate» keyword applied.

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.

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.

MagicDraw/Cameo 19SP3: The property path in callout does always correspond to the SysML spec examples.

MagicDraw/Cameo: Use a Customization to set the «keyword» on a custom Stereotype. Make sure to save, close, then re-open the project afterwards!

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

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!

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

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/Cameo does not explictly support tracking of satisfaction and verification of composite/compound requirements, but the "implied relations" facility can help.

MagicDraw/Cameo: A Requirement may appear on many kinds of such as a Block Definition Diagram or Package Diagram, not just a Requirement Diagram

MagicDraw/Cameo 19SP3: uses PascalCase instead of lowerCamelCase on some SysML compartment names

Magicdraw/Cameo has a powerful "implied relation" facility for use in query tables, dependency matrices, and as element properties

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

A FlowProperty need not have 'composite' AggregationKind, it can be 'shared' or 'none'. (The MagicDraw/Cameo default is 'none').

MagicDraw/Cameo 19SP3: Validation of required and provided Interfaces proxied between a ProxyPort and a part with a compatible contract fails

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.

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.

MagicDraw/Cameo: HOWTO get back an InformationFlow or ItemFlow when it vanishes from a redrawn Connector

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

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.

MagicDraw/Cameo: You can easily find all elements a Stereotype has been applied to via the Stereotype's specification dialog.

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).

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!

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).

MagicDraw/Cameo: By implementation the name of some Stereotype attributes and operations is UpperCase instead of lowerCase like in the UML and SysML specs

MagicDraw/Cameo does not seem to offer the display option Apply SysML Callout Style on CentralBufferNode

MagicDraw/Cameo: DOES NOT support the Namespace compartment on Block

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.

MagicDraw/Cameo 19SP3: Can't seem to show {control} notation on control Pin

MagicDraw/Cameo: Has ControlValue not ControlValueKind (due to known SysML spec 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

Stereotypes applied to behaviors may appear on the notation for CallBehaviorAction when invoking those behaviors, as shown in Figure 11-2.

Source

OMG Systems Modeling Language (SysML) 1.6

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)

MagicDraw/Cameo: Supports embedding of one or more Diagrams in another via the Diagram Overview feature. Awesome!

MagicDraw/Cameo 19SP3: Does not yet support AddFlowPropertyValueOnNestedPortAction

MagicDraw/Cameo 19SP3: enumeration 'FeatureDirection' should be 'FeatureDirectionKind' (reflects known error in older SysML specification versions)

MagicDraw/Cameo: the keyword for PropertySpecificType is «PropertySpecificType» not «pst»

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).

UML4SysML is a specification abstraction (concept) only, it does not find direct expression (such as via a namespace) in tools like MagicDraw/Cameo

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.)

Webel recommends (usually) display the header of a Package, Model, ModelLibrary, or Profile in the 'tab' (rather than 'top')

Figure D.41 - Supporting InstanceSpecification tree for 'initialValues (context-specific values) in MagicDraw/Cameo

Gallery

Tutorial

TRAIL: The SysML-1.6 Hybrid SUV sample and specification diagrams in MagicDraw/Cameo (with annotations)

Section

Section: SysML-1.6: HSUV sample

Slide kind

snapshot

MagicDraw/Cameo: To show the type of initialValues (context-specific values) use the display option Show Slot Type

MagicDraw/Cameo: 19SP3: Callout of allocatedFrom on Connector vs ObjectFlow shows «decisionInputFlow» not «objectFlow» keyword

MagicDraw/Cameo 19SP3: Can't callout from ItemFlow on Connector, the Note handle pulls from the Connector not the ItemFlow

MagicDraw/Cameo: The display option Apply SysML Callout Style shows elements with their Metaclass or Stereotype keywords and no vendor-specific icons

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)

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

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!

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

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

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

Webel recommends when using MagicDraw/Cameo: AVOID the "elided Pin" abstract ObjectNode notation on Activity Diagrams, use explicit Pins!

MagicDraw/Cameo: DO NOT use the ObjectNode menu item on Activity Diagrams ever!

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.

Prefer the Name Display Mode 'both' on CallBehaviorAction symbols (rather than 'Show Action Name', 'Show Behavior Name', or 'Show Both or Behavior Name')

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)

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)

MagicDraw/Cameo: Consider showing the constraint parameter name and type label inside the small rectangular parameter symbol on SysML Parametric Diagrams!

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')

MagicDraw/Cameo: Offers a customised Views and Viewpoints Diagram type with dedicated menus and some Viewpoint types.

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

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

MagicDraw/Cameo: HOWTO Create a nested Property "shortcut" symbol with a dot property path in a Parametric Diagram or Internal Block Diagram

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.

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").

The MagicDraw/Cameo feature "Enable Parts Compartments" really means "Enable SysML Compartments"

MagicDraw/Cameo: the (not so well named) "Enable Parts Compartment" feature on Ports is highly recommended and can make diagrams much easier to read.

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".

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

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).

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!

HSUV trail slide: Figure D.4: IBD: Could not show Connector typed by an anonymous Association as 'connectorName:' with trailing colon

Nobody said that UML or SysML modelling is only about diagrams!

Magicdraw/Cameo has powerful relationship maps!

Magicdraw/Cameo has powerful query tables!

MagicDraw/Cameo: the coloured stereotype icons for some kinds of elements can't be removed from all diagrams, tables, or matrix views

Magicdraw/Cameo has powerful relationship Dependency Matrix diagrams, and in many cases one can assign or remove relationships directly in the cells of the matrix just by clicking!

SysML: MagicDraw/Cameo can optionally indicate Requirement IDs in tables

MagicDraw/Cameo query tables use a single row (with a group of elements) to represent multiple targets/hits from a relationship, rather than one row per hit.

MagicDraw/Cameo derived relationships and metachain navigation are very powerful and worth exploring

SysML: The «system», «subsystem», «external», «domain» and «system context» keywords are for "user defined" block Stereotypes (they are not part of core SysML); they are supported in MagicDraw/Cameo as Non-Normative Extensions.

In MagicDraw/Cameo one can display many element properties (and metamodel properties) directly in compartments on most element symbols

In MagicDraw/Cameo one can "call-out" many element properties (and metamodel properties) into a Note using the Edit Compartments context menu item

MagicDraw/Cameo: AVOID the the vendor-specific «useCaseModel» stereotype for Model packages, it leads to confusion with the rectangular 'subject' notation

MagicDraw/Cameo can't show tagged values in {braces} below owner name on instance symbols

MagicDraw/Cameo: There are lots of spelling mistakes in the ISO-80000 ModelLibrary

MagicDraw/Cameo: Most QuantityKind in the ISO-80000 ModelLibrary in are lower case

In MagicDraw/Cameo the ProfileApplication relationship is only available in Profile Diagram menus

MD SysML and Cameo 19SP3 can't yet validate provided/required Feature subsets (such as Features of one Block against Features of multiple Ports)

In the Webel recipe for SysML, DO use a "standard" Port until you have a truly compelling reason to commit to a FullPort or ProxyPort

DO NOT use the FlowPort or FlowSpecification menu items or smart manipulator items in MagicDraw SysML or Cameo, they are completely OBSOLETE!

HOWTO get at and display "standard" Ports that have been unnecessarily hidden and suppressed in MD SysML 19SP3 and Cameo 19SP3

HOWTO easily "hack" the SysML-1.6 ~InterfaceBlock conjugation and «~interfaceBlock» keywords in MagicDraw/Cameo (until it is supported)

There is no ElementValue in UML-2.5.1 (although one has been proposed) it is an extension used by the MagicDraw tool family for handling tagged values

Webel's Best Practice policy notes for UML and SysML and the MagicDraw/Cameo tools

Keywords

Keywords

• UML
• Unified Modeling Language
• SysML
• Systems Modeling Language
• MagicDraw SysML
• MagicDraw UML
• Cameo Systems Modeler
• Magic Model Analyst [Cameo Simulation Toolkit]
• Webel Best Practice

The Webel Best Practice items for SysML (and UML) (tuned for the MagicDraw/Cameo tools) represent the world's most comprehensive guide to robust, fluent, enjoyable, consistent modelling for Model-Based Systems Engineering (MBSE), developed over two decades, and proven to work on extremely demanding real-world projects!

UML has an Integer type, not an 'int' type, but the MagicDraw and Cameo tools include a DataType 'int' in an additional profile

MagicDraw, Cameo Systems Modeler, and Cameo Simulation Toolkit use the name 'English' for a "default" vendor-specific action scripting language

StateMachine diagram for comparing action language access to an operation for a guard

Gallery

Tutorial

HOWTO invoke an operation as a Transition guard in Cameo Simulation Toolkit

Section

Slide kind

UML StateMachine Diagram

Class diagram for comparing action language access to an operation for a guard

Gallery

Tutorial

HOWTO invoke an operation as a Transition guard in Cameo Simulation Toolkit

Section

Slide kind

UML Class Diagram

The vendor-specific Action Language Helper (ALH) API can be accessed from all of the various action scripting languages available in MagicDraw, Cameo Systems Modeler, and Cameo Simulation Toolkit

HOWTO set a ValueSpecificationAction to use the * LiteralUnlimitedNatural to drive an 'insertAt' InputPin on an AddStructuralFeatureValueAction in Cameo Simulation Toolkit and Cameo Systems Modeler

Screencast: Mini tutorial: UML/SysML: Cameo Simulation Toolkit: Send and receive a Signal using a SendSignalAction and an AcceptEventAction

Keywords

• SysML
• UML
• Systems Modeling Language
• Unified Modeling Language
• Magic Model Analyst [Cameo Simulation Toolkit]
• MagicDraw UML
• MagicDraw SysML
• Cameo Systems Modeler

Video style

• screencast
• narrated
• 4K

A very simple demonstration of sending a Signal using a SendSignalAction and receiving it with an AcceptEventAction within Activities. Uses SysML but the same applies to UML.

Uses Cameo Simulation Toolkit for MagicDraw SysML and Cameo System Modeler.

© Copyright 2020 Darren R C Kelly (Webel IT Australia). All rights reserved.

Screencast: Mini tutorial: UML/SysML: Cameo Simulation Toolkit: StateMachine with doActivity and a Transition with a ChangeEvent trigger

Keywords

• SysML
• UML
• state machine
• Magic Model Analyst [Cameo Simulation Toolkit]
• Cameo Systems Modeler
• MagicDraw UML
• MagicDraw SysML

Video style

• screencast
• narrated
• 4K

A very simple demonstration of a StateMachine with a doActivity and a Transition that uses a trigger with a ChangeEvent for checking a value. Uses SysML but the same applies to UML.

Uses Magic Model Analyst^® (Cameo Simulation Toolkit^®) for MagicDraw SysML and Cameo System Modeler Enterprise Edition.

© Copyright 2020 Darren R C Kelly (Webel IT Australia). All rights reserved.

Screencast: Mini tutorial: UML/SysML: Cameo Simulation Toolkit: StateMachine with entry Activity and Transition guard

Keywords

• SysML
• UML
• state machine
• guard
• Magic Model Analyst [Cameo Simulation Toolkit]
• Cameo Systems Modeler
• MagicDraw UML
• MagicDraw SysML

Video style

• screencast
• narrated
• 4K

A very simple demonstration of a StateMachine with an entry Activity and Transitions that use guards to check a value. Uses SysML but the same applies to UML.

Uses Cameo Simulation Toolkit for MagicDraw SysML and Cameo System Modeler.

© Copyright 2020 Darren R C Kelly (Webel IT Australia). All rights reserved.

Screencast: MagicDraw SysML/Cameo analysis: Possible "gotchas" when extending the SysML Block stereotype

Keywords

• Cameo Systems Modeler
• Block
• stereotype
• Domain Specific Language
• SysML
• Systems Modeling Language
• systems engineering
• Unified Modeling Language
• UML

Video style

• 4K
• narrated
• annotated
• screencast
• instructional
• tutorial

Audience: Users of MagicDraw SysML or Cameo Systems Modeler who are experimenting with creating custom stereotypes that extend Block.

This screencast video has been created to demonstrate some issues that can arise if you "naively" create a custom stereotype that extends Block without: (1) closing then re-opening your project; (2) creating an appropriate MD Customization. It is not about any actual "bug" in MagicDraw/Cameo (as long as you follow the recommended procedure). If you watch it, please do watch it to the end to find how to handle such stereotypes properly.

• Read more about Screencast: MagicDraw SysML/Cameo analysis: Possible "gotchas" when extending the SysML Block stereotype

Screencast: MagicDraw SysML/Cameo: Pros and Cons of custom stereotypes in combination with Block inheritance and Part Property structures

Keywords

• Cameo Systems Modeler
• stereotype
• Block
• inheritance
• Part Property
• Systems Modeling Language
• SysML
• Model-Based Systems Engineering
• systems engineering
• Unified Modeling Language
• UML

Video style

• 4K
• narrated
• annotated
• screencast
• instructional
• tutorial

Audience: Users of MagicDraw SysML or Cameo Systems Modeler who are experimenting with creating custom stereotypes for SysML.

This screencast video has been created to illustrate some pros and cons of using custom stereotypes in combination with Block inheritance and Part Property structures, and demonstrates some possible "gotchas". It concerns especially use of custom stereotypes to indicate: (1) cross-cutting aspects such as model layer membership; (2) use of tagged values to carry per-Element metadata.

• Read more about Screencast: MagicDraw SysML/Cameo: Pros and Cons of custom stereotypes in combination with Block inheritance and Part Property structures

Screencast: The LogicalWrapper: A proposal for a new element for UML and SysML

Keywords

• LogicalWrapper
• Cameo Systems Modeler
• SysML
• Systems Modeling Language
• Model-Based Systems Engineering
• MBSE
• logical grouping
• UML
• Unified Modeling Language

Video style

• 4K
• narrated
• annotated
• screencast
• instructional
• tutorial
• proposal

© Copyright 2019 Darren R C Kelly (Webel IT Australia). All rights reserved.

This 4K narrated screencast video accompanies the white paper of the same name by Darren Kelly of Webel IT Australia available here.

• Read more about Screencast: The LogicalWrapper: A proposal for a new element for UML and SysML

Course: Model-based systems engineering with the OMG's Systems Modeling Language® and the SysML Plugin for MagicDraw® and Cameo™ (CATIA Magic)

Keywords

Keywords

• course
• training
• seminar
• workshop
• education
• SysML
• Systems Modeling Language
• Model-Based Systems Engineering
• MBSE
• systems engineering
• systems
• graphical engineering
• requirements analysis
• requirements engineering
• Cameo Systems Modeler
• MagicDraw SysML
• Magic Model Analyst [Cameo Simulation Toolkit]
• CATIA Magic

---

Webel IT now offers all courses worldwide as live online web seminars, including online tool workshop sessions! On-site courses within Australia may be subject to interstate travel restrictions.

Magic Cyber-Systems Engineer (Cameo Systems Modeler) zone

Keywords

Keywords

• SysML
• Systems Modeling Language
• Model-Based Systems Engineering
• MBSE
• systems engineering
• systems
• graphical engineering
• requirements analysis
• requirements engineering
• Cameo Systems Modeler
• Magic Cyber-Systems Engineer

The product bundle formerly known as Cameo Systems Modeler^® is now offered as Magic Cyber-Systems Engineer^® and includes the following No Magic components:

• MagicDraw Enterprise
• SysML Plugin
• Cameo Requirements Modeler Plugin
• Cameo DataHub Plugin
• Merge Plugin
• Cameo Data Modeler Plugin

---

Magic Cyber-Systems Engineer^® (Cameo Systems Modeler^®) is a Model-Based Systems Engineering (MBSE) en

The Webel Parsing Analysis recipe for UML

Keywords

Keywords

• UML
• Unified Modeling Language
• model-based development
• systems engineering
• graphical engineering
• domain analysis
• requirements analysis
• requirements engineering
• Webel Parsing Analysis
• Cameo Systems Modeler
• model elicitation

This zone is about a version of the  Webel Parsing Analysis recipe for document-driven, model-based, graphical software engineering with Unified Modeling Language (UML^®).

The Webel Parsing Analysis recipe for SysML

Keywords

Keywords

• SysML
• Systems Modeling Language
• Model-Based Systems Engineering
• MBSE
• systems engineering
• systems
• graphical engineering
• requirements analysis
• requirements engineering
• Webel Parsing Analysis
• Cameo Systems Modeler
• model elicitation
• requirement elicitation
• WPA:«pa»
• WPA:«snippet»
• WPA:«document»

Webel IT Australia is the home of the  Webel Parsing Analysis recipe for SysML^®, a very powerful technique for translating text from authoritative domain source documents traceably into Systems Modeling Language (SysML^®) models.