GCE (A/L) ICT | UNIVERSAL LOGIC GATES | UNIT 04 English Tamil Medium Online Class Notes

UNIT 4 – DIGITAL CIRCUITS (Beginner Friendly Notes)

Digital circuits are the foundation of computers and electronic devices. They work using only two values:

• 0 – OFF / FALSE / No electricity
• 1 – ON / TRUE / Electricity present

---

(i) LOGIC GATES

A logic gate is an electronic component that takes one or more binary inputs (0 or 1) and produces a binary output.

1. AND Gate

Rule: Output is 1 only if all inputs are 1.

A	B	A · B
0	0	0
0	1	0
1	0	0
1	1	1

Real-life example: You can enter a room only if you have an ID card AND permission.

2. OR Gate

Rule: Output is 1 if at least one input is 1.

A	B	A + B
0	0	0
0	1	1
1	0	1
1	1	1

3. NOT Gate

Rule: Output is the opposite of the input.

A	Ā
0	1
1	0

4. NAND Gate

Rule: Output is the opposite of AND gate.

NAND gate gives output 0 only when both inputs are 1.

5. NOR Gate

Rule: Output is the opposite of OR gate.

NOR gate gives output 1 only when both inputs are 0.

6. XOR Gate

Rule: Output is 1 when inputs are different.

A	B	Output
0	0	0
0	1	1
1	0	1
1	1	0

7. XNOR Gate

Rule: Output is 1 when inputs are same.

---

Universal Gates

NAND and NOR are called Universal Gates because all other logic gates can be created using only NAND gates or only NOR gates.

---

(ii) BOOLEAN ALGEBRA

Boolean Algebra is a mathematical method used to analyze and simplify digital circuits.

Basic Boolean Laws

• A + A = A
• A · A = A
• A + 1 = 1
• A · 0 = 0
• A + Ā = 1
• A · Ā = 0

De Morgan’s Laws

• (A · B)̅ = Ā + B̅
• (A + B)̅ = Ā · B̅

SOP and POS

SOP (Sum of Products): AND operations first, then OR.

Example: A·B + C·D

POS (Product of Sums): OR operations first, then AND.

Example: (A + B)(C + D)

---

(iii) DESIGNING LOGIC CIRCUITS

Boolean expressions can be converted into logic circuits using gates.

Example: Y = (A + B) · C

• A + B → OR gate
• Output AND with C
• Final output is Y

Truth tables are used to verify the correctness of circuits.

---

(iv) CPU AND MEMORY (RAM)

Half Adder

A Half Adder adds two binary bits.

A	B	Sum	Carry
0	0	0	0
0	1	1	0
1	0	1	0
1	1	0	1

Sum is generated using XOR gate and Carry using AND gate.

Full Adder

A Full Adder adds three bits: A, B and Carry-in. It is used in the Arithmetic Logic Unit (ALU) of the CPU.

Memory and Flip-Flops

Memory circuits store data using feedback loops.

Flip-Flop: A basic memory unit capable of storing 1 bit of data.

---

Boolean Algebra Laws – Step by Step for Beginners

Boolean algebra works with only two values:

• 1 = TRUE (ON)
• 0 = FALSE (OFF)

---

1. Commutative Law

Changing the order does not change the result.

A · B = B · A

A + B = B + A

2. Associative Law

Changing the grouping does not change the result.

A · (B · C) = (A · B) · C

A + (B + C) = (A + B) + C

3. Idempotent Law

Repeating the same variable has no effect.

A · A = A

A + A = A

4. Double Negative Law

Opposite of opposite gives original value.

Ā̄ = A

5. Complementary Law

A · Ā = 0

A + Ā = 1

6. Intersection Law

A · 1 = A

A · 0 = 0

7. Union Law

A + 1 = 1

A + 0 = A

8. Distributive Law

A · (B + C) = (A · B) + (A · C)

A + (B · C) = (A + B) · (A + C)

9. Absorption Law

A · (A + B) = A

A + (A · B) = A

10. Redundancy Law

A · (Ā + B) = A · B

A + (Ā + B) = A + B

