Open adenteo opened 1 year ago
Thank you for pointing this out. Firstly, on the point of flags, while each command has many flags that can be used, many of them are optional. The reason for doing this was that we wanted to have a detail-driven product that allowed users to plan their events for the semester knowing when and where they should be at a given time. Secondly, on the point of inability to search for any modules, this was in the pipeline, however due to the tight constraints of the TP, we did not have enough time to implement this feature and thus had to rely on NUSMods for searching up mods. As such, this is not in the scope of the project.
Team chose [response.NotInScope
]
Reason for disagreement: I still think that my point applies. The goal of the CLI application was to allow users, who can type fast, to complete certain tasks quicker. Considering the fact that users would have to refer back to NUSMods anyways to search for modules as noted by the team, there seems to be not much incentive to use the CLI app since it would be much easier to just click and add the modules when the users are already on NUSMods. Furthermore, the team mentioned that it was within their pipeline, which I feel should have been targetted since the start, and hence they would then be able to propose that their app allows users to keep track of their schedule offline, which was what I suggested in my initial report. Hence, I believe this issue is indeed in the scope.
The value proposition is as such
NUSPlanner aims to help students who are studying in the National University of Singapore better manage their hectic schedules, allowing them to take charge of their schedules and ensure that they have their upcoming events well-planned out.
However, I feel that the sheer amount of flags I have to indicate to add an entry, followed by the inability to search for any modules makes it quite difficult.
Perhaps the plus point that could be stated is this application allows for offline usage.