DiplomaIntermediate

DIT - Diploma in Information Technology

Computing fundamentals, programming, databases, networking, cloud awareness, digital security and an applied IT project.

Talk to a counsellor about DIT - Diploma in Information Technology

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

What you will cover
  • Computing fundamentals
  • programming
  • databases
  • networking
  • cloud awareness
  • digital security
  • an applied IT 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 8 stations. Each week builds one skill you can show, not just a topic you have heard.

  1. Computing fundamentals

    Understand computers, data and operating systems and maintain a PC.

    • Week 1 Inside a computer system
    • Week 2 Number systems and data representation
    • Week 3 Operating systems: Windows and Linux
    • Week 4 Files, storage and backup
    • Week 5 Assembling a PC and peripherals
    • Week 6 Troubleshooting and maintenance
  2. Office productivity and safe digital work

    Use office tools, email and AI with safety and checking.

    • Week 7 Word processing for work
    • Week 8 Excel for data and decisions
    • Week 9 Presentations and professional email
    • Week 10 Online safety and AI tools with checks
  3. Programming with Python

    Solve problems with algorithms and write structured Python programs.

    • Week 11 Algorithms and flowcharts
    • Week 12 Python basics: variables and input
    • Week 13 Python: making decisions
    • Week 14 Python: loops
    • Week 15 Python: strings
    • Week 16 Python: lists and tuples
    • Week 17 Python: dictionaries and sets
    • Week 18 Python: functions and modules
    • Week 19 Python: files and CSV
    • Week 20 Python: errors and debugging
    • Week 21 Python: classes and objects
    • Week 22 Python testing and mini-project
  4. Databases and SQL

    Design relational databases and query them.

    • Week 23 Data and relational databases
    • Week 24 Relational design and normalisation
    • Week 25 SQL: creating tables
    • Week 26 SQL: inserting and changing data
    • Week 27 SQL: SELECT, WHERE and ORDER BY
    • Week 28 SQL: aggregates and grouping
    • Week 29 SQL: joins and subqueries
    • Week 30 Database project with Python
  5. Web development basics

    Build and publish a responsive site.

    • Week 31 How the web works and HTML
    • Week 32 HTML forms and tables
    • Week 33 CSS fundamentals
    • Week 34 CSS layout and responsive design
    • Week 35 JavaScript and the DOM
    • Week 36 Validation, publishing and web basics review
  6. Networking

    Understand and troubleshoot small networks.

    • Week 37 Network concepts and models
    • Week 38 IP addressing and subnets
    • Week 39 LAN devices and cabling
    • Week 40 Network services and tools
    • Week 41 Network troubleshooting and documentation
  7. Cloud and security

    Choose cloud services and protect systems and data.

    • Week 42 Cloud awareness
    • Week 43 Digital security fundamentals
    • Week 44 Privacy, policy and security practice
  8. Applied IT project

    Deliver an integrated project.

    • Week 45 Project: requirements and design
    • Week 46 Project: build the data and logic
    • Week 47 Project: build the interface and test
    • Week 48 Project: documentation, demo and review
  9. Clinic or Coaching Centre Appointment and Fee System

    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

  • Explain hardware, number systems, operating systems and file storage, and assemble and maintain a basic computer.
  • Use office tools and email productively and safely, including checked AI assistance.
  • Design algorithms and flowcharts and write, test and debug Python programs using functions, collections, files and classes.
  • Design a relational database and write SQL queries with joins, grouping and constraints.
  • Build and publish a responsive web page with HTML, CSS and JavaScript.
  • Explain how networks work, plan an IP scheme and troubleshoot common connectivity problems.
  • Describe cloud service models and choose suitable options for a small organisation.
  • Identify common security threats and apply authentication, encryption, backup and privacy practices.
  • Plan, build, test, document and present an applied IT project in a team or individually.

Who it suits

  • School Students in Classes 11-12 who want a broad, structured foundation in IT before college.
  • College College students and fresh graduates who want a practical IT base covering programming, databases, web and networking.
  • Professional Career changers, office staff and small-business owners moving toward IT support, web or data-handling roles.

Prerequisites: Basic reading and arithmetic. Comfort with using a computer is helpful, but the course starts from fundamentals. Tools: Windows and a Linux distribution (Ubuntu or similar, via dual boot or virtual machine), Python 3 with VS Code or Thonny, SQLite with DB Browser and MySQL or PostgreSQL for server practice, A browser with developer tools and a text editor for HTML, CSS and JavaScript, Cisco Packet Tracer or GNS3 or a similar network simulator, Git and a free GitHub account, LibreOffice or Microsoft Office.

Weekly plan

Computing fundamentals Weeks 1–6

Week 1: Inside a computer system

