Try it on paper first. A hint, the key idea and the worked solution are here when you need them.
A team is making a program that lets pupils order lunch from the school canteen before the morning break. Here are six things the team does, not in order.
Name the stage of the program development life cycle for each one.
The program development life cycle has four stages. Analysis: identify the problem and the requirements, with abstraction and decomposition. Design: decomposition, structure diagrams, flowcharts and pseudocode. Coding: write the program code, with iterative testing. Testing: test the whole program with test data.
Have you tried it?
Work it out on paper first. It is fine to get stuck or make a mistake: that is how we learn. When you are ready, go through the solution one step at a time, and check each step against your own.
Plan. Ask what the team is doing: finding out what is needed (analysis), planning how (design), writing code (coding) or testing the whole program (testing).
Step 1. (a) Writing the screen in a programming language is coding.
Step 2. (b) Asking the cooks what to record finds the requirements. That is analysis.
Step 3. (c) A structure diagram is design.
Step 4. (d) Running the finished program with chosen orders is testing with test data.
Step 5. (e) Testing one function as soon as it is written, then fixing and testing again, is iterative testing. It belongs to coding.
Step 6. (f) Pseudocode is a plan of the steps, so it is design.
Watch out. Item (e) is a test, but it is not the testing stage. Testing each part while it is written is part of coding.
Log in to join the discussion.
Loading…