The SysML textual notation has been updated to allow user-defined keywords in the following additional places:
assume#keywordconstraintconstraint-usage
require#keywordconstraintconstraint-usage
frame#keywordconcernconcern-usage
verify#keywordrequirementrequirement-usage
actor#keywordusage
stakeholder#keywordusage
subject#keywordusage
objective#keywordrequirement-usage
Note. In items 1–4, the constraint, concern, or requirement keyword is optional when a user-defined keyword is included. However, if neither keyword is included, then the declaration is a reference, rather than the declaration of a named usage. For example,
requireaGoal;
is equivalent to
require constraint referencesaGoal;
while
require #goalaGoal;
is equivalent to
require #goal constraintaGoal;
where aGoal is a name of the required constraint usage, not a reference to another constraint usage.
The SysML textual notation has been updated to allow user-defined keywords in the following additional places:
assume#keywordconstraintconstraint-usagerequire#keywordconstraintconstraint-usageframe#keywordconcernconcern-usageverify#keywordrequirementrequirement-usageactor#keywordusagestakeholder#keywordusagesubject#keywordusageobjective#keywordrequirement-usageNote. In items 1–4, the
constraint,concern, orrequirementkeyword is optional when a user-defined keyword is included. However, if neither keyword is included, then the declaration is a reference, rather than the declaration of a named usage. For example,requireaGoal;is equivalent to
require constraint referencesaGoal;while
require #goalaGoal;is equivalent to
require #goal constraintaGoal;where
aGoalis a name of the required constraint usage, not a reference to another constraint usage.