Surveys and UAT: Chapters 3 and 5 testing that passes defense

In computing and software engineering final year projects, examiners scrutinize Chapter 5: System Testing and Evaluation to ensure claims of system success are backed by empirical, measurable evidence rather than anecdotal praise.

1. The Two Halves of Chapter 5

A defensible Chapter 5 consists of two distinct testing phases:

1. System / Unit Testing: Objective technical verification (e.g., test suites, API endpoint latencies, load testing, coverage percentages).
2. User Acceptance Testing (UAT): Subjective and behavioral validation performed by target end users against pre-defined test cases and usability criteria.

2. Standardizing User Acceptance Testing (UAT)

UAT must never be summarized as a vague paragraph stating “ten participants tested the system and found it easy to use.” Examiners demand structured Test Case Matrices:

Test Case ID	Feature Evaluated	Step-by-Step Scenario	Expected Result	Actual Result	Status
TC-01	Git Scanner	Upload repository containing 15 TypeScript files	Manifest extracts models, routes, and tests	All models indexed within 1.2s	PASS
TC-02	Cadence Linter	Process uniform 12-word sentences	Flag burstiness under threshold (< 35.0)	Warning triggered with rewrite tips	PASS
TC-03	Word Assembler	Compile 80-page manuscript with APA tables	38mm gutter margin applied, Roman numerals	Document opens in Word with 0 errors	PASS

3. Measuring Usability with the SUS Scale

The System Usability Scale (SUS) is a 10-item questionnaire with five response options (1 = Strongly Disagree to 5 = Strongly Agree).

• Scores range from 0 to 100.
• A score above 68 indicates above-average usability.
• A score above 80.3 denotes excellent, top-tier usability.

UniReport includes survey analysis engines to compute mean SUS scores, standard deviations, and Likert frequency charts ready for inclusion in Chapter 5.