-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Game Physics: Lacking Non-Functional Requirements #53
Comments
Hello @Mornix. To make these issues easier to address, could you include more information? What is the title of section 5.2? What are some examples of missing non-functional requirements. What else should be added? If it makes sense, this issue could be split into multiple issues. |
(Issue #29) The Game Physics SRS mentions which nonfunctional requirements (Section 5.2) are a priority, but never details what the requirements for those categories are. For example:
|
@Mornix, please add the nonfunctional requirements that you have mentioned to the SRS. This would improve the documentation. In some cases you mention the NFRs, but include questions on how they are measured or checked. If you could make an attempt at how they might be written as requirements, that would be great. We can review as you go along. We don't have to have perfect NFRs, but you have noticed a weakness in the original documentation that should be improved upon. Once the new NFRs are in place, we will have to create another issue to port these changes to the Drasil version of the Game Physics SRS. |
Section 5.2 is very vague and lacking with respect to the non-functional requirements. The section could be greatly expanded.
The text was updated successfully, but these errors were encountered: