Add command is too long and restrictive

[lipwei1808]

Description

The add command is too long and restrictive. It enforces the presence of every single field which might prove to be too restrictive as there might be scenarios where a user might not want to enter all the fields and want to quickly enter a user into the application. As an application optimised for CLI, the commands should be easy to type. The long command with many different prefixes to remember might prove to be a feature flaw as it is not truly optimised for CLI users.

Reason for severity

Likely to affect a large portion of users at the very beginning when they first use the application. Severity decreases as users gets used to the application and uses it more.

[nus-se-script]

Team's Response

We'd like to clarify that while the command may seem extensive, it aligns with our intention to capture essential information for comprehensive user profiles. In a job application context, each field serves a distinct purpose, contributing to a thorough and accurate representation of the user.

Furthermore, the add command is designed as a one-time data entry primarily intended for HR managers who typically possess all necessary employee information already. In our design choice, this decision aimed to optimise the process of calculating payroll or retrieving attendance records later, instead of leaving the fields to be optional then requiring them to fill the details in when needed.

Items for the Tester to Verify

❓ Issue response

Team chose [response.Rejected]

• I disagree

Reason for disagreement: [replace this with your explanation]

---