Project Doubts #57
Project Doubts
#57
-
|
When talking about the requirements, which is the purpose of assigning a code to them? Thanks! |
Beta Was this translation helpful? Give feedback.
Answered by
Albert-Alvarez
May 6, 2021
Replies: 1 comment
-
|
To have an unequivocal reference to each one of them. This, when using the code, allows to show which requirement is being talked about. It is also useful when it is necessary to make control/monitoring tables where putting the whole specification as a column header, for example, is not feasible. This is how you will find it tomorrow in project specifications. |
Beta Was this translation helpful? Give feedback.
0 replies
Answer selected by
Albert-Alvarez
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
To have an unequivocal reference to each one of them. This, when using the code, allows to show which requirement is being talked about. It is also useful when it is necessary to make control/monitoring tables where putting the whole specification as a column header, for example, is not feasible. This is how you will find it tomorrow in project specifications.