-
Key: CSRM-14
-
Status: closed
-
Source: Dassault Systemes ( Mr. Daniel Brookshier)
-
Summary:
The following changes are proposed (note that there are some changes from the original proposal to make it more complete and correct):
Changes to: 7.6.3 ExtRequirement
1) add /validatedBy:ValidationActivity[0..*]
Documentation: The query getValidatedBy() returns all the NamedElements that are suppliers ( "to" end) of a «Validation» relationship whose client is the element input parameter, ref.
2) add getValidatedBy():ValidationActivity[0..*]
documentation: The validatedBy is derived from all elements that are the client of a «validation» relationship for which this requirement is a supplier.
specification: Validate.allInstances()->select(base_Abstraction.client=ref).base_Abstraction.supplierChanges to: 7.6.3 VerificationActivity
add:
verifies : AbstractRequirement[0..*] - The requirements that this VerificationActivity verifies.
add to doc (was already part of profile):
verificationMethod : VerificationMethodKind -The verificationMethod indicates the primary method that «VerificationActivity» uses to verify a Requirement.added
getVerifies():AbstractRequirement[0..*]
Specification: Verification.allInstances()->select(base_Abstraction.client=ref).base_Abstraction.supplier
Documentation: The query getVerifies() returns all AbstractRequirement that are suppliers ( "to" end of the concrete syntax ) of a «Verifies» relationship whose client is the element input parameter, ref. This is a static query.Change to: Figure 7 SysML Extensions Profile
Update diagram to reflect the addition of /validatedBy:ValidationActivity[0..*] element on the ExtRequirement Stereotype.Change to: Figure 5 Validation and Verification Profile
Update diagram to show the addition of /verifies:AbstractRequirement[0..*] on the VerificationActivity stereotype. -
Reported: CSRM 1.0b2 — Fri, 22 Apr 2022 20:31 GMT
-
Disposition: Resolved — CSRM 1.0
-
Disposition Summary:
Add derived properties and methods to improve usability.
Add elements and add a clarifying note to model and specification:
Changes to ExtRequirement
1) add /validatedBy:ValidationActivity[0..*]
Documentation: The query getValidatedBy() returns all the NamedElements that are suppliers ( "to" end) of a «Validation» relationship whose client is the element input parameter, ref.
2) add getValidatedBy():ValidationActivity[0..*]
documentation: The validatedBy is derived from all elements that are the client of a «validation» relationship for which this requirement is a supplier.
specification: Validate.allInstances()->select(base_Abstraction.client=ref).base_Abstraction.supplierNote about this change: First, this is intended to mirror the same pattern as SysML. Second, the verifies and verifiedBy already exists in abstractRequirement. Because Verifies is a kind of Verify, no change is required.
Changes to VerificationActivity
1) add /verifies:VerificationActivity[0..*]
2) add getVerifies():VerificationActivity[0..*]
Specification: Verification.allInstances()->select(base_Abstraction.client=ref).base_Abstraction.supplier
Documentation: The query getVerifies() returns all the NamedElements that are suppliers ( "to" end of the concrete syntax ) of a «Verifies» relationship whose client is the element input parameter, ref. This is a static query.Change to: Figure 7 SysML Extensions Profile
Update diagram to reflect the addition of /validatedBy:ValidationActivity[0..*] element on the ExtRequirement Stereotype.Change to: Figure 5 Validation and Verification Profile
Update diagram to show the addition of /verifies:AbstractRequirement[0..*] on the VerificationActivity stereotype. -
Updated: Tue, 27 Sep 2022 12:48 GMT