Tags and keywords
A TestCase for verifying a Requirement can be an Operation or a Behavior (such as an Activity):
The block SoundMeter has a «testCase» Operation testSoundLevel() : VerdictKind.
There is also a «testCase» Activity (with verbose name):
'Visit neighbours and ask whether they are really annoyed by the loud sound'.
Webel Best Practice: The name of a «testCase» Behavior may be verbose and may use natural language, but should always start with a Capital letter.
An Activity Diagram could be used to elaborate on the steps for the test, such as: knocking on the door of your neighbour's flat; asking politely whether you can do a sound test; phoning your flat-mate (still in your flat) to ask them to crank the sound system up to 11; asking the neighbour whether they are really annoyed by the loud sound; recording the neighbour's response; leaving the neighbour's flat; giving the neighbour a six-pack of beer later as thanks afterwards etc.
For some situations one might prefer a Sequence Diagram to specify a «testCase» Interaction.
We see next how composite (a.k.a. compound) requirements work.