tp

Dave Gunawan - Project Portfolio Page

Overview

Future Academic Planner (FAP) is a robust academic management software designed to help streamline NUS Computer Engineering (CEG) student’s academic journey at NUS. If you can type fast, FAP can get your module planning done faster than your traditional GUI app.

• New Feature: View modules needed to graduate
  • What it does: Allows users to view specific CEG Modules they have to take in order to fullfil graduation requirements.
  • Justification: Improves product by helping users keep track of what core modules they need to complete.
  • Highlight: Requires understanding of the user’s viewpoint to maintain feasible implementation without compromising the user’s experience.
• New Feature: View specific module information
  • What it does: Allows users to view a specific NUS AY23/24 module’s title, MCs and description within the CLI.
  • Justification: Enhances user experience by allowing users to view what a certain module is about without leaving the application.
  • Highlight: Requires reworking the CommandMetadata to allow matching of optional regex.
• New Feature: Remove modules
  • What it does: Allows users to remove a module from the current list.
  • Justification: Necessary in the case of a mistaken input or a failed module.
  • Highlight: Involves robust integration and exception handling to ensure it works without fail.

• Code Contributed: Reposense

• Enhancements to existing features:

  • Implemented CommandMetadata to support optional user arguments (Pull request #104).
  • Implemented support for equivalent modules in CEGModules (Pull request #85).
  • Thorough JUnit tests for ViewGraduateCommand (Pull request #147).
  • Thorough JUnit tests for RemoveCommand (Pull request #66)
• Documentation:
  • User Guide:
    • Added documentation for graduate, remove, view c/COURSE_CODE (Pull requests #87, #147).
  • Developer Guide:
    • Design details and class diagram of Command class (Pull request #160).
    • Implementation details and sequence diagrams of the view commands (Pull request #160).
    • Appendix: Instructions for manual testing (Pull request #162).
• Contributions to team-based tasks:
  • Submission of final deliverables and issued the v2.1 release.
  • Helped team with the initial setup of the team and individual repositories.
  • Provided non-trivial PR review and approvals (Pull request #150).
• Community:
  • Provided non-trivial Developer Guide reviews of fellow teams (example: 1)
  • Reported bugs and suggestions for other teams in the class (examples: 1, 2, 3)