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!

Icon class

icon_class

far fa-sticky-note

icon_class_computed

far fa-sticky-note

Note kind

Policy level

UML keywords

NamedElement::name

SysMLv1.x keywords

AbstractRequirement::/satisfiedBy

AbstractRequirement::/tracedTo

This competes with

Webel Best Practice: SysML: Webel: "Trust the Type!" - Often the name of the Type of an anonymous Property or instance-level element is completely sufficient to indicate its role - unless multiple Properties of the same Type have different roles within the same owner context!

Webel Best Practice: "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.

See however:

Webel has a proposal for clearly revealing anonymous typed elements in SysML callouts and on derived Properties from operation queries.

And this deeper discussion here:

Webel: SysMLv1: Dr Darren for LinkedIn: On "Trusting The Type" and avoiding unnecessary verbose repetitive Property names ... unless you really, really need them and really do have reasons to use them, and then only use concise role indicators anyway!

Relates to

Related notes

Related notes (backlinks)

Related snippets (extracts)

Visit also

Visit also (backlinks)

Flags