GfSE
Do not expose abstract concepts
Abstract concepts should not be exposed in viewpoints. This affects
- System Requirement
- General Functional Parameter
- General Functional Exchange
- General Physical Role
- General Functional Usage instead the concepts specialing the abstract concepts should be exposed.
Does this mean any change for stereotypes of the abstract concept elements? If so, please keep in mind, that SAF_SystemRequirement is required as stereotype for transfering model elements to/from RM Tools ...
Hi Eric, this depends how we solve the issue, e.g we might chose to make the concept system requirement non Abstract, change the inheritance of stereotypes, we can discuss the options.
i think functional requirement should inherit from system requirement anyway.
In RM tools, often classes of requirements are tagged by attributes, e.g. as safety relevant, mitigating.
In SAF, we can use stereotypes to distinguish them, if they really differ. Some properties/ relations of requirements have a meaning dependent of the type, e.g. function for a functional requirement could refer to the function it refines, and.on a nonfunctional requirement refer to the function it constrains.
This was the motivation for those different stereotypes. Of course both should inherit from system requirement.
Safety analysis properties should not change the kind. It could add stereotypes, or be part of a base stereotype.
There is a similar challenge, because contributing reqs. link to hazard differently than mitigating reqs.
They have different sets of "derived properties'
Are there tool specific constraints for RM tool exchange for EA?