Missing important terms in glossary of DG

[ziqing26]

Expected:

The glossary is supposed to contain definition of key terms in the project such as application submission interview deadlines as they have application-specific definitions that need to be made clear to developers.

Actual:

The glossary was too brief such that it does not contain important project-specific definitions.

[nus-se-bot]

Team's Response

Glossary is supposed to include terms that may be unfamiliar to the target audience. In the case of DG, the target audience should be the developers who are interested in the design considerations and implementation details of our product. It's really unnecessary to include the definitions of terms such as application submission interview deadlines as they should be quite obvious.

Indeed, these are application-specific definitions that need to be made clear, but it's the user, not the developer, to whom we need to make clear. And in this case, we've already included terms such as application in the glossary of our UG.

Items for the Tester to Verify

:question: Issue response

Team chose [response.Rejected]

• [ ] I disagree

Reason for disagreement: [replace this with your reason]

---