diff --git a/7 SEMESTER/Software Engineering/Assignment/Assignment 1/Entities and Attributes.docx b/7 SEMESTER/Software Engineering/Assignment/Assignment 1/Entities and Attributes.docx
new file mode 100644
index 0000000..e791753
Binary files /dev/null and b/7 SEMESTER/Software Engineering/Assignment/Assignment 1/Entities and Attributes.docx differ
diff --git a/7 SEMESTER/Software Engineering/Assignment/Assignment 1/Entities and Attributes.pdf b/7 SEMESTER/Software Engineering/Assignment/Assignment 1/Entities and Attributes.pdf
new file mode 100644
index 0000000..089746e
Binary files /dev/null and b/7 SEMESTER/Software Engineering/Assignment/Assignment 1/Entities and Attributes.pdf differ
diff --git a/7 SEMESTER/Software Engineering/Assignment/Assignment 1/TaskFlow_Pro_SRS.docx b/7 SEMESTER/Software Engineering/Assignment/Assignment 1/TaskFlow_Pro_SRS.docx
new file mode 100644
index 0000000..288055e
Binary files /dev/null and b/7 SEMESTER/Software Engineering/Assignment/Assignment 1/TaskFlow_Pro_SRS.docx differ
diff --git a/7 SEMESTER/Software Engineering/Assignment/Assignment 1/TaskFlow_Pro_SRS.pdf b/7 SEMESTER/Software Engineering/Assignment/Assignment 1/TaskFlow_Pro_SRS.pdf
new file mode 100644
index 0000000..c3e6783
Binary files /dev/null and b/7 SEMESTER/Software Engineering/Assignment/Assignment 1/TaskFlow_Pro_SRS.pdf differ
diff --git a/7 SEMESTER/Software Engineering/Assignment/Assignment 2/Assignment 2.docx b/7 SEMESTER/Software Engineering/Assignment/Assignment 2/Assignment 2.docx
new file mode 100644
index 0000000..3962120
Binary files /dev/null and b/7 SEMESTER/Software Engineering/Assignment/Assignment 2/Assignment 2.docx differ
diff --git a/7 SEMESTER/Software Engineering/Assignment/Assignment 2/Assignment 2.pdf b/7 SEMESTER/Software Engineering/Assignment/Assignment 2/Assignment 2.pdf
new file mode 100644
index 0000000..9a45013
Binary files /dev/null and b/7 SEMESTER/Software Engineering/Assignment/Assignment 2/Assignment 2.pdf differ
diff --git a/7 SEMESTER/Software Engineering/Assignment/Assignment 2/Questions.txt b/7 SEMESTER/Software Engineering/Assignment/Assignment 2/Questions.txt
new file mode 100644
index 0000000..308bf73
--- /dev/null
+++ b/7 SEMESTER/Software Engineering/Assignment/Assignment 2/Questions.txt	
@@ -0,0 +1,8 @@
+Q1 Difference between function and services in software systems.
+
+
+Q2 Make use case diagram/class diagram.
+ 
+Tool Link: 
+
+https://online.visual-paradigm.com/
\ No newline at end of file
diff --git a/7 SEMESTER/Software Engineering/Books/Clean Code_ A Handbook of Agile Software Craftsmanship.pdf b/7 SEMESTER/Software Engineering/Books/Clean Code_ A Handbook of Agile Software Craftsmanship.pdf
new file mode 100644
index 0000000..6a4b9a8
Binary files /dev/null and b/7 SEMESTER/Software Engineering/Books/Clean Code_ A Handbook of Agile Software Craftsmanship.pdf differ
diff --git a/7 SEMESTER/Software Engineering/Notes/Unit 1/Unit 1 Notes.pdf b/7 SEMESTER/Software Engineering/Notes/Unit 1/Unit 1 Notes.pdf
new file mode 100644
index 0000000..b7de96d
Binary files /dev/null and b/7 SEMESTER/Software Engineering/Notes/Unit 1/Unit 1 Notes.pdf differ
diff --git a/7 SEMESTER/Software Engineering/Notes/Unit 2/Unit 2 Notes.pdf b/7 SEMESTER/Software Engineering/Notes/Unit 2/Unit 2 Notes.pdf
new file mode 100644
index 0000000..420db26
Binary files /dev/null and b/7 SEMESTER/Software Engineering/Notes/Unit 2/Unit 2 Notes.pdf differ
diff --git a/7 SEMESTER/Software Engineering/Notes/Unit 3/Programming Paradigms.html b/7 SEMESTER/Software Engineering/Notes/Unit 3/Programming Paradigms.html
new file mode 100644
index 0000000..f5cbb4e
--- /dev/null
+++ b/7 SEMESTER/Software Engineering/Notes/Unit 3/Programming Paradigms.html	
@@ -0,0 +1,185 @@
+<!-- 
+Author: Madhurima Rawat
+Date: 21 November 2024
+Brief: This HTML document presents a table comparing various programming paradigms. It includes the paradigm's principles, key languages, and key concepts associated with each paradigm. 
+The table helps users understand the different programming styles, their foundations, and their application in modern development.
+
+Additional Details:
+- Color Palette: The table features a pastel color scheme with alternating row colors such as coral, cyan, lavender, and light teal, creating a visually appealing and easy-to-read format.
+- Emoji Usage: Each paradigm and its respective column headers are paired with relevant emojis (e.g., ⚙️ for Procedural Programming, 🏛️ for Object-Oriented Programming, 🔗 for Functional Programming), adding clarity and engagement to the table.
+- Design: The table is styled with alternating background colors for rows to improve readability. The table header is highlighted with a coral background for emphasis, and each row has its own distinct color for easier navigation.
+- Purpose: The goal of this table is to provide a concise comparison of programming paradigms, helping developers and learners quickly grasp the core concepts, languages, and approaches associated with each paradigm.
+-->
+
+
+<!DOCTYPE html>
+<html lang="en">
+
+<head>
+    <meta charset="UTF-8">
+    <meta http-equiv="X-UA-Compatible" content="IE=edge">
+    <meta name="viewport" content="width=device-width, initial-scale=1.0">
+    <title>Programming Paradigms Table</title>
+    <style>
+        body {
+            font-family: Arial, sans-serif;
+            background-color: #f7f7ff;
+            margin: 20px;
+            color: #333;
+            text-align: center;
+        }
+
+        h1 {
+            color: #FF6347;
+        }
+
+        table {
+            width: 100%;
+            border-collapse: collapse;
+            font-family: Arial, sans-serif;
+        }
+
+        th,
+        td {
+            padding: 12px;
+            border: 1px solid #ccc;
+        }
+
+        th {
+            background-color: #FF6347;
+            color: #fff;
+        }
+
+        tr:nth-child(2) th,
+        tr:nth-child(2) td {
+            background-color: #ffe4e1;
+        }
+
+        /* Muted pink */
+        tr:nth-child(3) th,
+        tr:nth-child(3) td {
+            background-color: #e6e6fa;
+        }
+
+        /* Lavender */
+        tr:nth-child(4) th,
+        tr:nth-child(4) td {
+            background-color: #e0ffff;
+        }
+
+        /* Cyan */
+        tr:nth-child(5) th,
+        tr:nth-child(5) td {
+            background-color: #ffebcd;
+        }
+
+        /* Lemon */
+        tr:nth-child(6) th,
+        tr:nth-child(6) td {
+            background-color: #ffcccb;
+        }
+
+        /* Coral */
+        tr:nth-child(7) th,
+        tr:nth-child(7) td {
+            background-color: #e0f2f1;
+        }
+
+        /* Teal */
+        tr:nth-child(8) th,
+        tr:nth-child(8) td {
+            background-color: #fafad2;
+        }
+
+        /* Lemon Chiffon */
+        tr:nth-child(9) th,
+        tr:nth-child(9) td {
+            background-color: #d0f0c0;
+        }
+
+        /* Light Teal */
+        td:first-child {
+            font-weight: bold;
+        }
+
+        /* Last Child */
+        tr:last-child th,
+        tr:last-child td {
+            background-color: #FFFEA3;
+            /* Light teal */
+        }
+    </style>
+</head>
+
+<body>
+    <h1>Programming Paradigms 🔧</h1>
+    <table>
+        <tr>
+            <th>Programming Paradigm 📝</th>
+            <th>Principles 🏷️</th>
+            <th>Languages 💻</th>
+            <th>Key Concepts 🔑</th>
+        </tr>
+        <tr>
+            <td>Procedural Programming ⚙️</td>
+            <td>Focuses on a sequence of instructions</td>
+            <td>C, Pascal, Python, JavaScript</td>
+            <td>Functions, control flow, modularization</td>
+        </tr>
+        <tr>
+            <td>Object-Oriented Programming 🏛️</td>
+            <td>Based on objects encapsulating data & methods</td>
+            <td>Java, C++, Python, C#</td>
+            <td>Classes, objects, inheritance, encapsulation</td>
+        </tr>
+        <tr>
+            <td>Functional Programming 🔗</td>
+            <td>Treats computation as function evaluation</td>
+            <td>Lisp, JavaScript</td>
+            <td>Pure functions, immutability, recursion</td>
+        </tr>
+        <tr>
+            <td>Declarative Programming ✨</td>
+            <td>Specifies *what* to achieve, not *how*</td>
+            <td>SQL, HTML, CSS</td>
+            <td>Logic, rules, no explicit control flow</td>
+        </tr>
+        <tr>
+            <td>Event-Driven Programming 🔔</td>
+            <td>Behavior determined by events</td>
+            <td>JavaScript, C#, VB.NET</td>
+            <td>Event handlers, listeners, callbacks</td>
+        </tr>
+        <tr>
+            <td>Concurrent/Parallel Programming ⏳</td>
+            <td>Executes multiple computations simultaneously</td>
+            <td>Java, Python, C++</td>
+            <td>Threads, processes, synchronization</td>
+        </tr>
+        <tr>
+            <td>Component-Based Programming 🧩</td>
+            <td>Uses interchangeable, reusable components</td>
+            <td>C#, Java</td>
+            <td>Components, interfaces, reusability</td>
+        </tr>
+        <tr>
+            <td>Data-Driven Programming 📊</td>
+            <td>Control flow driven by data changes</td>
+            <td>R, Python, SQL</td>
+            <td>Data pipelines, real-time updates</td>
+        </tr>
+        <tr>
+            <td>Logic Programming 🧠</td>
+            <td>Program in logical form, with rules and facts</td>
+            <td>Prolog</td>
+            <td>Facts, rules, queries, inference</td>
+        </tr>
+    </table>
+</body>
+
+<br>
+<footer>
+    <p style="color: #FF6347; font-size: 20px;"><b>&copy; 2024 Madhurima Rawat. All rights reserved.</b></p>
+</footer>
+
+</html>
\ No newline at end of file
diff --git a/7 SEMESTER/Software Engineering/Notes/Unit 3/Programming Paradigms.png b/7 SEMESTER/Software Engineering/Notes/Unit 3/Programming Paradigms.png
new file mode 100644
index 0000000..f549f42
Binary files /dev/null and b/7 SEMESTER/Software Engineering/Notes/Unit 3/Programming Paradigms.png differ
diff --git a/7 SEMESTER/Software Engineering/Notes/Unit 3/Unit 3 Notes.pdf b/7 SEMESTER/Software Engineering/Notes/Unit 3/Unit 3 Notes.pdf
new file mode 100644
index 0000000..345e52a
Binary files /dev/null and b/7 SEMESTER/Software Engineering/Notes/Unit 3/Unit 3 Notes.pdf differ
diff --git a/7 SEMESTER/Software Engineering/Notes/Unit 4/Legacy System Modernization and Migration Strategies.html b/7 SEMESTER/Software Engineering/Notes/Unit 4/Legacy System Modernization and Migration Strategies.html
new file mode 100644
index 0000000..7e86fca
--- /dev/null
+++ b/7 SEMESTER/Software Engineering/Notes/Unit 4/Legacy System Modernization and Migration Strategies.html	
@@ -0,0 +1,184 @@
+<!-- 
+Author: Madhurima Rawat
+Date: 21 November 2024
+Brief: This table provides a comparison of different legacy system modernization strategies, including encapsulation, rehosting, refactoring, rebuilding, and more.
+It outlines the key properties such as strategy name, description, when to use, and real-life examples. This comparison helps users understand the various approaches to modernizing and migrating legacy systems.
+
+Additional Details:
+- Color Palette: The table uses a pastel color scheme with alternating shades like misty rose, lavender, and light teal to ensure the content is visually appealing and easy to follow.
+- Emoji Usage: Each strategy name is paired with a relevant emoji (e.g., 🧩 for Encapsulation, ☁️ for Rehosting, 🖥️ for Replatforming, 🔧 for Refactoring), enhancing the table's engagement and accessibility.
+- Design: The alternating row colors make the table easy to read, with highlighted header cells for clear differentiation. The design is simple yet effective, ensuring that the information is presented in a digestible format.
+- Purpose: The goal of this table is to provide a quick and insightful comparison of various legacy system modernization strategies. It helps businesses and developers understand the differences, use cases, and scenarios for each strategy, enabling informed decision-making for system modernization.
+-->
+
+
+<!DOCTYPE html>
+<html lang="en">
+
+<head>
+    <meta charset="UTF-8">
+    <meta name="viewport" content="width=device-width, initial-scale=1.0">
+    <title>Legacy System Modernization</title>
+    <style>
+        body {
+            font-family: Arial, sans-serif;
+            background-color: #f7f7ff;
+            margin: 20px;
+            color: #333;
+            text-align: center;
+        }
+
+        h1 {
+            color: #FF6347;
+        }
+
+        table {
+            width: 100%;
+            border-collapse: collapse;
+            font-family: Arial, sans-serif;
+        }
+
+        th,
+        td {
+            padding: 12px;
+            border: 1px solid #ccc;
+        }
+
+        th {
+            background-color: #FF6347 !important;
+            /* Tomato */
+            color: #fff;
+        }
+
+        tr:nth-child(2) th,
+        tr:nth-child(2) td {
+            background-color: #ffe4e1;
+            /* Misty Rose */
+        }
+
+        tr:nth-child(3) th,
+        tr:nth-child(3) td {
+            background-color: #e6e6fa;
+            /* Muted Pink */
+        }
+
+        tr:nth-child(4) th,
+        tr:nth-child(4) td {
+            background-color: #e0ffff;
+            /* Lavender */
+        }
+
+        tr:nth-child(5) th,
+        tr:nth-child(5) td {
+            background-color: #ffebcd;
+            /* Cyan */
+        }
+
+        tr:nth-child(6) th,
+        tr:nth-child(6) td {
+            background-color: #ffcccb;
+            /* Lemon */
+        }
+
+        tr:nth-child(7) th,
+        tr:nth-child(7) td {
+            background-color: #d0f0c0;
+            /* Coral */
+        }
+
+        tr:nth-child(8) th,
+        tr:nth-child(8) td {
+            background-color: #d0f0c0;
+            /* Teal */
+        }
+
+        tr:nth-child(9) th,
+        tr:nth-child(9) td {
+            background-color: #d0f0c0;
+            /* Lemon Chiffon */
+        }
+
+        td:first-child {
+            font-weight: bold;
+        }
+
+        /* Last Child */
+        tr:last-child th,
+        tr:last-child td {
+            background-color: #FFFEA3;
+            /* Light Teal */
+        }
+    </style>
+</head>
+
+<body>
+    <h1>Legacy System Modernization & Migration Strategies 🛠️</h1>
+    <table>
+        <thead>
+            <tr>
+                <th>Strategy 🚀</th>
+                <th>Description 📝</th>
+                <th>When to Use 📌</th>
+                <th>Examples/Scenarios 📋</th>
+            </tr>
+        </thead>
+        <tbody>
+            <tr>
+                <td>Encapsulation 🧩</td>
+                <td>Wrap the legacy system with modern APIs or web services to add new functionality.</td>
+                <td>When the legacy system's core functionality is valuable but lacks flexibility or integration.</td>
+                <td>A bank exposes legacy core banking functions through REST APIs for mobile banking apps.</td>
+            </tr>
+            <tr>
+                <td>Rehosting (Lift and Shift) ☁️</td>
+                <td>Move the legacy system to a new environment (e.g., cloud) with minimal changes.</td>
+                <td>When the hardware is outdated or costly but the software meets business needs.</td>
+                <td>Migrating an on-premises CRM system to AWS or Azure without code changes.</td>
+            </tr>
+            <tr>
+                <td>Replatforming 🖥️</td>
+                <td>Migrate to a modern platform with minor optimizations to improve performance.</td>
+                <td>When a balance between minimal disruption and the need for optimization is required.</td>
+                <td>Moving a legacy app to a modern OS while adopting cloud-managed services.</td>
+            </tr>
+            <tr>
+                <td>Refactoring 🔧</td>
+                <td>Rework and improve the existing codebase to enhance maintainability and scalability.</td>
+                <td>When technical debt is high, but core functionality is still valuable.</td>
+                <td>Refactoring a monolithic app into microservices for scalability and performance.</td>
+            </tr>
+            <tr>
+                <td>Rebuilding 🌟</td>
+                <td>Rewrite the system from scratch using modern technologies and best practices.</td>
+                <td>When the current system is outdated, hard to maintain, and no longer meets business needs.</td>
+                <td>Redesigning an ERP system with cloud-native architecture.</td>
+            </tr>
+            <tr>
+                <td>Replacement 🔄</td>
+                <td>Replace the legacy system with an off-the-shelf or custom-built solution.</td>
+                <td>When rebuilding or refactoring is too costly, and business needs are met by available solutions.
+                </td>
+                <td>Replacing a legacy HR system with a modern SaaS-based solution.</td>
+            </tr>
+            <tr>
+                <td>Retiring 🛑</td>
+                <td>Phase out the legacy system without replacement.</td>
+                <td>When the system is no longer needed or its functionality is duplicated elsewhere.</td>
+                <td>Decommissioning a billing system after migrating to a modern ERP.</td>
+            </tr>
+            <tr>
+                <td>Hybrid Approach 🔀</td>
+                <td>Combine multiple strategies for modernization, such as rehosting while refactoring components.</td>
+                <td>When parts of the system have different modernization requirements.</td>
+                <td>Rehosting a legacy database while rebuilding the user-facing application.</td>
+            </tr>
+        </tbody>
+    </table>
+</body>
+
+<br>
+<footer>
+    <p style="color: #FF6347; font-size: 20px;"><b>&copy; 2024 Madhurima Rawat. All rights reserved.</b></p>
+</footer>
+
+</html>
\ No newline at end of file
diff --git a/7 SEMESTER/Software Engineering/Notes/Unit 4/Legacy System Modernization and Migration Strategies.png b/7 SEMESTER/Software Engineering/Notes/Unit 4/Legacy System Modernization and Migration Strategies.png
new file mode 100644
index 0000000..315220e
Binary files /dev/null and b/7 SEMESTER/Software Engineering/Notes/Unit 4/Legacy System Modernization and Migration Strategies.png differ
diff --git a/7 SEMESTER/Software Engineering/Notes/Unit 4/Unit 4 Notes.pdf b/7 SEMESTER/Software Engineering/Notes/Unit 4/Unit 4 Notes.pdf
new file mode 100644
index 0000000..a839afc
Binary files /dev/null and b/7 SEMESTER/Software Engineering/Notes/Unit 4/Unit 4 Notes.pdf differ
diff --git a/7 SEMESTER/Software Engineering/Notes/Unit 5/Gantt_Chart.html b/7 SEMESTER/Software Engineering/Notes/Unit 5/Gantt_Chart.html
new file mode 100644
index 0000000..90a7fb1
--- /dev/null
+++ b/7 SEMESTER/Software Engineering/Notes/Unit 5/Gantt_Chart.html	
@@ -0,0 +1,312 @@
+<!-- 
+Author: Madhurima Rawat
+Date: 21 November 2024
+Brief: This webpage presents a comprehensive Gantt chart example, demonstrating the use of overlapping tasks and their durations across multiple weeks. The chart visually represents how different tasks within a project can run concurrently over a 5-week period. Each task is associated with a color-coded bar indicating its timeline, and detailed explanations are provided for each task's significance and timeline.
+
+Additional Details:
+- Color Palette: The chart uses a blend of blue, red, green, yellow, and other distinct colors for each task to differentiate them easily and enhance visual appeal.
+- Task Duration: The duration of each task is represented by the width of the bars, with a small text label showing the number of weeks each task spans.
+- Task Explanations: Below the chart, a detailed list explains the purpose of each task, such as planning, design, development, testing, and documentation.
+- Design: The chart is designed with a grid layout for both days and weeks, and the bars are positioned in such a way to illustrate overlapping tasks, creating a visual timeline of the project.
+- Purpose: The goal of this Gantt chart is to help users understand how project timelines are structured, how overlapping tasks are handled, and how they can use such charts for project management in real-world scenarios.
+-->
+
+
+<!DOCTYPE html>
+<html lang="en">
+
+<head>
+    <meta charset="UTF-8">
+    <meta http-equiv="X-UA-Compatible" content="IE=edge">
+    <meta name="viewport" content="width=device-width, initial-scale=1.0">
+    <title>Comprehensive Gantt Chart with Overlapping Tasks</title>
+    <style>
+        body {
+            font-family: 'Arial', sans-serif;
+            background-color: #f4f4f9;
+            color: #333;
+            padding: 20px;
+        }
+
+        .container {
+            max-width: 1200px;
+            margin: auto;
+            background-color: #fff;
+            padding: 20px;
+            border-radius: 8px;
+            box-shadow: 0 4px 8px rgba(0, 0, 0, 0.1);
+        }
+
+        h1 {
+            text-align: center;
+            color: #2c3e50;
+        }
+
+        .description {
+            margin-bottom: 30px;
+        }
+
+        .gantt-chart {
+            display: grid;
+            grid-template-columns: repeat(25, 1fr);
+            gap: 2px;
+            border: 1px solid #ddd;
+            margin-bottom: 20px;
+            border-collapse: collapse;
+        }
+
+        .day,
+        .task {
+            border: 1px solid #ddd;
+            /* Adds border to each day and task cell */
+            padding: 5px;
+            text-align: center;
+            font-size: 10px;
+
+        }
+
+        /* White color text for task cells */
+        .task {
+            color: white;
+        }
+
+        .week-label {
+            grid-column: span 5;
+            background-color: #2c3e50;
+            color: #fff;
+            text-align: center;
+            padding: 5px;
+            font-weight: bold;
+        }
+
+        .task-row {
+            display: grid;
+            grid-template-columns: repeat(25, 1fr);
+            gap: 2px;
+            border: 1px solid #ddd;
+            /* Adds grid lines for the task rows */
+
+        }
+
+        .task-detail {
+            margin-top: 20px;
+
+        }
+
+        .task-detail ul {
+            list-style: none;
+            padding: 0;
+        }
+
+        .task-detail li {
+            margin-bottom: 5px;
+            padding: 5px;
+            background-color: #e8f8f5;
+            border-left: 4px solid #3498db;
+        }
+
+        h1 {
+            text-align: center;
+            color: #2c3e50;
+        }
+
+        .description {
+            margin-bottom: 30px;
+        }
+
+        .gantt-chart_1 {
+            display: grid;
+            grid-template-columns: 1fr 4fr;
+            gap: 10px;
+        }
+
+        .task-label {
+            background-color: #ecf0f1;
+            padding: 10px;
+            border-radius: 4px;
+            text-align: right;
+            font-weight: bold;
+        }
+
+
+        .bar {
+            height: 30px;
+            border-radius: 4px;
+            position: relative;
+        }
+
+        .bar::before {
+            content: attr(data-duration);
+            position: absolute;
+            right: 5px;
+            top: 5px;
+            font-size: 12px;
+            color: #fff;
+        }
+
+        .bar-1 {
+            background-color: #3498db;
+            width: 40%;
+            /* Adjust to represent duration */
+        }
+
+        .bar-2 {
+            background-color: #e74c3c;
+            width: 50%;
+            /* Adjust to represent duration */
+        }
+
+        .bar-3 {
+            background-color: #2ecc71;
+            width: 70%;
+            /* Adjust to represent duration */
+        }
+
+        .bar-4 {
+            background-color: #f1c40f;
+            width: 60%;
+            /* Adjust to represent duration */
+        }
+
+        footer {
+            text-align: center;
+            margin-top: 40px;
+            color: #777;
+        }
+    </style>
+</head>
+
+<body>
+
+    <div class="container">
+        <h1>Understanding Gantt Charts</h1>
+        <div class="description">
+            <p>A Gantt chart is a type of bar chart that represents a project schedule. It displays the start and finish
+                dates of the various tasks or phases of a project. Gantt charts are widely used in project management to
+                visualize the project timeline, helping teams to plan, coordinate, and track specific tasks.</p>
+        </div>
+
+        <h2>Sample Gantt Chart</h2>
+        <div class="gantt-chart_1">
+            <div class="task-label">Task 1: Research</div>
+            <div class="bar bar-1" data-duration="2 weeks"></div>
+
+            <div class="task-label">Task 2: Design</div>
+            <div class="bar bar-2" data-duration="3 weeks"></div>
+
+            <div class="task-label">Task 3: Development</div>
+            <div class="bar bar-3" data-duration="5 weeks"></div>
+
+            <div class="task-label">Task 4: Testing</div>
+            <div class="bar bar-4" data-duration="4 weeks"></div>
+        </div>
+    </div>
+
+    <div class="container">
+        <h1>Comprehensive Gantt Chart with Overlapping Tasks</h1>
+        <div class="description">
+            <p>This example showcases a Gantt chart with detailed day labels and overlapping tasks, illustrating
+                concurrent project timelines and their duration.</p>
+        </div>
+
+        <h2>5-Week Gantt Chart Overview</h2>
+        <div class="gantt-chart">
+            <!-- Week Labels -->
+            <div class="week-label" style="grid-column: 1 / span 5;">Week 1</div>
+            <div class="week-label" style="grid-column: 6 / span 5;">Week 2</div>
+            <div class="week-label" style="grid-column: 11 / span 5;">Week 3</div>
+            <div class="week-label" style="grid-column: 16 / span 5;">Week 4</div>
+            <div class="week-label" style="grid-column: 21 / span 5;">Week 5</div>
+        </div>
+
+        <!-- Days Row -->
+        <div class="task-row">
+            <div class="day">Day 1</div>
+            <div class="day">Day 2</div>
+            <div class="day">Day 3</div>
+            <div class="day">Day 4</div>
+            <div class="day">Day 5</div>
+            <div class="day">Day 6</div>
+            <div class="day">Day 7</div>
+            <div class="day">Day 8</div>
+            <div class="day">Day 9</div>
+            <div class="day">Day 10</div>
+            <div class="day">Day 11</div>
+            <div class="day">Day 12</div>
+            <div class="day">Day 13</div>
+            <div class="day">Day 14</div>
+            <div class="day">Day 15</div>
+            <div class="day">Day 16</div>
+            <div class="day">Day 17</div>
+            <div class="day">Day 18</div>
+            <div class="day">Day 19</div>
+            <div class="day">Day 20</div>
+            <div class="day">Day 21</div>
+            <div class="day">Day 22</div>
+            <div class="day">Day 23</div>
+            <div class="day">Day 24</div>
+            <div class="day">Day 25</div>
+        </div>
+
+        <!-- Task Rows -->
+        <div class="task-row">
+            <div class="task" style="grid-column: 1 / span 1; background-color: #3498db;">Task A</div>
+        </div>
+        <div class="task-row">
+            <div class="task" style="grid-column: 1 / span 2; background-color: #e74c3c;">Task B</div>
+        </div>
+        <div class="task-row">
+            <div class="task" style="grid-column: 2 / span 3; background-color: #2ecc71;">Task C</div>
+        </div>
+        <div class="task-row">
+            <div class="task" style="grid-column: 5 / span 4; background-color: #f1c40f;">Task D</div>
+        </div>
+        <div class="task-row">
+            <div class="task" style="grid-column: 8 / span 5; background-color: #8e44ad;">Task E</div>
+        </div>
+        <div class="task-row">
+            <div class="task" style="grid-column: 10 / span 3; background-color: #1abc9c;">Task F</div>
+        </div>
+        <div class="task-row">
+            <div class="task" style="grid-column: 13 / span 5; background-color: #34495e;">Task G</div>
+        </div>
+        <div class="task-row">
+            <div class="task" style="grid-column: 17 / span 4; background-color: #d35400;">Task H</div>
+        </div>
+        <div class="task-row">
+            <div class="task" style="grid-column: 20 / span 5; background-color: #2980b9;">Task I</div>
+        </div>
+        <div class="task-row">
+            <div class="task" style="grid-column: 22 / span 3; background-color: #9b59b6;">Task J</div>
+        </div>
+        <div class="task-row">
+            <div class="task" style="grid-column: 24 / span 2; background-color: #e67e22;">Task K</div>
+        </div>
+
+        <div class="task-detail">
+            <h2>Task Explanations</h2>
+            <ul>
+                <li><strong>Task A:</strong> Initial setup and kick-off (Day 1)</li>
+                <li><strong>Task B:</strong> Planning phase (Days 1-2)</li>
+                <li><strong>Task C:</strong> Design discussions (Days 2-4)</li>
+                <li><strong>Task D:</strong> Development start (Days 5-8)</li>
+                <li><strong>Task E:</strong> Mid-project review (Days 8-12)</li>
+                <li><strong>Task F:</strong> Early testing phase (Days 10-12)</li>
+                <li><strong>Task G:</strong> Main development (Days 13-17)</li>
+                <li><strong>Task H:</strong> Bug fixing (Days 17-20)</li>
+                <li><strong>Task I:</strong> Final adjustments (Days 20-25)</li>
+                <li><strong>Task J:</strong> Presentation preparation (Days 22-24)</li>
+                <li><strong>Task K:</strong> Documentation completion (Days 24-25)</li>
+            </ul>
+        </div>
+    </div>
+
+</body>
+
+<br>
+<footer>
+    <p style="color: #2c3e50; font-size: 20px;"><b>&copy; 2024 Madhurima Rawat. All rights reserved.</b></p>
+</footer>
+
+
+</html>
\ No newline at end of file
diff --git a/7 SEMESTER/Software Engineering/Notes/Unit 5/Unit 5 Notes.pdf b/7 SEMESTER/Software Engineering/Notes/Unit 5/Unit 5 Notes.pdf
new file mode 100644
index 0000000..1670434
Binary files /dev/null and b/7 SEMESTER/Software Engineering/Notes/Unit 5/Unit 5 Notes.pdf differ