🎓 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 4: Cryptographic Password Hashing: Salt, SHA-256 & Rainbow Table Defense

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

📋 Experiment Overview & Curriculum Specifications

Cybersecurity & Defense â€ĸ Medium â€ĸ 30 mins

Aim / Objective: To formulate, implement, and analyze cryptographic password storage security comparing raw hashing, salted hashing, and iterative key-stretching (PBKDF2) against precomputed Rainbow Table attacks.

Prerequisites & Domain Concepts

Cryptographic hash functions (SHA-256), avalanche effect, salt generation, dictionary attacks.

Asymptotic Complexity Bounds

â€ĸ Time Complexity: O(I) where I is iteration count (100,000 iterations requires ~50-100ms compute, intentional speed bump)
â€ĸ Space Complexity: O(1) memory footprint for 32-byte derived key

Step-by-Step Algorithm

  1. Step 1: Build a simulated Rainbow Table mapping raw SHA-256 hashes of top common passwords ("password123", "admin2026", "secret") to plaintext.
  2. Step 2: Show that an unsalted hash is instantly cracked in O(1) time via dictionary lookup.
  3. Step 3: Implement hash_password(password): generate 16 cryptographically random salt bytes using os.urandom.
  4. Step 4: Execute PBKDF2-HMAC-SHA256 with 100,000 iterations to derive a 32-byte key.
  5. Step 5: Store formatted string: salt$iterations$hash.
  6. Step 6: Implement verify_password(stored_record, input_password) extracting salt and iterations.
  7. Step 7: Compute candidate hash and verify using constant-time comparison (hmac.compare_digest) to prevent timing side-channel attacks.
  8. Step 8: Demonstrate successful verification and rainbow table resistance.

Verified Academic Source Code (PYTHON)

import hashlib
import os
import hmac

class PasswordSecurityVault:
    def __init__(self, iterations=100000):
        self.iterations = iterations

    @staticmethod
    def unsalted_hash(password):
        """VULNERABLE: Deterministic unsalted SHA-256"""
        return hashlib.sha256(password.encode('utf-8')).hexdigest()

    def secure_hash_password(self, password):
        """SECURE: Cryptographic Salt + PBKDF2 Key Stretching"""
        # 16 bytes of cryptographically secure random salt
        salt = os.urandom(16)
        derived_key = hashlib.pbkdf2_hmac(
            'sha256',
            password.encode('utf-8'),
            salt,
            self.iterations
        )
        # Format: iterations$salt_hex$hash_hex
        return str(self.iterations) + "
