Below are examples of nonfunctional requirements. Specify which of these requirements are verifiable and which are not.
What will be an ideal response?
• “The system must be usable.” [not verifiable, no precise definition of “usable”]
• “The system must provide visual feedback to the user within 1 second of issuing a command.”[verifiable]
• “The availability of the system must be above 95%.” [verifiable, assuming sufficient resources]
• “The user interface of the new system should be similar enough to the old system such that users familiar
with the old system can be easily trained to use the new system.” [not verifiable, no precise definition of
“easily trained”]
You might also like to view...
Placing throw() after a function's parameter list:
a. Guarantees that all exceptions can be thrown in this function. b. Guarantees that only programmer-defined exceptions can be thrown in this function. c. Indicates that throwing an exception in this function would call unexpected. d. Indicates that the compiler will issue an error if the function contains a throw expression.
____________________ means the data is in an easily read or viewed industry-wide standard format.
Fill in the blank(s) with the appropriate word(s).
The output of the statement: cout << pow(3.0, 2.0) + 5 << endl; is ____.
A. 11.0 B. 12.0 C. 13.0 D. 14.0
WPS has a security flaw that allows a hacker to repeatedly guess the ______________ -digit numeric code.
Fill in the blank(s) with the appropriate word(s).