Table of Contents

I. Computational Thinking

1.1 Definition

Computational thinking was popularised by Jeannette Wing (2006), who argued that CT is a fundamental skill for everyone, not just computer scientists — comparable to reading, writing and arithmetic. The core insight is that CT is about abstraction and decomposition, not about syntax or a specific programming language.

1.2 The Four Pillars of Computational Thinking

(a) Decomposition

Breaking a large, complex problem into smaller, manageable sub-problems that can be solved independently. Each sub-problem is easier to understand, test and debug.

Example: "Build an e-commerce website" decomposes into user authentication, product catalogue, shopping cart, payment gateway, order tracking and admin dashboard.

(b) Pattern Recognition

Identifying similarities, trends or regularities among problems, data or processes. Recognised patterns allow reuse of previously proven solutions.

Example: Noticing that "search a student by roll number", "search a product by ID" and "search a contact by name" are all the same search pattern.

(c) Abstraction

Filtering out irrelevant detail and keeping only the essential features needed to solve the problem. Abstraction creates models.

Example: A metro rail map is an abstraction — it shows stations and connectivity but ignores real distances, terrain and curves.

(d) Algorithm Design

Developing a precise, finite, step-by-step set of instructions that transforms an input into the desired output. An algorithm must be unambiguous, finite, effective and have well-defined inputs/outputs.

1.3 Characteristics of a Good Algorithm

1.4 Ways of Representing an Algorithm

• Pseudocode — language-independent structured English.
• Flowchart — graphical symbols: oval (start/end), parallelogram (I/O), rectangle (process), diamond (decision), arrow (flow).
• Program code — implementation in C, Python, Java, etc.

Pseudocode conventions used in this course

BEGIN
    READ n
    SET sum ← 0
    FOR i ← 1 TO n DO
        sum ← sum + i
    END FOR
    PRINT sum
END

BEGIN
    READ a, b, c
    IF a ≥ b AND a ≥ c THEN
        PRINT a
    ELSE IF b ≥ a AND b ≥ c THEN
        PRINT b
    ELSE
        PRINT c
    END IF
END

II. Computing Environment & Software Development Practices

2.1 The Computing Environment

2.2 Operating System — Functions

• Process management — scheduling, creation, termination, inter-process communication.
• Memory management — allocation, paging, segmentation, virtual memory.
• File management — creation, deletion, permissions, directories.
• Device management — I/O scheduling, buffering, spooling.
• Security & protection — authentication, access control, isolation.

2.3 Types of Operating Systems

2.4 Software Development Practices & SDLC

The Software Development Life Cycle (SDLC) is the structured process used to plan, build, test, deploy and maintain software.

SDLC Models — Comparison

2.5 Version Control Systems (VCS)

Core Git Terminology

git init                              # create a new local repository
git config --global user.name "Aarav"
git config --global user.email "aarav@example.com"

git status                            # see modified files
git add main.py                       # stage a specific file
git add .                             # stage everything
git commit -m "Add login module"      # snapshot

git branch feature-login              # create branch
git checkout feature-login            # switch to it
git push -u origin feature-login      # publish branch

git checkout main
git merge feature-login               # merge branch into main
git log --oneline --graph             # visualise history

<<<<<<< HEAD
timeout = 30
=======
timeout = 60
>>>>>>> feature-login

III. Cyber Security Basics

3.1 The CIA Triad

Two extended pillars are often added: Authentication (proving identity) and Non-repudiation (inability to deny an action, achieved via digital signatures).

3.2 Security Threats and Malware

Phishing Red Flags — the "5 S" checklist

• Sender — domain misspellings (@paypa1.com).
• Subject — urgency, threats, "account suspended".
• Spelling — grammatical errors and odd formatting.
• Subscription — unexpected attachment or invoice.
• Site — hover over a link before clicking; verify the real URL.

3.3 Firewalls

Firewall Rule Anatomy

ACTION   PROTO   SRC            DST          PORT   COMMENT
ALLOW    TCP     any            10.0.0.5     443    Allow HTTPS to web server
ALLOW    TCP     any            10.0.0.5     22     Allow SSH from admin subnet (restrict!)
DENY     ANY     any            any          any    Default deny (implicit last rule)

The default-deny policy (deny everything not explicitly allowed) is the industry best practice, as opposed to default-allow.

DMZ (Demilitarised Zone)

A sub-network that exposes public-facing services (web, mail, DNS) to the Internet while keeping the internal LAN isolated. Traffic between the DMZ and LAN is filtered by an internal firewall.

3.4 User Account Types and Privileges

Access Control Models

Authentication vs Authorisation

