🎓 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
Syllabus Completion 0 / 84
Avg Quiz Score -
Bookmarked Labs 0
⚡
Microprocessor & Microcontroller (MPMC) Simulator 8085 â€ĸ 8086 â€ĸ 8051
Simulate assembly code, input data into memory, inspect live registers, flags, and step-by-step outputs.
Launch MPMC Simulator →
How to Use Curriculum Labs: Select your department and semester below to filter matching syllabus experiments. Click any lab card to open interactive theory, algorithm flowchart, and runnable in-browser code.
Department:
6 Academic Tracks â€ĸ 84 Experiments
Semester:

đŸ”Ŧ University Practical Laboratory Curriculum & Viva Voce Manual

Standardized undergraduate computer science and engineering laboratory syllabus reference. Includes rigorous algorithms, complete runnable source implementations, expected outputs, time complexity bounds, viva questions, and the official 18-point university lab record documentation format.

📋 Official 18-Point University Lab Record Standardization Format

Academic Compliance â€ĸ AICTE & ABET Guidelines

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).

đŸ’ģ Academic Track 1: Programming Fundamentals & Data Structures

Pointers â€ĸ Dynamic Memory (malloc/free) â€ĸ Linear & Non-Linear Lists

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)$.

☕ Academic Track 2: Object-Oriented Programming & Multi-Threading (Java)

Encapsulation â€ĸ Polymorphism â€ĸ Synchronized Monitors â€ĸ Thread Safety

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.

đŸ—„ī¸ Academic Track 3: Database Management Systems & SQL Lab

Relational Algebra â€ĸ Multi-Table Joins â€ĸ Triggers & Stored Procedures

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.

âš™ī¸ Academic Track 4: Operating Systems & POSIX Systems Programming

Process Management (fork/exec) â€ĸ CPU Scheduling â€ĸ Pipes & IPC

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.

🌐 Academic Track 5: Computer Networks & Socket Programming

TCP/IP Sockets â€ĸ Client-Server Model â€ĸ Packet Sniffing & Routing

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.

🤖 Academic Track 6: AI, Machine Learning & Computer Vision

Supervised Learning â€ĸ Feature Scaling â€ĸ Confusion Matrix â€ĸ Scikit-Learn

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.

đŸ”Ŧ Experiment 5: Cloud Auto-Scaling Elasticity Simulation with Metric Threshold Alarms

Standardized university practical engineering curriculum manual across Computer Science and Information Technology degree programs.

📋 Experiment Overview & Curriculum Specifications

Cloud Computing & DevOps â€ĸ Medium â€ĸ 30 mins

Aim / Objective: To design, simulate, and analyze cloud horizontal auto-scaling elasticity with high/low CPU utilization threshold alarms and cooldown stabilization periods.

Prerequisites & Domain Concepts

Cloud infrastructure concepts, load balancing, server metrics, queue backlogs.

Asymptotic Complexity Bounds

â€ĸ Time Complexity: O(1) evaluation per telemetry reporting cycle
â€ĸ Space Complexity: O(H) for storing telemetry history

Step-by-Step Algorithm

  1. Step 1: Initialize AutoScaler with min_inst=2, max_inst=8, target_cpu=60%, scale_out_thresh=75%, scale_in_thresh=25%, cooldown_cycles=2.
  2. Step 2: Maintain current_instances = min_inst and current_cooldown = 0.
  3. Step 3: Define process_metric(avg_cpu, cycle): check if current_cooldown > 0; if yes, decrement and skip scaling (stabilizing).
  4. Step 4: If avg_cpu > scale_out_thresh and current_instances < max_inst: compute desired_instances = min(max_inst, ceil(current_instances * (avg_cpu / target_cpu))). Launch instances and set cooldown.
  5. Step 5: If avg_cpu < scale_in_thresh and current_instances > min_inst: compute desired_instances = max(min_inst, ceil(current_instances * (avg_cpu / target_cpu))). Terminate instances and set cooldown.
  6. Step 6: Feed a sequence of 8 telemetry cycles modeling a morning traffic spike followed by evening cooldown.
  7. Step 7: Output scaling events, instance counts, and cost/performance efficiency metrics.

Verified Academic Source Code (PYTHON)

import math

class CloudAutoScaler:
    def __init__(self, min_instances=2, max_instances=8, target_cpu=60.0,
                 scale_out_threshold=75.0, scale_in_threshold=25.0, cooldown_cycles=2):
        self.min_instances = min_instances
        self.max_instances = max_instances
        self.target_cpu = target_cpu
        self.scale_out_threshold = scale_out_threshold
        self.scale_in_threshold = scale_in_threshold
        self.cooldown_cycles = cooldown_cycles

        self.current_instances = min_instances
        self.cooldown_remaining = 0
        self.history = []

    def evaluate_cycle(self, cycle_num, avg_cpu_percent):
        event = "STEADY"
        old_count = self.current_instances

        # Check if currently in cooldown stabilization period
        if self.cooldown_remaining > 0:
            self.cooldown_remaining -= 1
            event = f"COOLDOWN ({self.cooldown_remaining} cycles remaining)"
        else:
            # Rule 1: Scale-Out Check (High CPU Alarm)
            if avg_cpu_percent > self.scale_out_threshold and self.current_instances < self.max_instances:
                # Target tracking formula: desired = ceil(current * (actual / target))
                desired = math.ceil(self.current_instances * (avg_cpu_percent / self.target_cpu))
                desired = min(self.max_instances, max(self.current_instances + 1, desired))
                added = desired - self.current_instances
                self.current_instances = desired
                self.cooldown_remaining = self.cooldown_cycles
                event = f"SCALE-OUT (+{added} instances -> {self.current_instances})"

            # Rule 2: Scale-In Check (Low CPU Alarm)
            elif avg_cpu_percent < self.scale_in_threshold and self.current_instances > self.min_instances:
                desired = math.ceil(self.current_instances * (avg_cpu_percent / self.target_cpu))
                desired = max(self.min_instances, min(self.current_instances - 1, desired))
                removed = self.current_instances - desired
                self.current_instances = desired
                self.cooldown_remaining = self.cooldown_cycles
                event = f"SCALE-IN (-{removed} instances -> {self.current_instances})"

        record = {
            'cycle': cycle_num,
            'cpu': avg_cpu_percent,
            'instances': self.current_instances,
            'event': event
        }
        self.history.append(record)
        return record

