“Usability” and “Testability” are two types of quality requirements (non-functional requirements). How would you test the non-functional requirement “The system should be easy to use”?
@karlwiegers775 жыл бұрын
I would discard that "easy to use" requirement because it is vague, ambiguous, subjective, and untestable. However, there's obviously an important idea there that needs to be explored. So the BA should work with whoever said "the system should be easy to use" to turn that into a set of more precise, specific, and testable requirements. The BA might ask questions like: What does "easy to use" mean to you? Can you give me some examples of other products that you think are easy or not easy to use? How would we know if it was easy to use or not? That kind of discussion could lead to some more specific usability requirements that could in fact be tested.
@MG-vb6ms4 жыл бұрын
One of the requirements of a new accounts management system is that it must allow users to scale the size of text on the screen. The requirement states that the text can be reduced to 10% of normal size and increased up to 500% of normal size, depending on the preference of the user. What would this requirement be classified as? general or non functional? Can you please let me know this? Thanks in advance.
@vivianmardikios85773 жыл бұрын
please tell ............which type of non-functional requirements are the most difficult to discover ? why?
@HIBA_Hz4 жыл бұрын
I need your help please , if you have any Books about (analysis activity of requirement engineering in Big data 😢)