ay1920s1-cs2113t-w17-3 / main

🦉OwlMoney is an application that helps you manage your finances

OwlMoney

• OwlMoney is a finance tracker desktop application. It has a Graphical User Interface (GUI) but most of the user interaction happens in the Command Line Interface (CLI).

• OwlMoney is designed to help undergraduates and fresh graduates track and manage their finanaces.

• OwlMoney is optimized for those who prefer using a CLI. The commands used to interact with the application are designed to be simple and intuitive, so even those who are unfamiliar with CLI can use OwlMoney with ease.

• OwlMoney allows users to:

  • track their finances quickly and more conveniently.

  • track their finances in different currencies. (coming soon)

  • provide an informed decision so that the user is able to decide how much to spend and save.

Site Map

• User Guide

• Developer Guide

• About Us

• Contact Us

Acknowledgements

• Original source: PersonalAssistant-Duke created by SE-EDU initiative

• Libraries used: JUnit5, OpenCSV, ShadowJar

• Modified icon from Font Awesome

Licence : MIT

main's Issues

DG: Lacking multiple appendix details for v1.1

• Appendix A: Product Scope
• Appendix B: User Stories
• Appendix C: Use Cases
• Appendix D: Non Functional Requirements
• Appendix E: Glossary
• Base UML diagrams or high level diagrams

As an existing user, I can edit recurring expenditure

So that I can amend the recurring expenses.

AboutUs missing

AboutUs page is required this week with relevant details of each team member.

As an existing user, I can compare overall expenditure of different month

So that I can review my spending.

As a careless user, I can edit my expenditure

So that I can correct my errors.

Feedback on week 6 project progress for CS2113T-W17-3

Leftovers from the previous week

• You are done with previous weeks work(:heavy_check_mark: well done!)

Progress of this week

• A version tagged A-Gradle is in the repo(:heavy_check_mark: well done!)

• A version tagged A-CheckStyle is in the repo(:heavy_check_mark: well done!)

• A version tagged A-Jar is in the repo(:heavy_check_mark: well done!)

• A version tagged B-Reminders is in the repo(:heavy_check_mark: well done!)

• A version tagged B-FindFreeTimes is in the repo(:exclamation: try to do by next milestone)

• A version tagged B-ViewSchedules is in the repo(:heavy_check_mark: well done!)

• A version tagged B-DetectAnomalies is in the repo(:heavy_check_mark: well done!)

• A version tagged B-Snooze is in the repo(:heavy_check_mark: well done!)

• A version tagged B-TentativeScheduling is in the repo(:exclamation: try to do by next milestone)

• A version tagged B-RecurringTasks is in the repo(:heavy_check_mark: well done!)

• A version tagged B-DoAfterTasks is in the repo(:exclamation: try to do by next milestone)

• A version tagged B-DoWithinPeriodTasks is in the repo(:exclamation: try to do by next milestone)

• A version tagged B-FixedDurationTasks is in the repo(:exclamation: try to do by next milestone)

• Updated the README page(:exclamation: try to do by next milestone)

• Made a release containing a JAR file.(:heavy_check_mark: well done!)

Individual progress of @mong-nus

• Team repo forked to your GitHub account(:heavy_check_mark: well done!)

• You have reviewed at least 1 PR(:exclamation: try to do by next milestone)

PR created for:

• [CS2113T-W17-3]-mong-nus-B-Reminders

Individual progress of @shamussy

• Team repo forked to your GitHub account(:heavy_check_mark: well done!)

• You have reviewed at least 1 PR(:heavy_check_mark: well done!)

PR created for:

• [CS2113T-W17-3]-shamussy-B-RecurringTasks

• [CS2113T-W17-3]-shamussy-A-Travis

• [CS2113T-W17-3]-shamussy-A-Jar

• [CS2113T-W17-3]-shamussy-A-CheckStyle

• [CS2113T-W17-3]-shamussy-A-Gradle

Individual progress of @BrianTKM

• Team repo forked to your GitHub account(:heavy_check_mark: well done!)

• You have reviewed at least 1 PR(:heavy_check_mark: well done!)

PR created for:

