nus-cs2103-AY2425S1 / forum

12 stars 0 forks source link

Missing team size and naming convention #769

Closed annabellekk closed 4 hours ago

annabellekk commented 5 hours ago

Hi, in the textbook, it says to state the team size under the section of planned enhancement so that the tester can know whether the count exceeds the allowed number. If the team does not state the team count, is this a documentation bug? Since it is only applicable in this course to aid testing.

Screenshot 2024-11-16 at 11 06 35 AM

Secondly, if the team names the sections differently, e.g. known problems / known bugs instead of known issues, or future plans / future enhancements instead of planned enhancements can I assume that they are each referring to the known issues and planned enhancement section as per the textbook, and apply the same rules? (i.e. bugs in known issues do not have immunity but bugs in planned enhancements do)

damithc commented 5 hours ago

Hi, in the textbook, it says to state the team size under the section of planned enhancement so that the tester can know whether the count exceeds the allowed number. If the team does not state the team count, is this a documentation bug? Since it is only applicable in this course to aid testing.

@annabellekk Yes, requirements imposed by the course on the tP are non-functional project requirements. Not meeting them is a bug.

Secondly, if the team names the sections differently, e.g. known problems / known bugs instead of known issues, or future plans / future enhancements instead of planned enhancements can I assume that they are each referring to the known issues and planned enhancement section as per the textbook, and apply the same rules? (i.e. bugs in known issues do not have immunity but bugs in planned enhancements do)

Yes, if there is no ambiguity, you can ignore minor deviations in the section name.

annabellekk commented 4 hours ago

Thank you prof!