Aditi Gupta's Project Portfolio Page

Project: LibTask

LibTask is a desktop application used by librarians to keep track of books, overdue books, and contact details of patrons who have borrowed them and those who requested them. The user interacts with it using a CLI, and it has a GUI created with JavaFX. It is written in Java, and has about 10 kLoC. This project is based on AddressBook - Level 3. Given below are my contributions to the project.

• New Feature:
  • Added ID attribute to patron. #60
    • What it does:
      • Allows library users to register their student ID with LibTask.
    • Justification:
      • Assists communication and management of student book loans by librarians if they can link library users to their student/staff IDs.
    • Highlights:
      • This addition was challenging as it required several checks and constraints to be placed on the format of NUS student/staff IDs.
      • Several precautions needed to be taken during implementation such as ensuring that no patron feature links were broken and data integrity was maintained in writing and reading information to and from json files.
  • Added patron overdue feature to LibTask’s existing patron features with tests. #102
    • What it does:
      • Allows users to view a list of all patrons with overdue books.
    • Justification:
      • Improves book processing by enhancing communication between libraries and library users. Increases LibTask’s efficiency and ease of navigation by allowing users to minimise command executions.
    • Highlights:
      • This addition to LibTask’s existing patron features was challenging to implement due to the following reasons:
        1. Feature required double filtering of data (LibTask’s patron list had to be filtered based on the statuses of every book borrowed by each patron).
        2. Implementation of this feature had to be done similar to how other patron and book features had been implemented to maintain similar levels of abstraction (hard SLAP) and code quality.
        3. Implementation of the patron overdue feature required sound knowledge of features added by other teammates to reduce code redundancies.

• Code and PR Review contributions: RepoSense link, tp Comments Dashboard

• Project management:
  • Suggested development of a library management software during initial project ideation stages.
  • Proposed LibTask functionalities and features
  • Reviewed and approved PRs for merging
  • Created issues for PRs
• Enhancements to existing features:
  • Updated AB-3 person to patron through removal of person address. #60
  • Adaptation of person features to match updated patron attributes. #60
  • Heavy refactoring of person associated classes to accommodate for patron. #60, #64
  • Added test cases for patron features. #102
  • Edited existing test cases for original person features to accommodate for patron. #70
• Documentation:
  • User Guide:
    • Drafted tutorial steps 1, 2 and 3. #211, #232
    • Documentation (with screenshots) for new patron overdue feature #116
    • Enhancements in documentation (with screenshots) for patron and book features. #116, #148
  • Developer Guide:
    • Product scope with target user profile and value proposition #211
    • Non-functional requirements #211
    • Implementation and design considerations for patron overdue feature #211
    • Activity and Sequence diagrams for patron overdue feature #211
    • Appendix: Instructions for manual testing for patron overdue feature #211
    • Appendix: Instructions for manual testing enhancements to all book and patron features. #232
    • Glossary additions #218, #220, #242, #244
• Review/mentoring contributions:
  • PR reviewed (with non-trivial review comments): #20, #60, #63, #69, #72, #73, #75, #101, #108, #112, #113, #127, #129, #134, #136, #138, #139, #146, #205, #207, #208, #209, #214, #215, #222, #224, #228, #229, #235, #239, #240, #246, #251.
• Community:
  • Bugs reported for other teams can be found here.
• Tools:
  • Assertions, Gradle, Intellij