Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[CS2113T-F08-4] UniTracker #31

Open
wants to merge 553 commits into
base: master
Choose a base branch
from

Conversation

BlubberMonster
Copy link

Our product is user-specific as it allows users to customize and personalize their own module information and deadlines to suit their needs. Our product allows users to organize their own daily schedules and keep track of their deadlines all on one platform.

nagiteja pushed a commit to nagiteja/tp that referenced this pull request Mar 17, 2021
Returning to module information menu...
```
Given below is the sequence diagram for the feature:
![Diagram](diagrams/addNewReview.png)
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe can change the format of objects to "name :Class1" or " :Class1"
image

5) `Message` <br> Example: `Good job!`

Given below is the sequence diagram for the feature:
![Diagram](diagrams/addNewTask.png)
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe can end the lifelines of ModuleInfo and Module objects after they have been deleted
image

5) `Message` <br> Example: `Good job!`

Given below is the sequence diagram for the feature:
![Diagram](diagrams/addNewTask.png)
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

To reduce clutter, maybe some of the activation bars and return arrows can be omitted

Returning to module information menu...
```
Given below is the sequence diagram for the feature:
![Diagram](diagrams/addNewReview.png)
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe can consider breaking this sequence diagram into smaller fragments using ref frames

Copy link

@jovanhuang jovanhuang left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Overall, looks good! :)

Returning to module information menu...
```
Given below is the sequence diagram for the feature:
![Diagram](diagrams/addNewReview.png)

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Generally, quite a detailed sequence diagram. The logic flows correctly, from top to bottom.

It would be better if the "ModuleInfo" is ":ModuleInfo" instead. I see the same thing in other places.

5) `Message` <br> Example: `Good job!`

Given below is the sequence diagram for the feature:
![Diagram](diagrams/addNewTask.png)

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It would be good if the "printing error" methods are from the Logger instead of Ui class (same as the sequence diagram of addNewReview) for consistency. :)

### 4.05 Add Zoom Link

Given below is the sequence diagram for the feature:
![Diagram](diagrams/addZoomLink.png)

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It would be good if the methods being called have () behind it in the sequence diagram.

for Example: use printAndGetModule() instead of printAndGetModule. :)

This feature allows user to add user-defined module components and its related weightage for an
existing module.

![Diagram](diagrams/addComponent.png)

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In the sequence diagram of addComponent, it would be good if it is shown where "command" is used for after it was returned to Component. (or at least show that it is subsequently returned to ModuleInfo & Duke if "command" is used for other parts) :)

Copy link

@KimIdeas8 KimIdeas8 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Overall, nice DG over there! 👏💐🎂🥳💃

- `Storage`: Write data to, and loads data to hard disk

![Diagram](diagrams/MainArchitecture.png)

Copy link

@KimIdeas8 KimIdeas8 Mar 31, 2021

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  1. should ui be pointing to the other classes?
  2. for a class name like 'helpGraduation', a suggestion can be to write in CamelCase.
    image

user has to input a valid format for the __date__ and __time__ field (refer to section 3.3.1 of User
Guide or the example above), and our application will convert it to a more readable format for the
user. Using the example above,

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's nice to have numberings to improve formatting here :))

tasks in the `ArrayList` for the task type they chose will then be printed out, and the user has to
input the index of the task they want to delete. The task they select will then be deleted from
the `ArrayList`.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same for improving formatting :))

3) `Date` <br> Example: `2021-03-21`
4) `Time` <br> Example: `23:59`
5) `Message` <br> Example: `Good job!`

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

cool to add <br> after each example so the next argument can fall on the next line :))
image

Returning to module information menu...
```
Given below is the sequence diagram for the feature:
![Diagram](diagrams/addNewReview.png)
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sequence diagram seems to be quite detailed, however may not follow the standard format. Do remember to also include the colon : at the front of the class.
image

Sequence diagram should not end in with the object at the bottom I think. Consider just leaving the dotted lines if the object is not destroyed?
image

5) `Message` <br> Example: `Good job!`

Given below is the sequence diagram for the feature:
![Diagram](diagrams/addNewTask.png)
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The sequence diagram is very detailed, as such it may be a bit lengthy and confusing? Consider splitting the blocks into separate diagrams and explaining them separately.

Returning to module information menu...
```
Given below is the sequence diagram for the feature:
![Diagram](diagrams/addNewReview.png)
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Diagrams are also missing () for the methods.
image

Consider standardizing the sequence diagrams as the other diagrams in 4.01 and 4.05 have the brackets

image

@@ -1,34 +1,315 @@
# Developer Guide

## Design & implementation
## Table of Contents
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The numberings of the content page do not line up
image
Additionally, the formatting of the sub sections are not standardized

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Numbering in the sections themselves are ok.

Copy link

@soepaingzaw soepaingzaw left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Overall a comprehensive DG with aptly used sequence diagrams. Understandably, certain components are still in process. Further refinement will set you guys in for the final submission!

Comment on lines 140 to 148
**Problem**: When the user wants to review a module, he/she should be able to type ___multiple lines
of input___, as reviews are generally long and detailed.

**Solution**: A `while` loop is used to take in multiple lines of input until the input contains
the `/end` symbol. Anything typed after this `/end` symbol will be erased.

**When overwriting this review with a new review**: The old review will be printed for user
reference. The user will also be alerted that this action will delete his/her old review via a log.
The log is printed out as a warning.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Appreciate this form of writing due to readability and comprehension. Maybe this can be improved by mentioning the classes involved or methods involved? Similar to what was written in section 4.05.
image

Comment on lines 169 to 173
1) `Module Code` <br> Example: `CS2113T`
2) `Task Description` <br> Example: `Finish v2.0`
3) `Date` <br> Example: `2021-03-21`
4) `Time` <br> Example: `23:59`
5) `Message` <br> Example: `Good job!`

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Explanation here may not be intuitive due to format and structure of presentation viewed on the DG:

image

Perhaps improving format can increase comprehension.

Comment on lines 163 to 166
This feature allows the user to add tasks of type `task`, `assignment`, `midterm`, `final exam` to a
task list.

All task types (except `Task`, which contains arguments 1, 2 and 5) contain 5 arguments upon

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Best to standardize the capitalization of task types

### 4.05 Add Zoom Link

Given below is the sequence diagram for the feature:
![Diagram](diagrams/addZoomLink.png)

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good Sequence diagram. Perhaps it is alright to end the sequence diagram at the bottom with just lifelines? Maybe there is no need to end it with the object "boxes"

image

motorpeople101 and others added 30 commits April 12, 2021 20:14
update userguide on cap simulator.
fix checkstylemain in JavaDoc for Component class.
removed warning from DG + JavaDoc
update PPP and fix bug in moduleInfo.
make more OOP, fix acadamicRecords, ModuleGradeEnum prints to Ui class.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

10 participants