Advanced & Post-Graduate DiplomaIntermediate

PGDCA / HDCA - Post Graduate / Higher Diploma in Computer Applications

Office applications, C foundations, C++ or TallyPrime elective, Python, SQL/MySQL, AI productivity and a practical application project.

Talk to a counsellor about PGDCA / HDCA - Post Graduate / Higher Diploma in Computer Applications

Fees, batch dates and timings are shared by a counsellor. No payment is needed to ask.

What you will cover
  • Office applications
  • C foundations
  • C++ or TallyPrime elective
  • Python
  • SQL/MySQL
  • AI productivity
  • a practical application project

Topic list from the institute's programme record.

Certification

Certificate terms for this programme are confirmed by the institute at admission. Any ADIVAS course-completion certificate is an institute certificate; it is not a university degree, an externally accredited qualification or a vendor certification (such as AWS or Microsoft) unless the institute states so in writing.

The programme title is as supplied in the institute's list. Please confirm the awarding body and recognition with the institute before enrolling.

Curriculum 0.1 · Draft: written for ADIVAS and awaiting academic review and approval. Topics and weeks may change before your batch starts.

Your skill trail

You move through 7 stations. Each week builds one skill you can show, not just a topic you have heard.

  1. Computer and office applications

    Use files, Google Workspace, Word, Excel and PowerPoint with confidence.

    • Week 1 Computer systems, files and networks
    • Week 2 Internet, email and Google Workspace
    • Week 3 Word: documents for work
    • Week 4 Word: long documents and mail merge
    • Week 5 Excel: worksheets and formulas
    • Week 6 Excel: logic and lookups
    • Week 7 Excel: data tools, pivots and charts
    • Week 8 PowerPoint and the office report
  2. Problem solving and C

    Solve problems algorithmically and implement them in C.

    • Week 9 Problem solving and flowcharts
    • Week 10 C: setup, types and input/output
    • Week 11 C: operators and expressions
    • Week 12 C: decisions with if and switch
    • Week 13 C: loops
    • Week 14 C: nested loops, patterns and debugging
    • Week 15 C: arrays
    • Week 16 C: strings
    • Week 17 C: functions
    • Week 18 C: pointers basics
    • Week 19 C: structures and files
    • Week 20 C mini project
  3. Elective: C++ or TallyPrime

    Complete one elective track with a mini project.

    • Week 21 Elective: C++ basics / Tally company and masters
    • Week 22 Elective: classes and objects / vouchers
    • Week 23 Elective: constructors and encapsulation / GST invoices
    • Week 24 Elective: inheritance and polymorphism / inventory
    • Week 25 Elective: STL and files / reports and reconciliation
    • Week 26 Elective mini project
  4. Python programming

    Write and test Python programs and automate office tasks.

    • Week 27 Python: setup, variables and input
    • Week 28 Python: decisions and loops
    • Week 29 Python: lists, tuples, sets and dictionaries
    • Week 30 Python: functions and modules
    • Week 31 Python: strings, files and CSV
    • Week 32 Python: errors, testing and debugging
    • Week 33 Python: object-oriented basics
    • Week 34 Python: data handling and reports
    • Week 35 Python: automating office tasks
    • Week 36 Python mini project
  5. SQL and MySQL

    Design and query relational databases.

    • Week 37 Databases and design basics
    • Week 38 SQL: creating tables and constraints
    • Week 39 SQL: insert, update and delete
    • Week 40 SQL: SELECT, filters and aggregates
    • Week 41 SQL: joins and subqueries
    • Week 42 SQL: normalisation and better design
    • Week 43 SQL: views, indexes, security and Python connection
  6. AI productivity

    Use AI responsibly with verification.

    • Week 44 AI productivity with checks
  7. Application project

    Plan, build, test and present a data application.

    • Week 45 Project: requirements and design
    • Week 46 Project: database and application build
    • Week 47 Project: testing, documents and report
    • Week 48 Project: demonstration and portfolio
  8. Coaching Institute Admissions and Fees Manager

    Your project, reviewed by a trainer.

The ADIVAS mastery ladder: how each skill is recognised
  1. Explored You have seen the idea and tried a first example.
  2. Practising You can do it with hints and keep improving.
  3. Proficient You complete the weekly practical task correctly on your own.
  4. Proven You apply it in a project reviewed by your trainer.

Skill-level tracking is being added to the learner workspace. Your trainer already reviews weekly practical work.

What you will be able to do

  • Manage files, email and Google Workspace and produce professional Word documents, including long documents and mail merge.
  • Build Excel workbooks with formulas, lookups, validation, pivot tables and charts for reports.
  • Prepare a clear PowerPoint presentation and a short written office report from data.
  • Break a problem into steps and express it as an algorithm, flowchart and test cases.
  • Write, trace and debug C programs using conditions, loops, arrays, strings, functions, pointers and files.
  • Complete the chosen elective: object-oriented programs in C++ (Track A) or GST accounting in TallyPrime (Track B).
  • Write Python programs with functions, collections, files, exceptions and tests, and automate a routine office task.
  • Design a normalised MySQL database and write SQL for create, insert, update, delete, joins, aggregates and views.
  • Connect Python to MySQL to build a small data application with reports.
  • Use AI tools to draft, explain and review code and documents, then verify the output and protect private data.
  • Plan, build, test, document and present a practical application project.

