Open nus-pe-bot opened 6 days ago
Adding extra details for each cases of invalid format may result in repetition in use cases. This will reduce the readability.
Like the example in the textbook, the use case does not provide detailed discussion on different types of erroneous data input. It uses one extension 3a "OBS detects error in the entered data" to generalize and describe the interaction between the system and user when erroneous data are provided to the system.
Hence, the bug discovered is invalid and we decide to reject.
--
Many of the use case extensions use the term "input format is invalid". Does this mean that the input from the user is missing the prefix? Or does it mean that the values after those prefixes are invalid? Perhaps extra extensions can be added to make this clearer.
I only included 2 screenshots but this is a recurring problem for many of the use cases.
[original: nus-cs2103-AY2425S1/pe-interim#2635] [original labels: severity.Low type.DocumentationBug]