• Authentication — "Who are you?" (password, OTP, fingerprint, smart card).
• Authorisation — "What are you allowed to do?" (permissions, roles, ACLs).
• Accounting / Auditing — "What did you do?" (logs, SIEM).

Together these form the AAA framework.

Multi-Factor Authentication (MFA)

MFA combines factors from different categories:

Using two passwords is not MFA — the factors must be from different categories.

III. Cyber Security Basics (continued)

3.5 Safe Internet Practices

Password Strength

Example: An 8-character password from lowercase letters only: \(26^{8} \approx 2.09\times10^{11}\). A 12-character passphrase mixing upper, lower, digits and symbols (\(C=94\)): \(94^{12}\approx 4.6\times10^{23}\). Length dominates complexity — a longer passphrase is stronger than a short cryptic one.

3.6 Digital Footprint

Why the Digital Footprint Matters

• Permanence: deleted content may persist in caches, archives (Wayback Machine) and screenshots.
• Employability: recruiters routinely screen social profiles; 70%+ report rejecting candidates based on online content.
• Reputation: it forms your online personal brand, whether you manage it or not.
• Security: oversharing (birthdate, pet names, school) fuels social engineering and password guessing.
• Privacy: aggregated passive data enables detailed profiling by advertisers and data brokers.

Managing Your Digital Footprint

1. Audit — Google your own name; review old posts and tagged photos.
2. Prune — delete outdated, offensive or overly personal content.
3. Lock down — set social profiles to private; disable location tagging.
4. Separate — keep a professional identity (LinkedIn, GitHub) distinct from personal social media.
5. Monitor — set Google Alerts for your name; use Have I Been Pwned for breach checks.
6. Build positively — publish technical blogs, projects and certifications to crowd out negative content.

3.7 Cyber Ethics

The Ten Commandments of Computer Ethics (Computer Ethics Institute)

1. Thou shalt not use a computer to harm other people.
2. Thou shalt not interfere with other people's computer work.
3. Thou shalt not snoop around in other people's files.
4. Thou shalt not use a computer to steal.
5. Thou shalt not use a computer to bear false witness.
6. Thou shalt not copy or use proprietary software for which you have not paid.
7. Thou shalt not use other people's computer resources without authorisation.
8. Thou shalt not appropriate other people's intellectual output.
9. Thou shalt think about the social consequences of the program you write.
10. Thou shalt use a computer in ways that show consideration and respect.

Indian Legal Framework (selected)

IV. Introduction to EDU-RevolUTION

4.1 Concept and Vision

Vision: To create a holistic learning ecosystem in which every student graduates with verified technical competency, professional readiness, and a portfolio of real-world achievements — not merely a transcript of marks.

4.2 Objectives

1. Curriculum enrichment — supplement core courses with MOOCs, certifications and industry modules.
2. Flexible credit pathways — allow credits earned through approved platforms (NPTEL, SWAYAM, Coursera, edX) to be transferred into the degree.
3. Industry alignment — bridge the gap between classroom theory and workplace practice.
4. Holistic development — develop communication, leadership, ethics and entrepreneurial thinking alongside technical skill.
5. Learner autonomy — let students choose learning paths aligned to their career aspirations.
6. Continuous assessment — evaluate through projects, tasks and portfolios rather than one-time examinations.
7. Employability enhancement — produce graduates whose profiles are immediately attractive to recruiters.

4.3 Components of the Initiative

4.4 Importance for Student Development

V. AI, ML, Generative AI, Agentic AI & Emerging Technologies

5.1 Artificial Intelligence

Types of AI by Capability

Types of AI by Functionality

• Reactive machines — no memory; respond to current input (Deep Blue).
• Limited memory — use recent past data (self-driving cars, LLM context windows).
• Theory of mind — understand beliefs and emotions of others (research stage).
• Self-aware — conscious of its own existence (hypothetical).

5.2 Machine Learning

Tom Mitchell's formal definition: a computer program is said to learn from experience \(E\) with respect to task \(T\) and performance measure \(P\), if its performance at \(T\), as measured by \(P\), improves with experience \(E\).

Supervised Learning: Regression vs Classification

Deep Learning

Deep Learning uses artificial neural networks with many hidden layers. Each layer learns increasingly abstract features from raw data. It powers computer vision (CNNs), sequence modelling (RNNs, LSTMs) and modern language models (Transformers).

5.3 Generative AI

How an LLM Works (Simplified Pipeline)

1. Tokenisation — text is split into sub-word tokens.
2. Embedding — each token becomes a high-dimensional vector.
3. Self-attention — the model weighs the relevance of every token to every other token.
4. Prediction — the network outputs a probability distribution over the next token.
5. Decoding — a token is sampled (greedy, top-k, temperature) and appended; the loop repeats.

