Learn about Webel IT's new SysMLv2/MBSE Workshop Seminar course!
VIDEO: The Webel SysMLv2/MBSE course has landed! Take a quick tour!
Webel now has a SysMLv2 Online Self-Study course with self-test Quizzes!

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

Icon class
icon_class
far fa-sticky-note
icon_class_computed
far fa-sticky-note
Note kind
TOOL
WARNING
UML keywords
NamedElement::name
SysMLv1.x keywords
Requirement
AbstractRequirement::text
Please consider also this:
Webel suggests using a verbose 'name' for leaf (child) Requirements but NO 'text' to prevent Single Source of Truth issues and for improved callout vs relationships (but this might not always work when syncing with external requirements management tools)
Relates to
A most basic Requirement with a 'name', an 'id', and 'text'
Related notes
[POLICY]{STRONG} About the Single Source of Truth (SSOT) and Don't Repeat Yourself (DRY) principles
[NAMING, POLICY]{SUGGESTED} Webel suggests using a verbose 'name' for leaf (child) Requirements but NO 'text' to prevent Single Source of Truth issues and for improved callout vs relationships (but this might not always work when syncing with external requirements management tools)
Related notes (backlinks)
Related snippets (extracts)
Visit also
Visit also (backlinks)