Who it suits

  • School Class 11 and 12 learners with an interest in computing who want a structured, practical start before college.
  • College Graduates and final-year students who want a broad, applied computer applications base for jobs and further study.
  • Professional Working professionals and career changers who need office automation, programming and database skills for data and application work.

Prerequisites: Basic computer skills and a graduation or equivalent level of study; no programming experience is assumed. Tools: Microsoft Word, Excel and PowerPoint (or LibreOffice equivalents), Google Workspace account, A C compiler (GCC or MinGW) with a code editor, C++ compiler (Track A) or TallyPrime (Track B), Python 3 with pip, a code editor and a package for MySQL connection, MySQL Server and MySQL Workbench, A free AI assistant for the checked-use weeks.

Weekly plan

Computer and office applications Weeks 1–8

Week 1: Computer systems, files and networks

Theory
  • Hardware, operating system, storage, memory
  • Folders, file naming, backup, compression
  • LAN, Wi-Fi, IP address, router basics, safe passwords
Lab
Build a naming and backup plan; inspect your computer's specs and network settings; identify five phishing samples.
Homework
Draw a block diagram of a computer lab network.
Deliverable
Folder system, naming guide and a lab network sketch.
Weekly checkpoint
Short test and a file-organising task.
You will be able to
Manage files, email and Google Workspace and produce professional Word documents, including long documents and mail merge.

Week 2: Internet, email and Google Workspace

Theory
  • Email etiquette, Cc/Bcc, calendar
  • Drive, Docs, Sheets, Forms and sharing roles
  • Search skills and source checking
Lab
Create a shared Drive folder for a mock project team, collect data through a Google Form and write a professional email report.
Homework
Document who has what access to your folder.
Deliverable
Shared folder, Form with 10 responses and a report email.
Weekly checkpoint
Spot sharing mistakes in a sample setup.
You will be able to
Manage files, email and Google Workspace and produce professional Word documents, including long documents and mail merge.

Week 3: Word: documents for work

Theory
  • Formatting, tables, images and page layout
  • Business letters, notices and bilingual text
  • Proofreading and PDF export
Lab
Prepare a letter, a notice and a one-page profile of a fictional institute with a table and a logo.
Homework
Redo a poorly formatted document.
Deliverable
Three formatted documents in DOCX and PDF.
Weekly checkpoint
Timed formatting task.
You will be able to
Manage files, email and Google Workspace and produce professional Word documents, including long documents and mail merge.

Week 4: Word: long documents and mail merge

Theory
  • Styles, headers, page numbers, table of contents
  • Mail merge letters and labels
  • Track changes and comments
Lab
Style a 10-page report, add a contents page and merge a fee-reminder letter with Excel data.
Homework
Review a peer's document with tracked changes.
Deliverable
Styled report and merged letters.
Weekly checkpoint
Update the contents and fix a failing merge.
You will be able to
Manage files, email and Google Workspace and produce professional Word documents, including long documents and mail merge.

Week 5: Excel: worksheets and formulas

Theory
  • Cells, formats, ₹ and dates
  • SUM, AVERAGE, ROUND, MIN, MAX
  • Relative and absolute references
Lab
Build a mark sheet and a GST bill with a locked rate cell.
Homework
Check totals by hand.
Deliverable
Mark sheet and GST bill workbook.
Weekly checkpoint
Explain a wrong result caused by a missing $.
You will be able to
Build Excel workbooks with formulas, lookups, validation, pivot tables and charts for reports.

Week 6: Excel: logic and lookups

Theory
  • IF, nested IF, AND, OR
  • COUNTIFS, SUMIFS, AVERAGEIF
  • XLOOKUP or VLOOKUP and IFERROR
Lab
Create a result analysis with grades and an invoice with lookup rates.
Homework
Fix three broken formulas.
Deliverable
Result analysis and lookup invoice workbook.
Weekly checkpoint
Debug a wrong nested IF.
You will be able to
Build Excel workbooks with formulas, lookups, validation, pivot tables and charts for reports.

Week 7: Excel: data tools, pivots and charts

Theory
  • Sorting, filters, data validation, conditional formatting
  • PivotTables and slicers
  • Choosing and labelling charts
Lab
Clean a 200-row enquiry list, add dropdowns and build a pivot dashboard.
Homework
Write three business questions the pivot answers.
Deliverable
Cleaned list with a dashboard sheet.
Weekly checkpoint
Answer five questions from a dataset with filters and a pivot.
You will be able to
Build Excel workbooks with formulas, lookups, validation, pivot tables and charts for reports.

Week 8: PowerPoint and the office report

Theory
  • Slide design: one message per slide
  • Charts from Excel, speaker notes, handouts
  • Report structure: summary, key numbers, actions