# Simulation Scenario: Workload fluctuations across 8 operational cycles
scaler = CloudAutoScaler(min_instances=2, max_instances=8, cooldown_cycles=2)

traffic_telemetry = [
    (1, 45.0, "Normal baseline traffic"),
    (2, 85.0, "Traffic Surge: Morning flash sale begins!"),
    (3, 88.0, "Sustained high load during scale-out cooldown"),
    (4, 55.0, "Stabilized load distributed across new cluster"),
    (5, 78.0, "Secondary traffic peak"),
    (6, 18.0, "Evening traffic drops sharply"),
    (7, 15.0, "Night quiet hours during scale-in cooldown"),
    (8, 20.0, "Post-cooldown scale-in to minimum instances")
]

print("=== Cloud Auto-Scaling Elasticity Simulation ===")
print(f"Cluster Constraints : Min = {scaler.min_instances} instances | Max = {scaler.max_instances} instances")
print(f"Scaling Alarms      : Scale-Out > 75% CPU | Scale-In < 25% CPU | Cooldown = 2 cycles\n")

print(f"{'Cycle':>5} | {'Avg CPU':>8} | {'Instances':>9} | {'Action / Status':>38}")
print("-" * 68)

for cycle, cpu, desc in traffic_telemetry:
    rec = scaler.evaluate_cycle(cycle, cpu)
    print(f"{rec['cycle']:>5} | {rec['cpu']:>7.1f}% | {rec['instances']:>9} | {rec['event']:>38}")

print("\n--- Elasticity & Financial Impact Summary ---")
print(f"Cluster gracefully expanded from 2 to {max(r['instances'] for r in scaler.history)} instances during peak demand (Zero Downtime).")
print(f"Cluster contracted back down to {scaler.current_instances} instances during off-peak, minimizing cloud compute costs.")
â–ļ Run in Online IDE

Sample Test Input

Telemetry across 8 cycles modeling flash sale surge (85-88% CPU) and evening cooldown (15-20% CPU)

Expected Terminal Output

=== Cloud Auto-Scaling Elasticity Simulation ===
Cluster Constraints : Min = 2 instances | Max = 8 instances
Scaling Alarms      : Scale-Out > 75% CPU | Scale-In < 25% CPU | Cooldown = 2 cycles

Cycle |  Avg CPU | Instances |                        Action / Status
--------------------------------------------------------------------
    1 |    45.0% |         2 |                                 STEADY
    2 |    85.0% |         3 |          SCALE-OUT (+1 instances -> 3)
    3 |    88.0% |         3 |           COOLDOWN (1 cycles remaining)
    4 |    55.0% |         3 |           COOLDOWN (0 cycles remaining)
    5 |    78.0% |         4 |          SCALE-OUT (+1 instances -> 4)
    6 |    18.0% |         3 |           SCALE-IN (-1 instances -> 3)
    7 |    15.0% |         3 |           COOLDOWN (1 cycles remaining)
    8 |    20.0% |         3 |           COOLDOWN (0 cycles remaining)

--- Elasticity & Financial Impact Summary ---
Cluster gracefully expanded from 2 to 4 instances during peak demand (Zero Downtime).
Cluster contracted back down to 3 instances during off-peak, minimizing cloud compute costs.
University Viva Voce Questions & Model Answers:

â€ĸ Q: What is the fundamental difference between Cloud Elasticity and Cloud Scalability?
â€ĸ Answer: Scalability is the architectural ability of a system to handle increased load by adding resources (hardware/software). Elasticity is the dynamic, automated adaptation of capacity in real time matching fluctuating demand, scaling both out AND in to optimize costs.

â€ĸ Q: What is "Flapping" (Thrashing) in auto-scaling and how is it prevented?
â€ĸ Answer: Flapping occurs when an auto-scaler repeatedly scales out and immediately scales in due to noisy, fluctuating metrics. It is prevented by implementing cooldown periods, evaluation intervals (e.g. 3 consecutive breaches required), and wider gaps between scale-out and scale-in thresholds.

â€ĸ Q: How does the Kubernetes Horizontal Pod Autoscaler (HPA) compute desired replicas?
â€ĸ Answer: Using the formula: desiredReplicas = ceil(currentReplicas * (currentMetricValue / targetMetricValue)). For example, 2 pods at 80% CPU with a 50% target yields ceil(2 * (80/50)) = 4 pods.

â€ĸ Q: What is the difference between Scale-Up (Vertical) and Scale-Out (Horizontal)?
â€ĸ Answer: Scale-Up (Vertical) increases the CPU, RAM, or disk of an existing virtual machine (often requires reboot/downtime and hits hardware ceilings). Scale-Out (Horizontal) adds more independent machine instances in parallel behind a load balancer with zero downtime.

â€ĸ Q: What is Target Tracking Scaling compared to Step Scaling in AWS?
â€ĸ Answer: Step scaling increases instances based on discrete graduated threshold steps (e.g. +1 if CPU > 60%, +3 if CPU > 80%). Target tracking automatically adjusts capacity to maintain a specific metric level (e.g. keep average CPU at 60%), scaling proportionally.