🎓 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 1: Text Preprocessing, Tokenization, Stopwords & Rule-Based Stemming

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

📋 Experiment Overview & Curriculum Specifications

NLP & Generative AI â€ĸ Easy â€ĸ 25 mins

Aim / Objective: To engineer an end-to-end natural language text preprocessing pipeline from scratch comprising case folding, regex tokenization, custom stopword filtration, and suffix stripping stemming.

Prerequisites & Domain Concepts

Regular expressions, Python string methods, set data structures, linguistic morphology.

Asymptotic Complexity Bounds

â€ĸ Time Complexity: O(N) where N is total number of characters in the input text
â€ĸ Space Complexity: O(W) where W is the number of extracted tokens

Step-by-Step Algorithm

  1. Step 1: Convert input text to lowercase (case folding).
  2. Step 2: Use regex pattern r'\b[a-z]+\b' to extract alphabetical word tokens, dropping punctuation and numbers.
  3. Step 3: Define a set of English stopwords (e.g., "the", "a", "an", "is", "and", "in", "to", "of").
  4. Step 4: Filter token list, keeping only words not present in the stopword set.
  5. Step 5: Implement rule-based stemmer: check suffix rules in order of decreasing length ('sses' -> 'ss', 'ies' -> 'i', 'ing' -> '', 'ed' -> '', 'ly' -> '').
  6. Step 6: Apply minimum stem length constraint (stem length >= 3) to prevent over-stemming.
  7. Step 7: Output tokenization stages and compare vocabulary reduction.

Verified Academic Source Code (PYTHON)

import re

class TextPreprocessor:
    def __init__(self):
        # Common English stopword list
        self.stopwords = {
            'a', 'about', 'above', 'after', 'again', 'against', 'all', 'am', 'an',
            'and', 'any', 'are', 'aren', 'as', 'at', 'be', 'because', 'been',
            'before', 'being', 'below', 'between', 'both', 'but', 'by', 'for',
            'from', 'further', 'had', 'has', 'have', 'having', 'he', 'her', 'here',
            'hers', 'herself', 'him', 'himself', 'his', 'how', 'i', 'if', 'in',
            'into', 'is', 'it', 'its', 'itself', 'just', 'me', 'more', 'most',
            'my', 'myself', 'no', 'nor', 'not', 'now', 'of', 'off', 'on', 'once',
            'only', 'or', 'other', 'our', 'ours', 'ourselves', 'out', 'over',
            'own', 'same', 'she', 'should', 'so', 'some', 'such', 'than', 'that',
            'the', 'their', 'theirs', 'them', 'themselves', 'then', 'there',
            'these', 'they', 'this', 'those', 'through', 'to', 'too', 'under',
            'until', 'up', 'very', 'was', 'we', 'were', 'what', 'when', 'where',
            'which', 'while', 'who', 'whom', 'why', 'with', 'you', 'your', 'yours'
        }

    def tokenize(self, text):
        """Case folding and regex boundary tokenization"""
        return re.findall(r'\b[a-z]+\b', text.lower())

    def remove_stopwords(self, tokens):
        """O(1) hash set membership filtering"""
        return [t for t in tokens if t not in self.stopwords]

    def stem_word(self, word):
        """Simplified rule-based morphological suffix stripper"""
        # Rule 1: Plural and third person singular
        if word.endswith('sses'):
            return word[:-2]
        if word.endswith('ies'):
            return word[:-2]
        if word.endswith('ss'):
            return word
        if word.endswith('s') and len(word) > 3:
            return word[:-1]

        # Rule 2: Past tense and progressive participle
        if word.endswith('eed'):
            if len(word) > 4:
                return word[:-1]
        elif word.endswith('ed'):
            stem = word[:-2]
            if len(stem) >= 3:
                return stem
        elif word.endswith('ing'):
            stem = word[:-3]
            if len(stem) >= 3:
                # Handle doubled consonants: running -> run
                if len(stem) >= 3 and stem[-1] == stem[-2]:
                    stem = stem[:-1]
                return stem

        # Rule 3: Adverbial suffixes
        if word.endswith('ly') and len(word) > 4:
            return word[:-2]

        return word

    def process(self, raw_text):
        raw_tokens = self.tokenize(raw_text)
        filtered_tokens = self.remove_stopwords(raw_tokens)
        stemmed_tokens = [self.stem_word(w) for w in filtered_tokens]
        return raw_tokens, filtered_tokens, stemmed_tokens