Lab
Turn the dashboard into a six-slide deck and a two-page report; present for 3 minutes.
Homework
Rehearse and note questions.
Deliverable
Deck, handout and two-page report.
Weekly checkpoint
Peer feedback checklist and number cross-check.
You will be able to
Prepare a clear PowerPoint presentation and a short written office report from data.
Problem solving and C Weeks 9–20

Week 9: Problem solving and flowcharts

Theory
  • Algorithms and the steps of problem solving
  • Flowchart symbols and pseudocode
  • Test cases: normal, boundary and invalid input
Lab
Write algorithms and flowcharts for a bill total, the largest of three numbers and an ATM withdrawal; list test cases for each.
Homework
Write the algorithm for a daily routine task.
Deliverable
Three flowcharts with test tables.
Weekly checkpoint
Trace a flowchart for given inputs.
You will be able to
Break a problem into steps and express it as an algorithm, flowchart and test cases.

Week 10: C: setup, types and input/output

Theory
  • Compiler setup, structure of a C program
  • int, float, char, variables and constants
  • printf, scanf and format specifiers
Lab
Install a C compiler, run a first program, then write programs for rectangle area and a simple interest calculator.
Homework
Write a program that converts rupees to paise.
Deliverable
Three small C programs.
Weekly checkpoint
Predict output and fix compile errors in four snippets.
You will be able to
Write, trace and debug C programs using conditions, loops, arrays, strings, functions, pointers and files.

Week 11: C: operators and expressions

Theory
  • Arithmetic, relational, logical operators
  • Precedence, integer division and modulus
  • Type conversion and common overflow mistakes
Lab
Programs: swap two numbers, split seconds into hours/minutes/seconds, check even or odd using %.
Homework
Evaluate ten expressions by hand then in code.
Deliverable
Three programs with hand-trace notes.
Weekly checkpoint
Output prediction quiz.
You will be able to
Write, trace and debug C programs using conditions, loops, arrays, strings, functions, pointers and files.

Week 12: C: decisions with if and switch

Theory
  • if, else if, nested conditions
  • switch and menu programs
  • Boundary testing
Lab
Write a grade calculator, an electricity bill slab calculator and a menu-driven simple calculator.
Homework
Create test cases that cover every branch.
Deliverable
Three programs with test tables.
Weekly checkpoint
Find the bug in a wrong grade program.
You will be able to
Write, trace and debug C programs using conditions, loops, arrays, strings, functions, pointers and files.

Week 13: C: loops

Theory
  • while, do-while and for loops
  • Counters, accumulators and trace tables
  • break and continue
Lab
Write programs: sum of 1 to n, multiplication table, digit sum, and a retry-password loop with three attempts.
Homework
Trace a loop on paper with a table.
Deliverable
Four programs with trace tables.
Weekly checkpoint
Trace the output of three loops.
You will be able to
Write, trace and debug C programs using conditions, loops, arrays, strings, functions, pointers and files.

Week 14: C: nested loops, patterns and debugging

Theory
  • Nested loops and patterns
  • Prime and factorial logic
  • Debugging: print statements, reading compiler messages
Lab
Print triangle and pyramid patterns, list primes up to 100 and fix five planted bugs.
Homework
Write a bug diary of mistakes made.
Deliverable
Pattern programs and a debugging log.
Weekly checkpoint
Debug timed exercise.
You will be able to
Write, trace and debug C programs using conditions, loops, arrays, strings, functions, pointers and files.

Week 15: C: arrays

Theory
  • One-dimensional arrays and traversal
  • Searching and sorting (linear search, bubble sort)
  • Two-dimensional arrays for tables
Lab
Store marks of 10 students, find highest, average and search a mark; sort the marks; add a 2D table of 3 subjects.
Homework
Trace bubble sort on five numbers.
Deliverable
Marks analysis program with sort.
Weekly checkpoint
Trace a sort and spot an off-by-one error.
You will be able to
Write, trace and debug C programs using conditions, loops, arrays, strings, functions, pointers and files.

Week 16: C: strings

Theory
  • Character arrays and the null terminator
  • string.h: strlen, strcpy, strcmp, strcat
  • Reading lines safely
Lab
Programs: count vowels, reverse a string, palindrome check and a simple username validator.
Homework
Find three string bugs in sample code.
Deliverable
Four string programs.
Weekly checkpoint
Predict outputs of string snippets.
You will be able to
Write, trace and debug C programs using conditions, loops, arrays, strings, functions, pointers and files.

Week 17: C: functions

Theory
  • Function definition, call, parameters, return
  • Scope and recursion basics
  • Modular programs
Lab
Refactor the earlier marks program into functions; write factorial (loop and recursion) and a fee calculator function.
Homework
Draw the call flow of your program.
Deliverable
Modular marks program.
Weekly checkpoint
Trace function calls and returns.
You will be able to
Write, trace and debug C programs using conditions, loops, arrays, strings, functions, pointers and files.

Week 18: C: pointers basics

Theory
  • Memory address and pointer variables
  • Pass by value vs pass by reference
  • Pointers and arrays