Theory
  • Input, processing, output, storage
  • CPU, RAM, storage, motherboard and ports
  • Software types: system, application, utility
Lab
Open a desktop PC with a trainer, identify the parts, record the specification in a table and compare it with a laptop and a phone.
Homework
Write a one-page comparison of a phone and a desktop PC.
Deliverable
A labelled hardware sheet and specification table.
Weekly checkpoint
Match components to functions; read a spec sheet.
You will be able to
Explain hardware, number systems, operating systems and file storage, and assemble and maintain a basic computer.

Week 2: Number systems and data representation

Theory
  • Binary, decimal, octal, hexadecimal
  • Bits, bytes, ASCII and Unicode (including Tamil)
  • How images and sound become numbers
Lab
Convert 20 numbers between binary, decimal and hexadecimal by hand, check them with a calculator tool and encode your name in ASCII.
Homework
Estimate storage for 500 photos at 3 MB and a 2-minute song.
Deliverable
A conversion worksheet with storage estimates.
Weekly checkpoint
Conversion and storage calculation problems.
You will be able to
Explain hardware, number systems, operating systems and file storage, and assemble and maintain a basic computer.

Week 3: Operating systems: Windows and Linux

Theory
  • Roles of an OS: process, memory, file and device management
  • Windows tools: settings, task manager, users
  • Linux basics: terminal, ls, cd, mkdir, cp, mv, permissions
Lab
Boot a Linux virtual machine, create a user, navigate the file system, create and move files with commands and monitor running processes in Windows Task Manager.
Homework
Write a table of five tasks done in the Windows interface and the Linux terminal.
Deliverable
A command log and OS comparison table.
Weekly checkpoint
Practical: file tasks using terminal commands.
You will be able to
Explain hardware, number systems, operating systems and file storage, and assemble and maintain a basic computer.

Week 4: Files, storage and backup

Theory
  • File systems, paths and extensions
  • HDD, SSD, USB and cloud storage
  • Backup types: full, incremental; the 3-2-1 idea
Lab
Partition a virtual disk, create a folder structure, back up a project folder to two locations and restore a file after deleting it.
Homework
Design a backup plan for a small clinic with times and locations.
Deliverable
A backup plan and a tested restore.
Weekly checkpoint
Scenario questions on backup choices; a hands-on restore.
You will be able to
Explain hardware, number systems, operating systems and file storage, and assemble and maintain a basic computer.

Week 5: Assembling a PC and peripherals

Theory
  • Safe handling and tools
  • Installing CPU, RAM, storage and power supply
  • Printers, scanners and drivers
Lab
Assemble and disassemble a training PC following a checklist, install an OS from a bootable USB and install a printer driver.
Homework
Create a parts list with prices for a Rs 35,000 office PC using current shop listings.
Deliverable
A completed assembly checklist and a costed parts list.
Weekly checkpoint
Sequence the assembly steps; a hands-on assembly check.
You will be able to
Explain hardware, number systems, operating systems and file storage, and assemble and maintain a basic computer.

Week 6: Troubleshooting and maintenance

Theory
  • Systematic fault finding
  • Common faults: no display, no boot, slow system
  • Preventive maintenance: updates, antivirus, cleaning
Lab
Diagnose six planted faults on lab PCs using a flowchart and record the symptom, cause, fix and test for each.
Homework
Write a first-aid guide for a shop owner whose PC will not start.
Deliverable
A fault log with six entries.
Weekly checkpoint
Troubleshooting scenarios with decision steps.
You will be able to
Explain hardware, number systems, operating systems and file storage, and assemble and maintain a basic computer.
Office productivity and safe digital work Weeks 7–10

Week 7: Word processing for work

Theory
  • Styles, headings, sections and table of contents
  • Tables, headers, footers and mail merge
  • Templates, track changes and PDF export
Lab
Write a six-page report with a table of contents and a mail merge of 15 letters from an Excel list.
Homework
Prepare a one-page company profile using only styles.
Deliverable
A formatted report and merged letters.
Weekly checkpoint
Timed document fix and a mail merge check.
You will be able to
Use office tools and email productively and safely, including checked AI assistance.

Week 8: Excel for data and decisions

Theory
  • Formulas, absolute references, IF, SUMIF, lookup
  • Sort, filter, tables and PivotTables
  • Charts and clear data stories
Lab
Analyse 150 rows of shop sales with formulas, a PivotTable and two charts and write three insights in plain language.
Homework
Find a spreadsheet error in a supplied file and explain the fix.
Deliverable
An analysis workbook with insights.
Weekly checkpoint
Practical data-analysis task on a supplied file.
You will be able to
Use office tools and email productively and safely, including checked AI assistance.

Week 9: Presentations and professional email

