: Public Note
Created: |
3/12/2021 3:58:52 PM |
Modified: |
5/17/2021 8:33:53 AM |
|
Project: |
|
Author: |
1362763084C |
Version: |
1.0 |
Phase: |
1.0 |
Status: |
Proposed |
Complexity: |
Easy |
Difficulty: |
|
Priority: |
|
Multiplicity: |
|
Advanced: |
|
UUID: |
{635E6FD4-406B-4fff-85B3-EAC0E9C1C311} |
Appears In: |
DID_CDRL_ViewpointsViews |
The Navy's 516C model has the criterion modeled via custom profile as an inheritance of #lt;#lt;AbstractRequirement#gt;#gt; attributes with other abstract elements to create an element that is similar to a custom requirement, but isn't technically a requirement. It seems to borrow the idea from the SysML 1.5 appendix E.8 non-normative definition of a Property-Based Requirement that marries the #lt;#lt;AbstractRequirement#gt;#gt; with specific block types to create a "requirement" with block characteristics such as ports, operations, value types, etc. Creates a hard link between a requirement and the block that satisfies the requirement.<br/>