Scribd
Upload
0 views2 pages

CS 2401-01 Programming Assign. Unit 2

The document evaluates various user interface requirements for testability. Some requirements, like user-friendliness and minimal training, are deemed untestable due to their subjective nature, while others, such as the number of mouse clicks and hyperlink latency, are testable with defined criteria. Additionally, the requirement for easy recovery after failure is partially testable, as it includes measurable components but lacks clear metrics for recovery ease.

Uploaded by

kyawkhant1391999
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0 views2 pages

CS 2401-01 Programming Assign. Unit 2

The document evaluates various user interface requirements for testability. Some requirements, like user-friendliness and minimal training, are deemed untestable due to their subjective nature, while others, such as the number of mouse clicks and hyperlink latency, are testable with defined criteria. Additionally, the requirement for easy recovery after failure is partially testable, as it includes measurable components but lacks clear metrics for recovery ease.

Uploaded by

kyawkhant1391999
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 2

1. "The user interface must be user-friendly and easy to use.

"

o Testable? No.

o Reason: "User-friendly" and "easy to use" are subjective and lack measurable

criteria. Usability can be assessed via qualitative methods (e.g., user surveys,

heuristic evaluations), but there is no objective pass/fail test.

2. "The number of mouse clicks to navigate to any window must be less than 10."

o Testable? Yes.

o Acceptance Test:

 For each window in the system, document the navigation path from the

home screen.

 Count the number of mouse clicks required to reach the window.

 Pass Criteria: No window requires more than 10 clicks.

3. "The UI must be simple enough for users to operate with minimal training."

o Testable? No.

o Reason: "Minimal training" is undefined. Without specifying training duration or

success metrics (e.g., 90% of users complete tasks after a 1-hour training session),

this requirement is too vague for objective testing.

4. "Maximum latency of 1 second for hyperlink rendering over broadband."

o Testable? Yes.
o Acceptance Test:

 Use network throttling tools (e.g., Chrome DevTools) to simulate a

broadband connection (e.g., 5 Mbps).

 Measure the time between clicking a hyperlink and the start of page

rendering (via browser developer tools or performance APIs).

 Pass Criteria: Latency ≤1 second for all tested hyperlinks.

5. "System must be easy to recover with minimal data loss after failure."

o Testable? Partially.

o Testable Component:

 Data Loss: Simulate a system failure (e.g., crash, power outage) and

verify that all critical data is recoverable from backups.

 Test: Restore from the most recent backup and check data integrity.

 Pass Criteria: No loss of data marked as "important."

o Untestable Component:

 "Easy to recover": Without defined metrics (e.g., recovery time <15

minutes), this is subjective and not directly measurable.

You might also like