• [CS2113T-W17-3]-BrianTKM-B-Snooze

Individual progress of @TerenceTanWT

• Team repo forked to your GitHub account(:heavy_check_mark: well done!)

• You have reviewed at least 1 PR(:exclamation: try to do by next milestone)

PR created for:

• [CS2113T-W17-3]-TerenceTanWT-B-DetectAnomalies

Individual progress of @valerietyj

• Team repo forked to your GitHub account(:heavy_check_mark: well done!)

• You have reviewed at least 1 PR(:exclamation: try to do by next milestone)

PR created for:

• [CS2113T-W17-3]-valerietyj-B-ViewSchedules

Tutor: @jylee-git

_{Note: the above observation was done by the CS2113-feedback-bot and covers changes up to 2019-09-18 00:00:00 only. If you think the above observation is incorrect, please let us know by replying in this thread. Please include links to relevant PRs/comments in your response.}

As an existing user, I can set short and long term financial goals

So that I can achieve financial stability.

As an indecisive user, I can edit my existing financial goals

So that it can adapt to any changes.

As a credit card user, I can delete credit cards from my account

So that I can remove wrongly added credit cards.

Phase 1 code not ported to master

UG: Features and command syntax not up to date

Multiple syntax changes needs to be reflected on the UG with reference to latest agreement on syntax structure

As an existing user, I can search for specific transactions by category, description or date

So that I can search and view specific transaction records for purpose such as deletion or edit.

As an existing user, I can edit my income

So that I can change it when there are changes to my income.

As an existing user, I can have my money transfer from one bank account to another bank account

so that I can organize them as investment or saving account for ease in tracking different expenditure.

As an existing user, I can be reminded when my payment is due

So that I can pay on time without penalties.

Feedback on week 5 project progress for CS2113T-W17-3

Progress of this week

• A version tagged A-Packages is in the repo(:heavy_check_mark: well done!)

• A version tagged v1.0 is in the repo(:heavy_check_mark: well done!)

Tutor: @jylee-git

_{Note: the above observation was done by the CS2113-feedback-bot and covers changes up to 2019-09-11 00:00:00 only. If you think the above observation is incorrect, please let us know by replying in this thread. Please include links to relevant PRs/comments in your response.}

As a credit card user, I can add new credit cards to my account

So that I can credit my spending till the end of the month.

As an organised user, I can list my card details

So that I can have a view of my card details.

As an existing user, I can view recurring expenditure

So that I can review it to check for error.

As an achievement oriented user, I can view different types of achievements

So that I can view my achievement that has been attained or yet to be attained

As an achievement oriented user, I can view the description of an achievement

So that I can understand how to achieve it.

As a careless user, I can delete my expenditure

So that I can remove wrongly added expenses.

As an organised user, I can list my card expenditures

So that I can have a view of my spending.

TaskList class switch statement missing default case in switch statement

The switch statement on line 38 does not have a default case.

As an existing user, I can delete my investment account (bond)

so that I can sell it before the maturity date.

As an achievement oriented user, I can gain achievements when I achieve system pre-defined goals

So that I am motivated to pursue my financial goal.

As a credit card user, I can edit my credit card details

So that I can update the details when there are changes to my card.

Feedback on week 8 project progress for CS2113T-W17-3

Team progress for mid v1.2

• Updated the README page(:heavy_check_mark: well done!)
• Updated the About us page(:heavy_check_mark: well done!)
• Mockup-photo uploaded to docs/images and named Ui.png in the correct case.(:heavy_check_mark: well done!)
• Issue tracker setup:
  • type.* labels setup(:heavy_check_mark: well done!)
  • priority.* labels setup(:heavy_check_mark: well done!)
  • severity.* labels setup(:heavy_check_mark: well done!)
• Milestones setup:
  • Milestone v1.2 setup(:heavy_check_mark: well done!)
  • Milestone v1.3 setup(:heavy_check_mark: well done!)
  • Milestone v1.4 setup(:heavy_check_mark: well done!)
• Milestone v1.2 planned:
• A suitable deadline set(:exclamation: try to do by next milestone)
• Issues allocated to it #56 #55 #54 #44 #29 #25 #23 #22 #21 #20 (:heavy_check_mark: well done!)

