← CSC 411 Final Year Computer Science Project
Verification, Validation, Deployment, and Academic Documentation
Notes
Testing and Quality Assurance
Verification ensures the software matches architectural specifications, while validation confirms it satisfies user needs. A high-scoring project demonstrates comprehensive automated and manual testing strategies. Unit testing validates individual functions and methods using frameworks like Jest, PyTest, or JUnit. Integration testing assesses communication between interconnected modules, such as backend services interfacing with third-party payment gateways. System testing validates end-to-end user workflows against functional requirements.
User Acceptance Testing and Deployment
User Acceptance Testing, UAT, involves deploying prototypes to representative end-users to gather quantitative feedback through usability metrics and qualitative feedback through structured questionnaires. Deployment turns theoretical software into an accessible product. Students must utilize containerization platforms like Docker to ensure environment consistency across development and production. Production instances should be hosted on cloud platforms such as AWS, Google Cloud, or Render, configured with continuous integration and continuous deployment, CI/CD, pipelines via GitHub Actions.
Academic Documentation Structure
The final project report represents fifty percent or more of the evaluation. Kenyan university standards generally follow five structured chapters: Chapter One covers the introduction, problem statement, objectives, and project scope. Chapter Two reviews related literature and existing commercial platforms, highlighting clear research gaps. Chapter Three outlines system design, methodology, and architectural diagrams. Chapter Four presents implementation details, interface screens, and testing outcomes. Chapter Five provides discussions, limitations, future work, and conclusions. Citations must strictly adhere to academic formats such as IEEE or APA.
Viva Voce Preparation
The final defense, or viva voce, requires students to present their work before an examination panel. Presentations must emphasize personal contribution, algorithmic complexity, architectural soundness, and a live, unrecorded demonstration. Students must be prepared to justify design trade-offs, explain edge-case handling, and walk examiners through actual source code.
Practical example
A student designs an electronic triage and bed allocation management system for Kiambu Level 5 Hospital.
During verification, the student creates PyTest unit tests validating the emergency severity indexing algorithm, ensuring critical patients are prioritized irrespective of arrival sequence.
For validation, the student conducts UAT sessions with five hospital triage nurses, recording system usability scale scores and documenting how offline-first caching handles frequent local power fluctuations.
The application is containerized with Docker and deployed onto an Ubuntu cloud virtual machine behind an Nginx reverse proxy secured by Let's Encrypt SSL certificates.
In the final documentation, Chapter Four features comprehensive test execution tables detailing inputs, expected outputs, actual outcomes, and pass or fail statuses.
During the viva voce defense, the external examiner asks how the system prevents concurrent assignment of the same physical bed. The student defends the work by walking through database row-level locking mechanisms implemented in the booking transaction queries.
Quiz
1. What is the primary objective of User Acceptance Testing (UAT) in a final year capstone project?
2. During the viva voce defense, what should a student prioritize to demonstrate authentic mastery of their project?
3. In academic capstone documentation, which chapter typically details the theoretical context and gaps in existing systems?
Sign in to submit and securely grade your quiz.