Project: JeeqTracker

JeeqTracker is a desktop application created for home-based business owners / resellers that helps them manage the clients that they interact with by keeping track of their BUY / SELL transactions, and REMARKS of clients. It is written in Java, and has about 10 kLoC.

Given below are my contributions to the project.

  • New Feature: Added buy and sell commands
    • What it does: allows the user to create buy and sell commands and link them to the specific client to keep track of their transactions with them.
    • Justification: This feature is essential for users to input transactions so that our application can keep track of them.

  • Code contributed: RepoSense link

  • Project management:
    • Managed release v1.3 PE (1 release) on Github
  • Enhancements to existing features:
    • Refactored multiple classes to transition from AB3 to JeeqTracker
      • Person to Company (Pull requests #97, #109, #120)
      • AddressBook to JeeqTracker (Pull request #112)
      • POC to Company (Pull request #173, #177, #183)
      • Company to Remarks (Pull request #200)
    • Updated storage to include POCs which has been changed to remarks (Pull request #138)
    • Updated edit command to allow users to have more freedom in entering phone number, and email. Instead of blocking user input like +65 9876 5432 (HOME), a warning message will be given instead (Pull request #222)
    • Upgraded buy and sell commands to allow easy continuous inputs. (Pull request #151)
    • Removed tags from Remark as it was unnecessary to have tags in remarks. (Pull request #278)
  • Documentation:
    • Developer Guide:
      • Updated Storage component (Pull request #300)
      • Updated buy/sell transactions feature implementation (Pull request #308)
      • Added buy/sell transactions in Appendix: Manual testing section (Pull request #308)
      • Added use cases for buy/sell transactions (Pull request #308)
  • Community:
    • PRs reviewed (with non-trivial review comments): #184, #153, #136, #111
    • Reported bugs and suggestions for other teams in the class (examples: 1, 2, 3, 4, 5)
    • Contributed to a forum discussion. (#64)