Programming project (analysis→design→build→test→evaluate) - Computer Science A Level Study Notes

Think of the programming project lifecycle like planning and building a dream treehouse. You don't just grab some wood and nails and start hammering, right? That would be chaos!

Instead, you follow a sensible plan, and that's exactly what the programming project process is:

• Analysis (What do we want?): This is like figuring out who will use the treehouse (you and your friends), what they want to do in it (play games, read books), and where it will go (in your garden). You're gathering all the ideas and needs.
• Design (How will we build it?): Now you draw blueprints! You decide how many rooms, where the windows go, what materials you'll use, and how to make it safe. You're planning the structure and how everything fits together.
• Build (Let's make it!): This is the fun part – actually cutting the wood, nailing things together, and putting up the walls. You're writing the code (instructions for the computer).
• Test (Does it work?): Before anyone climbs in, you'd check if the ladder is sturdy, if the floor is safe, and if the roof keeps out the rain. You're checking your code for mistakes (bugs) and making sure it does what it's supposed to.
• Evaluate (How can we make it better?): After using the treehouse for a bit, you might think, "Hmm, a pulley system for snacks would be awesome!" or "The door squeaks." You look back at your work and think about improvements for next time. You're reflecting on the project and suggesting future enhancements.

Let's imagine a real-world company wants to create a new online ordering system for a local pizza shop.

1. Analysis: The company talks to the pizza shop owner and customers. They find out: "Customers want to order online easily," "The owner needs to see orders quickly," "They need to pay with cards," and "The menu changes often." They write down all these requirements (what the system needs to do).
2. Design: The developers draw out how the website will look (like a sketch of the order page), how customers will click through to choose toppings, how payments will work, and how the pizza shop's computer will receive the order. They plan the database (where all the pizza and customer information is stored) and the user interface (what the user sees and interacts with).
3. Build: The programmers start writing the actual code using programming languages like Python or JavaScript. They create the website pages, the payment processing parts, and the system that sends orders to the kitchen printer. This is where they turn the designs into a working program.
4. Test: Before launching, the company pretends to be customers and orders pizzas. They try different toppings, pay with different cards, and even try to break the system (e.g., ordering 100 pizzas at once) to find any bugs (errors in the code). The pizza shop owner also tests receiving orders.
5. Evaluate: After the system has been used for a few months, the company asks the pizza shop and customers: "Is it easy to use?" "Are there any features missing?" "Is it fast enough?" They might find out customers want to save their favourite orders, or the owner wants a report on daily sales. This feedback helps them plan for future improvements or a 'Version 2.0' of the system.