Consider the following nonfunctional requirements and determine which of them
can be verified and which cannot. Write acceptance tests for each requirement or
explain why it is not testable.
a. “The user interface must be user-friendly and easy to use.”
Nonfunctional requirement for the user interface is verifiable since it’s
possible to test with a user and ask them if the solution meets their need and
if it’s easy to use. Different features like the menu can be tested manually to
ascertain the usability. One example of acceptance test that can be done to
ascertain the friendliness of the user interface is to test each features of the
UI with different users and make a conclusion based on their feedback.
b. “The number of mouse clicks the user needs to perform when navigating to
any window of the system’s user interface must be less than 10.”
The number of clicks that a user has to perform is also verifiable since all this
can be manually done during the testing phase of the project. The developer
can manually count the number of clicks needed then be able to determine if
they are too many or good for the user. The acceptance test for this will be,
are they too many? If so, how can it be reduced?
c. “The user interface of the new system must be simple enough so that any user
can use it with a minimum training.”
The simplicity of the user interface might not be easy to determine, since the
whole process of determining the simplicity is not quantifiable. The
simplicity of a system to one user might not be simple to another user so
hence a good training for users who deem the UI not simple has to be
intense compared to an early adopter.
d. “The maximum latency from the moment the user clicks a hyperlink in a web
page until the rendering of the new web page starts is 1 second over a
broadband connection.”
The maximum latency time is also not testable for example if a system is to
be deployed for different users. This different users can have different
broadband connection speeds therefore loading times can be hard to
determine.
can be verified and which cannot. Write acceptance tests for each requirement or
explain why it is not testable.
a. “The user interface must be user-friendly and easy to use.”
Nonfunctional requirement for the user interface is verifiable since it’s
possible to test with a user and ask them if the solution meets their need and
if it’s easy to use. Different features like the menu can be tested manually to
ascertain the usability. One example of acceptance test that can be done to
ascertain the friendliness of the user interface is to test each features of the
UI with different users and make a conclusion based on their feedback.
b. “The number of mouse clicks the user needs to perform when navigating to
any window of the system’s user interface must be less than 10.”
The number of clicks that a user has to perform is also verifiable since all this
can be manually done during the testing phase of the project. The developer
can manually count the number of clicks needed then be able to determine if
they are too many or good for the user. The acceptance test for this will be,
are they too many? If so, how can it be reduced?
c. “The user interface of the new system must be simple enough so that any user
can use it with a minimum training.”
The simplicity of the user interface might not be easy to determine, since the
whole process of determining the simplicity is not quantifiable. The
simplicity of a system to one user might not be simple to another user so
hence a good training for users who deem the UI not simple has to be
intense compared to an early adopter.
d. “The maximum latency from the moment the user clicks a hyperlink in a web
page until the rendering of the new web page starts is 1 second over a
broadband connection.”
The maximum latency time is also not testable for example if a system is to
be deployed for different users. This different users can have different
broadband connection speeds therefore loading times can be hard to
determine.