Lab
Write a swap function using pointers, a function that returns min and max through pointers, and explore addresses of array elements.
Homework
Draw a memory diagram for a small program.
Deliverable
Pointer programs with memory diagrams.
Weekly checkpoint
Diagram a pointer swap and find a null pointer error.
You will be able to
Write, trace and debug C programs using conditions, loops, arrays, strings, functions, pointers and files.

Week 19: C: structures and files

Theory
  • struct for records
  • Reading and writing text files
  • Simple record storage and search
Lab
Store student records in a struct array and save/load them from a text file; search a record by roll number.
Homework
Design the record layout for a library book.
Deliverable
Student record program with file storage.
Weekly checkpoint
Handle a missing file without crashing.
You will be able to
Write, trace and debug C programs using conditions, loops, arrays, strings, functions, pointers and files.

Week 20: C mini project

Theory
  • Requirements and menu design
  • Combining functions, arrays, structs and files
  • Testing with a plan
Lab
Build a menu-driven library or billing program with add, view, search and update, saving to a file.
Homework
Write a test table of at least 12 cases.
Deliverable
Working C mini project with test table.
Weekly checkpoint
Demo and code walkthrough.
You will be able to
Break a problem into steps and express it as an algorithm, flowchart and test cases. Write, trace and debug C programs using conditions, loops, arrays, strings, functions, pointers and files.
Elective: C++ or TallyPrime Weeks 21–26

Week 21: Elective: C++ basics / Tally company and masters

Theory
  • Track A: C++ structure, cin/cout, references, namespaces. Track B: TallyPrime company creation, groups and ledgers
  • Track A: differences from C. Track B: chart of accounts for a small trader
  • Both: learning plan and exercises
Lab
Track A: rewrite two C programs in C++ with cin/cout and a function using references. Track B: create a company and set up 25 ledgers for a stationery trader.
Homework
Track A: list five differences between C and C++. Track B: classify 20 items as asset, liability, income or expense.
Deliverable
Track A: two C++ programs. Track B: company with ledger masters.
Weekly checkpoint
Track-specific five-question check.
You will be able to
Complete the chosen elective: object-oriented programs in C++ (Track A) or GST accounting in TallyPrime (Track B).

Week 22: Elective: classes and objects / vouchers

Theory
  • Track A: class, object, member functions, access specifiers. Track B: sales, purchase, receipt, payment and journal vouchers
  • Track A: modelling a bank account. Track B: debit/credit rules with examples
  • Both: validation of inputs and records
Lab
Track A: BankAccount class with deposit and withdraw rules. Track B: record 20 transactions of a stationery shop and check the trial balance.
Homework
Track A: model a Student class. Track B: correct three wrongly passed entries.
Deliverable
Track A: BankAccount program. Track B: voucher entries and trial balance.
Weekly checkpoint
Find errors in a given class or in three voucher entries.
You will be able to
Complete the chosen elective: object-oriented programs in C++ (Track A) or GST accounting in TallyPrime (Track B).

Week 23: Elective: constructors and encapsulation / GST invoices

Theory
  • Track A: constructors, destructors, encapsulation, getters. Track B: GST setup, CGST, SGST and IGST, HSN/SAC details
  • Track A: object lifecycle. Track B: tax invoice, GST on intrastate and interstate sales
  • Both: error handling
Lab
Track A: add constructors and validation to the bank program. Track B: set GST ledgers and prepare invoices for local and out-of-state customers.
Homework
Track A: trace object creation order. Track B: compute GST for five invoices by hand.
Deliverable
Track A: improved class. Track B: five GST invoices.
Weekly checkpoint
Compute CGST/SGST/IGST for given sales or predict constructor output.
You will be able to
Complete the chosen elective: object-oriented programs in C++ (Track A) or GST accounting in TallyPrime (Track B).

Week 24: Elective: inheritance and polymorphism / inventory

Theory
  • Track A: inheritance, overriding, virtual functions. Track B: stock groups, items, units, godowns
  • Track A: Employee and Manager classes. Track B: purchase and sales with stock tracking
  • Both: reorder logic
Lab
Track A: build Employee, Manager and Clerk classes with salary calculation. Track B: create stock items and process purchases and sales with closing stock.
Homework
Track A: draw a class diagram. Track B: reconcile physical stock with Tally stock.
Deliverable
Track A: hierarchy program. Track B: inventory entries and stock summary.
Weekly checkpoint
Predict polymorphic output or check closing stock.
You will be able to
Complete the chosen elective: object-oriented programs in C++ (Track A) or GST accounting in TallyPrime (Track B).

Week 25: Elective: STL and files / reports and reconciliation

Theory
  • Track A: vector, string, map, simple file I/O. Track B: bank ledger, reconciliation, day book, GST returns summary report
  • Track A: storing objects in a vector. Track B: reading Balance Sheet and Profit & Loss
  • Both: exports
