tp

Khairul Aizat - Project Portfolio Page

Overview

SecureNUS is a desktop CLI app for managing and storing passwords. Its features include adding, deleting, listing, revealing, searching, saving and loading passwords, and editing password details. The app is simple and efficient to use, and users can access a menu function for command summaries and syntax.

Summary of Contributions

Code contributed

• RepoSense Link

Feature	Difficulty	Description
Revealing a password view	★	To maintain security when listing passwords, the actual passwords will not be revealed. To reveal a specific password, the user inputs the name of the password to view. If the password name does not match any stored password, an error message is printed.
Searching for a password search	★★	Searches for passwords with names that contain the specified name, and optionally in the specified folder. If a folder name is provided, it searches in that specific folder, otherwise it searches in all passwords. The search results are printed out in a formatted table along with the number of matches found.
Edit a password edit	★★★	To edit a password, the user inputs the name of the password, and optionally the new name and new folder of the password. The user then inputs the new values of the relevant fields to be updated (e.g. password, credit card number, NUSnet ID, etc.).

Enhancements implemented:

• Wrote and tested ~50% of JUnit tests whilst ensuring quality and efficiency of test cases. Achieved >80% Method coverage. (RepoSense)
• Beautified the table output of Search command. (#222)

Major difficulties faced:

• There are many variations of editable fields based on the type of Secret. Handling all of them separately was challenging.
• Handling JUnit tests for methods that require user input.

Contributions to the UG:

• Contributed to initial draft of UG.
• Contributed to FAQs segment.

Contributions to the DG:

• Created UML Sequence diagrams for Implementation segment (add, delete and list features)
• Wrote Appendices: Product Scope, User Stories, Non-Functional Requirements, Glossary and Instructions for manual testing

Contributions to team-based tasks:

• Set up Team’s GitHub organisation and tP repository.
• Maintain the issue tracker by ensuring each Issue/PR had the correct Assignees, Labels and Milestone tags.
• Heavily involved in the triage of bugs from the PE Dry-Run. Assigned and/or resolved >30 bugs. (#103-148, etc.)
• Performed penetration testing for add, delete and list features. (#201, #206)

Review/mentoring contributions:

• See my team’s PRs that I reviewed

Contributions beyond the project team:

• See my review of another team’s Developer Guide

• See my review of other teams’ tP product

Contributions to the Developer Guide (Extracts):

• Refer to Implementation segment and appendices: Product Scope, User Stories, Non-Functional Requirements, Glossary and Instructions for manual testing of our DG.