Capstone Project Guide — B.Tech IT Sem 8

Capstone Project — Overview

Final year project = 8 semesters ki learning ka practical demonstration. Industry-ready skills + problem solving capability dikhana hai.

Timeline (Typical 6 months):

Month 1: Topic selection, domain research, team formation
Month 2: SRS document, system design, prototype
Month 3-4: Core development, database setup
Month 5: Testing, bug fixes, deployment
Month 6: Report writing, presentation prep, viva

---

1. Project Ideas by Domain

Web/Full-Stack

✅ E-learning Platform (WohoTech-style)
   - Course management, video streaming, quizzes, certificates
   
✅ Hospital Management System
   - OPD, appointments, EMR, billing, inventory
   
✅ Job Portal for Freshers
   - Resume upload, skill matching, company dashboard
   
✅ College ERP
   - Attendance, marks, fees, library, hostel

AI/ML Projects

✅ Plant Disease Detection (CNN + Mobile App)
   - Camera → detect disease → suggest treatment
   
✅ Resume Screening System (NLP)
   - Job description + resume → match score + recommendations
   
✅ Fake News Detector
   - NLP model → classify news articles
   
✅ Crop Yield Prediction
   - Weather + soil data → yield forecasting (regression)

IoT/Embedded

✅ Smart Irrigation System
   - Soil moisture sensor + weather API → automated watering
   
✅ Air Quality Monitoring
   - Sensors + dashboard + alert system
   
✅ Smart Home Controller
   - ESP32 + MQTT + mobile app

Cybersecurity

✅ Network Vulnerability Scanner
   - Port scanning, service detection, CVE lookup
   
✅ Log Analysis Dashboard (SIEM lite)
   - Aggregate logs → detect anomalies

---

2. SRS Document Template

SOFTWARE REQUIREMENTS SPECIFICATION
Project: [Project Name]
Version: 1.0
Date: [Date]
Team: [Names and Roles]
Supervisor: [Guide Name]

1. INTRODUCTION
   1.1 Purpose
       Kya banaya ja raha hai aur kyon
   1.2 Scope
       System ki boundary — kya include, kya nahi
   1.3 Definitions & Acronyms
       API, CRUD, JWT, REST, etc.
   1.4 References
       Related papers, existing systems, tools
   1.5 Overview
       Document ka structure

2. OVERALL DESCRIPTION
   2.1 Product Perspective
       Standalone / part of larger system
   2.2 Product Features (high-level)
       User management, Content management, Reporting
   2.3 User Classes
       Admin, Teacher, Student, Guest
   2.4 Operating Environment
       Web browser, Node.js 18+, PostgreSQL 15
   2.5 Constraints
       Budget, time, team size, regulatory
   2.6 Assumptions
       Users have internet, basic tech literacy

3. FUNCTIONAL REQUIREMENTS
   FR-001: User Registration
     Description: New user can create account
     Input: Name, email, password, role
     Output: Account created, welcome email sent
     Priority: High
   
   FR-002: Course Enrollment
     Description: Student can enroll in courses
     ...

4. NON-FUNCTIONAL REQUIREMENTS
   NFR-001: Performance
     - Page load < 3 seconds on 4G
     - Support 100 concurrent users
   NFR-002: Security
     - Passwords hashed (bcrypt)
     - HTTPS only
     - JWT token expiry 24h
   NFR-003: Usability
     - Mobile responsive
     - WCAG 2.1 accessibility basic compliance
   NFR-004: Reliability
     - 99.5% uptime
     - Daily automated backups

5. EXTERNAL INTERFACES
   UI: React + Tailwind CSS
   API: REST/JSON over HTTPS
   DB: PostgreSQL
   Auth: NextAuth / JWT
   Email: Nodemailer / Resend
   Storage: AWS S3 / Cloudflare R2

---

3. System Design

Architecture Diagram

Client (Browser/Mobile)
         │ HTTPS
    [API Gateway / Next.js]
         │
   ┌─────┼─────────┐
[Auth]  [API]  [Static]
Service  Routes  Files
         │
   ┌─────┼─────┐
[DB]  [Cache] [Storage]
(PG)  (Redis)  (S3)
         │
   [Email Service]
   [Notification]

Database Design (ERD Principles)

-- User Management
CREATE TABLE users (
    id         UUID PRIMARY KEY DEFAULT gen_random_uuid(),
    email      VARCHAR(255) UNIQUE NOT NULL,
    password   VARCHAR(255) NOT NULL,  -- bcrypt hash
    name       VARCHAR(100) NOT NULL,
    role       VARCHAR(20) DEFAULT 'student',
    created_at TIMESTAMP DEFAULT NOW(),
    updated_at TIMESTAMP DEFAULT NOW()
);

-- Core Entity Example: Course
CREATE TABLE courses (
    id          UUID PRIMARY KEY DEFAULT gen_random_uuid(),
    title       VARCHAR(255) NOT NULL,
    description TEXT,
    instructor_id UUID REFERENCES users(id),
    created_at  TIMESTAMP DEFAULT NOW(),
    is_published BOOLEAN DEFAULT FALSE
);