Lab
Track A: store objects in a vector, sort and save to a file. Track B: reconcile a bank statement, produce reports and export to Excel.
Homework
Track A: add search to the program. Track B: explain the difference between cash and bank ledgers.
Deliverable
Track A: records program with file save. Track B: reconciliation and reports.
Weekly checkpoint
Find the three planted differences in a bank reconciliation or STL snippet bugs.
You will be able to
Complete the chosen elective: object-oriented programs in C++ (Track A) or GST accounting in TallyPrime (Track B).

Week 26: Elective mini project

Theory
  • Track A: design a console application with classes. Track B: record a month of transactions
  • Testing and presenting
  • Documentation
Lab
Track A: build a Library or Hostel management console app with classes. Track B: complete one month of books for a trader with GST, stock, bank reconciliation and reports.
Homework
Write a README or an explanation note of the entries.
Deliverable
Elective project files and a one-page note.
Weekly checkpoint
Demo and viva for your track.
You will be able to
Complete the chosen elective: object-oriented programs in C++ (Track A) or GST accounting in TallyPrime (Track B).
Python programming Weeks 27–36

Week 27: Python: setup, variables and input

Theory
  • Interpreter, editor, running scripts
  • Variables, numbers, strings, f-strings
  • input() and type conversion
Lab
Write a bill calculator, a temperature converter and a name formatter; compare with the C version.
Homework
List three ways Python differs from C.
Deliverable
Three Python scripts.
Weekly checkpoint
Fix common errors: indentation, wrong types.
You will be able to
Write Python programs with functions, collections, files, exceptions and tests, and automate a routine office task.

Week 28: Python: decisions and loops

Theory
  • if/elif/else and Boolean logic
  • for and while loops, range
  • Break, continue and nested loops
Lab
Re-implement the grade calculator, multiplication table, prime list and number-guessing game.
Homework
Trace a loop with a table.
Deliverable
Four Python programs.
Weekly checkpoint
Predict outputs of snippets.
You will be able to
Write Python programs with functions, collections, files, exceptions and tests, and automate a routine office task.

Week 29: Python: lists, tuples, sets and dictionaries

Theory
  • Lists, slicing, methods, tuples
  • Dictionaries and sets
  • Choosing a collection
Lab
Build a phone directory (dictionary), unique visitors (set) and a marks list with statistics.
Homework
Convert a table into list of dictionaries.
Deliverable
Directory and marks analysis scripts.
Weekly checkpoint
Choose the right collection for five cases.
You will be able to
Write Python programs with functions, collections, files, exceptions and tests, and automate a routine office task.

Week 30: Python: functions and modules

Theory
  • Parameters, defaults, return values
  • Scope, docstrings and modules
  • Using the standard library: math, random, datetime
Lab
Make a utilities module with fee, GST and age functions and use it in a small billing script.
Homework
Write docstrings for each function.
Deliverable
Utilities module and billing script.
Weekly checkpoint
Trace function calls and find a scope bug.
You will be able to
Write Python programs with functions, collections, files, exceptions and tests, and automate a routine office task.

Week 31: Python: strings, files and CSV

Theory
  • String methods and formatting
  • Reading/writing text files, with-statement
  • CSV reading and writing
Lab
Clean a CSV of customers (names, phones), find duplicates and write a summary file.
Homework
Create a CSV by hand and process it.
Deliverable
Cleaned CSV and summary.
Weekly checkpoint
Fix a script that fails on blank rows.
You will be able to
Write Python programs with functions, collections, files, exceptions and tests, and automate a routine office task.

Week 32: Python: errors, testing and debugging

Theory
  • try/except and specific exceptions
  • Assertions and simple unit tests
  • Reading tracebacks
Lab
Make the billing script robust (bad input, missing file) and write tests for three functions.
Homework
List five ways your program can fail.
Deliverable
Robust script with test file.
Weekly checkpoint
Predict which exception occurs and handle it.
You will be able to
Write Python programs with functions, collections, files, exceptions and tests, and automate a routine office task.

Week 33: Python: object-oriented basics

Theory
  • Classes, objects, __init__, methods
  • Encapsulation and simple inheritance
  • Modelling real entities
Lab
Model Student and Course classes with enrolment and fee due methods.
Homework
Compare with C structs and functions.
Deliverable
Student-Course model script.
Weekly checkpoint
Explain when a class is better than a dictionary.
You will be able to
Write Python programs with functions, collections, files, exceptions and tests, and automate a routine office task.

Week 34: Python: data handling and reports

Theory
  • Aggregating data with dictionaries
  • pandas basics: DataFrame, filter, groupby (optional but recommended)
  • Charts with matplotlib
Lab
Load a sales CSV, group by month and branch, and draw a chart; save a summary CSV.
Homework
Compare the result with an Excel pivot.
Deliverable
Sales analysis script and chart.
Weekly checkpoint
Answer five questions from the dataset using code.
You will be able to
Write Python programs with functions, collections, files, exceptions and tests, and automate a routine office task. Build Excel workbooks with formulas, lookups, validation, pivot tables and charts for reports.

Week 35: Python: automating office tasks

Theory
  • Working with Excel files via openpyxl or pandas
  • Renaming and organising files with os/pathlib
  • Generating simple reports
