search

nus-cs2103-AY2021S1 / pe-dev-response

0 stars 0 forks source link

This section lacks visuals and it would provide greater clarity if there were screenshots #1100

Open nus-se-bot opened 3 years ago

nus-se-bot commented 3 years ago

Note from the teaching team: This bug was reported during the Part II (Evaluating Documents) stage of the PE. You may reject this bug if it is not related to the quality of documentation.

No details provided. Screenshot 2020-11-13 at 1.20.42 PM.png

The above sections such as view seem straightforward and dont really require screenshots whereas this section seems more in need of screenshots to show the successful call of the command when u editpr or deletepr. Can improve screenshot appropriateness for all the sections

[original: nus-cs2103-AY2021S1/pe-interim#1002]

richardcom commented 3 years ago

Team's Response

Hi, thank you for your report! : ) We are glad and grateful that you have spent the effort to try out and test our products. We appreciate your effort in trying to help us further polish our product. We understand that you might have some confusions in some of our features. We would love to explain and elaborate more on this. However, after careful consideration and discussion, we decide to reject this problem.

Firstly, these two commands are very common and similar to find and edit in AB3. There is also no visual of the two commands in AB3 UG, and we follow the design consideration of AB3.

Moreover, as the two commands are deletepr and editpr, which are silmilar to the commands find and edit in books which we have explained earlier. Thus, we think that adding more visuals in these two commands would be against the simplicity rules.

Thirdly, we decide that the severity level shall be VeryLow instead. Reason: by referring to the CS2103 website, this reported case does not affect the usage of these commands and UG. We have explained the commands with details and provided examples on the usage of these commands.

With the given the reasons, our team decided to reject the issue. Thank you again for your response, and our team hopes that you can understand our decision.

Duplicate status (if any):

--