11. De Morgan’s Law

(A · B)̄ = Ā + B̄

(A + B)̄ = Ā · B̄

---

PART 1: BOOLEAN ALGEBRA – STEP-BY-STEP FOR BEGINNERS

First: Basic Meaning (Very Important)

Symbol	Meaning	Example
1	TRUE / ON	Light is ON
0	FALSE / OFF	Light is OFF
A, B	Inputs	Switches
A · B	AND	Both ON
A + B	OR	Any one ON
Ā	NOT A	Opposite of A

---

1. Commutative Law

Meaning: Order does NOT change the result

AND Example

• A = 1, B = 0

• A · B = 1 · 0 = 0

• B · A = 0 · 1 = 0

✅ Same answer → Order does not matter

OR Example

• A = 1, B = 0

• A + B = 1 + 0 = 1

• B + A = 0 + 1 = 1

✔️ Law proven

---

2. Associative Law

Meaning: Grouping does NOT matter

AND Example

Let A=1, B=1, C=0

Step 1:

A · (B · C)
= 1 · (1 · 0)
= 1 · 0
= 0

Step 2:

(A · B) · C
= (1 · 1) · 0
= 1 · 0
= 0

✔️ Same result

---

3. Idempotent Law

Meaning: Repeating same value changes nothing

Example

A = 1 → A · A = 1 · 1 = 1
A = 0 → A + A = 0 + 0 = 0

So:

• A · A = A

• A + A = A

✔️ No effect by repetition

---

4. Double Negative Law

Meaning: Opposite of opposite = original

Example:

• A = 1 → Ā = 0 → Ā̄ = 1

• A = 0 → Ā = 1 → Ā̄ = 0

✔️ Ā̄ = A

---

5. Complementary Law

Meaning: A and NOT A

AND Case

A · Ā
= 1 · 0 = 0
= 0 · 1 = 0

Always FALSE

OR Case

A + Ā
= 1 + 0 = 1
= 0 + 1 = 1

Always TRUE

---

6. Intersection Law (AND with constants)

Example

A · 1 = A
A · 0 = 0

Think:

• AND with TRUE → keeps value

• AND with FALSE → always FALSE

---

7. Union Law (OR with constants)

Example

A + 1 = 1
A + 0 = A

Think:

• OR with TRUE → always TRUE

• OR with FALSE → keeps value

---

8. Distributive Law

Meaning: Like normal algebra

Example 1

A · (B + C)
= A · B + A · C

Let A=1, B=0, C=1

Left:

1 · (0 + 1)
= 1 · 1
= 1

Right:

(1 · 0) + (1 · 1)
= 0 + 1
= 1

✔️ Works

---

9. Absorption Law

Meaning: Extra part is useless

Example

A · (A + B)

If A=1:

1 · (1 + B) = 1

If A=0:

0 · (0 + B) = 0

✔️ Always A

---

10. Redundancy Law

Meaning: Remove unnecessary terms

Example:

A · (Ā + B)

Since:

• A · Ā = 0

So:

A · B

✔️ Simpler form

---

11. De Morgan’s Law (VERY IMPORTANT)

Rule:

• NOT moves inside

• AND ↔ OR (swap)

• Each variable gets NOT

Example 1

(A · B)̄ = Ā + B̄

Example 2

(A + B)̄ = Ā · B̄

Used heavily in logic circuits & exams.

Tip: These laws are essential for simplifying digital logic circuits.

Conclusion: Logic gates form circuits, circuits form processors, and processors make computers work.

Web-Based Online Learning and Attendance Tracking System Student Project | detailed list of modules, their sub-modules, and functions based on industry-standard platforms like Moodle, Google Classroom, Canvas, Blackboard, Edmodo, and custom-built academic systems

Developing a Web-Based Online Learning and Attendance Tracking System requires a comprehensive understanding of both Learning Management Systems (LMS) and Attendance Management Systems. Below is a detailed list of modules, their sub-modules, and based on industry-standard platforms like Moodle, Google Classroom, Canvas, Blackboard, Edmodo, and custom-built academic systems.

📚 Core System Modules & Their Functions

