Some of the SID BEs have attributes stereotypes with <<required>>
Does this imply that:
If this is the case, then why is the <<required>> stereotype being used rather than the use of UML multiplicity - similar to the associations and aggregations? Or is the <<required>> stereotype another standard way of doing it?
Also, some BEs do not have any attributes with the <<required>> stereotype. does this mean that ALL the BE attributes are optional?
Thanks in advance
Hi @Gary Wilson,
The "required" stereotype on SID attributes is used for conformance purposes.
As you might know, a Software provider may ask to TMF to check their conformance to SID (it might concern a sub-list of ABEs).
So when an attribute is "required" it means that if the Software don't have this attribute , the conformance will be KO.
Some attributes might be considered as optional (without any stereotype) meaning: good to have but not essential.