eejian97
commented
5 years ago Team's Response
Thank you for your suggestion, however i will choose to reject the claim of it being a feature flaw, for the following reasons:
(1) The explanation is already provided for the various "criteria" is provided in the Developer Guide, such details should not be included in the user guide because the user guide should only contain details on how to use the various functionalities of the app. (2) For the "strength" of the password, more important for the user is the suggestion that the app provides as part of the analysis, such as "try to include special characters", to make his/her password stronger. (3) For common sequences, the seqences being caught are tokens such as "ABC" and "123", which are already very intuitive for the user. (4) A brief explanation is actually provided for criterion that are less intuitive. Unique criteria will mention something like: "The following accounts share the same password: "; Dictionary criterion will mention somethig like " The following tokens in your password were found inside our list of commonly used passwords:".
Hence, with the following reasons, I have decided to reject your bug. It is not a feature flaw, let alone a highly severe one becasue explanation is done where due. I thank you for your suggestion though!
Duplicate status (if any):
--
As a user, it will be best if we can see what are the criteria for the various password analysis category. As of now, if I was a user, I would not know how is the strength of my password is being measured and what "common sequences" actually mean.
These definitions are not found inside the UG and this may potentially impact the user's understanding on how the analysis feature actually works.
[original: nus-cs2103-AY1920S1/pe-interim#1377]