Lab
Write a script to rename 30 files by a rule, and read an Excel mark list to produce pass/fail text reports.
Homework
Run the script on a copy of a folder first and describe the results.
Deliverable
Two automation scripts.
Weekly checkpoint
Test on a sample folder safely.
You will be able to
Write Python programs with functions, collections, files, exceptions and tests, and automate a routine office task.

Week 36: Python mini project

Theory
  • Requirements and structure
  • Combining modules, files and classes
  • Testing and README
Lab
Build a console fee-tracker or inventory app with CSV storage, validation and a monthly summary.
Homework
Prepare 12 test cases.
Deliverable
Working Python project with README.
Weekly checkpoint
Demo and code review.
You will be able to
Write Python programs with functions, collections, files, exceptions and tests, and automate a routine office task. Break a problem into steps and express it as an algorithm, flowchart and test cases.
SQL and MySQL Weeks 37–43

Week 37: Databases and design basics

Theory
  • Why databases; tables, rows, columns, keys
  • Entity-relationship thinking
  • MySQL installation and workbench basics
Lab
Install MySQL, create a database and draw an ER diagram for a library or coaching institute.
Homework
Identify entities and relationships in a school.
Deliverable
Installed MySQL and an ER diagram.
Weekly checkpoint
Identify primary and foreign keys in examples.
You will be able to
Design a normalised MySQL database and write SQL for create, insert, update, delete, joins, aggregates and views.

Week 38: SQL: creating tables and constraints

Theory
  • CREATE TABLE, data types, primary and foreign keys
  • NOT NULL, UNIQUE, CHECK, DEFAULT
  • ALTER and DROP safely
Lab
Create tables for students, courses and enrolments with keys and constraints; insert sample rows.
Homework
Write constraints that stop invalid data.
Deliverable
Schema script (.sql file).
Weekly checkpoint
Find which row violates which constraint.
You will be able to
Design a normalised MySQL database and write SQL for create, insert, update, delete, joins, aggregates and views.

Week 39: SQL: insert, update and delete

Theory
  • INSERT, UPDATE, DELETE with WHERE
  • Transactions: START, COMMIT, ROLLBACK
  • Safe update practice and backups
Lab
Load 30 rows, update fees for one course, delete a wrong record and use ROLLBACK to undo a deliberate mistake.
Homework
Write a safe-update checklist.
Deliverable
Data script and transaction log.
Weekly checkpoint
Explain what happens when WHERE is forgotten.
You will be able to
Design a normalised MySQL database and write SQL for create, insert, update, delete, joins, aggregates and views.

Week 40: SQL: SELECT, filters and aggregates

Theory
  • SELECT, WHERE, ORDER BY, LIMIT, LIKE
  • COUNT, SUM, AVG, MIN, MAX
  • GROUP BY and HAVING
Lab
Write 15 queries on the institute database: fee totals per course, students per city, top five payers.
Homework
Predict the output of 5 queries.
Deliverable
Query file with results.
Weekly checkpoint
Write queries for five questions.
You will be able to
Design a normalised MySQL database and write SQL for create, insert, update, delete, joins, aggregates and views.

Week 41: SQL: joins and subqueries

Theory
  • INNER JOIN, LEFT JOIN
  • Subqueries and IN / EXISTS
  • Reading query plans at a basic level
Lab
Join students, enrolments and courses; list students with no enrolment; find courses above average fee.
Homework
Draw a diagram of how the join matches rows.
Deliverable
Join and subquery file.
Weekly checkpoint
Choose between INNER and LEFT JOIN for four requirements.
You will be able to
Design a normalised MySQL database and write SQL for create, insert, update, delete, joins, aggregates and views.

Week 42: SQL: normalisation and better design

Theory
  • Redundancy and anomalies
  • First, second and third normal form
  • Splitting a flat spreadsheet into tables
Lab
Take a flat Excel enquiry sheet with repeated course details and normalise it to three tables; migrate the data with SQL.
Homework
Explain why the original design caused update problems.
Deliverable
Normalised schema and migration script.
Weekly checkpoint
Normalise a given table to 3NF.
You will be able to
Design a normalised MySQL database and write SQL for create, insert, update, delete, joins, aggregates and views.

Week 43: SQL: views, indexes, security and Python connection

Theory
  • Views for reports; indexes and when to use them
  • Users, privileges and backup/restore
  • Connecting Python with a MySQL connector and parameterised queries
Lab
Create a fee-summary view, back up the database and write a Python script that reads and inserts records using parameterised queries.
Homework
Explain SQL injection in your own words.
Deliverable
View, backup file and a working Python script.
Weekly checkpoint
Spot an injection risk in a sample script.
You will be able to
Design a normalised MySQL database and write SQL for create, insert, update, delete, joins, aggregates and views. Connect Python to MySQL to build a small data application with reports.
AI productivity Weeks 44

Week 44: AI productivity with checks

Theory
  • Using AI to explain code, draft documents and generate test data
  • Checking: run it, test it, read it; spotting wrong or unsafe suggestions
  • Privacy, licences and responsible use
