Value proposition in the User Guide does not match the product

[tohpinren]

The the value proposition of the product in the introduction does not match the product. The introduction says that CCACommander is a desktop application that helps CCA leaders record details of their members and events, whilst tracking every member’s attendance.. However, the product only allows for the enrolment of a member to an event but does not help in keeping track of the member's attendance for the event - i.e. whether the member actually shows up for the event itself. There is a mismatch between the product and the value proposition in the user guide.

[nus-se-script]

Team's Response

Hello there, thank you for raising this issue but we believe that through CCACommander, you will be able to track the members' attendance by adding the number of hours accompanied with any remark. For instance, a member attending the event would have at least 1 hour and possibly any remark to give more information regarding their attendance. On the other hand, we are also able to mark the member as absent by adding a remark saying that they were absent and leaving the hours as 0.

Therefore we will be rejecting this issue. Thank you.

Items for the Tester to Verify

:question: Issue response

Team chose [response.Rejected]

• [x] I disagree

Reason for disagreement: This user guide introduces the product and says that one of its core features is tracking every member’s attendance. However, this was not made clear in the features that were presented in the user guide and in the product itself. At first glance, my impression of "being able to track attendance" is to mark whether the member actually attended the meeting or not. However, there was no clear indication for how to do there in the user guide. The user can only indirectly do this by adding a remark or adding hours to the enrolment which are both optional fields. Therefore, I do not think the product presented fulfils the core feature of "tracking attendance" adequately. If there was a component of the user guide that explains how you can track attendance by adding hours and remarks it would be more helpful.

---

## :question: Issue severity Team chose [`severity.VeryLow`] Originally [`severity.High`] - [x] I disagree **Reason for disagreement:** As explained above, there is a mismatch between the value proposition in the user guide and the product itself. It is not clear both in the product and in the user guide how it is intended for the user to track the attendance of the members for events (ie whether he attends and how many hours). Additionally, how the team intended to track the attendance is by two **optional** fields. This does not fulfil one of its core value proposition proposed. Therefore, I think this documentation affects most users and causes major problems for users because it is not clear how the user can achieve this value proposition through both the product and the user guide.

---