Prompt Engineering Basics

V. AI, ML, Generative AI, Agentic AI & Emerging Technologies (continued)

5.4 Agentic AI

5.5 Emerging Computing Technologies

5.6 Ethics in AI

VI. Career Planning

6.1 What is Career Planning?

It is iterative, not a one-time decision. The five stages are:

1. Self-assessment — interests, strengths, values, personality.
2. Opportunity exploration — roles, industries, cohorts, pathways.
3. Goal setting — SMART short-, medium- and long-term goals.
4. Action planning — Individual Development Plan (IDP).
5. Review & tracking — measure, reflect, adjust.

6.2 Identification of Interests, Strengths and Aspirations

Interests — the RIASEC Model (Holland Codes)

Strengths — SWOT Analysis

Values and Work Preferences

Values determine satisfaction, while skills determine eligibility. Common values: learning, autonomy, compensation, stability, impact, work–life balance, location, team culture.

Career Aspirations

An aspiration is a long-range professional destination, e.g. "become a cloud security architect in a product company within eight years". Aspirations should be decomposed into intermediate milestones.

6.3 Goal Setting — the SMART Framework

Goal Hierarchy

• Long-term (5–10 years): career destination.
• Medium-term (1–3 years): role, certification, degree.
• Short-term (1–6 months): weekly and monthly targets.

6.4 Competency and Skill-Gap Analysis

Steps in Conducting a Skill-Gap Analysis

1. Select a target role and collect 5–10 real job descriptions.
2. Extract the recurring competencies (technical + behavioural).
3. Rate the required level \(R_i\) (1–5) and your current level \(C_i\) (1–5).
4. Assign importance weights \(w_i\) and compute the weighted gap.
5. Prioritise: address highest \(w_i \times \text{Gap}_i\) first.
6. Define a learning action, resource and deadline for each priority gap.
7. Re-assess every quarter.

VI. Career Planning (continued)

6.5 Individual Development Plan (IDP)

Components of an IDP

6.6 Progress Tracking

Worked calculation: For SQL, \(R = 5\), \(C_{start} = 3\), \(C_{now} = 4\). Then

\[ \text{Gap Closure} = \frac{4-3}{5-3}\times 100 = 50\% \]

Half the SQL gap has been closed — measurable evidence of progress for the mentor review.

Tracking Tools and Cadence

6.7 Career Pathways and Cohorts

VII. Professional Readiness

7.1 Meaning of Professional Readiness

It has four dimensions: Technical (domain knowledge), Behavioural (communication, teamwork), Attitudinal (ownership, adaptability, ethics) and Documentary (resume, portfolio, profiles).

7.2 Industry Interaction

• Guest lectures and webinars — expose students to current tools, architectures and expectations.
• Industrial visits — show how processes, teams and infrastructure operate at scale.
• Internships — the single strongest signal on a fresher's CV; convert theory into shipped work.
• Live projects and capstones — real constraints, deadlines and stakeholders.
• Mentorship programmes — personalised guidance from practising engineers.
• Hackathons and coding contests — demonstrate problem-solving under time pressure.

7.3 Alumni Success Stories — Why They Matter

• Provide realistic, achievable role models from a similar starting point.
• Reveal the actual preparation strategy used (not the marketing version).
• Offer insider knowledge about hiring processes and company culture.
• Create referral opportunities through the alumni network.
• Motivate students by demonstrating that the pathway is navigable.

7.4 Study-Abroad Opportunities

7.5 Professional Networking

Networking Channels

• LinkedIn — the primary professional network; optimise headline, About, experience, skills and featured section.
• GitHub — public proof of technical ability; recruiters inspect commit history.
• Technical communities — Stack Overflow, Discord/Slack groups, local user groups.
• Conferences and meetups — conferences, GDG events, college tech fests.
• Alumni network — the highest-response-rate channel for students.
• Faculty and project guides — strong recommendation sources.

7.6 Workplace Communication

The 7 Cs of Effective Communication

Professional Email Structure

Subject: [CSE111] Request for project guide approval — Aarav Sharma, 1210XXXX

Dear Professor Menon,

I am Aarav Sharma (Roll No. 1210XXXX), a third-semester CSE student.
I have drafted a project proposal on "Anomaly Detection in Campus
Network Logs" and would like your guidance.

Attached: proposal.pdf (2 pages).

Could we meet for 15 minutes during your office hours this week?

Thank you for your time.
Regards,
Aarav Sharma
+91-XXXXXXXXXX | aarav@example.com | github.com/aarav

