Project: Recretary

Recretary is a one-stop contact and meeting management application specially made for secretaries, to help them improve productivity in businesses. For fast typists, Recretary is the faster option for finishing contact management tasks than traditional GUI apps because it is optimized for use via a Command Line Interface (CLI) while still having the benefits of a Graphical User Interface (GUI).

Given below are my contributions to the project.

  • New Feature: Added the ability to find all meeting within certain hours relative to the time of user’s local machine.
    • What it does: allows the user to view a list of upcoming meetings, user will specify the time
    • Justification: This feature improves the product because a user can now proactively check for upcoming meetings (filter out late future meetings)
    • Credits: The design and implementation is somewhat similar to find command in the original AB3 base code.
  • New Feature: Added a edituserpref command that allows the user to customize the interval value between meetings, and store the value inside preferences.json
    • What it does: allows the users to edit the interval value inside preferences.json, this will affect the behavior of conflict checking
    • Justification: This feature improves the product because now there is a customized break in between any two consecutive meetings. This break is important as it represents travel time or rest time in between meetings. This prevents users from scheduling tight/unreasonable meetings that might make the boss angry.
    • Highlights: Although we only allow user to edit interval value in preferences.json for now, I implement it with ArgumentMultimap when parsing user input. Therefore, it is quite easy to extend this feature to allow users to edit and even add new field in preferences.json

  • Code contributed: RepoSense link

  • Project management:
    • Managed releases v1.3b on GitHub
  • Enhancements to existing features:
    • Refactor code base and test cases so that all contacts have compulsory company fields and optional company role fields, minor refactor to differentiate contact and meeting commands also (Pull requests #50, #54)
    • Implement sort function for UniqueMeetingList, by calling this function whenever the order of list changes, this will make sure the meeting list is always sorted at all time. (Pull requests #91)
    • Implement conflict checking function for UniqueMeetingList and call this method whenever needed, eg: after addmeeting, editmeeting, etc (Pull requests #104, #116, #186)
    • Wrote substantial test cases for features/enhancement implemented with heuristics in mind. (Pull request #186)
  • Documentation:
    • User Guide:
      • Added documentation for the features edituserpref and remindmeeting #171
      • Did cosmetic tweaks to existing documentation of features addmeeting, editmeeting, etc: #171
      • Minor improvement to overall user guide #171
    • Developer Guide:
      • Minor edit to some old UML diagrams, eg: diagram for Model Component,etc .
      • Added sections(UML diagrams and description, etc) for edituserpref and remindmeeting.
      • Add appendix for Instructions for Manual Testing
  • Community:
    • Reported bugs and suggestions for other teams in the class (examples: 1, 2, 3, 4)