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.
See you,
Cécile
------------------------------
Cecile Ludwichowski
Orange
------------------------------
Original Message:
Sent: Sep 12, 2023 07:52
From: Gary Wilson
Subject: Use of 'required' BE attribute stereotype
Hi
Some of the SID BEs have attributes stereotypes with <<required>>
Does this imply that:
- All BE attributes stereotyped with <<required>> have a [1..1] multiplicity (i.e. mandatory)?
- All BE attributes NOT stereotyped with <<required>> have a [0..1] multiplicity (i.e. optional)?
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
#General
------------------------------
Gary Wilson
Airbus
------------------------------