Theory
  • Storyline, slide design and delivery
  • Email tone, attachments, Cc and Bcc
  • Meeting etiquette and file naming
Lab
Create and deliver a five-minute presentation on a local IT topic and send a professional email with the deck attached.
Homework
Rewrite a rude email politely.
Deliverable
A presentation and a professional email.
Weekly checkpoint
Peer scoring using a rubric.
You will be able to
Use office tools and email productively and safely, including checked AI assistance.

Week 10: Online safety and AI tools with checks

Theory
  • Passwords, two-step verification, phishing and UPI fraud
  • AI assistants: prompting, limits and hallucinations
  • Verification, privacy and acknowledging AI help
Lab
Review six suspicious messages, enable two-step verification on a practice account and use an AI assistant for a draft and an explanation; verify and log corrections.
Homework
Write a one-page personal safe-use guide.
Deliverable
A scam checklist and an AI check log.
Weekly checkpoint
Scenario questions on scams and AI errors.
You will be able to
Use office tools and email productively and safely, including checked AI assistance.
Programming with Python Weeks 11–22

Week 11: Algorithms and flowcharts

Theory
  • Defining a problem, inputs, outputs and steps
  • Flowchart symbols and pseudocode
  • Tracing an algorithm by hand
Lab
Write algorithms and flowcharts for finding the largest of three numbers, a bill with discount and an ATM withdrawal check; trace each with two inputs.
Homework
Create a flowchart for a daily routine decision.
Deliverable
A flowchart workbook with traces.
Weekly checkpoint
Trace-the-flowchart questions.
You will be able to
Design algorithms and flowcharts and write, test and debug Python programs using functions, collections, files and classes.

Week 12: Python basics: variables and input

Theory
  • Installing Python and running scripts
  • Variables, data types and operators
  • input, print and f-strings
Lab
Write programs for simple interest, area of a circle, converting rupees to dollars using a rate input and a formatted bill line.
Homework
Fix three type errors in supplied code.
Deliverable
Five working scripts.
Weekly checkpoint
Predict the output of six short programs.
You will be able to
Design algorithms and flowcharts and write, test and debug Python programs using functions, collections, files and classes.

Week 13: Python: making decisions

Theory
  • if, elif and else
  • Comparison and logical operators
  • Nested decisions and boundary cases
Lab
Write programs for grades, leap year, eligibility for a bus pass and a simple electricity bill by slabs; build a test table of boundary values for each.
Homework
Write boundary tests for a fee-concession rule.
Deliverable
Four programs and test tables.
Weekly checkpoint
Debug a decision program with a boundary error.
You will be able to
Design algorithms and flowcharts and write, test and debug Python programs using functions, collections, files and classes.

Week 14: Python: loops

Theory
  • for and while loops, range
  • Accumulators and counters
  • break, continue and nested loops
Lab
Write programs for a multiplication table, factorial, prime numbers up to 50, a number guessing game and a pattern.
Homework
Trace a nested loop on paper.
Deliverable
Five loop programs and a trace sheet.
Weekly checkpoint
Timed coding: two loop problems.
You will be able to
Design algorithms and flowcharts and write, test and debug Python programs using functions, collections, files and classes.

Week 15: Python: strings

Theory
  • Indexing, slicing and string methods
  • Searching, splitting and joining
  • Simple text processing
Lab
Write programs to count vowels, check palindromes, format names and clean a messy list of phone numbers.
Homework
Write a program to validate an email-like string.
Deliverable
A string utilities file.
Weekly checkpoint
Code-reading questions on slicing.
You will be able to
Design algorithms and flowcharts and write, test and debug Python programs using functions, collections, files and classes.

Week 16: Python: lists and tuples

Theory
  • Creating, indexing and slicing lists
  • List methods and loops over lists
  • Tuples and list comprehensions
Lab
Build a marks analyser: read marks, find total, average, highest and the students above average; sort and search.
Homework
Rewrite a loop as a comprehension.
Deliverable
A marks analyser program.
Weekly checkpoint
Predict list-method outputs.
You will be able to
Design algorithms and flowcharts and write, test and debug Python programs using functions, collections, files and classes.

Week 17: Python: dictionaries and sets

Theory
  • Key-value data
  • Counting with dictionaries
  • Sets for uniqueness
Lab
Build a word-frequency counter, a product price lookup and a duplicate remover for email lists.
Homework
Model a small inventory as a dictionary.
Deliverable
Three dictionary or set programs.
Weekly checkpoint
Choose the right collection for four scenarios.
You will be able to
Design algorithms and flowcharts and write, test and debug Python programs using functions, collections, files and classes.

Week 18: Python: functions and modules

Theory
  • Defining functions and returning values
  • Parameters, defaults and scope
  • Using the standard library and your own modules
