Open sayarinm opened 7 years ago
the division of responsibilities appears to be correct, although somewhat unrealistic. In many software systems, validation of and acceptance or rejection of input is the responsibility of the software (eg. exception handling etc.).
@sayarinm , can you please look at our wording? We didn't capture the idea that we were after. @inglis-dl , we want the software to do error checking, but there are some errors that it isn't possible for the software to detect. For instance, in a system where the user is supposed to enter a number, if they mean to type 10, but type 100, there is no way for the software to know. For fMRI software, if the data is non-parametric, but the user still uses a parametric assumption, as is done for 3dfim+, the software doesn't have any way of knowing.
We'll have to review our wording to try and clarify this point. Thank you for bringing it to our attention.
(Sections 2.2 and 3.1 in SRS)
Please read Scope of Requirements and System Context. Is the given division of responsibilities between the user and the system correct?
:star: GA