SPECTRA — Split SV1 stereotypes into mandatory and optional

Review 16-05-2025

Related to section Additional Information

From our perspective this [SPECTRA4SV1] would be considered a large profile.
o For our large programs we must petition and negotiate with systems engineering for each separate stereotype that we want added to the system model.
o Each engineering function has dozens, or hundreds, of stereotypes contained in various profiles that they all want added to do their analysis.
o For most large programs, systems engineering is resistant to adding any stereotypes beyond what is mandatory.
o I recommend splitting SPECTRA profile into the mandatory and optional stereotype packages and profiles so end-users can be more selective on what to bring into their model.
o As stated above, I also recommend refocusing SPECTRA so that the main use case is properly modeling cybersecurity needs in a system model. That way it can be the main bulk of the stereotypes we need to include in a model from a cyber perspective. If it is limited to just being an export translator profile, then we will likely need to have very similar profiles of our own that properly model cybersecurity needs from a system security engineering perspective. It would be better if SPECTRA could do that with a side effect of being able to export.

NM: section 6 "Additional Information: How to read this specification" already mentioned "essential" and "optional" stereotypes. I like the suggested approach to emphasize the "mandatory" nature of some elements, in the direction of "properly modelling cybersecurity needs in a system model".