Open vigonometry opened 1 year ago
It does not hinder the user's information given that there were no jargons used, therefore it should not be medium. The suggestion could be implemented in future iterations, which is why it is set to not in scope. Furthermore, there is no specific requirement to clarify novel or hard terms (which our UG does not have.) Therefore, we set it to Low and not in scope.
Team chose [response.NotInScope
]
Reason for disagreement: [replace this with your explanation]
Details
As stated. This results in users/developers having to search the internet for what the terms mean and these may not match with the intended definition.
Expected
Developers are expected to produce a glossary of terms that users may be unfamiliar with in the User Guide (e.g. Command Line Interface, Graphical User Interface, command terminal, etc.)
They are also expected to produce a glossary of terms that differ from what a developer is expected to know in the developer guide (the only term mentioned is Mainstream OS, but other terms such as CRUD, in-app reference, etc. should also be added
Screenshots / Screen recordings