-- Junction Table
CREATE TABLE enrollments (
    user_id    UUID REFERENCES users(id),
    course_id  UUID REFERENCES courses(id),
    enrolled_at TIMESTAMP DEFAULT NOW(),
    progress   INTEGER DEFAULT 0,
    PRIMARY KEY (user_id, course_id)
);

-- Indexes for performance
CREATE INDEX idx_courses_instructor ON courses(instructor_id);
CREATE INDEX idx_enrollments_user ON enrollments(user_id);

---

4. Development Stack Setup

# Next.js Full-Stack Project Setup
npx create-next-app@latest myproject --typescript --tailwind --app

# Essential packages
npm install @prisma/client prisma           # ORM
npm install next-auth @auth/prisma-adapter  # Auth
npm install bcryptjs zod                    # Security, validation
npm install react-hook-form                 # Forms
npm install axios                           # HTTP client

# Development tools
npm install -D @types/bcryptjs prettier eslint

# Initialize Prisma
npx prisma init
npx prisma migrate dev --name init
npx prisma generate

Project Folder Structure:

src/
├── app/
│   ├── (auth)/login/page.tsx
│   ├── (dashboard)/page.tsx
│   ├── api/
│   │   ├── auth/[...nextauth]/route.ts
│   │   └── courses/route.ts
│   └── layout.tsx
├── components/
│   ├── ui/
│   └── features/
├── lib/
│   ├── prisma.ts
│   ├── auth.ts
│   └── utils.ts
├── hooks/
└── types/

---

5. Testing Strategy

// Unit Test (Jest + Testing Library)
import { render, screen, fireEvent } from '@testing-library/react'
import LoginForm from '@/components/auth/LoginForm'

describe('LoginForm', () => {
  it('shows error for invalid email', async () => {
    render(<LoginForm />)
    fireEvent.change(screen.getByLabelText(/email/i), {
      target: { value: 'invalid' }
    })
    fireEvent.click(screen.getByRole('button', { name: /login/i }))
    expect(await screen.findByText(/valid email/i)).toBeInTheDocument()
  })
  
  it('calls onSubmit with valid data', async () => {
    const onSubmit = jest.fn()
    render(<LoginForm onSubmit={onSubmit} />)
    // ... fill form and submit
    expect(onSubmit).toHaveBeenCalledWith({ email: '...', password: '...' })
  })
})

// API Test (supertest)
import request from 'supertest'
import app from '@/app'

describe('POST /api/courses', () => {
  it('creates course for authenticated teacher', async () => {
    const res = await request(app)
      .post('/api/courses')
      .set('Authorization', `Bearer ${teacherToken}`)
      .send({ title: 'Test Course', description: 'Test' })
    expect(res.status).toBe(201)
    expect(res.body.id).toBeDefined()
  })
})

---

6. Deployment

# Vercel deployment (vercel.json)
{
  "framework": "nextjs",
  "env": {
    "DATABASE_URL": "@database_url",
    "NEXTAUTH_SECRET": "@nextauth_secret"
  }
}

# Or Railway/Render for full-stack
# Docker Compose for local dev
version: '3.8'
services:
  web:
    build: .
    ports: ["3000:3000"]
    environment:
      DATABASE_URL: postgresql://user:pass@db:5432/myapp
    depends_on: [db]
  db:
    image: postgres:15
    environment:
      POSTGRES_PASSWORD: pass
      POSTGRES_DB: myapp
    volumes: [pgdata:/var/lib/postgresql/data]
volumes:
  pgdata:

---

7. Viva Preparation

Common Questions & Answers:

Q: Project mein kya novel contribution hai? A: Existing systems se kya alag hai — specific feature, better UX, new integration, performance improvement. "We combined X with Y for Z use case which doesn't exist."

Q: Database indexing kyun ki? A: Frequently searched columns pe (email, course_id) — O(log n) search instead of O(n) full scan. EXPLAIN ANALYZE se slow queries identify karein.

Q: API security kaise handle ki? A: JWT authentication, role-based authorization middleware, input validation (Zod), rate limiting, HTTPS, bcrypt passwords, parameterized queries (no SQL injection).

Q: Scalability kaise handle karoge? A: Horizontal scaling (multiple instances), CDN for static assets, database connection pooling, caching (Redis), async job queues (BullMQ), read replicas for DB.

---

Report Writing Tips

Abstract: 200-300 words, cover all key points
Introduction: problem statement, motivation, objectives
Literature Review: 5-10 existing systems/papers compared
Methodology: development process (Agile sprints)
System Design: architecture, DB schema, API endpoints
Implementation: key code snippets (not full code)
Testing: test cases table, results, bugs fixed
Results & Discussion: screenshots, performance metrics
Conclusion & Future Work: what achieved, what next
References: IEEE format

Formatting:

• Font: Times New Roman 12pt
• Line spacing: 1.5
• Margins: 1 inch all sides
• Figures numbered and captioned
• Code in monospace font, syntax highlighted
• Page numbers bottom center