Lab
Ask an AI assistant to write a SQL query and a Python function; run and test both, record each error and correct it; write an AI-use policy for your project.
Homework
Review an AI answer that contains a deliberate bug.
Deliverable
AI use log with corrections and a one-page policy.
Weekly checkpoint
Find and fix three problems in AI-generated code.
You will be able to
Use AI tools to draft, explain and review code and documents, then verify the output and protect private data.
Application project Weeks 45–48

Week 45: Project: requirements and design

Theory
  • Choosing a project (admissions, inventory, billing, library)
  • Requirements, ER diagram and screen/report layouts
  • Plan, test cases and risk list
Lab
Write the requirement document, ER diagram, table list, report layouts and a four-week plan.
Homework
Collect realistic sample data of 50 rows.
Deliverable
Design document with ER diagram and plan.
Weekly checkpoint
Design review with the trainer.
You will be able to
Plan, build, test, document and present a practical application project. Break a problem into steps and express it as an algorithm, flowchart and test cases. Design a normalised MySQL database and write SQL for create, insert, update, delete, joins, aggregates and views.

Week 46: Project: database and application build

Theory
  • Create the schema and load data
  • Python app with menus and validation
  • Reports: SQL views plus Excel export
Lab
Implement the schema, Python application functions and at least three SQL reports.
Homework
Log issues and fixes.
Deliverable
Working database and application first version.
Weekly checkpoint
Show a working add/search/report flow.
You will be able to
Plan, build, test, document and present a practical application project. Connect Python to MySQL to build a small data application with reports. Write Python programs with functions, collections, files, exceptions and tests, and automate a routine office task.

Week 47: Project: testing, documents and report

Theory
  • Test plan execution, bug fixing
  • User guide and technical notes
  • Management report and presentation in Word and PowerPoint
Lab
Run all tests, fix bugs, write a user guide and prepare a short management report and deck with charts from your data.
Homework
Prepare a demo script.
Deliverable
Tested project, user guide and report deck.
Weekly checkpoint
Peer test: another learner follows the guide and reports problems.
You will be able to
Plan, build, test, document and present a practical application project. Manage files, email and Google Workspace and produce professional Word documents, including long documents and mail merge. Prepare a clear PowerPoint presentation and a short written office report from data. Use AI tools to draft, explain and review code and documents, then verify the output and protect private data.

Week 48: Project: demonstration and portfolio

Theory
  • Final corrections
  • Presenting and answering questions
  • Portfolio: code, SQL, documents and a README
Lab
Present the project in 10 minutes and submit the portfolio folder with code, scripts, documents and a one-page summary.
Homework
Prepare answers to likely questions.
Deliverable
Final project, presentation and portfolio.
Weekly checkpoint
Panel viva and rubric scoring.
You will be able to
Plan, build, test, document and present a practical application project. Use AI tools to draft, explain and review code and documents, then verify the output and protect private data.

Sample lessons

Week 13

C loops and the trace table

A loop repeats a block of statements while a condition stays true. A for loop packs three things in one line: the start value, the condition to continue and the change after each round. To understand any loop, write a trace table with one row per round and one column per variable. If you can fill the table by hand, you understand the program and can find its bugs.

Roundisum
111
223
336
4410
Fill the table round by round to understand a loop.

Step by step

  1. Write the problem: add the numbers 1 to 4.
  2. Declare sum = 0 before the loop and write for(i = 1; i <= 4; i++) sum = sum + i;.
  3. Draw a trace table with columns i and sum.
  4. Fill each round: i=1 sum=1, i=2 sum=3, i=3 sum=6, i=4 sum=10.
  5. Check the stop: when i becomes 5 the condition is false, so the loop ends and sum is 10.

In real life

A shop counter program adds the price of each item entered until the billing is over. The same loop idea repeats for every item.

Worked example

Problem. What does this print? int i, s = 0; for (i = 2; i <= 10; i += 2) s += i; printf("%d", s);

Solution. Rounds: i=2, 4, 6, 8, 10 give s = 2, 6, 12, 20, 30. The program prints 30.

Common mistakes

  • Forgetting to set sum = 0 before the loop.
  • Using <= when < is needed, giving one round too many.
  • Changing the loop variable inside the body by mistake.

Try it yourself

  • Trace a loop that prints the multiplication table of 5.
  • Write a loop that adds the digits of 4,827.

Week 41

SQL joins: combining tables correctly

Good databases keep each fact in one table, so a question usually needs data from two tables. A join matches rows using a key. INNER JOIN keeps only rows that have a match on both sides. LEFT JOIN keeps every row from the left table and fills the right side with NULL when there is no match, which is how you find customers who have never ordered. Choosing the wrong join silently changes the result.

INNER JOIN

  • Only matching rows
  • Unmatched rows are dropped

LEFT JOIN

  • All rows from the left table
  • NULL where nothing matches