1. User & Role Management

Purpose: Control user access and permissions.

Functions:

• Admin, teacher, student, parent accounts

• Role-based permissions

• Profile management (update personal info, password)

• Multi-school or multi-department support

---

2. Authentication & Security

Purpose: Secure access for multiple user types.

Functions:

• Login/logout with email/username

• Two-factor authentication (optional)

• Password reset via email/SMS

• Session management and access logs

---

3. Online Learning / LMS (Learning Management System)

Purpose: Core teaching and learning platform.

Functions:

• Course creation and organization (modules, units)

• Upload/host videos, PDFs, SCORM content, assignments

• Categorize courses by subject, grade, or program

• Module sequencing and learning paths

• Course catalogs for public browsing

• Course descriptions and prerequisites

---

4. Virtual Classroom / Live Sessions

Purpose: Deliver real-time online classes.

Functions:

• Integrated video conferencing (Zoom/BigBlueButton etc.)

• Screen sharing, live chat, virtual hand-raise

• Attendance capture within class sessions

• Recording and playback for later access

---

5. Attendance Tracking & Management

Purpose: Track presence in courses and live classes.

Functions:

• Manual or automatic attendance marking

• Attendance statuses: present, absent, late, excused

• Daily, weekly, monthly tracking and roll-call

• Bulk marking options

• Track attendance tied to scheduled timetable

• Attendance dashboards for quick insights

• Optional biometric/RFID/QR/face ID attendance capture

• Mobile app support for teacher marking

---

6. Timetable & Scheduling

Purpose: Organize classes & meetings.

Functions:

• Calendar views (day/week/month)

• Conflict detection (room or instructor overlap)

• Automated schedule generation

• Recurring sessions and holiday/exam schedules

• Sync to Google/Outlook calendar

---

7. Course Progress & Analytics

Purpose: Monitor learning progress.

Functions:

• Track lessons completed

• Course completion percentage

• Detailed progress dashboards

• Performance trend graphs

---

8. Assessments & Grading

Purpose: Measure student learning outcomes.

Functions:

• Online quizzes and exams

• Assignment upload and submissions

• Automatic or manual grading

• Rubric and feedback system

• Gradebook for teachers and students

---

9. Certificates & Badges

Purpose: Recognize achievement.

Functions:

• Auto-generate completion certificates

• Customizable templates (logo, signatures)

• Digital badges for milestones

---

10. Notifications & Communication

Purpose: Keep users informed.

Functions:

• Email/SMS/Push alerts for:

  • Attendance updates

  • Class start reminders

  • Assignment deadlines

  • Course enrollment confirmations

---

11. Discussion & Community

Purpose: Facilitate interaction.

Functions:

• Course forums and threads

• Chat between instructors and students

• Q&A boards

• Private messages

---

12. Reporting & Dashboards

Purpose: Data analysis and export.

Functions:

• Attendance reports (student, class, date range)

• Progress and performance dashboards

• Export to CSV/PDF

• Custom report builder

---

13. Payment & Billing (Optional)

Purpose: Monetize courses if public/paid.

Functions:

• Payment gateways (Stripe/PayPal)

• Course pricing/subscriptions

• Invoicing & receipts

• Refund processing

---

14. Parent/Guardian Portal

Purpose: Visibility into student performance.

Functions:

• View attendance records

• Progress and grades

• Notifications about absences

• Message teachers

---

15. Content & Resource Library

Purpose: Central repository of learning materials.

Functions:

• Upload files (docs, presentations, videos)

• Organize by subject or curriculum

• Version control

---

16. Integration & API

Purpose: Connect with external tools/services.

Functions:

• Integrate live class tools (BigBlueButton, Zoom)

• APIs for SIS / payment / SMS gateways

• Webhooks for real-time events

---

17. Admin & System Settings

Purpose: Central administration controls.

Functions:

• System configuration

• Role & permission settings

• Audit logs

• Data backup and restore

• Multi-language and timezone support

---

18. Security & Compliance

Purpose: Protect user data.

Functions:

• SSL encryption

• Data privacy controls (GDPR or local standards)