Lab
Refactor the marks analyser into functions in a module and write five test calls for each function.
Homework
Write a function with a default parameter for GST.
Deliverable
A modular program with test calls.
Weekly checkpoint
Practical: write a function from a description.
You will be able to
Design algorithms and flowcharts and write, test and debug Python programs using functions, collections, files and classes.

Week 19: Python: files and CSV

Theory
  • Reading and writing text files
  • CSV files and the csv module
  • Paths and file errors
Lab
Read a CSV of 50 student records, calculate totals, write a summary file and handle a missing file gracefully.
Homework
Create a CSV of your monthly expenses and total it with Python.
Deliverable
A program that reads and writes CSV files.
Weekly checkpoint
File handling questions and a hands-on read/write task.
You will be able to
Design algorithms and flowcharts and write, test and debug Python programs using functions, collections, files and classes.

Week 20: Python: errors and debugging

Theory
  • Syntax, runtime and logic errors
  • try, except and input validation
  • Debugging with prints and a debugger
Lab
Debug five faulty programs, add input validation to the bill program and keep a bug diary with cause and fix.
Homework
Collect five error messages with plain-language meanings.
Deliverable
A bug diary and a validated program.
Weekly checkpoint
Find and fix bugs in a supplied program.
You will be able to
Design algorithms and flowcharts and write, test and debug Python programs using functions, collections, files and classes.

Week 21: Python: classes and objects

Theory
  • Classes, objects and attributes
  • Methods and __init__
  • Modelling a small real system
Lab
Create Student and Course classes with methods for enrolling and showing a fee statement.
Homework
Draw the classes and their attributes for a library.
Deliverable
A class-based program with a diagram.
Weekly checkpoint
Predict outputs for class code.
You will be able to
Design algorithms and flowcharts and write, test and debug Python programs using functions, collections, files and classes.

Week 22: Python testing and mini-project

Theory
  • Writing test cases and simple unit tests
  • Planning a small command-line project
  • Reading code written by others
Lab
Build a small inventory or fee-register program with a menu, file storage and at least eight test cases; peer-review another project.
Homework
Fix the issues raised in the review.
Deliverable
A tested command-line application.
Weekly checkpoint
Demo and viva on the mini-project.
You will be able to
Design algorithms and flowcharts and write, test and debug Python programs using functions, collections, files and classes.
Databases and SQL Weeks 23–30

Week 23: Data and relational databases

Theory
  • Data, information and database types
  • Tables, rows, columns and keys
  • Entity-relationship diagrams
Lab
Draw an ER diagram for a library and a tuition centre, identifying entities, attributes and relationships.
Homework
Find three databases you use daily and describe what they store.
Deliverable
Two ER diagrams.
Weekly checkpoint
Match database terms; read an ER diagram.
You will be able to
Design a relational database and write SQL queries with joins, grouping and constraints.

Week 24: Relational design and normalisation

Theory
  • Primary, foreign and unique keys
  • Redundancy and anomalies
  • First, second and third normal form with examples
Lab
Take a messy order sheet in one table and split it into normalised tables, showing the keys and an example record.
Homework
Normalise a hospital appointment list.
Deliverable
A normalised design with justification.
Weekly checkpoint
Identify a normal form violation in a sample table.
You will be able to
Design a relational database and write SQL queries with joins, grouping and constraints.

Week 25: SQL: creating tables

Theory
  • Data types and constraints
  • CREATE, ALTER and DROP
  • Setting up SQLite and a server database
Lab
Create the library database with correct types, primary and foreign keys and NOT NULL and CHECK constraints.
Homework
Write the SQL for a student-course design.
Deliverable
A SQL script that builds the database.
Weekly checkpoint
Fix a faulty CREATE TABLE statement.
You will be able to
Design a relational database and write SQL queries with joins, grouping and constraints.

Week 26: SQL: inserting and changing data

Theory
  • INSERT, UPDATE and DELETE
  • Transactions: commit and rollback
  • Constraints in action and error messages
Lab
Insert 30 records, update and delete with conditions, trigger and read constraint errors and use a transaction to rollback a bad update.
Homework
Explain why UPDATE without WHERE is dangerous.
Deliverable
A data script and an error log.
Weekly checkpoint
Hands-on data change task with a rollback.
You will be able to
Design a relational database and write SQL queries with joins, grouping and constraints.

Week 27: SQL: SELECT, WHERE and ORDER BY

Theory
  • SELECT, DISTINCT and aliases
  • WHERE with AND, OR, IN, LIKE and BETWEEN
  • ORDER BY and LIMIT