# Sample document text
corpus_text = (
    "The distributed systems engineers were actively optimizing and testing "
    "their cloud computing architectures. Faster algorithms quickly solved "
    "the computational bottlenecks, running efficiently on modern processors."
)

pipeline = TextPreprocessor()
raw_toks, filtered_toks, stemmed_toks = pipeline.process(corpus_text)

print("=== NLP Text Preprocessing & Stemming Pipeline ===\n")
print(f"Original Text:\n\"{corpus_text}\"\n")
print(f"1. Raw Tokens ({len(raw_toks)} tokens):")
print(f"   {raw_toks}\n")
print(f"2. Stopwords Removed ({len(filtered_toks)} tokens):")
print(f"   {filtered_toks}\n")
print(f"3. Stemmed Word Forms ({len(stemmed_toks)} stems):")
print(f"   {stemmed_toks}\n")

print("--- Morphological Mapping Table ---")
for original, stem in zip(filtered_toks, stemmed_toks):
    arrow = "->" if original != stem else "=="
    print(f"  {original:15} {arrow} {stem}")
â–ļ Run in Online IDE

Sample Test Input

A 2-sentence paragraph containing plural forms, adverbs, past-tense verbs, and stopwords

Expected Terminal Output

=== NLP Text Preprocessing & Stemming Pipeline ===

Original Text:
"The distributed systems engineers were actively optimizing and testing their cloud computing architectures. Faster algorithms quickly solved the computational bottlenecks, running efficiently on modern processors."

1. Raw Tokens (25 tokens):
   ['the', 'distributed', 'systems', 'engineers', 'were', 'actively', 'optimizing', 'and', 'testing', 'their', 'cloud', 'computing', 'architectures', 'faster', 'algorithms', 'quickly', 'solved', 'the', 'computational', 'bottlenecks', 'running', 'efficiently', 'on', 'modern', 'processors']

2. Stopwords Removed (19 tokens):
   ['distributed', 'systems', 'engineers', 'actively', 'optimizing', 'testing', 'cloud', 'computing', 'architectures', 'faster', 'algorithms', 'quickly', 'solved', 'computational', 'bottlenecks', 'running', 'efficiently', 'modern', 'processors']

3. Stemmed Word Forms (19 stems):
   ['distribut', 'system', 'engineer', 'active', 'optimiz', 'test', 'cloud', 'comput', 'architectur', 'faster', 'algorithm', 'quick', 'solv', 'computational', 'bottleneck', 'run', 'efficient', 'modern', 'processor']

--- Morphological Mapping Table ---
  distributed     -> distribut
  systems         -> system
  engineers       -> engineer
  actively        -> active
  optimizing      -> optimiz
  testing         -> test
  cloud           == cloud
  computing       -> comput
  architectures   -> architectur
  faster          == faster
  algorithms      -> algorithm
  quickly         -> quick
  solved          -> solv
  computational   == computational
  bottlenecks     -> bottleneck
  running         -> run
  efficiently     -> efficient
  modern          == modern
  processors      -> processor
University Viva Voce Questions & Model Answers:

â€ĸ Q: What is the fundamental difference between Stemming and Lemmatization?
â€ĸ Answer: Stemming is a crude, rule-based heuristic that chops off word suffixes, often producing non-words (e.g. "comput"). Lemmatization uses vocabulary and morphological analysis with parts of speech (POS) to return valid dictionary root words (lemmas, e.g. "better" -> "good").

â€ĸ Q: Why is stopword removal beneficial for information retrieval systems?
â€ĸ Answer: Stopwords (e.g. "the", "is") appear with high frequency across nearly all documents, providing virtually zero discriminating information while consuming valuable storage and compute.

â€ĸ Q: What is the Martin Porter Stemming Algorithm?
â€ĸ Answer: Published in 1980, the Porter Stemmer is a 5-step cascade of rule-based suffix replacements based on consonant-vowel transitions (measure m), remaining the most widely used English stemmer.

â€ĸ Q: What are the two common errors in stemming?
â€ĸ Answer: Over-stemming: merging words with distinct meanings to the same stem (e.g. "organization" and "organ" to "organ"). Under-stemming: failing to merge words with the same conceptual root (e.g. "adhere" and "adhesion").

â€ĸ Q: When should stopword removal be skipped in NLP?
â€ĸ Answer: In sentiment analysis (where "not" reverses meaning), in machine translation, and in large language models (LLMs) where prepositions and functional grammar words provide essential syntactic structure.