|
1 | 1 | # Computing and Network Systems |
| 2 | + |
| 3 | +Great request! I’ll design you a **comprehensive AP CSP unit** on *Understanding Computer & Network Systems (Big Idea 4)* with lessons, projects, and activities that fit the AP CSP framework, keep students engaged, and prepare them for the AP exam. |
| 4 | + |
| 5 | +Here’s a structured unit you can use right away: |
| 6 | + |
| 7 | +--- |
| 8 | + |
| 9 | +**Unit: Understanding Computer & Network Systems (Big Idea 4)** |
| 10 | + |
| 11 | +**Unit Goals** |
| 12 | + |
| 13 | +* Explain how the Internet works (IP addresses, DNS, packets, protocols). |
| 14 | +* Demonstrate the importance of fault tolerance, redundancy, and scalability. |
| 15 | +* Explore parallel and distributed computing with real-world applications. |
| 16 | +* Apply concepts through simulations, unplugged activities, coding projects, and reflections. |
| 17 | + |
| 18 | +--- |
| 19 | + |
| 20 | +**Lesson Sequence** |
| 21 | + |
| 22 | +**Lesson 1: What is the Internet? (4.1)** |
| 23 | + |
| 24 | +**Objectives**: |
| 25 | + |
| 26 | +* Understand IP addresses, DNS, packets, and protocols. |
| 27 | +* Visualize how a request moves across the internet. |
| 28 | + |
| 29 | +**Activities**: |
| 30 | + |
| 31 | +1. **Unplugged Simulation** – "Passing Packets" game: students pass envelopes with parts of a message, simulating dropped/reordered packets. |
| 32 | +2. **Mini Lab** – Use `ping` and `tracert`/`traceroute` on school computers to see how packets travel. |
| 33 | +3. **Discussion** – Why do we need DNS? What happens if DNS fails? |
| 34 | + |
| 35 | +**Project/Check**: |
| 36 | + |
| 37 | +* Draw a **diagram of how a browser request works** (user → DNS → server → back to user). |
| 38 | +* Quick-write: "What role do IP addresses and DNS play in making the Internet usable?" |
| 39 | + |
| 40 | +--- |
| 41 | + |
| 42 | +**Lesson 2: Protocols and Communication (4.1)** |
| 43 | + |
| 44 | +**Objectives**: |
| 45 | + |
| 46 | +* Explore TCP/IP, HTTP, HTTPS. |
| 47 | +* See why protocols are critical for interoperability. |
| 48 | + |
| 49 | +**Activities**: |
| 50 | + |
| 51 | +1. **Classroom Protocol Game** – students pass secret notes with different "rules" for communication; only when they follow a shared set of rules can the message be read. |
| 52 | +2. **Wireshark or Online Demo** – (if allowed) capture network packets and see TCP/HTTP in action. |
| 53 | + |
| 54 | +**Project/Check**: |
| 55 | + |
| 56 | +* Create an infographic or short video explaining **one protocol** (HTTP, HTTPS, TCP, UDP) in plain English. |
| 57 | + |
| 58 | +--- |
| 59 | + |
| 60 | +**Lesson 3: Fault Tolerance & Redundancy (4.2)** |
| 61 | + |
| 62 | +**Objectives**: |
| 63 | + |
| 64 | +* Understand how redundancy improves reliability. |
| 65 | +* Explore routing and rerouting of data. |
| 66 | + |
| 67 | +**Activities**: |
| 68 | + |
| 69 | +1. **Unplugged Simulation** – students act as routers; if one path is blocked, data finds another route. |
| 70 | +2. **Case Study** – Look at a real-world event (e.g., Google outage, submarine cable cut, DNS outage). Discuss: what went wrong, how did redundancy help/fail? |
| 71 | + |
| 72 | +**Project/Check**: |
| 73 | + |
| 74 | +* Create a one-page **visual explanation of fault tolerance**: why redundancy matters, with examples. |
| 75 | + |
| 76 | +--- |
| 77 | + |
| 78 | +**Lesson 4: Scalability (4.2)** |
| 79 | + |
| 80 | +**Objectives**: |
| 81 | + |
| 82 | +* Learn how networks grow to handle more users. |
| 83 | +* Explore bottlenecks (bandwidth, servers, congestion). |
| 84 | + |
| 85 | +**Activities**: |
| 86 | + |
| 87 | +1. **Bandwidth Demo** – have students send messages with limited “bandwidth” (e.g., only 2 characters per round) vs. full sentences to simulate congestion. |
| 88 | +2. **Discussion** – What happens when millions of people stream Netflix or join Zoom? |
| 89 | + |
| 90 | +**Project/Check**: |
| 91 | + |
| 92 | +* Students research and present: *How do big companies like YouTube, Netflix, or Amazon scale their systems?* |
| 93 | + |
| 94 | +--- |
| 95 | + |
| 96 | +**Lesson 5: Parallel & Distributed Computing (4.3)** |
| 97 | + |
| 98 | +**Objectives**: |
| 99 | + |
| 100 | +* Compare sequential vs. parallel vs. distributed computing. |
| 101 | +* Recognize real-world uses (scientific research, AI, climate modeling, SETI@Home). |
| 102 | + |
| 103 | +**Activities**: |
| 104 | + |
| 105 | +1. **Unplugged Parallel Activity** – solve a large math problem (like adding 1–1000) sequentially vs. dividing among groups (parallel). |
| 106 | +2. **Coding Lab (optional, Python/JavaScript)** – |
| 107 | + |
| 108 | + * Write a program that processes a large list sequentially vs. with simple parallel methods (if environment supports threads/async). |
| 109 | + * OR simulate distributed computing with multiple students working on different parts of a dataset. |
| 110 | + |
| 111 | +**Project/Check**: |
| 112 | + |
| 113 | +* Reflection: *Why are parallel and distributed computing essential for modern problems like AI, space exploration, or healthcare?* |
| 114 | + |
| 115 | +--- |
| 116 | + |
| 117 | +**Lesson 6: Review & Synthesis** |
| 118 | + |
| 119 | +**Objectives**: |
| 120 | + |
| 121 | +* Bring together internet structure, protocols, fault tolerance, scalability, parallel/distributed computing. |
| 122 | +* Prepare for AP-style questions. |
| 123 | + |
| 124 | +**Activities**: |
| 125 | + |
| 126 | +1. **Concept Map** – students create a visual showing connections among IP, DNS, packets, protocols, fault tolerance, and distributed computing. |
| 127 | +2. **Practice AP CSP Exam Questions** – multiple choice and short-answer style. |
| 128 | + |
| 129 | +--- |
| 130 | + |
| 131 | +**Projects & Performance Tasks** |
| 132 | + |
| 133 | +1. **"Life of a Packet" Storyboard/Video** |
| 134 | + |
| 135 | + * Students create a comic, animation, or video that shows how data travels across the internet, including DNS, IP, packets, and protocols. |
| 136 | + |
| 137 | +2. **Network Outage Case Study** |
| 138 | + |
| 139 | + * Research a real-world outage (DNS failure, DDoS attack, cable break). |
| 140 | + * Present what happened, how redundancy helped (or didn’t), and lessons learned. |
| 141 | + |
| 142 | +3. **Parallel/Distributed Simulation Project** |
| 143 | + |
| 144 | + * Students simulate solving a problem (like word counting, searching, or sorting) using sequential, parallel, and distributed strategies. |
| 145 | + * Write a reflection on efficiency and scalability. |
| 146 | + |
| 147 | +4. **Scalability Research Project** |
| 148 | + |
| 149 | + * Students research how a major service (YouTube, Netflix, Zoom, Fortnite servers) handles massive numbers of users. |
| 150 | + * Create a presentation or infographic. |
| 151 | + |
| 152 | +--- |
| 153 | + |
| 154 | +**Assessment Options** |
| 155 | + |
| 156 | +* **Formative**: exit tickets, diagrams, reflections, class simulations. |
| 157 | +* **Summative**: |
| 158 | + |
| 159 | + * Project presentation (Life of a Packet, Network Outage Case Study, or Scalability Research). |
| 160 | + * Unit test with multiple choice + short answer (aligned to AP CSP style). |
| 161 | + |
| 162 | +--- |
| 163 | + |
| 164 | + |
0 commit comments