Tags and keywords
"It's important when teaching real Requirements Engineering to real engineers to use really real examples from real world projects, so I've chosen one here from the mockumentary film 'This is Spinal Tap'.From Wikipedia:
Before jumping straight in and using that 'text' field on all of your Requirements, please consider this recommendation:
The reality is, the Requirements system in SysML works brilliantly together with model-based engineering (other technologies don't) and the tool support for it is excellent.
You can't callout the 'text' of a Requirement into the compartments for the relevant relationships anyway (and you don't even really need it in query tables if you use a verbose 'name').
But if you use a short Requirement 'name' and a long 'text', the short 'name' won't be useful enough in callouts or even as a mental prod as soon as you have lots of requirements on a real project. So you might as well just use no 'text' at all if you can get away with it.One possibly good excuse for rejecting this recommendation here is that you wish to use this nice feature of MagicDraw SysML Plugin and Magic Cyber-Systems Engineer ® (Cameo Systems Modeler®):
And just in case you are tempted to "document" your requirements:
So, with all necessary caveats concerning the 'text' field behind us, the rest of this tutorial trail will in fact use the 'text' field anyway. We'll see next that the 'text' in fact lives in the AbstractRequirement along with some other essential requirements engineering goodies.