Webel has suggested primary/replica (or primary/copy) as an alternative to master/slave terminology for the SysML Copy relationship in future SysML versions

Icon class
icon_class
far fa-sticky-note
icon_class_computed
far fa-sticky-note
Note kind
PROPOSAL
Specification keywords
SysML-1.6
SysMLv1.x keywords
AbstractRequirement::/master
Copy
Requirement
Many technologies have moved away from the historically loaded "master/slave" terminology. For example, the 'master' branch in Git repos often now defaults to 'main'. However the "master/slave" terminology is deeply embedded in code, user manuals, and documentation, and migrating to newer terminology is a difficult task.
Relates to
The Copy relationship
Related notes
Related notes (backlinks)
Related snippets (extracts)
  [SysML-1.6] A Copy dependency created between two requirements maintains a master/slave relationship between the two elements for the purpose of requirements re-use in different contexts
  [SysML-1.6] A slave requirement is a requirement whose text property is a read-only copy of the text property of a master requirement. The text property of the slave requirement is constrained to be the same as the text property of the related master requirement.
  [SysML-1.6] Since the concept of requirements reuse is very important in many applications, SysML introduces the concept of a slave requirement.
  [SysML-1.6] The master/slave relationship is indicated by the use of the copy relationship.
  [SysML-1.6] AbstractRequirement::/master : AbstractRequirement [0..*] This is a derived property that lists the master requirement for this slave requirement. The master attribute is derived from the supplier of the Copy dependency ...
Visit also
Visit also (backlinks)