[CS2113T-F14-1] CCA Manager

[JohnNub]

CCA Manager
CCA Manager is a revolutionary tool that changes the way you can manage interest groups with unrivaled efficiency and simplicity. Its lightweight Command Line Interface (CLI) allows administrators to breeze through tasks quickly and easily while offering powerful features to advanced users.

[thngyuxuan]

Overall, this DG was well written, with simple diagrams that are easy to understand. Although the explanations are a bit lengthy, it was broken down into steps that made it easy to understand as well. Also, there are some minor formatting issues, such as section 3.5.4:

[thngyuxuan]

I'm not sure if the problem is on my computer, but on GitHub pages, the 'Setting Up' section comprises of only one sentence, 'Refer to the guide here.' with no hyperlink or any other prompts when I mouse over the words.

[tengkianen]

Please correct your numbering when revising the Developer Guide

[tengkianen]

Can you move the arrow to the start of the activation bar?

[tengkianen]

Can you move the condition to avoid it overlapping with the activation bar?

[tengkianen]

Can you move the dotted line to the middle of the activation bar?

[tengkianen]

Also, can you format the conditions to avoid overlapping with the activation bar?

[tengkianen]

Are you deleting the Event object when calling the clear() method?

[tengkianen]

Is the activation bar too long in this case?

[kaiwen98]

Overall, it is a detailed and well-substantiated Developer's Guide. Some formatting errors are indeed present, but I did get a good idea on the architecture and design decisions behind the application. Good Job!

[kaiwen98]

Not too sure if a class diagram is the correct format for the architecture of the application. I would recommend making of the diagram using Powerpoint!

The use of arrows is rather unclear here as to its purpose; I am not sure what the arrowhead means. Perhaps some annotation towards the arrow can be helpful in explaining the diagram better!

[kaiwen98]

As a newcomer to the application, I may not be familiar with the different components of the architecture. Perhaps a more detailed description with regards to each component can be helpful in explaining more clearly the function of each particular component!

For instance,

• [UI] : The UI of the App. Handles all console outputs onto the CLI interface.
• [Logic] : The command executor.

[kaiwen98]

Pertaining to eventList, the activation bar should start at the point of printEventList(), since class is active when the method is called. Similarly, the activation bar for the eventList should end at the return call, not extend beyond along the lifeline.

For the condition of the loop, I would choose a better phrasing, perhaps: "For each item in the arrayList".

[kaiwen98]

Pertaining to the condition "checkIfEventNameMatch()|checkIfEventDateMatch()", I would find it slightly confusing both in terms of format and the equivalent meaning conveyed. I would recommend implementing a separate method to handle checking of event altogether, which can then replace the expression above. Otherwise, I would recommend adding comments to further explain the expression.