Lab
Write twenty queries on a shop dataset, from simple filters to pattern searches and top-N lists.
Homework
Write five questions a manager may ask and the queries.
Deliverable
A queries file with outputs.
Weekly checkpoint
Write six queries from described questions.
You will be able to
Design a relational database and write SQL queries with joins, grouping and constraints.

Week 28: SQL: aggregates and grouping

Theory
  • COUNT, SUM, AVG, MIN, MAX
  • GROUP BY and HAVING
  • NULL handling
Lab
Compute sales by product, by month and customers with more than three orders; check every result against a manual total.
Homework
Explain the difference between WHERE and HAVING with an example.
Deliverable
A report query set with verification notes.
Weekly checkpoint
Predict the result of grouped queries.
You will be able to
Design a relational database and write SQL queries with joins, grouping and constraints.

Week 29: SQL: joins and subqueries

Theory
  • INNER, LEFT and self joins
  • Subqueries and IN or EXISTS
  • Checking row counts after a join
Lab
Answer ten business questions that need joins, including customers with no orders and orders above the average.
Homework
Find and fix a join that duplicates rows.
Deliverable
Ten join queries with explanations.
Weekly checkpoint
Join and subquery problem set.
You will be able to
Design a relational database and write SQL queries with joins, grouping and constraints.

Week 30: Database project with Python

Theory
  • Connecting Python to SQLite
  • Parameterised queries and SQL injection basics
  • Backup, export and import
Lab
Build a command-line fee or library system that stores data in SQLite using parameterised queries and exports a report to CSV.
Homework
Test an injection example on a vulnerable and a safe version.
Deliverable
A database-backed Python application.
Weekly checkpoint
Code review of queries; demo.
You will be able to
Design a relational database and write SQL queries with joins, grouping and constraints.
Web development basics Weeks 31–36

Week 31: How the web works and HTML

Theory
  • Client, server, URL, HTTP request and response
  • HTML document structure, headings, paragraphs, lists, links, images
  • Semantic tags
Lab
Build a four-page personal or business site in HTML with links, images and semantic structure, then inspect requests in the browser developer tools.
Homework
Sketch a sitemap for a local shop.
Deliverable
A multi-page HTML site.
Weekly checkpoint
Identify HTML errors; request/response questions.
You will be able to
Build and publish a responsive web page with HTML, CSS and JavaScript.

Week 32: HTML forms and tables

Theory
  • Forms and input types
  • Tables for data
  • Accessibility: alt text, labels, headings
Lab
Create an admission enquiry form and a fee table, label every field and check the page with a keyboard only.
Homework
Run an accessibility checker and fix three issues.
Deliverable
An accessible form page.
Weekly checkpoint
Spot form accessibility problems.
You will be able to
Build and publish a responsive web page with HTML, CSS and JavaScript.

Week 33: CSS fundamentals

Theory
  • Selectors, colours, fonts
  • Box model: margin, border, padding
  • Specificity and organising styles
Lab
Style the site with one stylesheet, a colour theme and consistent spacing and fix a conflict caused by specificity.
Homework
Reproduce a simple card design from a screenshot.
Deliverable
A styled site with one stylesheet.
Weekly checkpoint
Box-model calculation and selector questions.
You will be able to
Build and publish a responsive web page with HTML, CSS and JavaScript.

Week 34: CSS layout and responsive design

Theory
  • Flexbox and grid basics
  • Media queries and mobile-first thinking
  • Images, fonts and performance
Lab
Make the site responsive for phone, tablet and desktop widths using flexbox and one media query and test in the browser device mode.
Homework
List three changes that help a page load faster on mobile data.
Deliverable
A responsive layout tested at three widths.
Weekly checkpoint
Practical: fix a broken layout at a narrow width.
You will be able to
Build and publish a responsive web page with HTML, CSS and JavaScript.

Week 35: JavaScript and the DOM

Theory
  • Variables, functions, events
  • Selecting and changing page elements
  • A simple interactive feature
Lab
Add a fee calculator and a show or hide menu to the site using JavaScript and handle an empty input gracefully.
Homework
Trace what happens when a button is clicked.
Deliverable
An interactive page with a calculator.
Weekly checkpoint
Predict outcomes of short script snippets.
You will be able to
Build and publish a responsive web page with HTML, CSS and JavaScript.

Week 36: Validation, publishing and web basics review

Theory
  • Client-side validation and its limits
  • Publishing a static site with Git hosting
  • Web accessibility and privacy basics
Lab
Add validation to the enquiry form, publish the site on a free static host and test it on a phone.
Homework
Write a short launch checklist.
Deliverable
A published site link and a launch checklist.
Weekly checkpoint
Web module test with a hands-on fix.
You will be able to
Build and publish a responsive web page with HTML, CSS and JavaScript.
Networking Weeks 37–41

Week 37: Network concepts and models

