search

CodyChew / pe

0 stars 0 forks source link

Glossary #16

Open CodyChew opened 3 years ago

CodyChew commented 3 years ago

glossary can include NUS/NUS resident image.png

nus-se-bot commented 3 years ago

Team's Response

We believe it is sufficiently clear.

Regardless, it is not a Medium severity.

Items for the Tester to Verify

:question: Issue response

Team chose [response.Rejected]

Reason for disagreement: A glossary serves to ensure that all stakeholders have a common understanding of the noteworthy terms. Their Developer Guide only consists of one term "Mainstream OS" and fail to include other important terms for clarity. For e.g., the term "NUS"/"NUS resident" was used only used at the User stories and it would not be clear for people outside our NUS community. Besides this term, the glossary also misses out on other terms related to their implementation such as "vendor", "menu" and "order". Below shows some example usages of certain terms where it was first introduced and other usages in their developer guide.

image.png

image.png

image.png

image.png

As each entity has their own characteristics and have unique behaviours or specifications, (e.g. vendor data/ vendor's menu/selected menu, order/ order item/order quantity) it would be clearer to developers to specify what each entity entails.

:question: Issue severity

Team chose [severity.VeryLow] Originally [severity.Medium]

Reason for disagreement: I agree that it should be downgraded but perhaps to severity "Low" and not "VeryLow". Justification shown above. Stakeholders should be clear of the main terms used in this project.