engenhui1999
commented
1 year ago Team's Response
Keeping track of contact is part of managing an event, similar to how we have features such as revenue and remind helps in managing an event. Our main target users are freelancers and the benefits is to help streamline "your freelancing event management tasks" mentioned in the UG. It is not guaranteed that every event has a specific contact as the events within the freelancer's event book may just be his own personal events or software that he is creating to earn money, thus this is not generic enough and as a result, contact is not part of the main use cases.
Hence, we believe that linkcontact or contact features is an additional feature used to help manage events, but it is not always required in some use cases. Therefore, we believe that our use cases is general enough even for freelancers who do not require the linkcontact or contact features.
Duplicate status (if any):
--
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.
From the UG introduction it seems like Paidlancers is an application for the common freelancer to keep track of events, but there is also the added functionality of keeping track of other contacts and linking the contact to the event.
Do correct me if I misunderstood, the "clients" here are the ones paying the freelancer (the user of Paidlancer) for their service, and Paidlancer helps the user keep track of his clients by also being able to link clients to the event? If so then there could be more elaboration for use cases and also the benefits of using the linkcontact feature in the linkcontact section of the UG and also in the introduction as well.
[original: nus-cs2103-AY2223S2/pe-interim#190] [original labels: severity.VeryLow type.DocumentationBug]