Theory
  • LAN, WAN and the internet
  • TCP/IP and OSI layers in simple terms
  • Client-server and peer-to-peer
Lab
Map the home or lab network, label each device and trace what happens when a web page is opened using the layers.
Homework
Draw the network of your college or shop.
Deliverable
A labelled network diagram with a layer trace.
Weekly checkpoint
Match layers to protocols.
You will be able to
Explain how networks work, plan an IP scheme and troubleshoot common connectivity problems.

Week 38: IP addressing and subnets

Theory
  • IPv4 addresses, masks, private and public ranges
  • Subnetting basics with simple examples
  • Introduction to IPv6
Lab
Plan an IP scheme for an office with three departments using a private range, with network, host range and broadcast address for each subnet.
Homework
Check three addresses to say whether they are in the same network.
Deliverable
An IP plan table.
Weekly checkpoint
Subnet calculation problems.
You will be able to
Explain how networks work, plan an IP scheme and troubleshoot common connectivity problems.

Week 39: LAN devices and cabling

Theory
  • Switch, router, access point and modem roles
  • Ethernet cabling and crimping basics
  • Wi-Fi channels and placement
Lab
Build a small LAN in a network simulator with a switch, router and two departments and make a straight-through cable and test it.
Homework
Recommend devices for a ten-computer office.
Deliverable
A working simulator topology and a tested cable.
Weekly checkpoint
Choose devices for scenarios; hands-on cable test.
You will be able to
Explain how networks work, plan an IP scheme and troubleshoot common connectivity problems.

Week 40: Network services and tools

Theory
  • DNS, DHCP and NAT
  • HTTP, HTTPS, FTP and SMTP in everyday use
  • ping, traceroute, ipconfig/ip, nslookup
Lab
Configure DHCP in the simulator, use ping and traceroute to test connectivity and use nslookup to see a DNS answer on the lab network.
Homework
Explain to a friend what DNS does using a phone book idea.
Deliverable
A tool-output log with explanations.
Weekly checkpoint
Interpret tool outputs.
You will be able to
Explain how networks work, plan an IP scheme and troubleshoot common connectivity problems.

Week 41: Network troubleshooting and documentation

Theory
  • Layered troubleshooting method
  • Common faults: wrong IP, cable, DNS, gateway
  • Network documentation and change records
Lab
Fix five planted faults in the simulator or lab, record each in a ticket with symptom, steps and fix and write a network document.
Homework
Create a one-page checklist for "no internet" calls.
Deliverable
Five fault tickets and a network document.
Weekly checkpoint
Networking module test with troubleshooting scenarios.
You will be able to
Explain how networks work, plan an IP scheme and troubleshoot common connectivity problems.
Cloud and security Weeks 42–44

Week 42: Cloud awareness

Theory
  • IaaS, PaaS, SaaS and public/private cloud
  • Storage, compute and cost ideas
  • Choosing cloud for a small business
Lab
Compare two free cloud storage or hosting options for a small shop, list features, costs and risks and recommend one with reasons; deploy a small file share.
Homework
List five cloud services you already use.
Deliverable
A comparison and recommendation note.
Weekly checkpoint
Match cloud models to examples and scenarios.
You will be able to
Describe cloud service models and choose suitable options for a small organisation. Identify common security threats and apply authentication, encryption, backup and privacy practices.

Week 43: Digital security fundamentals

Theory
  • Threats: malware, phishing, ransomware, social engineering
  • Authentication, access control and encryption basics
  • Updates, firewalls and backups
Lab
Audit a lab computer against a security checklist, enable a firewall, set up user permissions and encrypt a test file.
Homework
Write the steps to recover from ransomware using backups.
Deliverable
A completed security audit.
Weekly checkpoint
Scenario questions on threats and controls.
You will be able to
Describe cloud service models and choose suitable options for a small organisation. Identify common security threats and apply authentication, encryption, backup and privacy practices.

Week 44: Privacy, policy and security practice

Theory
  • Personal data and consent in simple terms
  • Acceptable use and incident reporting
  • Security awareness for staff
Lab
Write a one-page security and privacy policy for a small clinic, run a mock incident drill and record lessons.
Homework
Teach three security habits to a family member.
Deliverable
A short policy and incident report.
Weekly checkpoint
Policy scenario questions; security module test.
You will be able to
Describe cloud service models and choose suitable options for a small organisation. Identify common security threats and apply authentication, encryption, backup and privacy practices.
Applied IT project Weeks 45–48

Week 45: Project: requirements and design

Theory
  • Choosing a problem and stakeholders
  • Requirements, use cases and scope
  • Design: data model, screens and network or security needs
