Nobody (informed) said that SysML (or even UML) modelling and MBSE is only about graphical modelling, notations, and diagrams! Information can be extracted in many different ways and presented in many different formats from the underlying model!

Icon class
icon_class
far fa-sticky-note
icon_class_computed
far fa-sticky-note
Note kind
TIP
Policy level
TIP
Specification keywords
SysML-1.6
SysML-1.7
SysMLv2
UML-2.5.1
Keywords
Visit also for a discussion of table, matrix, and map views and links to many examples on this site:
SysML: MagicDraw/Cameo: Use query view tables, matrices, and maps, use them a lot! They help communicate well with other stakeholders. Learn how to use the Generic Table diagram type, custom relations, Simple Navigation & Metachain Navigation (expert)!
Visit also: 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!
Visit also: Magicdraw/Cameo has powerful query view tables, maps, and dependency matrix diagrams!
Visit also: [EXTERNAL LINKS] SysMLv1/UML: MagicDraw/Cameo: Derived properties, structured expressions, reusing opaque behaviours, metachain
Related:
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!
Relates to
MagicDraw/Cameo: Satisfy Requirement Matrix: Hybrid SUV vs Block (all)
[EXTERNAL LINKS] SysMLv1/UML: MagicDraw/Cameo: Derived properties, structured expressions, reusing opaque behaviours, metachain
[STUB] SysMLv1: MagicDraw/Cameo: SPECIFIC CASES of Structured Expressions, Derived Properties, Custom Scripts, and Metachain Navigation for table columns
Related notes
[ASSERTION, DISPLAY, SETTINGS, STYLE, TOOL]{STRICT} 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!
[CAPABILITY, TOOL] In MagicDraw/Cameo one can "call-out" many element properties (and metamodel properties) into a Note using the Edit Compartments context menu item
[CAPABILITY, TOOL] In MagicDraw/Cameo one can display many element properties (and metamodel properties) directly in compartments on most element symbols
[FEATURE, TIP, TOOL] MagicDraw/Cameo derived relationships and metachain navigation are very powerful and worth exploring
[CAPABILITY, FEATURE, TOOL] Magicdraw/Cameo has powerful query view tables, maps, and dependency matrix diagrams!
[CAPABILITY, FEATURE, TOOL] 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!
[CAPABILITY, FEATURE, TOOL] Magicdraw/Cameo has powerful relationship maps!
Related notes (backlinks)
Related snippets (extracts)
Visit also
Figure D.40 - Tabular Representation of Allocation from “Accelerate” Behavior Model to Power Subsystem (Table)
Figure D.14 - Requirements Relationships Expressed in Tabular Format (Table)
Allocation table in the MagicDraw/Cameo tool
Figure 15-9: Allocation Matrix showing Allocation for Hybrid SUV Accelerate Example
MagicDraw/Cameo: Satisfy Requirement Matrix: Hybrid SUV vs Block (all)
MagicDraw/Cameo: Satisfy Requirement Matrix: Hybrid SUV vs Block (relations only)
MagicDraw/Cameo: Satisfy Requirement Matrix: Hybrid SUV vs Block and PartProperty (relations only)
Visit also (backlinks)