by Gengis » Wed Jun 22, 2022 6:28 pm
I found very simple and disappoinment the built-in properties that the (stereotype) Requirements has. It is like a toy or simple test more than a serios useful one.
After many hours of searching and study, when I was almost a noobie on MD, I solved this issue creating a new Stereotype for my project requirements.
The steps were more or less these:
1. In contaiment tree, Create a new package named "z.Stereotypes"
2. Create a UML profile diagram, you need to use the upper menu, right click doesn't give you this option.
3. From the palet menu drag and drop a "stereotype", name it as "require..." and chose "Requirement".
4. Create a new stereotype with a new name, for example "RequirementsUseful" and create a generalization relation, so the new defined one heritage from the built-in Requirement one.
5. Click the black plus mini icon on the upper right corner of the new stereotype and add all the attributes than you need in your requirements, for example: rationale, priority, status, risk, comment, author, etc, etc. Assign proper types to them (string, integer, real, ENUM, etc).
6. If you are noobie, Enums need to be created separately before being assigned to properties.The easiest way is to right click in the package/folder of the stereotype and select Create Element->Enumeration. Rename the enumeration at your convenience. Then right click this and Create Element in a similar way under it but selecting "Enum. literal" (if you select property or other it is not going to work). Once finished to add all needed literals and all needed enums you are able to type your New Requirement-Useful attributes with the corresponding enums you just defined.
7. Now, you are able to Refractor the requirements with the right click menu to the new Stereotype. And then, you are able to include the new data for all of them. Also you are able to use all this information on a table and whereever you need.
I hope this help!
Gengis