not really a non-functional requirement

[nus-pe-bot]

Note from the teaching team: This bug was reported during the Part II (Evaluating Documents) stage of the PE. You may reject this bug if it is not related to the quality of documentation.

---

can been seen in page 30 in dg "project scope", the first two points are functional requirements.

---

_{[original: nus-cs2103-AY2021S1/pe-interim#4957]}

[jianhandev]

Team's Response

According to the textbook, Non-functional requirements specify the constraints under which system is developed and operated.

One constraint we face is the complexity that may arise if the app were to handle detailed medical information about patients. Such complexity can potentially lower the user's efficiency. Hence, we specify the constraint that the application is not needed to handle detailed medical information as Baymax is an application geared towards making appointment management more efficient.

As for the second point, we believe it is a valid NFR, a similar example is given in the textbook:

Duplicate status (if any):

--