Lab
Select a project such as a clinic appointment system or school fee portal, write requirements, design the database and sketch the pages.
Homework
Gather feedback from one real or role-played user.
Deliverable
A project proposal, data model and sketches.
Weekly checkpoint
Design review.
You will be able to
Plan, build, test, document and present an applied IT project in a team or individually.

Week 46: Project: build the data and logic

Theory
  • Implementing the database
  • Python logic for the main features
  • Version control with Git
Lab
Create the database, load sample data and implement the first two features with commits for each step.
Homework
Write test cases for each feature.
Deliverable
A working database and two features in the repository.
Weekly checkpoint
Progress check against the plan.
You will be able to
Plan, build, test, document and present an applied IT project in a team or individually.

Week 47: Project: build the interface and test

Theory
  • Web or command-line interface
  • Test plan and defect log
  • Security and backup checks
Lab
Build the interface, run the test plan, log and fix at least five defects and apply the security checklist.
Homework
Ask a peer to try the system and note problems.
Deliverable
A tested prototype and a defect log.
Weekly checkpoint
Test evidence review.
You will be able to
Plan, build, test, document and present an applied IT project in a team or individually.

Week 48: Project: documentation, demo and review

Theory
  • User guide and technical notes
  • Demo script and presentation
  • Reflection and next steps
Lab
Write the documentation, rehearse and deliver a ten-minute demo, answer questions and complete the final review form.
Homework
Update your resume with the project.
Deliverable
A completed project folder, demo and reflection.
Weekly checkpoint
Final demo scored on the rubric plus viva.
You will be able to
Plan, build, test, document and present an applied IT project in a team or individually.

Sample lessons

Week 38

IP addresses and a simple subnet plan

Every device on a network needs an IP address, which is like a house number inside a street. An IPv4 address has four numbers written with dots, and a subnet mask tells which part names the network (the street) and which part names the host (the house). Private ranges such as 192.168.x.x are used inside offices and homes and are not routed on the internet. Splitting an office network into subnets keeps departments separate and traffic tidy.

SubnetNetworkUsable hostsBroadcast
Accounts192.168.10.0/26.1 to .62.63
Admission192.168.10.64/26.65 to .126.127
Lab192.168.10.128/26.129 to .190.191

Step by step

  1. List the departments and the number of devices in each.
  2. Choose a private range such as 192.168.10.0.
  3. Give each department its own subnet, for example /26 with 62 usable hosts.
  4. Write the network address, first and last usable host and broadcast address for each subnet.
  5. Reserve the first usable address for the gateway.
  6. Test in a simulator that two devices in the same subnet can ping each other.

In real life

A school office has Accounts, Admission and Lab computers. Separate subnets stop the lab traffic from slowing the accounts computers and make faults easier to find.

Worked example

Problem. The network is 192.168.10.0/26. What are the first usable address, last usable address and broadcast?

Solution. A /26 has 64 addresses (0 to 63). Network address: 192.168.10.0. First usable: 192.168.10.1. Last usable: 192.168.10.62. Broadcast: 192.168.10.63. So 62 devices can be assigned.

Common mistakes

  • Assigning the network or broadcast address to a device.
  • Giving two devices the same IP address.
  • Choosing a subnet too small for future growth.

Try it yourself

  • Plan three /26 subnets from 192.168.20.0 and list their ranges.
  • Decide whether 192.168.10.70 and 192.168.10.20 are in the same /26 network.

Week 24

Normalising an order sheet

A single wide table that repeats customer names, addresses and product prices on every row causes problems: the same fact is typed many times, so a change must be made in many places and mistakes creep in. Normalisation splits the data into related tables so that each fact is stored once. Customers, Products, Orders and OrderItems each hold one kind of thing and are linked with keys. The result is smaller, more reliable and easier to query with joins.

  1. 1Customers
  2. 2Orders
  3. 3OrderItems
  4. 4Products

Step by step

  1. Write the original sheet with repeated customer and product details.
  2. Pick a unique key for each kind of thing: CustomerID, ProductID, OrderID.
  3. Move customer details to a Customers table and product details to Products.
  4. Create Orders linked to Customers and OrderItems linked to Orders and Products.
  5. Check that each non-key column depends only on its table's key.
  6. Rebuild the original sheet using a join to confirm nothing is lost.

In real life

A stationery shop keeps one big sheet of sales. After normalising, changing a product price or fixing a customer phone number is done once and every report is correct.

Worked example

Problem. A sheet has OrderID, CustomerName, CustomerPhone, Product, Price, Quantity. Split it.

Solution. Customers(CustomerID, Name, Phone); Products(ProductID, Product, Price); Orders(OrderID, CustomerID, Date); OrderItems(OrderID, ProductID, Quantity). A join on the keys rebuilds the full sheet and the phone number now exists once per customer.