Rules: professional subject line, formal salutation, context in the first two lines, specific ask, attachments named clearly, professional signature block, proofread before sending.

Workplace Communication Channels

VII. Professional Readiness (continued)

7.7 Leadership

Leadership in a student context: leading a hackathon team, coordinating a college fest committee, serving as class representative, or maintaining an open-source project with contributors.

7.8 Interpersonal Skills

Giving Feedback — the SBI Model

Example: "In yesterday's stand-up (Situation), you reported the module as complete when two tests were failing (Behaviour). It delayed integration by a day for the whole team (Impact)." This is specific, non-personal and actionable.

7.9 Career Decision Making

Steps in Structured Career Decision Making

1. Define the decision — e.g. "Which of two job offers should I accept?"
2. Identify criteria — learning, salary, location, brand, role clarity, growth.
3. Assign weights based on personal values.
4. Score each option against each criterion (1–10).
5. Compute weighted totals and rank.
6. Apply intuition as a sanity check, then decide.
7. Commit and review the decision after a defined period.

7.10 Competency Requirements by Role (Indicative)

VIII. Professional Portfolio Development

8.1 Concept of a Professional Portfolio

8.2 Purpose and Importance

8.3 Components of a Professional Portfolio

Portfolio vs Résumé vs CV

Documenting a Project — the STAR-P Template

VIII. Professional Portfolio Development (continued)

8.4 Personal Branding

Elements of a Strong Personal Brand

• Clarity — a one-line positioning statement ("Final-year CSE student specialising in cloud-native backends").
• Consistency — the same headline, photo and description across LinkedIn, GitHub, portfolio and résumé.
• Credibility — evidence in the form of projects, certifications and recommendations.
• Visibility — regular, relevant publishing and engagement.
• Authenticity — do not claim skills you cannot demonstrate.

8.5 LinkedIn Profile Optimisation

8.6 GitHub Profile Optimisation

Sample Repository README Skeleton

# Campus Notice Portal
Real-time notice delivery for university departments.

## Features
- Role-based access (student / faculty / admin)
- Department-wise filtering
- Push notifications in < 5 seconds

## Tech Stack
React 18 · Node.js · Express · MongoDB Atlas · JWT · GitHub Actions

## Setup
git clone https://github.com/<user>/campus-notice-portal
cd campus-notice-portal && npm install
cp .env.example .env      # add MONGODB_URI and JWT_SECRET
npm run dev

## Screenshots
![Dashboard](docs/dashboard.png)

## Licence
MIT

IX. Design Your Dream CV

9.1 Concept of a Dream CV

9.2 Significance

9.3 Standard Structure of a Fresher CV

Action Verbs for Strong Bullet Points

The Bullet-Point Formula

Weak: "Worked on a machine learning project."
Strong: "Trained a Random Forest classifier on 45,000 records to predict student dropout, achieving 92% F1-score and reducing manual review effort by 40%."

IX. Design Your Dream CV (continued)

9.4 Writing Each Section

Career Objective

Formula: [Role] + [Core skills] + [What you offer] + [Goal]

Example: "Final-year Computer Science student with hands-on experience in Python, SQL and cloud deployment, seeking a Data Analyst role where I can apply analytical rigour and data-visualisation skills to drive business decisions."

Education

B.Tech in Computer Science and Engineering           2023 – 2027
Lovely Professional University, Punjab               CGPA: 8.7/10
Relevant coursework: DSA, DBMS, Operating Systems, Computer Networks,
Cyber Security, Machine Learning

Technical Skills

Languages      : Python, Java, C, JavaScript, SQL
Frameworks     : React, Node.js, Express, Flask
Databases      : MySQL, MongoDB, PostgreSQL
Tools & Cloud  : Git, GitHub, Docker, AWS (EC2, S3), Postman, Linux

Rule: list only skills you can defend in a technical interview. Never use star ratings or progress bars — they are subjective and ATS-unfriendly.

Projects

Campus Notice Portal | React, Node.js, MongoDB          Jan 2026 – Apr 2026
• Built a real-time notice delivery system adopted by 4 departments,
  serving 400+ student accounts.
• Implemented JWT authentication and role-based access control for
  student, faculty and admin roles.
• Reduced notice-to-student latency from 3 days to under 5 minutes.
• Deployed on Render with GitHub Actions CI; code at github.com/aarav/notice-portal

Certifications

AWS Certified Cloud Practitioner — Amazon Web Services, 2025
  Credential ID: XXXX-XXXX  |  verify: credly.com/badges/xxxx

Achievements and Leadership