Step by step

  1. Identify the two tables and the matching columns, for example students.id and enrolments.student_id.
  2. Write SELECT s.name, e.course_id FROM students s INNER JOIN enrolments e ON s.id = e.student_id;.
  3. Run it and count the rows returned.
  4. Change to LEFT JOIN and look at rows where e.course_id is NULL.
  5. Add WHERE e.student_id IS NULL to list students with no enrolment.

In real life

A coaching institute wants a list of students who joined but have not enrolled in any course yet, so the counsellor can call them.

Worked example

Problem. Table students has 5 rows. Table enrolments has rows for 3 of those students. How many rows does an INNER JOIN return if each enrolled student has exactly one enrolment, and how many does a LEFT JOIN return?

Solution. INNER JOIN returns 3 rows (only matches). LEFT JOIN returns 5 rows; the 2 students without enrolment show NULL on the enrolment side.

Common mistakes

  • Joining without an ON condition, producing every combination.
  • Using INNER JOIN and wondering where unmatched rows went.
  • Putting a filter on the right table in WHERE, which turns a LEFT JOIN into an INNER JOIN.

Try it yourself

  • Write a query listing courses that have no students.
  • Count enrolments per student, including students with zero.

Try the questions

The same skills are asked at three levels: School (Classes 6–12), College and Professional. Switch the level and the language (English or Tamil), and say how sure you are before you check: knowing what you are unsure about is part of learning.

Classes 6–12: everyday examples, no prior knowledge. Practice only. Nothing here is graded or saved.

Question 1 / 4 · Order the steps of an algorithm

Arrange the steps to find the largest of three numbers.

  1. 1Read 3 numbers
  2. 2Keep first as largest
  3. 3Compare with 2nd
  4. 4Compare with 3rd
  5. 5Show largest
  1. Compare it with the second number and keep the bigger one
  2. Assume the first number is the largest
  3. Read the three numbers
  4. Compare the result with the third number and keep the bigger one
  5. Show the largest number
How sure are you?

Projects

Coaching Institute Admissions and Fees Manager

A small institute tracks enquiries, admissions and fee instalments in scattered Excel files. Design a normalised MySQL database, write a Python console application to add students, record payments and search records, and produce monthly reports for the manager as an Excel file and a short Word summary.

Tasks

  1. Draw the ER diagram and create at least five tables (students, courses, batches, enrolments, payments) with keys and constraints.
  2. Load 50 students and 80 payments of sample data using SQL scripts.
  3. Write the Python application with menus, input validation and parameterised queries.
  4. Create three SQL views: fee due per student, collection per month, enquiries not yet enrolled.
  5. Export a monthly report to Excel with a pivot or chart and write a one-page Word summary.
  6. Write 15 test cases and keep an AI-use log noting every AI suggestion you changed.

Sample input

Student: Karthik, Madurai, enquiry 3 June; course: Python, fee 12,000, three instalments of 4,000; payment of 4,000 on 10 June.

Expected output

Application records admission and payments; the fee-due view shows 8,000 for Karthik; the monthly report shows June collection with a chart; test table shows all cases passed or listed bugs.

How it is assessed

CriterionWeight
Database design and normalisation20%
Application correctness and validation25%
SQL queries and views15%
Reports, documents and presentation15%
Testing and debugging evidence15%
AI checking and documentation10%

Stretch challenge: Add a GST-ready invoice number and a simple role-based login.

C Billing and Record Program

Write a menu-driven C program for a small shop that stores items in a struct array, bills a customer with 18% GST, and saves daily sales to a text file. The program must handle invalid input and missing files without crashing.

Tasks

  1. Design the menu and functions on paper first.
  2. Implement add item, list items, and search by code.
  3. Implement billing with quantity, GST and a total.
  4. Save and load items from a file.
  5. Create a table of at least 12 test cases covering valid, boundary and invalid inputs.

Sample input

Item 101 Notebook 40 rupees; customer buys 3. GST 18%.

Expected output

Bill shows subtotal 120.00, GST 21.60, total 141.60 and the file contains the saved sale.

How it is assessed

CriterionWeight
Correct output and calculations35%
Program structure and functions25%
Input handling and file safety20%
Test cases and notes20%

Stretch challenge: Add sorting by price and a daily total report.

How you are assessed

Each week: a lab task (an Office file, a program, a SQL script or an application feature) submitted with a proper name, five checkpoint questions including a code-reading or file-based item, and a short note about one bug or mistake you fixed.

Practical work. Assessed through real artefacts: Word and Excel reports, C and Python programs with test tables, a SQL script and database, the elective mini project (C++ or TallyPrime) and an application project with documents. The trainer runs the code, opens the files and asks the learner to explain and modify them.

What trainers look forWeight
Working, correct output and files35%
Code or document quality and structure20%
Testing, debugging and data accuracy20%
Documentation and presentation10%
AI checking and responsible use15%

Where this can lead

  • Prepares you for junior programmer, data-entry-and-reporting and database support tasks.
  • Prepares you for accounting-software operation if you take the TallyPrime elective, and for advanced programming or data courses.

These describe skills you will build. ADIVAS does not guarantee jobs, placement or salary.