nus-pe-bot
commented
3 years ago Team's Response
traKCAL block is the main block, given that it is the name of the application. I do not quite understand what the tester does not understand.
Also, components are explained in greater details in subsequent sections and users can get more information from there. Therefore, this is unlikely to affect the normal operations of product and we have changed the severity level to very low.
Items for the Tester to Verify
:question: Issue response
Team chose [response.Rejected]
- [x] I disagree
Reason for disagreement: While I agree that the severity of the issue could have been lowered given that architechture diagrams are freeform, the explanation that "traKCAL block is the main block" does not clear up the confusion on what the user is interacting with, and why they do not interact with the storage (ie editing the human editable files as per the constraint) or not interacting with the user interface (which by definition is "is the point of human-computer interaction and communication in a device")
The alternative could have been to wrap all the blocks in a big group called traKCAL rather than adding in the ambiguous tracKCAL block.
The diagram causes unecessary confusion to the reader, thus the issue should not have been rejected.
:question: Issue severity
Team chose [severity.VeryLow]
Originally [severity.Medium]
- [x] I disagree
Reason for disagreement: Upon further inspection, there is no explanation on what the traKCAL block within the diagram refers to, the next diagram skipping to the UI instead, and no further mention of the block in the Design segment of the DG. The lack of explanation is a cause for concern as the reader would not be able to understand why the block was there, or the role of the block.
Thus the severity should have been Low and not VeryLow at least.
For this diagram:
What does the trackcal block represent, and why doesn't the user interact with the UI of the program?