Project EzContact

EzContact is a desktop app made for insurance agents to manage customer details, optimized for usage via Command Line Interface (CLI) while still having the benefits of a Graphical User Interface (GUI). If you can type fast, EzContact can get your contact management tasks done faster than traditional GUI apps.

Given below are my contributions to the project.

New Feature:
  • Implemented Insurance feature that includes a new insurance command and a new attribute to the customers in our EzContact.
    • What it does: User can assign or remove insurances associated with a customer on EzContact, by providing the name of the insurance.
    • Justification: Given that our users are insurance agents, our users have to constantly keep track of what insurances each customer currently holds, has interest in or plans to cancel. With this feature, our users can efficiently keep track of these information and make the correct decisions and moves when interacting with their customers, subsequently increasing their efficiency and chances of securing deals.
    • Highlights: Implementation of this feature requires in-depth analysis of the model component, different data structures to handle the information and handling of user behaviours (e.g. duplicate, conflicting insurances). These analysis determine our design choices from all the possible alternatives.
Enhancements to existing features:
  • Improve validation of input value for customer's information (e.g. name, phone, email...) #85
  • Change the definition of duplicate entries, allowing same name, but phone and email must be unique #191
  • Make command words and prefixes case-insensitive, giving users more flexibility in using the product #227
Documentation:
  • User Guide:
    • Added documentation for insurance feature #222 #285
    • Standardise formatting and layout of the entire User Guide #316
    • Added introduction to the User Guide #222
    • Added examples for find and remark feature #245
    • Improve description for find feature's documentation #245
    • Update the glossary #110
    • Ensure that all parts of the documentation are consistent and correct #316
  • Developer Guide:
    • Added documentation for Insurance feature (i.e. Implementation, design choices, UML diagrams...) #175 #214
    • Standardise the formatting and layout for Developer Guide #294 #316
    • Standardise the format for Appendix: Effort, Appendix: Planned Enhancement,Appendix: Instruction for Manual Testing and Acknowledgement #316
    • Added uses cases for Insurance feature
    • Updated product scope to be focused on insurance agents #110
    • Update and improve user stories to become more targeted towards insurance agents #110 #69
    • Wrote Appendix: Effort #316
    • Wrote Appendix: Planned Enhancement,Appendix: Instruction for Manual Testing and Acknowledgement for Insurance feature #294
Project management:
  • Attend weekly meetings and brainstorm sessions to decide direction of the project.
  • Have some commits and merged some pull requests in every milestone.
  • Have some reviews and comments on teammates' pull requests. #68 #33
  • Responses to teammates' comments. #110 #85
Community:
  • Reported 14 bugs in other team during PE-D repo