nus-se-bot
commented
4 years ago Team's Response
We will try to make it more distinct. However, we believe the aesthetic aspects of the DG should not be counted as a bug.
Items for the Tester to Verify
:question: Issue response
Team chose [response.Rejected]
- [x] I disagree
Reason for disagreement: Hi, thank you for your response but I diagree. This is not considered to be an aesthetic issue. As the reason for the color coding of components is to group certain classes under the same component, hence it is used to make the DG and the UML more understanable and readible. In this case, you did not use the color for aesthetic purpose, if so, then this is not correct as well. Also, this reflects the amount of effort you put into the documentation as this issue can easily be fixed by simply assigning a different colour to the component in the UML file. The reason why this affects the user as the user may misinterpret that State and Storage are under the same component, which may lead to further snowballing of misunderstanding.
As you can see here,
it is stated the even cosmetic issue are considered as bugs and are set as very low, however, in this case, it will actually affect the user and cause inconvenience to the user, which falls under the severity of medium.
Hence, this is considered to be a documentation issue. Hope this clear things up. Thank you!
The component color used to represent the State and Storage are extremely similar, which was confusing as the readers, me, thought that you have implemented them as a single component, which is not the case. I think you could have choosen another color to represent one of the mentioned components to better differentitate them.