đ University Curriculum & Practical Lab Manuals
Computer Science Practical Labs Catalog
Explore 14 standardized computer science practical laboratory categories. Every experiment includes formal Aims, Learning Objectives, Algorithms, Verified Source Code, Sample Inputs/Outputs, Test Cases, and Viva Voce Q&As.
Categories: 14 Subjects (A to N)
Format: 18-Point Standard
Execution: Client-Side & 100% Free
Direct: 1-Click Open in IDE
To ensure strict adherence to university academic grading criteria and accreditation bodies, every engineering practical laboratory experiment on VAB-CODE follows the standardized 18-point documentation structure:
Points 1 to 9: Formulation & Design
1. Experiment Title & Date: Clear curricular identifier.
2. Aim / Problem Statement: Concise statement of technical objective.
3. Apparatus & Software Environment: Compiler versions (GCC, Java 17, Python 3.11, MySQL).
4. Learning Objectives: Specific skills and competencies acquired.
5. Theoretical Background: Underlying mathematical or algorithmic foundations.
6. Mathematical Equations: Formal equations, asymptotic bounds, and formulas.
7. Architectural Flowchart: Logic diagram depicting program execution flow.
8. Step-by-Step Algorithm: Language-agnostic pseudocode steps.
9. Input Data Specifications: Domain constraints and variable ranges.
Points 10 to 18: Implementation & Evaluation
10. Complete Source Code: Syntactically verified and fully indented code.
11. Comments & Error Handling: Boundary safety and explanatory annotations.
12. Compilation & Build Commands: Exact terminal CLI invocation.
13. Sample Test Case (Nominal): Standard expected input and output.
14. Boundary Test Case (Edge): Zero, null, negative, or max-scale inputs.
15. Expected Terminal Output: Exact stdout transcript.
16. Result & Conclusion: Verification that the stated aim was fulfilled.
17. Viva Voce Questions & Model Answers: Oral examination preparation.
18. Academic References: Standard textbooks (Cormen, Silberschatz, Tanenbaum).
Data structures establish memory layout models and access patterns for algorithmic processing. Linear data structures (arrays, linked lists, stacks, queues) enforce sequential predecessor-successor relationships, whereas non-linear structures (trees, graphs) represent hierarchical and arbitrary network topologies.
Experiment 1: Implementation of Singly Linked List Operations
Aim: To write a modular C program to implement dynamic singly linked list operations: insertion at beginning/end, deletion by value, reversal of nodes, and display.
Algorithm:
1. Define struct Node containing integer data and pointer struct Node* next.
2. Insert at Beginning: Allocate memory via malloc(sizeof(struct Node)). Set newNode->next = head; update head = newNode.
3. Reverse: Initialize three pointers: prev = NULL, curr = head, next = NULL. In a loop while curr != NULL: save next = curr->next; reverse pointer curr->next = prev; advance prev = curr; advance curr = next. Set head = prev.
#include <stdio.h>
#include <stdlib.h>
struct Node {
int data;
struct Node* next;
};
struct Node* insertBeginning(struct Node* head, int val) {
struct Node* newNode = (struct Node*)malloc(sizeof(struct Node));
if (!newNode) { printf("Memory allocation failed!\n"); exit(1); }
newNode->data = val;
newNode->next = head;
return newNode;
}
struct Node* reverseList(struct Node* head) {
struct Node *prev = NULL, *curr = head, *next = NULL;
while (curr != NULL) {
next = curr->next;
curr->next = prev;
prev = curr;
curr = next;
}
return prev;
}
void printList(struct Node* head) {
struct Node* temp = head;
while (temp) {
printf("%d -> ", temp->data);
temp = temp->next;
}
printf("NULL\n");
}
Viva Voce Questions:
âĸ Q: Why is pointer reversal performed in $O(1)$ auxiliary space?
âĸ Answer: Three temporary pointer variables (prev, curr, next) are reused across all loop iterations without allocating new heap memory, bounding space to $O(1)$.
Object-oriented design organizes code around self-contained entities (objects) encapsulating state (attributes) and behavior (methods). Java implements concurrency using monitors and intrinsic thread locks.
Experiment 2: Inter-Thread Communication (Producer-Consumer Problem)
Aim: To demonstrate thread synchronization and inter-thread signaling in Java using a bounded buffer with synchronized methods, wait(), and notify().
Theory: When multiple concurrent threads access shared mutable state, race conditions emerge. Using intrinsic object monitors, the Producer thread waits when the buffer is full, and the Consumer thread waits when the buffer is empty.
import java.util.LinkedList;
import java.util.Queue;
class BoundedBuffer {
private final Queue<Integer> queue = new LinkedList<>();
private final int CAPACITY = 5;
public synchronized void produce(int item) throws InterruptedException {
while (queue.size() == CAPACITY) {
wait(); // Buffer full: release monitor and sleep
}
queue.add(item);
System.out.println("Produced: " + item + " | Buffer size: " + queue.size());
notifyAll(); // Wake up waiting consumer threads
}
public synchronized int consume() throws InterruptedException {
while (queue.isEmpty()) {
wait(); // Buffer empty: release monitor and sleep
}
int item = queue.poll();
System.out.println("Consumed: " + item + " | Buffer size: " + queue.size());
notifyAll(); // Wake up waiting producer threads
return item;
}
}
Viva Voce Questions:
âĸ Q: Why must wait() always be called inside a while loop instead of an if statement?
âĸ Answer: To guard against spurious wakeups, where a thread resumes execution without an explicit signal. The while loop re-checks the condition predicate before proceeding.
Relational databases store structured schemas governed by foreign keys and integrity constraints. SQL provides declarative data definition (DDL) and manipulation (DML).
Experiment 3: SQL Relational Queries, Grouping & Triggers
Aim: Create a University database schema (Department, Student, Course, Enrollment) and execute nested queries with GROUP BY, HAVING, and an automated audit trigger.
-- Schema Definition
CREATE TABLE Student (
student_id INT PRIMARY KEY,
name VARCHAR(50) NOT NULL,
dept_id INT,
gpa DECIMAL(3,2)
);
CREATE TABLE CourseEnrollment (
enrollment_id INT PRIMARY KEY,
student_id INT,
course_name VARCHAR(50),
grade VARCHAR(2),
FOREIGN KEY (student_id) REFERENCES Student(student_id)
);
-- Advanced Aggregation Query: Students with above-average GPA per Department
SELECT s.student_id, s.name, s.gpa, s.dept_id
FROM Student s
WHERE s.gpa > (
SELECT AVG(s2.gpa)
FROM Student s2
WHERE s2.dept_id = s.dept_id
);
Viva Voce Questions:
âĸ Q: What is the semantic difference between WHERE and HAVING in SQL?
âĸ Answer: The WHERE clause filters individual records before aggregation occurs; the HAVING clause filters aggregated groups produced by GROUP BY.
System programming interfaces directly with the operating system kernel via system calls to manage processes, file descriptors, and virtual memory.
Experiment 4: Round Robin CPU Scheduling Simulation in C
Aim: Implement Round Robin scheduling with a given time quantum $Q$ to compute turnaround times, waiting times, and average response metrics.
#include <stdio.h>
void roundRobin(int n, int burst[], int quantum) {
int rem_burst[n];
for (int i = 0; i < n; i++) rem_burst[i] = burst[i];
int t = 0; // Current time
int wait_time[n];
for (int i = 0; i < n; i++) wait_time[i] = 0;
while (1) {
int done = 1;
for (int i = 0; i < n; i++) {
if (rem_burst[i] > 0) {
done = 0;
if (rem_burst[i] > quantum) {
t += quantum;
rem_burst[i] -= quantum;
} else {
t += rem_burst[i];
wait_time[i] = t - burst[i];
rem_burst[i] = 0;
}
}
}
if (done == 1) break;
}
printf("PID\tBurst\tWaiting\tTurnaround\n");
for (int i = 0; i < n; i++) {
printf("P%d\t%d\t%d\t%d\n", i+1, burst[i], wait_time[i], wait_time[i] + burst[i]);
}
}
Viva Voce Questions:
âĸ Q: How does time quantum size affect Round Robin performance?
âĸ Answer: An excessively large time quantum reduces Round Robin to FCFS; an excessively small quantum causes high context-switching overhead, degrading CPU throughput.
Socket programming enables inter-process network communication across distributed machines using IP addressing and port numbers.
Experiment 5: Client-Server TCP Echo Socket in Python
Aim: Implement an iterative TCP echo server and client using the standard Python socket library.
# Python 3: TCP Echo Server Implementation
import socket
def run_server():
server_sock = socket.socket(socket.AF_INET, socket.SOCK_STREAM)
server_sock.setsockopt(socket.SOL_SOCKET, socket.SO_REUSEADDR, 1)
server_sock.bind(('127.0.0.1', 8080))
server_sock.listen(5)
print("TCP Server listening on 127.0.0.1:8080...")
while True:
client_sock, client_addr = server_sock.accept()
print(f"Connection established from {client_addr}")
data = client_sock.recv(1024)
if data:
print(f"Received payload: {data.decode()}")
client_sock.sendall(data) # Echo data back
client_sock.close()
Viva Voce Questions:
âĸ Q: Why is SO_REUSEADDR recommended for TCP server sockets?
âĸ Answer: It allows the server to immediately re-bind to the port even if previously closed sockets remain in the kernel's TIME_WAIT state.
Machine learning builds predictive data-driven models by discovering functional mappings $f(X) \approx Y$ from empirical training sets.
Experiment 6: Supervised Classification with Decision Trees & Evaluation
Aim: Train a Decision Tree classifier, compute the Confusion Matrix, and calculate Accuracy, Precision, Recall, and F1-Score metrics.
from sklearn.datasets import load_iris
from sklearn.model_selection import train_test_split
from sklearn.tree import DecisionTreeClassifier
from sklearn.metrics import classification_report, confusion_matrix
# Load dataset and partition 80/20
iris = load_iris()
X_train, X_test, y_train, y_test = train_test_split(iris.data, iris.target, test_size=0.2, random_state=42)
# Train Decision Tree with Gini Impurity
clf = DecisionTreeClassifier(criterion='gini', max_depth=3, random_state=42)
clf.fit(X_train, y_train)
# Evaluate model predictions
y_pred = clf.predict(X_test)
print("Confusion Matrix:\n", confusion_matrix(y_test, y_pred))
print("\nClassification Report:\n", classification_report(y_test, y_pred, target_names=iris.target_names))
Viva Voce Questions:
âĸ Q: Why is Precision preferred over Accuracy in imbalanced datasets?
âĸ Answer: Accuracy is deceptive when the majority class dominates (e.g. 99% negative cases); Precision ($TP / (TP + FP)$) measures exactness among positive predictions regardless of negative class volume.
Aim / Objective: To model process synchronization in the classic Producer-Consumer Bounded Buffer problem, enforcing mutual exclusion and preventing race conditions using simulated counting and binary semaphores.
Prerequisites & Domain Concepts
Shared memory, critical section problem, semaphores, mutex in C.
Asymptotic Complexity Bounds
âĸ Time Complexity: O(1) synchronization operations
âĸ Space Complexity: O(K) buffer memory
Step-by-Step Algorithm
- Step 1: Initialize semaphore mutex = 1, empty = BUFFER_SIZE, full = 0.
- Step 2: Producer: wait(empty); wait(mutex); insert item into buffer; signal(mutex); signal(full).
- Step 3: Consumer: wait(full); wait(mutex); remove item from buffer; signal(mutex); signal(empty).
- Step 4: Trace state of buffer across interleaved produce and consume cycles.
Verified Academic Source Code (C)
#include <stdio.h>
#include <stdbool.h>
#define CAPACITY 4
// Simulated Semaphore Structure
struct Semaphore {
int value;
};
void wait_sem(struct Semaphore* s) { s->value--; }
void signal_sem(struct Semaphore* s) { s->value++; }
struct BoundedBuffer {
int items[CAPACITY];
int in, out, count;
struct Semaphore mutex;
struct Semaphore empty;
struct Semaphore full;
};
void init(struct BoundedBuffer* b) {
b->in = 0;
b->out = 0;
b->count = 0;
b->mutex.value = 1;
b->empty.value = CAPACITY;
b->full.value = 0;
}
void produce(struct BoundedBuffer* b, int item) {
if (b->empty.value <= 0) {
printf("[Producer] Buffer FULL! Producer blocked on empty semaphore.\n");
return;
}
wait_sem(&b->empty);
wait_sem(&b->mutex);
b->items[b->in] = item;
printf("[Producer] Produced item %2d at slot %d (Buffer count: %d)\n", item, b->in, b->count + 1);
b->in = (b->in + 1) % CAPACITY;
b->count++;
signal_sem(&b->mutex);
signal_sem(&b->full);
}
void consume(struct BoundedBuffer* b) {
if (b->full.value <= 0) {
printf("[Consumer] Buffer EMPTY! Consumer blocked on full semaphore.\n");
return;
}
wait_sem(&b->full);
wait_sem(&b->mutex);
int item = b->items[b->out];
printf("[Consumer] Consumed item %2d from slot %d (Buffer count: %d)\n", item, b->out, b->count - 1);
b->out = (b->out + 1) % CAPACITY;
b->count--;
signal_sem(&b->mutex);
signal_sem(&b->empty);
}
int main() {
struct BoundedBuffer buf;
init(&buf);
printf("=== Producer-Consumer Concurrency Simulation (Capacity: %d) ===\n\n", CAPACITY);
produce(&buf, 101);
produce(&buf, 102);
produce(&buf, 103);
produce(&buf, 104);
produce(&buf, 105); // Attempt overflow
printf("\nStarting consumption:\n");
consume(&buf);
consume(&buf);
printf("\nProducing after space freed:\n");
produce(&buf, 105);
consume(&buf);
return 0;
}
Sample Test Input
Capacity = 4; Produce 5 items; Consume 2 items; Produce 1 item
Expected Terminal Output
=== Producer-Consumer Concurrency Simulation (Capacity: 4) ===
[Producer] Produced item 101 at slot 0 (Buffer count: 1)
[Producer] Produced item 102 at slot 1 (Buffer count: 2)
[Producer] Produced item 103 at slot 2 (Buffer count: 3)
[Producer] Produced item 104 at slot 3 (Buffer count: 4)
[Producer] Buffer FULL! Producer blocked on empty semaphore.
Starting consumption:
[Consumer] Consumed item 101 from slot 0 (Buffer count: 3)
[Consumer] Consumed item 102 from slot 1 (Buffer count: 2)
Producing after space freed:
[Producer] Produced item 105 at slot 0 (Buffer count: 3)
[Consumer] Consumed item 103 from slot 2 (Buffer count: 2)
University Viva Voce Questions & Model Answers:
âĸ Q: What is a Semaphore in operating systems?
âĸ Answer: A synchronization tool: an integer variable accessed only through two atomic operations: wait() (or P) and signal() (or V).
âĸ Q: What is the Critical Section Problem?
âĸ Answer: A code segment where shared resources (memory, files) are accessed; only one process must execute in its critical section at any given time (Mutual Exclusion).
âĸ Q: Why is the order wait(empty) followed by wait(mutex) critical in Producer-Consumer?
âĸ Answer: Swapping the order causes deadlock: if the buffer is full, the producer acquires the mutex and sleeps waiting for empty space; the consumer cannot acquire the mutex to free space, causing permanent freeze.
âĸ Q: What is the difference between a Mutex and a Binary Semaphore?
âĸ Answer: A mutex has ownership (only the thread that locked it can unlock it); a binary semaphore can be signaled by any thread.
âĸ Q: What is Priority Inversion?
âĸ Answer: A scenario where a high-priority task is indirectly preempted by a lower-priority task holding a shared resource mutex.