search

minhao23 / pe

0 stars 0 forks source link

Glossary #8

Open minhao23 opened 1 week ago

minhao23 commented 1 week ago

image.png could probably do with a better glossary with more terms.

nus-pe-bot commented 4 days ago

Team's Response

There were many repeated terms across the UG and DG (eg: guest, vendor). We did not want to repeat these terms across the UG and DG glossaries, to avoid unncessary repetition as mentioned in the CS2103T website. Hence, we chose to place most of the repeated terms in the DG glossary only.

From website about DG requirements:

image.png

We would make this clearer in the next iteration.

Items for the Tester to Verify

:question: Issue response

Team chose [response.NotInScope]

Reason for disagreement: I would have to reject this argument. I believe the cs2103 requirements mean that you should use a more general entity (class diagram) instead of repeating multiple similar elements if it achieves the same result. Aside from that, the DG and UG serve very different purposes, so your arguments only make sense if you are expecting your users to read the DG as well. Furthermore, the non-technical terms that may be important to the user are only located in the DG. (Things like tag, rsvp etc.. if you think they are clear and easily understood, then why put them in the DG glossary?).

However, I do understand where you are coming from, and hence it was spotted as an error of very low serverity.