• Regular security audits

---

👩‍💻 Optional Advanced Modules

These aren’t required but are strong value-adds:

• AI-Powered Learning Analytics (adaptive suggestions)

• Gamification (points/levels)

• Mobile Apps (Android/iOS)

• Offline Content Sync

• Offline Attendance Capture

---

📌 Summary

Module	Core Functions
LMS	Course management, content delivery
Attendance	Marking, tracking, automated capture
Online Class	Live sessions with attendance
Scheduling	Timetables & conflict management
Assessment	Quizzes, grading, certificates
User Management	Roles & permissions
Communication	Alerts, messaging
Reporting	Dashboards & exports
Parent Portal	Visibility & notifications
Payments	Billing & invoicing

---

🔍 Real-World Examples to Study:

• Moodle: Open-source, highly modular
• Google Classroom: Simple, integrates with G Suite
• Canvas LMS: Modern UI, strong analytics
• Edmodo: K-12 focused, includes badges & parent access
• TalentLMS / LearnDash: For corporate or custom e-learning

---

More:

• A database schema for this system
• Tech stack recommendations (e.g., React + Node.js + MongoDB)
• Wireframes or user flow diagrams
• Priority-based development roadmap (MVP vs full version)

Good luck with your project! 🚀

ICT Internship opportunities in sri lanka IT Internship opportunities in sri lanka for students Internships for undergraduates Sri Lanka Internship Vacancies in Sri Lanka 2025 Paid internships in Sri Lanka Online internship opportunities in sri lanka Internship Vacancies 2025 Government Internships for undergraduates Sri Lanka Internship for undergraduates

---

# **Final Year Project Proposal & Software Requirements Specification (SRS)**

**Title:** *Small shops don’t track customers* → **Software Solution: Lightweight CRM for Small Retailers**

*Submitted in partial fulfillment of the requirements for the Bachelor of Information Technology (BIT) – External Degree Programme, University of Moratuwa*

---

## **1. Introduction**

### 1.1 Problem Statement

Small retail shops—such as boutiques, hardware stores, mobile repair centers, and online resellers like your own business—**rarely maintain structured customer records**. Most rely on:

- Memory or handwritten notes,

- WhatsApp chats or phone call logs,

- Spreadsheets with inconsistent or outdated data.

This leads to:

- **Missed repeat sales** (e.g., not recognizing loyal customers),

- **Inability to follow up** on inquiries or pending orders,

- **No personalized communication** (e.g., birthday offers, restock alerts),

- **Lost customer history** when staff change or phones are replaced,

- **Inefficient after-sales service** due to lack of purchase records.

In short, small shops **leave money on the table** because they can’t remember who their customers are, what they bought, or when they last interacted.

### 1.2 Proposed Solution

A **lightweight, web-based Customer Relationship Management (CRM) system** designed specifically for Sri Lankan small retailers and solo entrepreneurs.

The system enables shop owners to:

- **Capture customer profiles** (name, phone, address, preferences),

- **Log every interaction** (inquiry, quote, sale, complaint),

- **Track order and payment status**,

- **Set follow-up reminders** (e.g., “Call Amal about pending payment”),

- **Send bulk WhatsApp/SMS notifications** (e.g., “New stock arrived!”),

- **View customer lifetime value** and purchase trends.

Built with **zero accounting complexity**, **mobile-first design**, and **WhatsApp integration**, this CRM fits seamlessly into the workflows of non-technical shop owners.

---

## **2. Objectives**

- Digitize and centralize customer data for small retailers.

- Replace memory/WhatsApp with a structured interaction history.

- Increase repeat sales through timely follow-ups and reminders.

- Enable basic segmentation (e.g., frequent buyers, high-value customers).

- Improve customer service with quick access to past orders.

- Provide a **free, low-friction alternative** to enterprise CRMs like Salesforce or Zoho.

---

## **3. Scope**

### 3.1 In Scope

- **Web application** (mobile-optimized) for shop owners and staff.

- **Customer Management**:

- Add/edit customers (name, phone, address, notes).