Common mistakes

  • Using a name as a primary key although names can repeat.
  • Keeping the price only in OrderItems so a later price change rewrites history, without noting that history sometimes needs the price at the time of sale.
  • Splitting into too many tables without a clear reason.

Try it yourself

  • Normalise a list of appointments with patient and doctor details.
  • Draw the relationships and mark the keys.

Week 18

Python functions that return values

A function is a named block of code that does one job and can be used again and again. It receives inputs called parameters and gives back a result with return. Splitting a program into functions makes it shorter, easier to test and easier to fix, because each function can be checked by itself. A good function has one clear purpose and a name that says what it does.

  1. 1Inputs (parameters)
  2. 2Function body does one job
  3. 3return gives the result
  4. 4Caller uses the result

Step by step

  1. Choose a job, such as calculating a bill with GST.
  2. Write def bill_total(amount, rate=5): and decide what it must return.
  3. Calculate inside the function and use return to send the result back.
  4. Call the function with sample values and print the result.
  5. Write at least three test calls, including zero and a large amount.
  6. Use the function inside a loop for a list of items.

In real life

A shop program uses one bill_total function for every invoice, so when the rule changes it is updated in one place.

Worked example

Problem. Write a function that returns the amount with 5 percent GST and test it with 200.

Solution. def bill_total(amount, rate=5): return amount + amount * rate / 100 print(bill_total(200)) prints 210.0. Test also bill_total(0) which gives 0.0 and bill_total(200, 12) which gives 224.0.

Common mistakes

  • Printing inside the function instead of returning, so the value cannot be reused.
  • Changing global variables inside a function without meaning to.
  • Forgetting to call the function after defining it.

Try it yourself

  • Write is_even(n) that returns True or False and test with five numbers.
  • Write grade(marks) that returns a letter and test boundary marks.

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 · Understand binary

A computer uses only 0 and 1. Why?

A computer uses only 0 and 1. Why?
How sure are you?

Projects

Clinic or Coaching Centre Appointment and Fee System

A small clinic or coaching centre in Madurai needs a simple system to record people, appointments or fees, search records and produce reports. Design and build a working prototype that uses a relational database, a Python application or web interface, basic network and security thinking, and clear documentation.

Tasks

  1. Write requirements and draw an ER diagram, then normalise the design to third normal form.
  2. Create the database in SQL with keys and constraints and load at least 30 sample records.
  3. Build a Python command-line or simple web interface to add, search and update records using parameterised queries.
  4. Write a test plan with at least ten cases and log and fix defects.
  5. Prepare a short security and backup plan and a network note describing how staff would access the system.
  6. Document the system and give a ten-minute demonstration.

Sample input

Patient Meena books Dr Karthik on 12 Nov 10:30; second booking for the same slot

Expected output

The first booking is saved; the second is rejected with a clear message; a daily report lists appointments by doctor.

How it is assessed

CriterionWeight
Requirements and database design20%
Working features and queries25%
Testing and defect handling15%
Security, backup and network plan15%
Documentation10%
Demo and explanation15%

Stretch challenge: Add a role-based login (reception and doctor) and a monthly summary chart.

Responsive Local Business Website

Build a four-page responsive website for a local business with a contact form, a price table and a simple calculator, published on a free static host and checked for accessibility.

Tasks

  1. Plan the sitemap and wireframes for phone and desktop.
  2. Write semantic HTML and one CSS file with a flexbox or grid layout.
  3. Add JavaScript for a quote calculator with input validation.
  4. Check accessibility and performance and fix the issues found.
  5. Publish the site and write a short maintenance guide.

Sample input

Quote inputs: quantity 3, rate 250, GST 5%

Expected output

The calculator shows 787.50 and shows a clear message for empty or negative input; the site works at phone width.

How it is assessed

CriterionWeight
HTML structure and accessibility25%
Responsive CSS layout25%
JavaScript function and validation25%
Publishing and documentation25%

Stretch challenge: Add a language toggle between Tamil and English text.

How you are assessed

Each week: six questions (knowledge, scenario, and one diagram, code or formula item), a timed hands-on task and a short reflection. Module tests at weeks 6, 22, 30, 36, 41 and 44.

Practical work. Hardware, networking and troubleshooting are assessed on lab tasks and tickets; office work on saved files; Python and SQL on hidden test cases and code reading; web work on a published page; the applied project through a demo and viva.

What trainers look forWeight
Correct, working result30%
Design, logic and quality20%
Testing and troubleshooting15%
Security and safe habits10%
Documentation and file hygiene10%
Explanation and presentation15%

Where this can lead

  • Prepares you for IT support, junior web, data-entry and technical office roles.
  • Gives a broad base to continue into programming, networking, cloud or data courses.

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