nus-se-bot
commented
9 months ago Team's Response
There are three parts in this report:
- Pointer 20
- Pointer 21
- Pointer 22
Each bug should be a separate issue i.e., do not report multiple problems in the same bug report. If there are multiple bugs in the same report, the dev team will select only one of the bugs in the report and discard the others.
https://nus-cs2103-ay2324s1.github.io/website/admin/tp-pe.html#pe-phase-2-developer-response
Where applicable, we select the first part to respond to.
Non-functional requirements specify the constraints under which the system is developed and operated.
Compliance with regulations, Documentation
-
Pointer 20 is an NFR. For example, if we wanted to skip having any
Ui.pngby deleting it altogether, or instead decided on our own naming convention such asConText_UI.jpg, we would violate constraints under which the project must be developed.Add a UI mockup of your intended final product. Note that the image of the UI should be docs/images/Ui.png so that it can be downloaded by our scripts. Limit the file to contain one screenshot/mockup only and ensure the new image is roughly the same height x width proportions as the original one. Reason: when we compile these images from all teams into one page (example), yours should not look out of place.\ If you did the above update correctly, UI mock up and profile photos should appear in your project website and this Project List Page.
-
Pointer 21 is an NFR. For example, if we wanted to skip the about us page by deleting it altogether, wanted to change the template a lot, or wanted to skip having any validly named profile photo, we would violate constraints under which the project must be developed.
Please follow the format closely or else our scripts will not be able to give credit for your work.
Add your own details. Include a suitable photo as described here.
The filename of the profile photo should be docs/images/github_username_in_lower_case.png\ Note the need for lower case ( why lowercase?) e.g. JohnDoe123 -> docs/images/johndoe123.png not docs/images/JohnDoe123.png.\ If your photo is in jpg format, name the file as .png anyway.
-
Pointer 22 is an NFR. For example, if we wanted to skip having any PPPs in the project, wanted to use our own naming convention for the raw page files, wanted to specify arbitrarily few sections in our PPPs, or wanted our PPPs to go over the indicated page limits per section, we would violate constraints under which the project must be developed.
Items for the Tester to Verify
:question: Issue response
Team chose [response.Rejected]
- [ ] I disagree
Reason for disagreement: [replace this with your explanation]
## :question: Issue severity Team chose [`severity.Low`] Originally [`severity.Medium`] - [ ] I disagree **Reason for disagreement:** [replace this with your explanation]
Non-functional requirements specify the constraints under which the system is developed and operated. These points were written under non-functional requirements in DG. However, it is not clear how its a NFR.