- Tag customers (e.g., “VIP”, “Wholesale”, “Online Buyer”).

- **Interaction Logging**:

- Log calls, WhatsApp messages, in-person visits, inquiries.

- Attach photos (e.g., product image sent by customer).

- **Order & Payment Tracking**:

- Link interactions to orders.

- Track status: Inquiry → Quoted → Paid → Delivered.

- Record payment method and proof (e.g., bank deposit screenshot).

- **Follow-Up System**:

- Set reminders with due dates and notes.

- Get daily task list (e.g., “Follow up with 3 customers today”).

- **Bulk Communication**:

- Send WhatsApp/SMS to selected customers (e.g., restock alert).

- Message templates (e.g., “Hi [Name], your order is ready!”).

- **Dashboard & Insights**:

- Total customers, active inquiries, overdue follow-ups.

- Top customers by interaction frequency.

- **Data Export**: Export customer list or interaction history as CSV.

### 3.2 Out of Scope

- Integrated payment processing (e.g., Stripe, Genie).

- Inventory or POS functionality (can link to your other project separately).

- Email marketing (focus on WhatsApp/SMS only).

- Multi-user role permissions beyond basic staff access.

- AI-driven recommendations or predictive analytics.

---

## **4. Functional Requirements**

| Module | Feature | Description |

|-------|--------|------------|

| **Authentication** | Shop Owner Login | Secure access via email/password |

| | Staff Access (Optional) | View-only or limited edit rights |

| **Customer Management** | Add Customer | Name, phone (primary key), address, notes |

| | Customer Profile | View all interactions, orders, tags |

| | Search & Filter | By name, phone, tag, last contact date |

| **Interaction Log** | Log New Interaction | Type (call, WhatsApp, in-person), date, notes |

| | Attach Media | Upload image (e.g., product photo from customer) |

| | Link to Order | Optional association |

| **Order Tracking** | Create Order from Inquiry | Auto-generate from interaction |

| | Status Workflow | Inquiry → Quoted → Confirmed → Paid → Delivered |

| | Payment Proof Upload | Screenshot of bank deposit or transfer |

| **Follow-Up System** | Create Reminder | Set date/time, assign to self, add note |

| | Daily Task List | Show pending follow-ups due today |

| | Mark as Completed | With optional resolution note |

| **Bulk Messaging** | Select Customers | By tag, last purchase, or manual selection |

| | Send WhatsApp/SMS | Via WhatsApp Business API or Twilio |

| | Save Templates | Reusable message formats |

| **Dashboard** | Key Metrics | Total customers, active inquiries, overdue follow-ups |

| | Recent Activity Feed | Last 10 interactions |

| | Customer Insights | Top 5 most engaged customers |

| **Settings** | Shop Info | Name, contact, logo |

| | Notification Preferences | Enable/disable reminders, message logs |

---

## **5. Non-Functional Requirements**

- **Usability**: Fully operable on a smartphone; data entry in <30 seconds.

- **Privacy**: Customer phone numbers never exposed publicly; encrypted at rest.

- **Performance**: Load customer list in <1.5s with 1,000+ contacts.

- **Offline Support**: Allow draft interaction logging (sync when online)—optional.

- **Reliability**: Daily cloud backup; no data loss on refresh.

- **Cost Efficiency**: Free to deploy; uses low-cost SMS/WhatsApp APIs.

- **Localization**: Support Sinhala/English toggle (Phase 2).

---

## **6. System Architecture**

- **Frontend**: React.js + Tailwind CSS (mobile-first, fast)

- **Backend**: Node.js/Express **or** Django (Python)

- **Database**: PostgreSQL (relational, ideal for customer-interaction links)

- **Authentication**: JWT or Firebase Auth

- **Messaging**: WhatsApp Cloud API (Meta) + Twilio (SMS fallback)

- **File Storage**: Firebase Storage or Cloudinary (for inquiry images)

- **Hosting**: Vercel (frontend), Render (backend) — free tiers supported

---

## **7. Database Design (Key Entities)**

- **Users**

(`user_id`, `shop_name`, `email`, `password_hash`, `phone`, `created_at`)

