Repository navigation
docs: initial draft of requirement process - #377
Conversation
|
The created documentation from the pull request is available at: docu-html |
aschemmel-tech
left a comment
There was a problem hiding this comment.
No OSS publishing issues found. Detailed content review pending.
masc2023
left a comment
There was a problem hiding this comment.
Documentation in Sphinx based on metamodel shows some issues, attribute safety/security are shown, where not needed, e.g. process requirements, having tag structure?, Attribute text for workflows and work product are not ok
| :status: valid | ||
| :tags: attribute, mandatory | ||
|
|
||
| Each requirement shall have a type of one of following options: |
There was a problem hiding this comment.
Do we have to support multi selection. E.g. A legal requirement can request a Non-Functional requirement. What shall be selected here?
There was a problem hiding this comment.
In general you could select both attributes, there is no check for it that you can only name one
Requirements Process description including: - contept - getting startet - process requirements - checklists - templates fixed #308 Also-by: aschemmel-tech
953ea2e to
3bd31cc
Compare
masc2023
left a comment
There was a problem hiding this comment.
Please correct the templates to the agreed form
corrected findings of 2nd review
masc2023
left a comment
There was a problem hiding this comment.
Review findings resolved
Requirements Process description including:
fixed #308
Also-by: aschemmel-tech