Icon class icon_class fas fa-quote-left icon_class_computed fas fa-quote-left Related content Webel has suggested primary/replica as an alternative to master/slave terminology for the SysML Copy relationship in future SysML versions The Copy relationship Source OMG Systems Modeling Language (SysML) 1.6 Copyright information About Object Management Group copyright in text extracts quoted from OMG specifications for educational purposes Snippet kind INFO UML keywords Dependency::supplier Dependency::client SysML keywords AbstractRequirement Requirement Copy AbstractRequirement::/master AbstractRequirement::text Keywords requirements engineering Previous snippet Since the concept of requirements reuse is very important in many applications, SysML introduces the concept of a slave requirement. Full quote /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 that has this requirement as the slave. (derived) Next snippet Webel has suggested primary/replica as an alternative to master/slave terminology for the SysML Copy relationship in future SysML versions Related snippets The use of namespace containment to specify requirements hierarchies precludes reusing requirements in different contexts since a given model element can only exist in one namespace. A Copy relationship is a dependency between a supplier requirement and a client requirement that specifies that the text of the client requirement is a read-only copy of the text of the supplier requirement. 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 When a Copy dependency exists between two requirements, the requirement text of the client requirement is a read-only copy of the requirement text of the requirement at the supplier end of the dependency. Copy::1_source_and_taget_are_requirements A Copy dependency may only be created between two NamedElements that have a subtype of the abstractRequirement stereotype applied Copy::2_same_text The text property of the client requirement is constrained to be a read-only copy of the text property of the supplier requirement and this applies recursively to all subrequirements Since the concept of requirements reuse is very important in many applications, SysML introduces the concept of a slave requirement. Related snippets (backlinks) Visit also Visit also (backlinks) Flags