- **Customers**

(`customer_id`, `user_id`, `name`, `phone`, `address`, `notes`, `tags`, `created_at`)

- **Interactions**

(`interaction_id`, `customer_id`, `type`, `date`, `notes`, `media_url`, `order_id` [nullable])

- **Orders**

(`order_id`, `customer_id`, `status`, `total_amount`, `payment_proof_url`, `created_at`, `updated_at`)

- **FollowUps**

(`followup_id`, `customer_id`, `due_date`, `note`, `completed`, `completed_at`)

- **MessageTemplates**

(`template_id`, `user_id`, `name`, `content`)

- **SentMessages**

(`message_id`, `customer_id`, `template_id`, `channel` [whatsapp/sms], `status`, `sent_at`)

*(Normalized structure: one customer → many interactions/orders/follow-ups.)*

---

## **8. Feature Comparison with Real-World Systems**

| Feature | **Proposed Lightweight CRM** | **Existing CRMs (e.g., Zoho CRM, HubSpot, Excel)** |

|--------|------------------------------|---------------------------------------------------|

| **Designed for Small Shops** | ✅ Yes — simple, no jargon | ❌ Enterprise-focused; overwhelming for 1-person shops |

| **WhatsApp Integration** | ✅ Native support for inquiry photos & bulk alerts | ❌ Requires paid add-ons or complex setup |

| **Order + Payment Tracking** | ✅ Built-in for resellers (like your business) | ❌ Requires separate invoicing module |

| **Follow-Up Reminders** | ✅ Task-based, mobile-friendly | ⚠️ Available but buried in menus |

| **Cost** | ✅ Free to self-host | ❌ Zoho: ~LKR 1,500+/user/month; HubSpot: starts free but limited |

| **Data Ownership** | ✅ Full control; export anytime | ❌ Locked in cloud; hard to migrate |

| **Offline Use** | ✅ Planned (drafts) | ❌ Most require constant internet |

| **Sri Lankan Context** | ✅ Optimized for phone-based, cash/deposit workflows | ❌ Assumes credit cards, email, formal invoicing |

> ✅ **Key Advantage**: This CRM **mirrors your real business workflow**—from receiving a product photo via WhatsApp to confirming a bank deposit—**without forcing you into complex sales pipelines**.

---

## **9. Development Roadmap**

| Phase | Duration | Deliverables |

|------|--------|-------------|

| **Phase 1** | Weeks 1–2 | Requirements, DB schema, UI wireframes |

| **Phase 2** | Weeks 3–5 | Auth, customer management, interaction logging |

| **Phase 3** | Weeks 6–8 | Order & payment tracking + follow-up system |

| **Phase 4** | Weeks 9–10 | WhatsApp/SMS integration + message templates |

| **Phase 5** | Week 11 | Dashboard, reporting, export features |

| **Phase 6** | Week 12 | Testing, deployment, documentation, demo video |

---

## **10. Expected Outcomes & Impact**

- Help small shop owners **retain 20–30% more customers** through systematic follow-ups.

- Reduce missed opportunities from forgotten inquiries.

- Provide **actionable insights** without data science complexity.

- Serve as a **real-world tool** you can use in your own buy-and-sell business.

- Fulfill all academic, technical, and innovation criteria for a BIT final-year project.

---

## **11. Conclusion**

The *Lightweight CRM for Small Retailers* solves a silent but costly problem: **customer invisibility**. By digitizing the informal relationships that drive small businesses, it turns memory and WhatsApp chaos into a strategic asset—**all within a simple, affordable, and locally relevant system**.

This document is **complete, detailed, and ready for immediate development**, meeting all standards for a **University of Moratuwa BIT final-year Project Proposal and SRS**.

---

Would you like any of the following to finalize your submission?

- **UML Diagrams** (Use Case: “Log Customer Inquiry”, Class Diagram)

- **UI Mockups** (Customer profile, interaction log, follow-up list)

- **Risk & Feasibility Analysis**

- **BIT-compliant formatting (cover page, ToC, references)**

Just let me know—I’m ready to help you deliver an outstanding project!