quot; + salt.hex() + "quot; + derived_key.hex() def verify_password(self, stored_record, candidate_password): """Constant-time verification protecting against timing attacks""" try: iters_str, salt_hex, hash_hex = stored_record.split('#39;) iters = int(iters_str) salt = bytes.fromhex(salt_hex) expected_key = bytes.fromhex(hash_hex) candidate_key = hashlib.pbkdf2_hmac( 'sha256', candidate_password.encode('utf-8'), salt, iters ) # Constant-time comparison return hmac.compare_digest(candidate_key, expected_key) except Exception: return False # Demonstration Simulation vault = PasswordSecurityVault(iterations=100000) print("=== Cryptographic Password Hashing & Salting Analysis ===\n") # Phase 1: Rainbow Table Attack on Unsalted Hashes common_passwords = ["password123", "admin2026", "qwerty", "letmein123"] rainbow_table = {vault.unsalted_hash(pw): pw for pw in common_passwords} user_password = "password123" leaked_unsalted_hash = vault.unsalted_hash(user_password) print("--- Phase 1: Unsalted Hash Vulnerability (Rainbow Table) ---") print(f"Victim Password : '{user_password}'") print(f"Leaked Hash : {leaked_unsalted_hash}") # Attacker lookup if leaked_unsalted_hash in rainbow_table: cracked = rainbow_table[leaked_unsalted_hash] print(f" -> [CRACKED INSTANTLY] Attacker recovered plaintext: '{cracked}' via Rainbow Table!\n") # Phase 2: Secure Salted PBKDF2 Storage print("--- Phase 2: Salted PBKDF2 Storage & Verification ---") # Two users with identical passwords stored_user1 = vault.secure_hash_password("password123") stored_user2 = vault.secure_hash_password("password123") print(f"User 1 Stored Record: {stored_user1[:50]}...") print(f"User 2 Stored Record: {stored_user2[:50]}...") print("Notice: Even though both users chose 'password123', their stored hashes are COMPLETELY DIFFERENT due to unique salts.\n") # Phase 3: Login Verification test_attempts = [ ("password123", "Correct Password"), ("wrongPassword", "Incorrect Password"), ("Password123", "Case Sensitivity Check") ] print("--- Phase 3: Authentication Verification Tests ---") for pw_attempt, desc in test_attempts: valid = vault.verify_password(stored_user1, pw_attempt) status = "[ACCESS GRANTED]" if valid else "[ACCESS DENIED]" print(f"Attempt: '{pw_attempt:15}' ({desc:23}) -> {status}")
â–ļ Run in Online IDE

Sample Test Input

Victim password: "password123"; Evaluated under Rainbow table attack and Salted PBKDF2 storage

Expected Terminal Output

=== Cryptographic Password Hashing & Salting Analysis ===

--- Phase 1: Unsalted Hash Vulnerability (Rainbow Table) ---
Victim Password : 'password123'
Leaked Hash     : ef92b778bafe771e89245b89ecbc08a44a4e166c06659911881f383d4473e94f
  -> [CRACKED INSTANTLY] Attacker recovered plaintext: 'password123' via Rainbow Table!

--- Phase 2: Salted PBKDF2 Storage & Verification ---
User 1 Stored Record: 100000$c92b7c4d18fae120d9...
User 2 Stored Record: 100000$87d192a0e4420bf13a...
Notice: Even though both users chose 'password123', their stored hashes are COMPLETELY DIFFERENT due to unique salts.

--- Phase 3: Authentication Verification Tests ---
Attempt: 'password123    ' (Correct Password        ) -> [ACCESS GRANTED]
Attempt: 'wrongPassword   ' (Incorrect Password      ) -> [ACCESS DENIED]
Attempt: 'Password123     ' (Case Sensitivity Check  ) -> [ACCESS DENIED]
University Viva Voce Questions & Model Answers:

â€ĸ Q: What is a Rainbow Table and how does a Cryptographic Salt neutralize it?
â€ĸ Answer: A Rainbow Table is a precomputed table of hash values for millions of common passwords, allowing instant O(1) hash cracking. A random salt appended to each password creates a unique combined string, rendering generic precomputed tables completely useless.

â€ĸ Q: What is Key-Stretching and why is it necessary?
â€ĸ Answer: Modern computers and GPUs can compute billions of SHA-256 hashes per second. Key-stretching runs the hash function through many thousands of iterations (e.g. 100,000 rounds of PBKDF2), making brute-force guessing computationally too slow to execute at scale.

â€ĸ Q: What is a Timing Attack in password verification and how is it prevented?
â€ĸ Answer: Standard string equality (==) returns False as soon as the first non-matching byte is found, leaking time differences. Attackers can deduce passwords byte-by-byte based on response latency. hmac.compare_digest() compares all bytes in constant time regardless of mismatches.

â€ĸ Q: Why is Argon2id considered superior to PBKDF2 for modern password storage?
â€ĸ Answer: PBKDF2 is compute-hard but requires very little memory, allowing attackers to parallelize cracking on GPUs and custom ASICs. Argon2id is a memory-hard function requiring substantial RAM per thread, defeating GPU/ASIC parallelization.

â€ĸ Q: Does salting protect against a targeted dictionary attack against a single user?
â€ĸ Answer: Salting prevents multi-target attacks and rainbow tables, but it does NOT stop an attacker from trying dictionary guesses against a specific salted hash. Key-stretching (high iteration count) and strong password complexity policies are required to mitigate targeted dictionary attacks.