File handling and modular design - Computer Science A Level Study Notes

Let's break down these two big ideas:

• File Handling: Think of your computer's hard drive (or SSD) like a giant library with millions of books. Each 'book' is a file. File handling is simply how your computer program learns to:

  • Open a book (file) to read what's inside.
  • Write new notes into a book (add data).
  • Close a book so it's safe and saved.
  • Maybe even create a brand new blank book or delete an old one.

  Why do we need this? Because when your program is running, it uses its memory (like your short-term memory). But when you turn off the computer, that memory is wiped clean! Files let programs store information permanently, like saving your game progress or your school project.

• Modular Design: Imagine you're making a delicious, multi-layered cake. You don't just throw all the ingredients into one bowl and hope for the best! Instead, you make the sponge in one bowl, the frosting in another, and the filling in a third. Each part is a module (a self-contained piece of code).

  Modular design means breaking a big, complicated computer program into smaller, independent, and reusable chunks (modules). Each chunk has a specific job. For example, in a game, one module might handle player movement, another might manage the score, and another might draw the graphics. This makes programs much easier to build, understand, and fix.

Let's use the example of an online shopping website, like one where you buy books or games:

1. File Handling in Action: When you add an item to your shopping cart, the website needs to remember what you've chosen. If you close your browser and come back later, your cart might still be there. How does it do this? It uses file handling (or something similar like a database, which is built on file handling principles) to write your cart's contents to a file on its server. When you revisit, it reads that file to show you your items. When you complete your purchase, it writes your order details to another file for records and then might update a 'stock' file to show one less item available.

2. Modular Design in Action: That same online shopping website is HUGE! It's not one giant block of code. Instead, it's built with many modules:

   • One module handles user accounts (logging in, creating new accounts).
   • Another module manages the product catalog (showing all the items, their pictures, and descriptions).
   • A separate module deals with the shopping cart functionality (adding, removing items).
   • Another module processes payments (connecting to banks).
   • Yet another module handles shipping information.

   Each of these modules is like a separate team working on one part of the website. They all work together, but they are developed and maintained independently. This means if there's a problem with the payment system, the developers only need to fix that specific payment module, not the entire website!