Open paing-oo opened 2 years ago
In the use case, we are not supposed to go in-depth about the implementation of a feature. It is possible that the fields and requirements for each field for Positions
may change in the future, thus we should not include such specific details that requires updating of the use case.
Team chose [response.Rejected
]
Reason for disagreement: It is wrong for the developers to assume that a feature might change in the future and hence not include such important extensions in the use cases. If the fields change in the future which might affect the use cases, it is the developers duty to update affected use cases in the DG. Moreover, the missing extensions are important as most users will likely encounter them.
In the UG, there are a lot of requirements for certain fields for
edit -p
command.The DG did not handle such extensions when user fails to meet these requirements of the fields for the command.