Individual progress of @mong-nus for mid v1.2

• Team repo forked to your GitHub account(:heavy_check_mark: well done!)
• Photo uploaded(:heavy_check_mark: well done!)
• Merged updates to code (Java/FXML) files during the past week(:exclamation: try to do by next milestone)
• Has issues/PRs assigned for the next milestone(:exclamation: try to do by next milestone)
• You have reviewed at least 1 PR #71 (:heavy_check_mark: well done!)

Individual progress of @shamussy for mid v1.2

• Team repo forked to your GitHub account(:heavy_check_mark: well done!)
• Photo uploaded(:heavy_check_mark: well done!)
• Merged updates to code (Java/FXML) files during the past week(:heavy_check_mark: well done!)
• Has issues/PRs assigned for the next milestone(:heavy_check_mark: well done!)
• You have reviewed at least 1 PR (:exclamation: try to do by next milestone)

Individual progress of @BrianTKM for mid v1.2

• Team repo forked to your GitHub account(:heavy_check_mark: well done!)
• Photo uploaded(:heavy_check_mark: well done!)
• Merged updates to code (Java/FXML) files during the past week(:exclamation: try to do by next milestone)
• Has issues/PRs assigned for the next milestone(:exclamation: try to do by next milestone)
• You have reviewed at least 1 PR #70 (:heavy_check_mark: well done!)

Individual progress of @TerenceTanWT for mid v1.2

• Team repo forked to your GitHub account(:heavy_check_mark: well done!)
• Photo uploaded(:heavy_check_mark: well done!)
• Merged updates to code (Java/FXML) files during the past week(:exclamation: try to do by next milestone)
• Has issues/PRs assigned for the next milestone(:exclamation: try to do by next milestone)
• You have reviewed at least 1 PR (:exclamation: try to do by next milestone)

Individual progress of @valerietyj for mid v1.2

• Team repo forked to your GitHub account(:heavy_check_mark: well done!)
• Photo uploaded(:heavy_check_mark: well done!)
• Merged updates to code (Java/FXML) files during the past week(:exclamation: try to do by next milestone)
• Has issues/PRs assigned for the next milestone(:heavy_check_mark: well done!)
• You have reviewed at least 1 PR (:exclamation: try to do by next milestone)

Tutor: @jylee-git

_{Note: the above observation was done by the CS2113-feedback-bot and covers changes up to 2019-10-09 00:00:00 only. If you think the above observation is incorrect, please let us know by replying in this thread. Please include links to relevant PRs/comments in your response.}

As a user, I can add saving accounts

So that I can categorise and track my finances.

Feedback on week 7 project progress for CS2113T-W17-3

Team progress for v1.1

• Updated the README page(:heavy_check_mark: well done!)
• Made a release containing a JAR file.(:heavy_check_mark: well done!)
• Issue tracker setup:
  • type.* labels setup(:heavy_check_mark: well done!)
  • priority.* labels setup(:heavy_check_mark: well done!)
  • severity.* labels setup(:heavy_check_mark: well done!)
• Milestones setup:
  • Milestone v1.1 setup(:heavy_check_mark: well done!)
  • Milestone v1.2 setup(:heavy_check_mark: well done!)
  • Milestone v1.3 setup(:heavy_check_mark: well done!)
  • Milestone v1.4 setup(:heavy_check_mark: well done!)
• Milestone v1.1 completed(:heavy_check_mark: well done!)
• Milestone v1.1 closed(:heavy_check_mark: well done!)
• Code tagged as v1.1(:heavy_check_mark: well done!)
• Updated the About us page(:heavy_check_mark: well done!)

Individual progress of @mong-nus for v1.1

• Team repo forked to your GitHub account(:heavy_check_mark: well done!)
• Photo uploaded(:heavy_check_mark: well done!)
• PR created: #65 #17 (:heavy_check_mark: well done!)
• You have reviewed at least 1 PRhttps://github.com//pull/66 #64 #60 (:heavy_check_mark: well done!)

Individual progress of @shamussy for v1.1

