Assignment Unit 2

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.
“Acceptance testing and installation testing check the system against the project agreement and is
done by the client, if necessary, with help by the developers.” (Bruegge & Dutoit, 2010)
1. “The user interface must be user-friendly and easy to use.”
This can be verified.
Acceptance test: Tester (user) can manually test the interface to verify the nonfunctional requirement.
Questionnaire the user to get feedback.
2. “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.”
This can be verified.
Acceptance test: Using the mouse event handler, we can keep track of the number of mouse clicks. A
mouse click count can be used to verify to see the average of the mouse clicks.
3. “The user interface of the new system must be simple enough so that any user can use it with
a minimum training.”
This can be verified.
Acceptance test: Similarly to the Nr. 1 requirement, tester (user) can manually test the interface to
verify the nonfunctional requirement. Questionnaire the user to get feedback.
4. “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.”
This can be verified.
Acceptance test: The user or developer will click the hyperlink and measure the time before the new
web page starts.
5. “In case of failure, the system must be easy to recover and must suffer minimum loss of
important data.”
This can't be tested because failure can depend on many factors. Therefore, it is not possible to
guarantee an easy recovery or minimal loss.

References:
Marsic, I (2012) Software Engineering. Rutgers University, New Brunswick, New Jersey
Bruegge, B., & Dutoit, A. H. (2010). Object oriented software engineering: Using UML, patterns,
and Java#x2122. Boston: Prentice Hall. Retrieved from:
https://doc.lagout.org/programmation/Java/Object-
Oriented%20Software%20Engineering%20using%20UML%2C%20Patterns%2C%20and%20Java
%20%283rd%20ed.%29%20%5BBruegge%20%26%20Dutoit%202009-08-08%5D.pdf