-
Key: SYSML16-168
-
Status: closed
-
Source: Commissariat a l Energie Atomique-CEA ( Mr. Benoit Maggi)
-
Summary:
Here are the constraints for DeriveReqt
[1]The supplier must be an element stereotyped by «requirement» or one of «requirement» subtypes.
[2]The client must be an element stereotyped by «requirement» or one of «requirement» subtypes.DeriveReqt extends Abstraction and an Abstraction can have many NamedElement as Client and Supplier.
7.3.12 Dependency (from Dependencies)
client: NamedElement [1..*]
supplier: NamedElement [1..*]Here are some options:
- add a constraint to restrict to 1 NamedElement in Client and Supplier
- Stereotype required only on the first NamedElement
- Stereotype required on all NamedElement
-
Reported: SysML 1.4 — Fri, 20 May 2016 15:06 GMT
-
Disposition: Closed; No Change — SysML 1.6
-
Disposition Summary:
Already constrained through trace stereotype specialization
Already constrained because deriveReqt specializes Trace stereotype which constrains both the client and the supplier to be limited to one.
-
Updated: Mon, 1 Apr 2019 18:17 GMT
SYSML16 — DeriveReqt constraints multiplicity of Client and Supplier
- Key: SYSML16-168
- OMG Task Force: SysML 1.6 RTF