• Team repo forked to your GitHub account(:heavy_check_mark: well done!)
• Photo uploaded(:heavy_check_mark: well done!)
• PR created: #59 #53 #68 #66 #50 #19 #15 #14 #13 #12 #11 #10 #8 #4 #2 (:heavy_check_mark: well done!)
• You have reviewed at least 1 PRhttps://github.com//pull/67 #51 #16 #17 (:heavy_check_mark: well done!)

Individual progress of @BrianTKM for v1.1

• Team repo forked to your GitHub account(:heavy_check_mark: well done!)
• Photo uploaded(:heavy_check_mark: well done!)
• PR created: #67 #64 #51 (:heavy_check_mark: well done!)
• You have reviewed at least 1 PRhttps://github.com//pull/68 #19 #18 #16 #15 #14 #13 #12 #11 #10 #8 #4 #2 (:heavy_check_mark: well done!)

Individual progress of @TerenceTanWT for v1.1

• Team repo forked to your GitHub account(:heavy_check_mark: well done!)
• Photo uploaded(:heavy_check_mark: well done!)
• PR created: #60 #18 (:heavy_check_mark: well done!)
• You have reviewed at least 1 PRhttps://github.com//pull/59 #65 (:heavy_check_mark: well done!)

Individual progress of @valerietyj for v1.1

• Team repo forked to your GitHub account(:heavy_check_mark: well done!)
• Photo uploaded(:heavy_check_mark: well done!)
• PR created: #16 (:heavy_check_mark: well done!)
• You have reviewed at least 1 PRhttps://github.com//pull/53 (:heavy_check_mark: well done!)

Tutor: @jylee-git

_{Note: the above observation was done by the CS2113-feedback-bot and covers changes up to 2019-10-02 00:00:00 only. If you think the above observation is incorrect, please let us know by replying in this thread. Please include links to relevant PRs/comments in your response.}

As a new user, I can create my own profile

So that I can start keeping track of my finances.

As an existing user, I can edit my profile details

So that I can keep my details up to date.

Issues with error messages

• deadline gg /by 12/12/2019 1200
  Output: ☹ OOPS!!! Time must be in the format day#/month#/yyyy hhmm.
  Issue: Error message will have #

• event gg /at 12/12/2019 1200
  Output: ☹ OOPS!!! Time must be in the format day#/month#/yyyy hhmm.
  Issue: Error message will have #

• done
  Output: ☹ OOPS!!! The task number should be numeric only
  Issue: Error should be "The task number cannot be empty"

As a credit card user, I can charge my expenditures to my credit card

So that I can track my credit card rebates.

Produce functional code for v1.1

• working code for: /add /savings
• working code for: /delete /savings
• working code for: /add /expenditure
• working code for: /delete /expenditure

As an existing user, I can add investment account (bond)

so that I can track my investment bond earnings.

As an existing user, I can undo my last command

So that I can revert back to the previous state in the event of a mistake.

As an organised user, I can list my expenditure

So that I can have a view of my spending.

As an existing user, I can set recurring expenditures

So that I do not need to enter it repeatedly for each month.

As a spendthrift, I can be warned when I am close to exceeding my budget or have exceeded my budget

So that I will reduce my spending.

As a user with income, I can edit recurring income

So that I can remove it accordingly.

As an existing user, I can edit my investment account (bond)

so that I can amend any errors in my investment bond account.

As an organised user, I can export to view my expenditures statement

So that I can review my expenditure records with ease.

Javadoc failing checkstyle in Parser Class

There is a missing period in Line 27 and Line 37 of the Javadocs in Parser.java
Line 27:
* Checks if the user has any more input during input redirection
Line 37:
* Takes in user input line by line

As a user, I can add income

So that I can calculate my recommended budget.

As a spendthrift, I can add expenditures

So that I can keep track of my spending.

As a user with income, I can view recurring income

So that I can review it to check for error.

As an existing user, I can have my investment account’s (bond) interest being accumulated automatically every half yearly

so that I do not have to go through the hassle of entering it manually.

As a user with income, I can set recurring income

so that I do not need to enter it repeatedly for each month.

As an existing user, I can edit my saving account

So that I can correct any errors.