[v1.5][F12-B2] Personal Trainer Pro

[hypertun]

No description provided.

[nus-se-pr-bot]

Hi @hypertun, your pull request title is invalid.

For phase A, it should be in the format of [Learning Outcome ID][Team ID] Your Name, where [Learning Outcome ID] has no dashes or spaces (e.g. [W3.1a]) and [Team ID] has one dash only and no spaces (e.g. [W14-A2] means Wednesday 2pm (14 hrs), Phase A, Team 2).

For phase B, it should be in the format of [v1.x][Team ID] Product Name, replacing v1.x with current milestone progress.

Please follow the instructions given strictly and edit your title for reprocessing.

Submit only one learning outcome per pull request (unless otherwise stated in instructions) and do remember to create your branches from the commit where the master branch is pointing at so that each PR you submit only consist of commits meant for the activity.

Note: this comment is posted by a bot. If you believe this is done in error, please create an issue at cs2103-pr-bot and add a link to this PR.

[erik0704]

Important Do remember to give credit to code sources if your code is inspired from elsewhere. Just changing the variable names will not help - we will still be able to tell that it has been adapted. Please follow the guidelines as given in the learning resources!

Also please do not close this PR as we will use it to track your progress.

[erik0704]

Nice work updating the badge.

[erik0704]

Might want to be more specific in defining target user profile. Who are they? What they do? What are their problems? What are their current solutions? What your value proposition that might be better than these current solutions?

[erik0704]

Nice work with the command alias but remember to also update the user guide to match new behavior.

[erik0704]

@hypertun @ppalla0325 @wayneong95 @wenhao53 you should think through the product's end behavior and write the entire UG, for all the commands which you would want to implement. Then mark the features as future (v2.0) which you do not intend to implement in the project duration.

We should be able to understand what is your product aiming to do from reading the User guide, which as of now is not the case.

You should also indicate which features can be expected from which milestones. The PR title should be updated as weeks go by, i.e. now it should be 1.1.

One more thing, remember to enable auto-publishing features for documentations (ReadMe, AboutUs, UG, DG etc...)

[erik0704]

@hypertun @ppalla0325 @wayneong95 @wenhao53 I would want you to mention the following in your Developer guide

1. For each team member what are the features (major and minor) you are proposing?
2. Within the scope of the project, how does it fit in (just a one or 2 line summary)

[hypertun]

@erik0704 It was already added into the developer guide on Monday

[erik0704]

@hypertun @ppalla0325 @wayneong95 @wenhao53 Regarding how to documenting your enhancement implementation:

• Diagrams are very strong tools to effectively convey your information. It can shows the internal structure of your code in a high level manner. There are several tools which can help you creating UML diagrams.
• Quoting code snippets is ok but should be used sparingly only.
• If you want to convey UI components, screenshot tools are nice to have.
• Fix your formatting for the Implementation perhaps?