• Ranked 42nd of 1,850 teams in Smart India Hackathon (internal round), 2025
• Technical Head, Coding Club — conducted 6 workshops for 200+ students
• Solved 450+ DSA problems across LeetCode and Codeforces

9.5 ATS (Applicant Tracking System) Optimisation

9.6 Common CV Mistakes

1. Unprofessional email address (e.g. cool_boy99@...).
2. Broken or untested hyperlinks.
3. Photograph, date of birth, marital status, or "father's name" (unnecessary in most private-sector applications).
4. Listing every technology ever touched instead of a focused stack.
5. Passive phrasing — "was responsible for" instead of "developed".
6. No metrics; only duties and no results.
7. Inconsistent formatting (mixed fonts, bullet styles, date formats).
8. Typos — the single fastest route to rejection.
9. Reusing one CV for every application without tailoring the objective and skills order.
10. Claiming a CGPA or certification that cannot be verified.

X. Summary Tables & Quick Revision Sheet

10.1 Core Definitions — One Line Each

10.2 Key Formulas and Frameworks

10.3 Quick Comparison Grid

XI. Top 10 Exam Tips & Practice Questions

11.1 Top 10 Exam Tips

1. Always define before you describe. Start every answer with a precise one-sentence definition, then elaborate. Definitions carry guaranteed marks.
2. Use the four-pillar template. For any computational-thinking question, structure the answer as Decomposition → Pattern Recognition → Abstraction → Algorithm.
3. Draw the diagram. A firewall placement diagram, a CIA triad triangle, or an SDLC cycle earns marks that prose cannot.
4. Tabulate comparisons. Whenever the question says "differentiate", "compare" or "distinguish", answer in a two-column table with at least four parameters.
5. Quantify everything. In career-planning answers, include numbers — gaps, weights, percentages, deadlines. Markers reward specificity.
6. Use standard terminology. Write "principle of least privilege", "stateful inspection", "default-deny", "weighted decision matrix" — not paraphrases.
7. Cite the law and the code. For cyber-ethics questions, mention the IT Act 2000 (Sections 43, 66, 67) and the DPDP Act 2023 where relevant.
8. Answer the "why", not only the "what". Every practice described should be followed by the risk it mitigates.
9. Manage time by marks. Roughly one minute per mark; leave the last 10% of the paper for review.
10. Proofread for terminology consistency. Using "authorisation" and "authorization" interchangeably in one answer signals carelessness.

11.2 Practice Questions

XII. Solutions to Practice Questions

BEGIN
    READ year
    IF (year MOD 400 = 0) THEN
        PRINT "Leap Year"
    ELSE IF (year MOD 100 = 0) THEN
        PRINT "Not a Leap Year"
    ELSE IF (year MOD 4 = 0) THEN
        PRINT "Leap Year"
    ELSE
        PRINT "Not a Leap Year"
    END IF
END

git clone https://github.com/org/project.git
git checkout -b feature/xyz
# ... make changes ...
git add .
git commit -m "Add xyz feature"
git fetch origin
git rebase origin/main        # or: git merge origin/main
git push -u origin feature/xyz
# open a pull request → code review → merge

XII. Solutions to Practice Questions (continued)

XIII. References, Key Takeaways & CO Mapping

13.1 Textbooks

13.2 Reference Books

13.3 Other Reading and Online Resources

13.4 Audio-Visual Aids

13.5 Key Takeaways — 10 Points

1. Computational thinking rests on four pillars: decomposition, pattern recognition, abstraction and algorithm design — and applies far beyond programming.
2. A computing environment is a layered stack of hardware, system software, application software, network and users; each layer abstracts the one below it.
3. SDLC models differ mainly in how they handle change; Agile and DevOps dominate modern industry because they embrace change rather than resist it.
4. Version control is non-negotiable professional practice; a clean, meaningful Git history is itself a portfolio artefact.
5. Security is built on the CIA triad; every control and every attack can be mapped to confidentiality, integrity or availability.
6. Least privilege, MFA, patching and default-deny firewalls prevent the overwhelming majority of practical attacks.
7. Your digital footprint is permanent and is screened before your interview; manage it deliberately and build it positively.
8. AI ⊃ ML ⊃ DL; Generative AI creates content, while Agentic AI plans and acts — always with human oversight and ethical guardrails.
9. Career planning is a measured, iterative loop: assess → set SMART goals → compute the skill gap → execute the IDP → track progress and repeat.
10. A portfolio and Dream CV convert education into evidence; the distance between your current CV and your Dream CV is your development plan.

13.6 Course Outcome Mapping

13.7 Assessment Component Mapping